Async Communication Playbook

Default to writing. If a topic can be understood without real-time back-and-forth, put it in a document, a Loom, or a threaded message. Asynchronous communication respects time zones, deep work, and different working styles. The cost is slightly more upfront effort — you have to write clearly. The payoff is that 10 people can consume the information on their own time instead of sitting in a 30-minute meeting.

Real-time conversation is still the right tool for: (1) emotional or sensitive topics, (2) complex decisions with no clear framework, (3) brainstorming that benefits from rapid idea collision, and (4) urgent incidents. A good test: if the outcome is likely to change based on tone of voice or facial expression, use a call. If the outcome depends only on the information itself, write it down.

Use a **document** for anything that needs to be referenced later: project specs, decisions, onboarding, quarterly goals. Use **chat** for time-bound coordination: "Can you review this by Thursday?" Use a **video message** (Loom, async screen recording) for demos, walkthroughs, or when tone matters but time zones don't align. Never use chat for decisions that affect more than two people — the context gets buried.

A good async message has a clear question or action, context, and a deadline. Bad: "Thoughts on the proposal?" Good: "The Q3 budget proposal is ready for review (link). I need sign-off from Finance and Product by Thursday 5pm CET so we can submit Friday. Please comment directly in the doc or reply here with blockers." The second version gives recipients everything they need to act without a follow-up ping.

Async doesn't mean slow — it means predictable. Set clear expectations: "I respond to Slack within 4 hours during work hours" or "Docs get reviewed within 24 hours." This removes the anxiety of waiting for a reply. Urgent items should use an explicit escalation path (e.g., "If this blocks you, call me"). Without this, every message feels urgent, and people default to calling.

Replace live standups with a written update in a shared channel or tool. Each person posts: (1) what I completed yesterday, (2) what I'm working on today, (3) blockers or help needed. This takes 2 minutes to write and 30 seconds to read — versus a 15-minute meeting for 8 people (that's 2 hours of collective time saved daily). The trick is keeping updates brief and making blockers actionable.