Most teams that describe themselves as asynchronous are really synchronous teams using chat. Messages fly all day, everyone is expected to be present, and the only thing that changed is that the interruptions now arrive in writing. That is worse than a meeting, not better, because at least a meeting ends.
Genuine async work is a set of habits, and the habits are learnable. This is the playbook.
Habit one: define expected response times and publish them
The anxiety that keeps people glued to chat is not really about the messages. It is about not knowing how fast a reply is expected. In the absence of a stated norm, everyone assumes the strictest possible one and behaves accordingly.
Fix it by publishing explicit expectations per channel. Something like: chat messages get a reply within four working hours; anything in the project tool gets a reply by end of next working day; the phone is for genuine emergencies only, and here is the short list of what counts as one.
Once written down, this changes behavior almost immediately. People stop refreshing, because they know a four-hour gap is normal rather than negligent.
Habit two: write for someone reading tomorrow
Synchronous writing is a conversation: “hey, quick question.” Asynchronous writing is a document: it has to work without you present to clarify.
The practical difference is front-loading. Lead with what you need and by when. Then give context. Then give detail. Someone skimming should be able to stop after one line and know whether this concerns them.
Compare “hey do you have a sec about the Riley project” with “Riley project: I need your approval on the revised timeline by Thursday so we can confirm the vendor. Details and the two options below.” The second one can be answered while you sleep. The first one requires a round trip before the real question is even asked.
Habit three: give every question a deadline and a default
The most common failure of async decision-making is the question that sits unanswered for four days because nobody realized it was blocking anything.
Attach two things to every request: a deadline, and what happens if the deadline passes without a response. “If I do not hear back by Wednesday at noon, I will go with option B and we can revisit it later.” This is not passive aggression. It is a genuine unblocking mechanism, and it respects the reader’s time by making silence a valid answer.
Habit four: put decisions somewhere permanent
Chat is a river. Anything decided in it is gone within a day, and reconstructing it means scrolling through six hundred messages hoping you recognize the moment.
Adopt a simple rule: a decision does not exist until it is written in the durable place — the project tool, the wiki, the document. Discussion can happen anywhere; the conclusion has one home. Record four things each time: what was decided, who decided it, when, and what alternatives were rejected and why. That last item is the one people skip and the one that saves you from relitigating the same argument in six months.
Habit five: protect overlap hours for the things that need them
Async does not mean never talking. It means being deliberate about what deserves synchronous time.
Four things genuinely benefit from real-time conversation: creative work in its earliest stage, disagreements that have already had two written rounds without converging, anything emotionally sensitive, and complex debugging where the feedback loop needs to be seconds rather than hours.
Everything else is better in writing. Define a two- to four-hour overlap window when the whole team is available, keep it small, and use it only for the four categories above. A narrow overlap window is a feature: it forces the rest of the work into a form that survives being read later.
Habit six: make progress visible without asking
In an office, progress is ambient. Remotely, it becomes invisible, and invisibility breeds the check-in message that interrupts the very work it is asking about.
Replace the asking with a system. Task status stays current in one shared place. Each person posts a short written update on a fixed rhythm. Work in progress gets shared early and rough, rather than polished and late. Anything blocked is flagged the moment it blocks, not at the next scheduled meeting.
The bargain is explicit: the team keeps the board honest, and in exchange nobody gets messaged to ask how it is going.
Habit seven: use recorded video for the right things
Short screen recordings are underrated for anything spatial or visual: walking through a design, demonstrating a bug, explaining where something lives in a system. Three minutes of recording can replace a fifteen-minute call and can be watched at double speed by four people at four different times.
Keep two rules. Under five minutes, always. And always accompanied by a written summary, so people can decide whether to watch and can search for it later. Video that is not summarized is content nobody can find in three months.
The failure modes to watch for
- Chat that has become a meeting that never ends. If your team is in continuous conversation all day, you are synchronous with worse ergonomics.
- Documents nobody reads. Writing more is only useful if reading is treated as real work with real time allocated to it.
- Decisions made in the overlap window and never written down. Whoever was asleep is now permanently behind.
- Loneliness. Async removes the incidental social contact that made work bearable. Schedule something deliberately unproductive and optional to replace it.
- Long threads that should have been a call. Two rounds of written disagreement without convergence is the signal to switch channels.
Making the switch
Do not change everything at once. Take one habit a fortnight. Start with published response times, because it is the one that reduces anxiety fastest and costs nothing. Then move written updates before meetings. Then move decisions into a durable location.
Expect it to feel slower for the first month. It is slower, per exchange. What you get in return is uninterrupted hours, decisions that stay decided, and a written record that means the person who joins in March can understand the reasoning from January without asking anyone.