Login
Back to Blog
Remote WorkMeetingsDistributed TeamsAsync

Run Better Meetings on a Distributed Team

Rajat KapoorNovember 13, 20268 min read

Every Wednesday at 8am Pacific, seven people dialed into a 45-minute "team sync." For the engineer in Berlin it was 5pm, the tail end of her day. For the one in Sydney it was 3am, and he'd stopped pretending he wasn't answering from bed. The first twenty minutes were people reading their status out loud, one at a time, while everyone else half-listened and waited for their own turn. Then a real question came up, got talked in a circle for ten minutes, and ended with "let's take it offline." The last fifteen minutes were a demo that two people needed and five people sat through. Nobody would have called it a bad meeting. It happened every week, it felt productive enough, and it quietly ate the only hour in the day when all seven of them were awake at once.

That is the thing an office hides from you. A wasted meeting there is an annoyance. On a team spread across the planet, the same meeting spends something you can't get back.

The live hour is the most expensive thing you buy

In a co-located team, a mediocre meeting burns some time and everyone wanders back to their desks. The cost is real but small, and there is plenty more shared time where that came from. A distributed team has no plenty. If your people run from California to Central Europe to Australia, the window where all of them are awake at the same time might be forty-five minutes, or it might be zero. That sliver is the single scarcest thing the team owns, and a recurring meeting spends it in bulk, every week, whether or not the meeting earns it.

So do the arithmetic nobody does. Seven people for forty-five minutes is more than five person-hours. But the hours aren't really the price. The price is that those are the hours, the one moment these specific humans can talk in real time, and if you spend it on status readouts and a demo, you have spent your rarest resource on the two things that least needed to be live. Everything else in this post comes from taking that number seriously.

Most of what fills a meeting doesn't belong there

Watch a typical recurring sync and ask, segment by segment, whether that part actually needed everyone awake at the same instant. Usually most of it didn't.

Status updates are the worst offender. Reading out what you did this week, to a room of people politely waiting their turn, is a tax on the listeners and a mild performance for the speaker, and it works exactly as badly live as it sounds. That belongs in a written weekly update people read on their own clock, skimming what touches them and skipping what doesn't. A choice that one person could propose in writing and the rest could approve or argue with belongs in an async decision thread, not in a ten-minute live debate that ends with "let's take it offline" regardless.

Pull those out and a surprising amount of the meeting evaporates. What remains is the work that genuinely gets better with everyone in the same call: a disagreement where two people need to hear each other's tone before they can settle it, or an ambiguous problem that needs the fast back-and-forth a comment thread would stretch across three days. That is what the live hour is for. Guard it for that, and refuse to let the easy stuff creep back in, because it will keep trying.

Send the context before, not during

The quickest way to waste a live meeting is to spend the first half building context everyone could have had in advance. Someone shares a screen, walks a document line by line, and twenty minutes are gone before anyone says a thing that needed the group. Every person on that call could have read the same document in five minutes on their own time.

So make them. Send the pre-read, and mean it. The proposal, the numbers, whatever the meeting turns on, goes out far enough ahead that people in every timezone can read it inside their own working day before they show up. Then the meeting opens already past the setup, sitting on the question that actually needs a crowd. Some teams spend the first few minutes reading in silence together, which feels odd the first time and then feels obviously right, because it guarantees the context is fresh instead of assuming it is. The point holds either way. The live hour is for the conversation, not the briefing.

Someone has to actually run it

A meeting without a facilitator drifts to whoever is most comfortable talking, and on a distributed team that is almost always the people who share the host's timezone and a solid connection. The person dialing in at 11pm on a laggy line, half a second of delay riding every exchange, does not win the race to fill a pause. They just go quiet, and the silence gets read as agreement when it is really the mechanics beating them to it.

A facilitator fixes that on purpose. One person runs the agenda, keeps a single conversation going instead of three overlapping ones, watches the chat for whoever is typing because they can't find a gap in the audio, and pulls the quiet people in by name. It isn't a glamorous job and it should rotate, but the meeting is twice as good when someone owns it and close to worthless when nobody does. Timeboxing is the same job: when a topic has eaten its slot and is circling, the facilitator names someone to resolve it async and moves on instead of letting it swallow the rest of the agenda.

Write down what got decided, or it didn't happen

The call ends, everyone shuts the tab, and within the hour the only record is seven slightly different memories. For the people who were there, that is survivable. For the third of the team who were asleep, the meeting might as well not have happened, because whatever got settled now lives only in heads they can't reach until tomorrow.

So the last five minutes are not optional. Someone writes down what was decided, what is still open, and who owns each next step, then posts it where the sleeping half will find it in their morning. If the meeting carried information people who missed it will need, record it and write a short summary on top so nobody has to reverse-engineer it from a chat log or scrub through a replay hunting for the one minute that mattered. A decision that stays spoken never fully got made on a team where someone is always missing from the room.

The best meeting is often the one you cancel

The test I would put on every recurring meeting is almost embarrassingly simple: if the only thing on this week's agenda is status, cancel it this week. Not forever, just this week, because there is nothing live to do and the written update already carried the news. A standing meeting that convenes out of habit rather than need is spending the scarcest hour on the calendar to manufacture a feeling of alignment, and that feeling is not worth the hour it costs the person who took it at 3am.

The meetings that survive that test are the ones worth running well. Trim them to the people who actually need to be in the room instead of inviting the whole team as insurance. End early when you're done and hand the time back visibly, because a meeting that reliably finishes ten minutes short earns the trust that it won't waste you next time. And for the ones you keep, pick the time as a deliberate decision and spread the awkward slot around rather than parking 3am on the same person forever. A well-run meeting at a fairly chosen hour is one of the few live rituals worth defending. Almost everything else should have been a message.


Related Reading


Let Timely Handle the Clock Math

A meeting is only worth running well if the right people actually show up, and that falls apart the moment "sync moved to 9am" means a different hour to everyone reading it. When someone posts "standup at 9:30" or "demo pushed to 3pm ET," Timely reads each person's Slack timezone and shows that moment in their own local clock, so nobody misses the one live hour because they did the conversion wrong.

Add Timely to Slack — Free  ·  See how it works