The backlash against video meetings was earned. Calendars clogged with status calls that a shared doc would have handled better, “quick syncs” that were neither, all-hands where forty cameras stayed politely off.
In response, plenty of distributed companies swung hard toward asynchronous everything — write it down, record a Loom, protect the maker schedule.
The correction fixed the calendar and quietly broke something else. When companies cut video time indiscriminately, the first casualty is usually the one meeting format that pulls more weight than any other in a remote organization: the recurring one-on-one.
What the Async Purists Miss?
Buffer’s State of Remote Work — one of the longest-running surveys of distributed workers — keeps returning the same uncomfortable pair of findings: remote workers overwhelmingly want to stay remote, and a stubborn fraction of them struggle with loneliness and staying home too often, with roughly a third citing having no reason to leave the house and nearly a quarter citing loneliness itself (Buffer). Documents don’t fix that.
Documents are, in fact, the thing that lets a struggling teammate stay invisible for months while their written output looks fine.
A manager reading a status update learns what got done. A manager on a camera-on call learns everything else: the flat tone describing a project that should be exciting, the half-second hesitation after “how are things outside work,” the visible relief when a hard topic finally lands on the table.
Distributed teams run on trust, and trust runs on exactly the signals that async communication strips out — the same reason people double-check what technology tells them about each other in every other context (see Digital Edge’s look at how location-sharing really behaves on an iPhone: the interface never shows the whole story).
The Case for Making the 1:1 Sacred
The math is not subtle. A weekly 30-minute 1v1 video call per direct report costs a manager with six reports three hours a week.
Against that: attrition surprises caught a quarter early, blockers surfaced before they compound, and the single strongest predictor of whether a remote employee feels seen — someone senior looking at them, only them, with the tab-switching visibly off.
Three rules separate the 1:1s that earn their slot from the ones that become status theater:
- The report owns the agenda. Status lives in the tracker. The call is for what the tracker can’t hold: friction, ambition, doubt.
- Cameras on, by default, for this one meeting. Teams that go camera-optional everywhere else should still treat the 1:1 as the exception. Half the meeting’s value is in the faces.
- Never cancel — reschedule. Cancellation reads as “you’re the compressible part of my week.” Six cancellations in a row is an exit interview you didn’t know you scheduled.
What the Half Hour Should Actually Hold?
The commonest failure mode, once the slot is protected, is filling it wrong. A useful pattern for distributed teams is rotating the half hour through four lanes across the month rather than running the same conversation weekly:
| Week | Lane | What it covers |
|---|---|---|
| 1 | The work | Friction, slipping dependencies, the two-jobs problem — not status |
| 2 | The person | Energy, workload honesty, home-office reality, timezone strain |
| 3 | Growth | Skills wanting reps, hand-raised projects, feedback not yet given |
| 4 | Upward | What the manager could do differently; the company from the report’s seat |
The rotation does two things. It stops the meeting from collapsing into a project check-in, which is the fate of every unstructured 1:1 by roughly its sixth occurrence.
And it guarantees that the harder lanes — growth, upward feedback — actually happen on a schedule instead of “when there’s time,” which in distributed companies is a euphemism for never.
Cadence matters as much as content. Weekly for new hires and anyone mid-struggle; biweekly is defensible for tenured, thriving reports — but the interval should be a decision made together, not an accident of calendar pressure.
And across timezones, the burden of the awkward hour should rotate too. A 1:1 that’s always 7 a.m. for the same person is a small recurring message about whose time matters.
One structural addition helps more than any agenda template: a shared running document per report, owned by them, that both parties add to between calls.
It removes the “what did we even discuss last time” opening, gives the quieter half of the team a way to raise things without waiting for the slot, and turns the half hour into a continuing thread rather than fifteen unrelated conversations a year.
Cut Meetings. Keep This One.
The async movement is right about almost everything: most meetings are documents wearing a calendar invite, most “collaboration” is interruption, and deep work needs protecting. Prune ruthlessly. But prune with a scalpel, not a mower.
A distributed company that kills its one-on-ones to save three hours a week is deferring a much larger invoice — paid later in disengagement, quiet quitting, and the resignation letter that “came out of nowhere.” It never came out of nowhere. It came out of thirty missed conversations, half an hour at a time.
