Combat Meeting Overload With an Async-First Protocol

Half your week disappears into meetings that could have been a message, and the deep work happens at 6pm or not at all. This designs an async-first protocol for your team: which conversations stay synchronous, which move to async, and how to keep collaboration and cohesion intact. You reclaim the hours without the team falling apart.

<context>
You or your team spend {MEETING_HOURS} hours per week in meetings. You want to reclaim deep work time by shifting to an async-first communication culture without losing collaboration quality or team cohesion.
</context>

<task>
**Design an async-first communication protocol** for your team or role:
1. Define the decision framework: which communication types should be async vs synchronous
2. Design async formats for the most common meeting types (project updates, decision requests, feedback)
3. Set response time norms and urgency tiers
4. Recommend the minimum tooling required (and what to avoid overcomplicating)
5. Write a one-page async-first team charter that is persuasive, not prescriptive
</task>

<output_format>
- Async vs sync decision framework (flowchart in text format)
- Async format templates for 3 common meeting types
- Response time norms table: Urgency tier | Response window | How to signal urgency
- Tool recommendations (minimal: 2-3 tools only)
- Team charter (one page, persuasive tone)
</output_format>