Async Communication: Fewer Meetings, Better Decisions

Asynchronous communication means communicating without expecting an immediate reply: a written update, a recorded walkthrough, a comment on a document. Done well, it replaces a large share of meetings and gives everyone more time to focus. Done badly, it creates slow threads full of follow-up questions.

When to go async — and when not to

A good rule: if a thread has gone back and forth more than three times without progress, book a short call — then write up the result.

The anatomy of a good async message

1. The ask in the first line. "Need your approval on the Q3 budget by Thursday."
2. Context. What happened, what you've considered, links to the relevant documents.
3. Options. If there's a decision, lay out the choices and your recommendation.
4. A default. "If I don't hear back by Thursday 17:00, I'll go with option B."
5. Formatting. Short paragraphs, bullet points, bold for the key line.

Templates

Weekly update

Shipped: what's done this week In progress: what's moving, with expected dates Blocked: what's stuck and who can unblock it Next week: top three priorities

Decision request

Decision needed: one sentence By when: date and time with time zone Options: A, B, C — with one line on the trade-off of each Recommendation: which option and why Default if no reply: what you'll do

Handoff

What this is: one-sentence summary Where things are: links What's left: checklist Watch out for: known risks Who to ask: names

Setting team norms

Async only works when everyone shares expectations. Agree, in writing:

• Response times by channel (for example: chat within four working hours, email within one business day)
• What counts as urgent and how to flag it (a phone call, not an @channel)
• Where decisions are recorded — one place, searchable
• Core overlap hours if the team spans time zones

Async by work style

• Cartographers and Tinkerers usually love async — it protects focus. The risk is going silent; a short weekly update fixes that.
• Collaborators and Catalysts can find async slow. Short recorded videos and scheduled live sessions keep their energy in the loop.
• Coordinators are natural async champions — give them ownership of the team's norms.

Measure the win

Before rolling out async norms, count your team's meeting hours for one week. Check again after a month. Use the meeting cost calculator to put a number on the time you've given back.