Asynchronous Communication vs Meetings
Most teams default to meetings out of habit — even when a written update would be cheaper and clearer. Here's when async beats a meeting, when a meeting still wins, and how to shift the balance.
What "async" actually means
Asynchronous communication is any exchange that doesn't require everyone to be present at the same moment — a written update, a recorded video, a comment thread, a shared doc. Synchronous communication is the opposite: meetings, calls, and live chats where people coordinate in real time. Most teams default to sync out of habit, even when async would be cheaper and clearer.
Add up what a recurring meeting costs across the year — then decide whether async could do the job.
Open the Meeting Cost Calculator →When async wins
- Status updates and FYIs — a written post everyone reads on their own time.
- Sharing information that doesn't need debate.
- Decisions with time to spare, where written proposals and comments work fine.
- Distributed or multi-timezone teams, where a single live time is costly to find — see running meetings across time zones.
- Anything that benefits from a written record people can search later.
When sync (a meeting) wins
- Complex or contentious decisions that need real-time back-and-forth.
- Brainstorming, where energy and rapid building-on-ideas matter.
- Sensitive or emotional conversations — feedback, conflict, bad news.
- Relationship and trust building, especially for new teams.
Sync vs async at a glance
| Factor | Async favours | Sync favours |
|---|---|---|
| Urgency | Can wait hours/days | Needs an answer now |
| Complexity | Simple, one-directional | Nuanced, many viewpoints |
| Emotion | Neutral, factual | Sensitive, personal |
| Record | Want it written down | Record not essential |
| Audience | Large or distributed | Small, co-located |
How to shift more communication to async
Make written updates the default and meetings the exception that has to be justified. Give every recurring meeting an async test: if a clear written summary would do, cancel the meeting and post the summary. The "could this have been an email?" check helps decide case by case, and a meeting-free day forces the habit. For the full playbook, see reducing meeting costs.
Frequently Asked Questions
Neither is universally better — they're tools for different jobs. Async wins for status updates, sharing information, and distributed teams; sync (a meeting) wins for complex decisions, brainstorming, and sensitive conversations. The goal is to match the method to the task rather than defaulting to meetings.
Written status updates, comment threads on a shared document, recorded video walkthroughs, project-management ticket discussions, and channel posts that people read on their own schedule.
Make written updates the default and require meetings to be justified. Give recurring meetings an async test, replace status meetings with written posts, and consider a weekly meeting-free day to build the habit.