The async-first playbook for distributed teams

"Async-first" gets thrown around a lot. Most of the time it means "we have a Slack channel and sometimes people answer at 3 AM." Real async work is harder, slower to set up, and dramatically better for teams that span more than four time zones.

The four habits

Write before you call. Every meeting starts with a written doc. Read for 10 minutes, comment, then meet only on the unresolved items.
Default to public channels. Direct messages are a tax on the team. Public channels mean someone in another time zone can answer your question while you sleep.
Set "deep work" hours. Two-hour blocks where notifications are off, calendar is blocked, and you actually finish things.
Record everything. Loom for decisions, transcripts for meetings. Future-you and the Tokyo team will thank you.

What async is not

It's not "no meetings." It's not "answer whenever." It's a deliberate trade: you pay an upfront cost in writing, structure, and process, and you get back the freedom to not be online at the same time as everyone else. Teams that try to skip the writing step end up with the worst of both — meetings and chaos.

The minimum viable setup

A shared doc tool with comments (Notion, Google Docs, whatever).
One channel for decisions, one for status, one for water-cooler.
A weekly written update from each person — three lines, not three paragraphs.
One sync meeting a week, max, and only if there's a decision to make.

That's it. The hard part isn't tooling — it's the discipline to write things down when it would feel faster to just hop on a call.