playbook:communication:async_guidelines [Chenla Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== Async Communication Guidelines ======

These guidelines define how we work effectively when communication is not happening in real time. They help reduce interruptions, protect deep work, and keep distributed collaboration smooth.

===== Principles =====
  * Write with enough context that no follow-up is needed.
  * Default to clarity over speed.
  * Respect deep-work time; avoid expecting immediate replies.
  * Separate urgency from convenience.
  * Design messages so others can act without a meeting.

===== Expectations =====
  * Respond within the agreed window for your role (not instantly).
  * Use clear subject lines or headers for long messages.
  * Provide a summary at the top when sending multi-part updates.
  * If something is urgent, state the urgency and why.
  * Avoid DM’ing for tasks — use the appropriate shared space.

===== When to Switch to Sync =====
Move from async to real-time only when:
  * looping messages signal misalignment  
  * the issue is blocking work  
  * multiple stakeholders need rapid alignment  
  * emotional nuance or conflict is present  

===== Tools =====
Use tools that preserve structure and searchability.  
Write messages as artifacts others can reference later.

These guidelines evolve as the team learns how to collaborate across time and space.