What It Is
Async communication means sending a message without expecting an immediate response. The recipient responds when they are ready — not when you sent the message.
At its simplest, this is email. But modern async-first companies have turned it into a full operating system: replacing status meetings with structured written check-ins, replacing chat interruptions with threaded discussions, replacing verbal decision-making with documented deliberation.
Async is not the absence of communication. It is the deliberate design of communication so that it does not require two people to be available at the same moment.
Why It Works
Focus is a resource. Resuming full focus on a task after an interruption takes around 23 minutes, per Gloria Mark’s research at UC Irvine. (Source) A real-time communication culture that generates 10 interruptions per day costs four hours of productive output — before anyone accounts for the meetings themselves.
Writing forces clarity. When you cannot talk something out, you have to think it through clearly enough to write it. “Writing solidifies, chat dissolves,” in 37signals’ phrasing. (Source) The discipline of writing produces clearer thinking and better decisions.
Async scales across time zones. A company with teammates in Tokyo, Lagos, and São Paulo cannot have a functional synchronous communication culture. Async is the only model that does not systematically disadvantage employees in minority time zones.
It creates a permanent record. When decisions happen in meetings or voice calls, they disappear. When they happen in writing, they are searchable, referenceable, and visible to future employees. GitLab’s 2,000-page public handbook is the compounded output of 10 years of writing decisions down instead of talking them out. (Source)
Where It Fails
Without structure, it is just silence. Async does not automatically produce clarity. Without explicit mechanisms — required check-ins, named owners, defined response norms — async becomes a vacuum where work disappears into and nothing gets resolved. Companies that “go async” without building the supporting infrastructure just get slower, not calmer.
It delays but does not eliminate urgency. Crisis situations, rapidly evolving technical problems, and interpersonal conflicts all require real-time coordination. Async-first companies that have no synchronous fallback either let crises fester or break their own norms chaotically.
It disadvantages people who do not write well. Async-first culture systematically advantages people with strong written communication skills and disadvantages people who think better aloud. This is a real equity issue at hiring and promotion — companies need to hire for it, train for it, and accommodate different communication styles. [Inference — based on the explicit hire-for-writing requirements visible at Doist (mandatory cover letter; resume rejected without one) and Basecamp (manager-of-one expectation that depends on written self-direction). The companies do not publish hiring-funnel data broken out by communication-skill type, so the asymmetry is observed indirectly through the hiring practices.]
Notification norms require active management. “Async” with Slack’s default notification settings is not async — it is just intermittent stress. Buffer explicitly published their Slack notification agreements for this reason. (Source) The tools default to urgency; the norms have to actively override that default.
Best Examples
37signals / Basecamp — The most rigorously documented async operating system. Four required mechanisms (daily check-in, weekly check-in, heartbeat, kickoff) replace most status meetings with structured written updates. “Urgency is overrated, ASAP is poison.” (Source)
Doist — The most extreme async-first stance: no meetings by default, Slack deliberately excluded, Twist (their own threaded async tool) as the primary communication system. 15+ years of operating this way at ~90–100 people. (Source)
GitLab — Async by principle, with specific rules: when back-and-forth hits three exchanges, move to video. All decisions documented in GitLab issues. Slack treated as async, not real-time. (Source)
Buffer — Explicit about when async is not enough. Published documentation of when to use Zoom instead of Threads. The most honest public account of the limits of async-first. (Source)
Implementation Guide
1. Define what async means for your team. Does it mean “no expected response within 4 hours”? “You can respond the next working day”? Ambiguous async is worse than synchronous — people don’t know what to expect, so they either over-respond out of anxiety or under-respond and miss things. Write down the norm.
2. Replace status meetings with structured async mechanisms. The simplest version: a weekly “what are you working on this week?” question, answered in writing, on Monday. This alone eliminates one recurring meeting per week per team and creates a written record of priorities.
3. Pick one tool and enforce spatial context. If you discuss a task, discuss it in the comments under that task — not in Slack. If you are reviewing a document, comment on the document — not in a separate thread. Communication attached to its subject is findable; communication in a general chat is lost.
4. Set Slack (or whatever you use) to async by default. Configure notification schedules. Establish team norms that a message sent does not demand an immediate reply. The tool defaults to urgency; override it explicitly.
5. Write questions with preemptive context. Before sending a message, include: what you are trying to do, what you have already tried or considered, your best current answer, and what specifically you need. This cuts reply cycles in half.
6. Keep the synchronous fallback. Define when real-time is appropriate. 37signals says “tight collaboration in real time” is for genuine exceptions. GitLab says move to video after three async exchanges. Buffer says complex + urgent = Zoom. Pick your rule and write it down.
Common Mistakes
Going async without building structure first. Teams eliminate meetings without replacing them with anything. Result: work stalls, people feel disconnected, they create their own informal real-time communication workarounds.
Treating async as a productivity hack, not a coordination system. Async communication is not about individual productivity — it is about organizational coordination. Framing it as “fewer distractions” focuses on the individual; the real benefit is system-level.
Confusing tool adoption with practice adoption. Installing Twist or switching to Threads does not make your company async-first. The tool is the least important part. The norms, the expected response times, the structured check-ins — these are the practice.
Not training for async writing quality. Long, unclear async messages create more back-and-forth than a well-run synchronous conversation. Writing quality is a skill. It needs to be developed, coached, and rewarded.
Assuming everyone thrives in an async environment. Some people genuinely do better with more synchronous interaction — for cognitive, learning, or social reasons. Async-first companies that do not accommodate this lose people who would have performed well in a different communication structure.
Sources
- The 37signals Guide to Internal Communication: https://basecamp.com/guides/how-we-communicate
- 37signals Employee Handbook: How We Work: https://basecamp.com/handbook/how-we-work
- How Doist Works Remote: https://doist.com/how-we-work/how-doist-works-remote
- GitLab: How to Embrace Async Communication: https://handbook.gitlab.com/handbook/company/culture/all-remote/asynchronous
- How to Work Asynchronously — Zapier: https://zapier.com/blog/how-to-work-asynchronously
- Buffer is Remote but not Async-First: https://buffer.com/resources/remote-not-async-first/
- Gloria Mark, UC Irvine — research on attention and interruption (primary source for the 23-minute recovery figure): https://www.ics.uci.edu/~gmark/
Inferences
- The companies that execute async communication best are the ones that treat it as a system design problem, not a cultural preference. They specify the mechanisms: which tool for what, what response window is expected, what format the message should take. The companies that announce “we are async” without this specification usually revert to informal real-time coordination within six months.
- Async-first works best when the organizational culture also values written communication as a form of thinking — not just record-keeping. When writing is treated as intellectual work, the quality of async communication rises. When writing is treated as bureaucratic overhead, people do it reluctantly and poorly.
Work with Alex
If your team is drowning in meetings and you want to design a coordination system that actually gives people back their time, Alex helps leadership teams build the operating infrastructure for async-first distributed work.