Default async, meeting on purpose
Remote teams drown when every ambiguity becomes a calendar invite. The healthier default is write first, meet when writing failed or cannot work.
A meeting costs everyone the same hour at once. Async costs each person reading time spread across the day. Meetings win only when simultaneous attention saves more time than it burns.
Decision tree
Answer these in order. Stop at the first "yes."
1. Is the decision reversible in a day or less with low cost?
Yes: async doc with a deadline. No meeting.
2. Do people need to hear tone or emotion to avoid a costly misunderstanding?
Yes: short live conversation, often voice only, with notes posted after.
Examples: performance tension, sensitive client apology, two leaders talking past each other in text.
3. Is the problem novel and high stakes, with no shared model yet?
Yes: timeboxed working session with a written agenda and a scribe.
Examples: first incident response, brand-new architecture with safety constraints, major scope cut mid-release.
4. Will more than three back-and-forth async rounds likely happen without convergence?
Yes: meeting, but only after a pre-read doc exists.
5. Is someone blocked until a single synchronized choice is made?
Yes: urgent sync, smallest group possible, decision recorded before hang up.
If every answer is no, stay async.
Try these before you book
Structured doc with comments. One page: context, options, recommendation, questions. Comment deadline, then decide in writing.
Short Loom or screen recording. Walk through a prototype or bug. Often replaces a thirty-minute call with a ten-minute watch.
Pair on one narrow question. Two people, fifteen minutes, one outcome: approve copy, pick enum name, confirm repro steps.
Office hours. One optional slot per week instead of ad hoc pings.
When async is clearly enough
Status, handoffs, approvals on known options, routine planning, and anything with a template already on the site.
Use client status updates and end-of-day status instead of a standup when the team spans time zones.
When meetings routinely fail
Meetings without pre-reads become live discovery. Discovery belongs in writing so introverts and non-native speakers can contribute.
Meetings without a scribe produce conflicting memories within a week.
Meetings with more than eight people rarely decide anything; they broadcast.
If the outcome is "everyone is aligned," require a written decision line with owner and date before closing the call.
Time zones change the math
Overlap hours are scarce (timezone overlap matters more than local time). Spend them on tree branch 2 and 3 items, not readouts.
Use finding fair meeting times and the wider timezone collaboration guide so one region does not always eat the bad slot.
After the meeting
Post decisions where the work lives. Link from chat to the ticket or doc. Delete the slide deck nobody will open.
If you cannot summarize the decision in three bullets, the meeting may not have been ready to happen.
Capacity reminder
Every hour on the calendar comes out of someone’s deep work budget (planning eight hours into eight hours). Book meetings like spending cash, not like generating teamwork vibes.
Meetings are a sharp tool. Keep them rare, small, prepared, and written down.
Quick reference table
| Situation | Default |
|---|---|
| FYI update | Async post |
| Approve option A or B with doc | Async comment deadline |
| Emotional conflict | Short live talk, notes after |
| First production incident | Live, smallest group |
| Routine standup when status is written | Cancel or async |
| Brainstorm with no criteria | Doc first, then optional live |
Pin the table in your team wiki. When someone schedules a meeting, ask which row applies.
Standing meetings deserve a quarterly audit
Every recurring call should survive three questions:
- Did last three sessions change a decision or unblock work?
- Could the same outcome arrive from written status?
- Who pays the worst time zone cost?
If the answers are no, no, and the same person every time, cancel or rotate async.
Size and length caps
More than six decision-makers in one call usually means no decision. Cap at twenty-five minutes with five for pre-read confirmation. Longer meetings need breaks and a written agenda sent twenty-four hours ahead.
Your calendar is a team resource. Spend it deliberately.