Async Communication

Async communication lets distributed teams move fast without living on calendars. The trade: it demands clearer writing. This skill helps you make that trade well.

When async beats sync

Default to async when:

• The topic is informational (status, FYI, announcements).
• The decision benefits from reflection time.
• People are across time zones.
• A written record matters for later reference.

Use sync only for: high-emotion conversations, fast-moving brainstorms, relationship building, or genuine deadlock after async attempts.

The async message pattern

Structure every non-trivial message so the reader can act without a reply loop:

TL;DR: <one line — what you want from the reader>

Context: <why this is coming up — 2-3 sentences>

Details: <the substance>

Decision/Action needed:
- <specific ask> — owner: <who> — by: <when>

Default: <what happens if no one responds by the deadline>

The default line is the secret weapon: "If I don't hear back by Friday, I'll proceed with option B." It keeps work moving and respects everyone's time.

Replacing common meetings

• Status meeting -> written standup. Each person posts: done / doing / blocked.
• Decision meeting -> decision doc. State options, recommendation, request comments

by a deadline, then decide.

• Brainstorm -> async idea doc. Seed a doc, let people add ideas over a day,

then a short sync to converge (if needed).

• 1:1 -> rolling shared doc + occasional live time for the human stuff.

Writing for async

• Front-load the ask. Reader knows what's wanted in the first line.
• Be self-contained. Link or restate context so no back-and-forth is needed.
• Set explicit deadlines. "Soon" guarantees it never happens.
• Pick the right channel. Chat for quick/ephemeral, docs for decisions, issues for work.
• Over-communicate tone. Without faces/voices, add a word of warmth; assume good intent.

Response norms (agree as a team)

• Expected response window per channel (e.g. chat = same day, email = 24h).
• "Working hours" badges and Do-Not-Disturb are respected.
• Threads, not channel noise, keep topics navigable.

Anti-patterns

• "Quick call?" for something that's two written sentences.
• Walls of text with no TL;DR — readers bounce.
• No deadline and no default — the thread dies and work stalls.
• Treating every message as urgent — urgency inflation kills real urgency.