Asynchronous (“async”) communication means people don’t need to be online at the same time to move work forward. It is what makes flexitime, time-zone spread and four-day weeks possible.
When to go async, when to go live
| Use async for | Use a live call for |
|---|---|
| Status updates | Conflict or sensitive feedback |
| Proposals and reviews | Complex decisions with many trade-offs |
| Questions that can wait a few hours | Brainstorming from scratch |
| Demos and walkthroughs (recorded) | Onboarding and relationship-building |
Write messages that don’t need a reply to clarify
- Put the ask and the deadline in the first line.
- Give context, options and your recommendation.
- Link to the relevant document rather than pasting fragments.
- Say what happens if nobody replies: “If I don’t hear by Thursday I’ll go with option B.”
Decide in documents
For decisions that matter, write a one-page proposal: problem, options, recommendation and risks. Collect comments for a set period, then record the decision at the top. Future teammates can see what was decided and why.
Agree response-time norms
For example: urgent issues by phone; direct messages within four working hours; email within one working day. Norms remove the pressure to be always on.
Protect overlap time
Most distributed teams still need a few shared hours. Find yours with the time-zone overlap finder and use it only for things that need to be live.