# Remote Team Asynchronous Communication Manifesto *For a 24-person team across US Pacific (UTC-8), US Eastern (UTC-5) and Central Europe (UTC+1). Tools: Slack, Notion, Gmail/Google Docs, Zoom, Linear.* ## 1. Core Operating Principles - **Write first, meet last.** Every update, question and proposal starts as a written post. A live call is allowed only after written communication has been tried and has failed. - **Protect deep work.** Nobody is expected to reply instantly. Each person owns two 2-hour focus blocks a day, shown in their Slack status, with notifications off. "Fast" means within the SLA below, not within 10 minutes. - **If it isn't in Notion, it didn't happen.** Decisions, project updates and meeting outcomes live in Notion. Slack is for conversation, and Notion is the record. Slack DMs are never a place to decide anything. - **Write for a reader who is asleep.** Every post must stand alone: context, the ask, the deadline (in UTC), and the owner. Avoid "quick question?" openers. State the question. ## 2. Channel Decision Matrix & Tool Roles | Channel / Tool | Primary Purpose | Expected Response SLA | Prohibited Use Cases | | :--- | :--- | :--- | :--- | | **Slack** | Quick coordination, short questions, FYI notices, P1 pings. Always in public channels and threads. | Within 4 working hours in the recipient's timezone. No same-day reply is needed outside that window. | Decisions made in DMs. Project updates (use Notion). Long debates (3+ back-and-forths means move to a Notion doc). Expecting replies outside working hours. | | **Email (Gmail)** | Formal external communication, client or vendor records, milestone sign-offs, legal and HR matters. | Within 24 hours (1 business day). | Internal day-to-day discussion. Task assignment. Anything that belongs in Linear or Notion. | | **Notion** | Single source of truth: weekly project updates, decision log, proposals (RFCs), meeting notes, team handbook. | Comments and reviews within 24 hours (1 business day) of being tagged. | Casual chat. Urgent alerts. Undated or ownerless pages. | | **Linear** *(supporting)* | Task status, ownership and blockers. | Status updated by end of the assignee's working day. | Long-form discussion. Status updates that live only in Slack. | ## 3. The Meeting Kill-Switch (Zoom Elimination Protocol) **Pre-requisites for Scheduling a Live Meeting.** All must be true before an invite is sent: - [ ] A written brief exists in Notion (problem, options, desired outcome) and was shared at least 24 hours earlier. - [ ] A written async thread has run for at least one business day without reaching a decision. - [ ] The meeting needs real-time interaction (a conflict, a sensitive conversation, or complex brainstorming), not just information transfer. - [ ] There is a named decision-maker and a stated outcome the meeting must produce. - [ ] Attendees are capped at 8, and each is there to decide or contribute, not to observe. Observers get the notes. - [ ] It falls in the shared overlap window (see below) or the organizer has agreed to rotate the burden of inconvenient times. - [ ] It is a maximum of 25 minutes, with the agenda in the invite. **Shared overlap window.** Pacific, Eastern and Central Europe overlap for only about one hour: **16:00–17:00 UTC** (8–9am PT, 11am–12pm ET, 5–6pm CET). Treat it as scarce. Pacific and Europe have essentially no other overlap, so any meeting involving both must fit here. Always schedule in UTC, since US and EU daylight-saving changes fall on different dates. **Automatic Cancellation Triggers.** A meeting is cancelled and moved async if: - No Notion brief was posted 24 hours beforehand. - The agenda is missing or has no decision or outcome attached. - The decision-maker or required presenter cannot attend. - The content is purely informational (it becomes a written update or a Loom). - A key participant would have to attend outside 7am–7pm local time, unless they volunteered. **Meeting Replacements by Type.** | Meeting to eliminate | Async replacement | | :--- | :--- | | **Daily 30-min standup** | A written check-in posted in Slack by the end of each person's day, using the template: *Done / Doing next / Blocked (@owner).* Linear status is the source of truth. Blockers get tagged, not discussed live. | | **Weekly project status roundtable** | A single Notion page per project, updated by the project owner every Thursday (end of day, UTC). Format: *Status (red/yellow/green), Progress, Risks, Decisions needed.* Stakeholders comment in Notion. | | **Ad-hoc 15-min "catch-up" calls** | A written message with context and a specific question. If it's still unresolved after one round, use a 5-minute recorded Loom or screen recording, or post to the Notion decision thread. A live call needs the Section 3 pre-requisites. | | **Reviews and feedback sessions** | Google Docs or Notion comments with a 48-hour review deadline. An optional live Q&A runs once, only if comments show real disagreement. | ## 4. Urgency Tiers & Escalation Pathway - **P1 (Critical Outage / Blocker):** Production down, customer-facing failure, or a blocker halting multiple people. Post in **#incidents** with @-mention of the on-call owner, using the format *"P1: [what's broken] | impact | what I need."* **Response target: 15 minutes**, at any hour for the on-call person, who rotates by region (follow-the-sun). A Zoom call is allowed immediately without the Section 3 checklist. A post-incident summary goes into Notion within 48 hours. - **P2 (Standard Operational Query):** Work-blocking but not an emergency, or a question needed to finish today's work. Post in the relevant public Slack channel and tag the owner, with a clear deadline. **Response target: 4 working hours** in the recipient's timezone. If there is no reply after that, re-tag once and then escalate to their lead. - **P3 (Long-term Strategy / Feedback):** Proposals, process improvements, retrospectives, career or roadmap feedback. Write a Notion doc and tag reviewers. **Response target: 2 business days.** No Slack pings for P3 beyond one notification that the doc is ready. ## 5. Team Enforcement & Implementation Guide - **Rollout (4 weeks).** Week 1: publish this manifesto and the Notion templates (daily check-in, weekly update, decision log, meeting brief). Week 2: replace daily standups and set Slack statuses and focus blocks. Week 3: replace weekly roundtables with Notion updates. Week 4: apply the full kill-switch to all invites and review. - **Leader responsibilities.** Leads model the behavior first: they answer within SLA (not faster), cancel their own non-compliant meetings, and never reward instant replies. - **Audit monthly.** Track: meeting hours per person per week (target: at least 60% reduction from baseline), the share of decisions logged in Notion, median Slack response time versus SLA, and the number of meetings cancelled by the kill-switch. - **Handling violations.** First time: a friendly public-channel nudge ("please move this to a Notion brief"). Second time: a private note from the lead. Repeated: a discussion about expectations in the 1:1. Non-compliant meeting invites can be declined by any attendee citing Section 3, with no penalty. - **Decisions made in DMs.** Whoever received the decision copies it into the Notion decision log within one business day. A decision not logged is not binding. - **Review cadence.** Review this protocol quarterly and revise based on the audit data. Any change is proposed as a Notion RFC with a 5-business-day comment window. If you'd like, I can turn this into a shareable document or create the Notion templates (daily check-in, weekly project update, decision log, and meeting brief) next.