async-commslisted

# Async Communication ## Async-First Principles 1. **Default to async** — synchronous communication is expensive; use it only when async fails 2. **Write to be understood without back-and-forth** — assume no follow-up questions 3. **Make decisions visible** — document reasoning, not just outcomes 4. **Respect focus time** — don't expect immediate responses 5. **Over-communicate context** — remote colleagues lack ambient information ## Response Time Expectations by Urgency | Tier | When | Expected response | |------|------|------------------| | Urgent | Production down, blocker unblocking someone | < 1 hour | | High | Needs today to unblock work | < 4 hours | | Normal | Standard work item | < 24 hours | | Low | FYI, no action needed | No response required | Communicate urgency explicitly: `[URGENT]`, `[FYI]`, `[ACTION NEEDED by Fri]` in subject/header. ## Written Communication Standards ### Length Norms | Message type | Target length | |-------------|--------------| | Slack message | 1-3 sentences; longer → write a doc | | Status update | 3-5 bullet points | | Decision doc | 1-2 pages max | | RFC/proposal | Enough to get to a decision, no more | | Meeting notes | Action items + decisions only | ### Structure Template (for complex async messages) ``` ## [Title / What this is about] **TL;DR:** [One sentence summary] **Context:** [Why this matters, 1-2 sentences] **The Ask / Decision needed:** - [Option A — recommended] because [reason] - [Option B] — tradeoffs: [...]