The Meeting Trap
There's a well-worn pattern in modern work: whenever there's ambiguity, uncertainty, or a decision to make, someone schedules a meeting. Meetings feel productive because they're social and active. But they're often the most expensive way to communicate — they interrupt everyone's focused work, rarely produce durable records, and scale poorly as teams grow.
Async-first communication is an alternative philosophy: default to written, asynchronous communication and treat synchronous meetings as a deliberate, somewhat rare tool reserved for specific situations.
What Async-First Actually Means
Async-first doesn't mean "never meet." It means structuring communication so that:
- The default response window is hours, not seconds.
- Information is written down and searchable, not spoken and forgotten.
- Decisions have a documented rationale, not just an outcome.
- People can do their best thinking without coordinating schedules.
Companies like Basecamp, GitLab, and Automattic have operated this way for years, with distributed teams across many time zones. Their approaches offer a useful blueprint.
The Building Blocks of Async Communication
Write for Your Future Reader
Good async communication is self-contained. When you write a message or document, assume the reader can't immediately ask a clarifying question. Include context, clearly state what you need, and specify any timeline. This takes more effort upfront — and saves much more time downstream.
Use the Right Tools for the Right Jobs
| Tool Type | Best For | Examples |
|---|---|---|
| Long-form documents | Proposals, specs, decisions | Notion, Confluence, Google Docs |
| Chat | Quick questions, informal updates | Slack, Discord, Teams |
| Project tracking | Tasks, status, ownership | Linear, Jira, Basecamp |
| Video messages | Walkthroughs, feedback | Loom, Claap |
| Synchronous meetings | High-emotion topics, complex brainstorms | Zoom, Google Meet |
Establish Response Norms
The anxiety around async communication usually stems from unclear expectations. If people don't know whether to expect a reply in 10 minutes or 10 hours, they default to urgency. Set explicit norms: what's a same-day response, what's a next-business-day response, and what genuinely warrants an instant message or call.
When to Meet Synchronously
Some situations genuinely benefit from real-time conversation:
- Sensitive interpersonal issues where tone and nuance matter.
- Genuine brainstorming sessions where ideas build rapidly in dialogue.
- Onboarding situations where relationship-building is the goal.
- Decisions that have been circling asynchronously without resolution.
The key is intention. A meeting you choose because it's the right tool is valuable. A meeting you schedule because it's the default is a tax on everyone's time.
Getting Started
You don't need your whole organization to buy in. Start personally: the next time you're about to schedule a 30-minute meeting for something that could be a well-written message, write the message instead. Notice how often it works just as well — and how much everyone appreciates getting that time back.