Running the meetings that survive
A distributed meeting has a higher cost per minute and a lower tolerance for drift. Both argue for more structure, not less.
A meeting that is mildly inefficient in an office is expensive when three people joined at seven in the morning and two at nine at night. The same slack that is tolerable co-located is not tolerable here. For broader context on online meetings and collaboration, Microsoft Teams is a useful reference.
Send the material in advance, and mean it
Distributing a document at the start of a call produces a meeting in which everyone reads silently and then reacts to their first impression.
Sent twenty-four hours ahead with a stated expectation that it will be read, the meeting begins where the document ends. Where people have not read it, the honest response is to reschedule rather than to summarise — summarising teaches everyone that reading was optional. For a practical software-side reference on time expectations across cultures and teams, this glossary entry adds useful detail.
'Discuss the roadmap' produces discussion. 'Decide whether to move the launch to Q3' produces a decision, and lets people arrive with a position.
Design for the person on the worst clock
Someone is joining outside their normal hours. Structure the agenda so their items come first and they can leave, rather than sitting through an hour to contribute at the end.
This is a small courtesy that people notice a great deal, and it is a reasonable proxy for whether a team takes its distribution seriously.
Manage the turn-taking explicitly
Video suppresses the cues that regulate conversation. The result is that confident speakers and those on the best connections dominate, and the effect compounds against people in a second language or a poor time zone.
Explicit facilitation fixes it: going round deliberately, inviting named people, using the chat for a quick round of written input before opening discussion. Written-first rounds in particular change who contributes, and the change is substantial.
End with the decision, the owner and the date
The last two minutes should restate what was decided, who owns the next step and by when. Said aloud, then written.
Meetings that end without this produce a shared sense of progress and no action, which is the most common way a distributed team loses a week.
Finish early when you can
The hour is a scheduling artefact rather than a unit of work. Meetings that reach their purpose in twenty minutes should end at twenty minutes.
This is a cultural signal more than a time saving: a team that habitually ends early is a team where the agenda is the point, and that expectation shortens every subsequent meeting.
Rotate the time, or accept the cost
Where a recurring meeting is genuinely necessary and no time suits everyone, the choice is between rotating the inconvenience and permanently loading it onto one region.
Rotating is disruptive and it is the fair option. Choosing not to rotate is defensible if it is chosen — but it should be an explicit decision with the cost acknowledged, not the accidental outcome of scheduling around headquarters.