Every team claims to be async. Most are just asynchronous SLA violations punctuated by meetings.
Async is not "we use Slack instead of meetings." Async is a documented protocol for every communication channel your team uses. It defines what goes where, when it gets answered, and how to escalate when something actually burns. Without those rules, async is just an excuse for ignoring messages until someone calls you.
I run four engineering teams on async protocols. Zero Slack notifications. Zero daily standups. And my response time on urgent issues is faster than it was when I had notifications on — because the signal-to-noise ratio inverted. Every ping is a legitimate escalation. Not a brain cell tax.
The three zones of communication
Every message belongs to one of three zones. The zone determines the tool, the expected response time, and the behavior.
Zone 1: Asynchronous (response within 4-24 hours)
This is where nearly all communication lives. 95% of messages belong here.
| Tool | What goes here | Expected response |
|---|---|---|
| Linear / Jira | Tickets, task questions, code review requests | 4 hours during working hours |
| External communication, non-urgent internal | End of business day | |
| Pull requests | Code reviews, technical decisions | 4 hours during maker time |
| Shared docs | Proposals, design documents, strategy memos | 24 hours for final feedback |
This is an excerpt. The full teardown is at brainbrutalism.com.
