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
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 hoursExample output
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.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Build a stop-doing list for an overloaded team
Audit team workloads to eliminate low-ROI tasks, automate routine burdens, and protect core focus without sacrificing business results.
Audit recurring meetings to reclaim team focus time
Evaluate your team's recurring calendar load and turn wasteful status meetings into async updates, shorter syncs, or cancellations.
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.
Build cross-team handoff contracts and review SLAs
Establish firm definitions of done, entry criteria, and review turnaround times between dependent teams to stop delivery bottlenecks.
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.
Create a practical onboarding buddy guide
Equip team buddies with a clear four-week checklist and tactical conversational prompts to support new hires effectively.
- Distribute invisible glue work across your team
- Map post-reorg reporting lines and project continuity changes
- Run a decisive cross-team blocker meeting
- Script empathetic post-reorg check-ins for anxious direct reports
- Separate confirmed reorg facts from open leadership questions
- Set team communication norms to stop after-hours work