Async Communication: Different Doesn't Mean Slower

Synchronous communication feels productive. Everyone nods. You feel aligned.

But 15 people in a meeting for 30 minutes is 7.5 hours of humanity spent for 30 minutes of wall time.

• Async communication done right:
• Gets the same alignment
• Creates a written record
• Lets people think before responding
• Scales to larger teams

How to do it:

1. **Propose, don't ask** Not: "What should we do about the API?" Say: "I propose we upgrade the API like this [details]. Comments?"

This frames the discussion. People respond with specific feedback, not general opinions.

2. **Decisions in writing** "We're upgrading the API next quarter because [reasons]. Expected impact: [metrics]. Questions?"

This creates a decision record. New people onboard reading the why, not guessing.

3. **Response expectations clear** "Responses due by Thursday 3pm PT. Will move forward if no objections."

This prevents infinite discussion. People prioritize threads that need their input.

4. **Use channels and threads** Slack's thread feature is underutilized. One conversation per thread. Easy to follow. Easy to reference later.

• **What doesn't work async:**
• Brainstorming (do this live, briefly)
• Conflict resolution (do this 1:1 or small group)
• Whiteboard/planning sessions (too collaborative for async)

Async for decisions and documentation. Synchronous for creativity and conflict.

Most teams flip it. They brainstorm in every meeting and make critical decisions in Slack.

Reverse it. Better outcomes, more time for actual work.