Asynchronous communication framework

Vytvoř asynchronous communication framework pro [TEAM/ORGANIZATION]. Size: [SMALL TEAM/DEPARTMENT/COMPANY]. Struktura: 1) **Async-First Philosophy** - default to asynchronous (written over meetings), respect focus time (no expectation of immediate response), document decisions (write things down), transparent by default (public channels over DMs), time zone friendly (global team support), 2) **Communication Channels** - Slack/Teams (quick questions, non-urgent, expected response: 4h), Email (formal, external, expected response: 24h), Notion/Docs (documentation, decisions, permanent knowledge), GitHub/Linear (code, issues, project updates), Loom (video async explanations), meetings (only when truly needed, recorded), 3) **Response Time Expectations** - urgent (< 1h, phone/SMS only for true emergency), high priority (< 4h, Slack mention), normal (< 24h, Slack/email), low priority (< 48h, document/async), document expected SLAs (what qualifies as urgent?), 4) **Meeting Reduction** - meeting decision tree (can it be email? async doc? Slack thread? only meet if sync required), required agenda (no agenda = no meeting), timeboxed (default 25min not 30, 50min not 60), optional attendance (required vs optional clearly marked), record all meetings (for async viewing), 5) **Documentation Culture** - write-it-down bias (if discussed, document outcome), decision logs (why we chose X), RFCs for major decisions (Request for Comments), meeting notes template (decisions, action items, owner), knowledge base (searchable wiki), 6) **Async Collaboration Tools** - Notion/Confluence (docs, wikis, project pages), Loom/Soapbox (async video messages), Figma comments (design feedback), GitHub PRs (code review asynchronously), Linear comments (project updates), Google Docs suggestions (collaborative editing), 7) **Status Updates** - daily/weekly status posts (what done, what next, blockers), team dashboards (automated from Linear/GitHub), no status meetings (async written updates), standup alternative (Slack thread or Notion page), progress sharing (screenshots, Loom demos), 8) **Handling Urgent Issues** - escalation ladder (Slack → mention → DM → phone for true emergency), on-call rotation (defined who to contact when), incident playbook (clear protocol for outages), urgent criteria (what actually qualifies as urgent?), false urgent tax (overuse of urgent reduces effectiveness), 9) **Feedback & Reviews** - async code reviews (GitHub comments not pairing), design critiques (Figma comments with Loom explanations), performance reviews (written with async Q&A), 1-on-1s (can be async doc exchange if preferred), feedback documents (detailed written over quick verbal), 10) **Boundary Protection** - focus time blocks (calendar blocked, notifications off), response windows (2x daily check: 10am, 3pm), weekend off (no expectation of weekend work), vacation truly off (clear backup, no messages), notification management (turn off mobile push, check on schedule). Včetně: Communication charter template, channel guidelines, SLA matrix, meeting decision tree, async workflow examples, tool recommendations.