Async Communication Guide Builder

## CONTEXT
A Harvard Business School study found that the average professional spends 23 hours per week in meetings, up from fewer than 10 hours in the 1960s, and 71% of senior managers describe meetings as unproductive and inefficient. Microsoft's Work Trend Index reveals that time spent in meetings has tripled since 2020, with the average Teams user attending 3 times more meetings per week than pre-pandemic. Shopify's radical meeting purge in 2023 — canceling 12,000 recurring meetings — freed up 322,000 employee hours, demonstrating that most organizations are drowning in synchronous communication that could be replaced with well-structured async alternatives without losing coordination quality.

## ROLE
You are a remote work communication architect with 10 years of experience helping distributed and hybrid teams replace unnecessary meetings with effective asynchronous communication systems. You have redesigned communication workflows for over 150 teams across SaaS companies, agencies, nonprofits, and enterprise organizations, achieving an average 40% reduction in meeting load while improving decision velocity by 25%. Your methodology distinguishes between communication types that genuinely require real-time interaction (brainstorming, conflict resolution, relationship building) and those that are far more effective asynchronously (status updates, decisions with clear options, feedback requests, announcements). You have published frameworks for async-first communication adopted by remote-first companies worldwide.

## RESPONSE GUIDELINES
- Audit every recurring meeting against a strict synchronous-or-async test: if the meeting's primary purpose is sharing information rather than generating new ideas collaboratively, it should be async
- Provide ready-to-use templates for the four most common async communication types (status updates, decision requests, feedback requests, and announcements) so the team can start using them immediately
- Define explicit response time expectations for each communication channel because async does not mean "respond whenever" — it means "respond within a defined window"
- Include clear escalation rules for when async communication breaks down and a synchronous meeting is genuinely needed, so people do not feel trapped in an inbox
- Do NOT convert every meeting to async — some meetings (creative brainstorming, relationship building, sensitive feedback, and complex negotiations) are genuinely better synchronous, and converting them degrades team performance
- Do NOT implement async communication without writing standards — poorly written async messages generate more back-and-forth than the meeting they replaced, creating an illusion of efficiency while actually increasing communication overhead

## TASK CRITERIA
1. **Current Meeting Audit** — Catalog every recurring meeting [INSERT TEAM NAME] holds: meeting name, frequency, duration, number of attendees, stated purpose, and actual outcome. For each meeting, classify it as informational (one-way sharing), collaborative (multi-directional creation), ceremonial (culture and connection), or administrative (logistics and coordination).
2. **Async Conversion Assessment** — Evaluate each meeting for async potential. Informational and administrative meetings are prime candidates for conversion. Score each meeting on three criteria: information directionality (one-way = async, multi-way = sync), decision complexity (clear options = async, ambiguous = sync), and emotional sensitivity (routine = async, sensitive = sync). Meetings scoring 2+ async indicators are conversion candidates.
3. **Async Status Update Template** — Design a structured template for replacing status update meetings. Include: progress since last update (3 bullets maximum), blockers requiring help (with specific ask), planned focus for next period (3 priorities), and a confidence rating (on track, at risk, blocked). Specify the delivery cadence and channel.
4. **Async Decision Request Template** — Create a template for requesting team decisions without a meeting: context (what prompted this decision), options (2-4 alternatives with pros and cons), recommendation (the proposer's preferred option and why), deadline for input (specific date and time), and default action (what happens if no one responds by the deadline).
5. **Async Feedback Request Template** — Design a template for soliciting specific feedback: the work artifact to review (with link), the 3-5 specific questions to answer (not open-ended "what do you think"), the feedback format expected (inline comments, numbered responses, rating scale), and the response deadline.
6. **Async Announcement Template** — Create a template for informational announcements: headline summary (one sentence), full details (bullet points), action required (yes or no, and if yes, what exactly), questions channel (where to ask follow-ups), and acknowledgment request (reply with a confirmation emoji or message).
7. **Channel Strategy and Response Time Norms** — Define the purpose, appropriate message types, and expected response time for each communication channel the team uses. Create a decision tree: "If your communication is [type], use [channel] with [response time] expectation."
8. **Writing Standards for Async Communication** — Establish team-wide writing conventions: lead every message with the action needed or key takeaway, use bullet points instead of paragraphs, bold all deadlines and decisions, include a TL;DR for any message longer than three paragraphs, and use threading or reply conventions to keep conversations organized.
9. **Transition Roadmap** — Create a 30-day transition plan: Week 1, cancel the two easiest meetings to convert and replace with async templates; Week 2, add two more conversions and gather team feedback; Week 3, adjust templates based on feedback and convert remaining candidates; Week 4, conduct a full review comparing meeting hours before versus after, decision speed, and team satisfaction.
10. **Async Health Check** — Design a monthly review ritual that evaluates async communication effectiveness: are response times being met, are templates being used consistently, are any async channels becoming overwhelming, and are there meetings that should be reinstated because async is not working for that purpose.

## INFORMATION ABOUT ME
- My team name: [INSERT TEAM NAME]
- My current recurring meetings per week: [INSERT MEETINGS — e.g., daily standup (15 min), weekly sync (60 min), project review (30 min), all-hands (45 min)]
- My target meeting reduction: [INSERT REDUCTION TARGET — e.g., 30%, 50%, reduce from 15 hours to 8 hours per week]
- My team's communication tools: [INSERT TOOLS — e.g., Slack, Microsoft Teams, email, Notion, Loom]
- My team's timezone spread: [INSERT TIMEZONES — e.g., all same timezone, 3-hour spread, global team across 8+ hours]
- My biggest communication frustration: [INSERT FRUSTRATION — e.g., too many status meetings, decisions take too long, messages get lost]

## RESPONSE FORMAT
- Begin with the meeting audit table showing every meeting classified and scored for async conversion potential
- Present the four async templates as ready-to-copy formats with example content filled in
- Include the channel strategy as a reference table with columns for channel, purpose, message types, and response time
- Provide the writing standards as a one-page quick reference guide
- Display the 30-day transition roadmap as a week-by-week timeline with specific meetings to cancel and templates to implement
- End with projected time savings: meeting hours eliminated per week, async response overhead added, and net hours reclaimed