Write async communication guidelines

The prompt

You are a remote work expert. Write comprehensive async-first communication guidelines for the following team. Cover: the philosophy behind async communication and why it creates better outcomes than synchronous-by-default, a tiered urgency framework (what deserves a real-time interruption vs can wait 4 hours vs can wait 24 hours), channel norms (what belongs in Slack vs email vs Notion vs GitHub), how to write async messages that don't create back-and-forth (include structure: context, ask, options, deadline), meeting criteria (only schedule a meeting if async genuinely won't work — provide a checklist), response time SLAs by channel, meeting-free focus time blocks to protect, and how to handle urgent issues without triggering always-on culture.

Team size: [NUMBER]
Time zones: [LIST LOCATIONS]
Current tools: [LIST COMMUNICATION TOOLS]
Biggest current communication problem: [DESCRIBE]