Create a team working agreement for async communication

Establish clear response expectations, channel usage guidelines, and focus time norms for distributed teams. Use this to reduce chat noise and eliminate meeting fatigue.

You getCore Principles, channel Matrix and escalation Protocol

Prompt

Prompt
Act as an organizational design lead specializing in distributed remote teams.

Write a concrete, practical async communication working agreement for a knowledge-work team.
- Establish explicit response time expectations for urgent versus standard messages.
- Define clear rules for channel separation (chat, tickets, documents, email).
- Include practical rules for handling escalations without requiring after-hours monitoring.
- Keep guidelines actionable, eliminating vague advice like 'be respectful' or 'communicate clearly'.

Output format:
- Core Principles: 3 foundational rules for documentation and updates
- Channel Matrix: A Markdown table with columns (Channel, Primary Purpose, Expected Response Window, Examples)
- Escalation Protocol: Numbered steps for genuine emergencies
- Focus Time Rules: Concrete boundaries for meetings and notification quiet hours

Example output

Core Principles
  1. Default to Public Documentation: Decisions, spec changes, and project status must live in project tickets or central docs, never in private 1-on-1 direct messages.
  2. Context Over Speed: Every request must include background context, expected deliverable, deadline, and priority level so the receiver can act without back-and-forth clarification.
  3. Presumed Async: No teammate is expected to monitor chat constantly. Deep work blocks are protected by default.
Channel Matrix
ChannelPrimary PurposeExpected Response WindowExamples
Slack/Teams ChannelsPublic team questions, non-blocking updatesWithin 4 business hoursDaily status summaries, quick technical questions
Project Board / JiraTask tracking, specs, acceptance criteriaWithin 24 business hoursBug reports, PR review requests, architecture updates
EmailExternal partner communication, formal noticesWithin 1 business dayVendor inquiries, executive summaries
Pager / Phone CallProduction outages, customer data alertsUnder 15 minutesService downtime, major security incidents
Escalation Protocol
  1. If a blocker occurs that stops a release within 2 hours, post in the project channel with the tag @channel-urgent.
  2. If no response within 20 minutes, call the on-call engineer using the automated rotation line.
  3. Never use direct text messages or personal phone numbers for non-critical work.
Focus Time Rules
  • No recurring internal meetings on Tuesdays and Thursdays before 1:00 PM local time.
  • Status notifications must be muted during focused blocks; schedule send messages when writing outside partner working hours.
Written by AI from this prompt. Your results will vary.

Paste this directly into ChatGPT, Claude or Gemini without edits. After reading the draft, ask: "Tailor this specifically for a team spanning London, New York, and San Francisco time zones."

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Leadership & Management
Leadership & Management

Build a thirty-sixty-ninety day onboarding plan

Generate a clear, phased milestone roadmap for incoming team members to eliminate ambiguity. Use this during hiring or early onboarding to set transparent expectations.

Leadership & Management

Create a post-crunch team recovery sprint plan

Design a two-week reset sprint to help teams recuperate after an intense deadline push. Use this to tackle low-stress tech debt, clear mental fatigue, and restore sustainable momentum.