Julia Moser·
Wrote our team an async comms handbook with response-time rules that killed the fake-urgent DMs
Creates team async communication protocols with response time expectations, channel ownership, and escalation rules.
Async Communication Guidelines Generator
You are a remote work consultant specializing in async communication. Our team has {{team_size}} people across {{time_zones}} time zones. Our current pain points: {{communication_pain_points}}. Tools we use: {{communication_tools}}. Our work type: {{work_type}}. Urgency levels we need: {{urgency_levels}}. Create: (1) A channel/tool purpose matrix (what goes where), (2) Response time expectations by urgency and channel, (3) 'When to meet vs when to write' decision tree, (4) Async update templates (daily, weekly, project), (5) Escalation protocol for blocked work, (6) Documentation standards and expectations, (7) Onboarding checklist for new team members on our async culture. Format as a team handbook section. Include specific examples of before/after communication scenarios.
Ergebnisse
Async communication handbook for your 14-person team across 4 time zones. Core pain: people DM "urgent" things at all hours and feel obligated to reply instantly. We fix that with explicit norms.
## 1. Channel purpose matrix
| Channel/tool | Use for | Don't use for |
|--------------|---------|---------------|
| Slack `#team` | Quick questions, FYIs | Decisions, anything needing a record |
| Slack DM | Truly personal/sensitive | Work that others should see |
| Notion docs | Decisions, specs, anything durable | Real-time chat |
| Email | External + formal | Internal quick questions |
| Video call | Brainstorm, conflict, relationship | Status updates |
## 2. Response-time expectations
| Urgency | Channel | Expected response |
|---------|---------|-------------------|
| FYI | Slack/Notion comment | No reply needed |
| Normal | Slack `#team` | Within 1 working day (your TZ) |
| Time-sensitive | Slack + `@mention` | Within 4 working hours |
| Urgent (rare) | Phone call / `@here` + reason | ASAP — must justify |
**Default is async.** No one owes an instant reply.
## 3. When to meet vs write
```
Is it a decision with >2 viewpoints? → meet (or threaded async vote)
Is it status/FYI? → write
Is it emotionally charged? → meet/call
Can it wait 24h? → write
```
## 4. Async update templates
- **Daily (optional):** Done / Doing / Blocked, 3 lines.
- **Weekly:** Wins / Risks / Next, posted Friday.
- **Project:** Status (green/yellow/red) / Decisions needed / Owner / ETA.
## 5. Escalation protocol
Blocked >4h on time-sensitive work → `@mention` owner; >1 business day → `@here` in `#team` with the blocker and what you need.
## 6. Documentation standard
Every decision gets a Notion entry: context, options, decision, owner, date. "If it's not written, it didn't happen."
## 7. Onboarding checklist (new hires)
- [ ] Read this handbook
- [ ] Set Slack notification schedule to working hours
- [ ] Post a "my hours + time zone" intro
- [ ] Practice one async weekly update
**Before/after:** *Before:* "URGENT can you look at this???" (9pm DM). *After:* a `#team` post tagged `Normal`, answered next morning — no false alarm, no burnout.
Modell: Claude Sonnet 4
103 Likes21 SavesScore: 52
3 Kommentare
Grace Williams·
Okay this workflow automation output just fixed my week.
Noah Steiner·
Sent this to my whole team and we standardized on it the same day.
Leon Wirth·
The workflow automation structure here just clicks.