Every meeting is an interrupt. Every interrupt breaks flow. And flow is where the actual work happens. The async default flips the norm: start with written, asynchronous communication. Only go synchronous when you've proven it's necessary.
"Let's schedule a call" is the default. Make it the last resort.
Don't meet to share information. Meet to make decisions you can't make async.
Why Synchronous Is Expensive
Deep work requires unbroken time. A meeting at 2pm doesn't cost one hour - it costs the entire afternoon. The context switch before and after destroys focus.
A meeting with 6 people costs 6 person-hours. The cost multiplies with attendance. Async scales: write once, read many.
In meetings, the loudest voice wins. Async gives introverts time to think and compose. Better ideas surface when presence isn't required.
Someone always takes the inconvenient slot. Async eliminates the 6am call. Everyone responds in their own working hours.
When To Use Each
Go Async When...
- Sharing information or updates
- Gathering input or feedback
- Decisions that need time to think
- Documentation or status reports
- Anything that can be written
Go Sync When...
- Rapid back-and-forth is needed
- Emotional or sensitive topics
- Building relationships (early stages)
- Urgent decisions with incomplete info
- Creative brainstorming (sometimes)
How To Make Async Work
Before requesting a meeting, write the context, question, and options. If you can write it, you can async it. Often, writing clarifies enough that the meeting becomes unnecessary.
"Respond by Friday" is different from "respond when you can." Set expectations explicitly. Async doesn't mean ignored - it means not-right-now.
Quick question? Chat. Complex decision? Document with comments. Match the medium to the message. Not everything is an email; not everything is a Slack message.
Async creates a natural record. The decision lives in the thread. No more "what did we decide in that meeting?" - it's written.
Cultural Changes Required
Managers who equate "being in meetings" with "working hard" will resist. Output matters, not face time. Async requires trusting people to work without observation.
Async runs on clear writing. If people can't write well, async fails. Train for clarity. Value conciseness. Make writing a core skill.
If people have 6 hours of meetings, they can't go async. Cut meetings first. Create the space before demanding the behavior.
If leaders schedule meetings for everything, the culture follows. Leaders who write instead of meet signal that async is acceptable. Culture flows downhill.
Before Scheduling A Meeting
1. Can this be written?
If yes, write it. Share it. Discuss async.
2. What decision needs to be made?
If none, it's an update - send a doc.
3. Do we need real-time interaction?
If no, async it. If yes, make the meeting 25 minutes.
The default is meetings. It's comfortable. It's familiar. It's also wasteful. Most meetings could be docs. Most calls could be messages. Most synchronous communication is habit, not necessity.
Flip the default. Start async. Make meetings prove they're worth the cost.
Write first. Meet only when you must.