The average knowledge worker spends 4 hours per day in meetings. That's half their work week. And most of those meetings could have been an email.
Not a bad email. Not a long email. Just a clear, concise update that people read when they're ready to engage with it.
Here's the case for async updates over synchronous meetings.
The Case Against Real-Time
Meetings are synchronous by definition. They require everyone to be present at the same time, thinking about the same thing, at the same pace.
This has costs:
- Time zone hell: Your best thinking happens at 9am. Theirs happens at 3pm. Good luck finding a time that works for both.
- Context switching: After a 2-hour meeting block, most people need 30 minutes to get back to where they were. That's a 3-hour productivity hit.
- Introverts speak less: In groups, extroverts dominate. Async gives everyone equal space to contribute.
What Async Updates Look Like
A good async update answers four questions:
- What did you work on?
- What did you learn?
- What are you working on next?
- What's blocking you?
That's it. Four bullets. Posted in a shared doc or Slack channel by end of day.
No meeting required.
When to Actually Meet
Async doesn't replace all meetings. It replaces status update meetings. Keep the meetings that need real-time collaboration:
- Decision-making meetings
- Brainstorming sessions
- Sensitive conversations
- Team bonding
For everything else: write it down.
The Numbers
Teams that go async report:
- 50% reduction in meeting time
- Faster decision-making (no waiting for next week's sync)
- Higher contributor satisfaction (people hate meetings more than they admit)
Getting Started
Start with one change: replace your weekly team standup with a shared doc. Everyone writes their update by Friday afternoon. The Monday meeting becomes a discussion of what people wrote, not a reading of it.
You'll get more done with fewer meetings. Your calendar will thank you.
Top comments (0)