Every team that switches to async-first communication goes through the same honeymoon phase. Fewer meetings! More deep work! Then, about two weeks in, someone sends a message that just says “can we talk about the thing?” and the dream starts to wobble.
Async communication works — but only if you treat writing as the primary skill, not a side effect of reducing meetings.
The single biggest upgrade you can make is to write for someone who has zero context. Before you send anything, ask: would this make sense to someone who wasn’t in the conversation I’m having in my head? If the answer is no, add context. Link the relevant document. Name the decision you’re working toward. State what you need and by when. It adds thirty seconds to your message and saves everyone else ten minutes of back-and-forth.
The second principle is to separate types of communication clearly. Questions that need quick answers, updates that just need to be logged, decisions that need input — these all belong in different places with different expectations. Dumping all of them into one channel creates anxiety because nobody knows what requires a response versus what’s just informational noise.
Third: make decisions visible. The reason synchronous meetings feel productive is that they force a resolution in the room. Async has to work harder to achieve that. Threads should end with a clear summary of what was decided, by whom, and what happens next. Otherwise you end up relitigating the same conversation three months later.
Async isn’t about communicating less. It’s about communicating more precisely. That’s a learnable skill — and once your team has it, you really do get the deep work back.