Skip to content
TheChatArchiveThe Chat Archive
Grok 4.1 Fast· xaiHugging Face Frontier Reasoning Traces

Design an incident comms playbook: audiences, cadences, and artifacts.

  1. User

    Design an incident comms playbook: audiences, cadences, and artifacts.

  2. Assistant

    Incident Communications Playbook

    Purpose

    This playbook outlines who to communicate with (audiences), how often (cadences), and what to share (artifacts) during incidents. It ensures transparency, reduces anxiety, and maintains trust.

    Key Principles:

    • Communicate early and often—under-communicate is worse than over-communicate.
    • Use clear, concise language: What happened? Impact? Actions? ETA? Next update.
    • Designate a Comms Lead (e.g., from IR or PR team) during the incident.
    • Escalate if no update in 2x cadence interval.
    • Post-incident: Retrospective includes comms review.

    Severity Levels (assumed standard SRE model):

    SeverityDescriptionExample
    SEV1Critical business impact (e.g., full outage)Production down for all users
    SEV2Major degradation (e.g., 50% users affected)Regional outage
    SEV3Limited impact (e.g., single service degraded)Internal tool down

    Audiences

    Tailor messages by audience. Always start with internal alignment before external.

    AudiencePriorityChannelsNotes
    Internal - Incident Response (IR) TeamHighestSlack (#incidents), Zoom bridgeReal-time tactical updates
    Internal - Affected Teams/LeadershipHighSlack channels, email digest, all-hands SlackBusiness impact, ETAs
    Internal - All EmployeesMediumCompany-wide Slack/email, intranetHigh-level status only
    External - CustomersHigh (for SEV1/2)Status page, customer email, support ticketsProactive if >10% affected
    External - Partners/VendorsMediumDedicated email/Slack, status pageIf interdependent
    External - Media/RegulatorsLow (SEV1 only)PR team approval, press releaseLegal review required
    External - Public/SocialLowTwitter/Status pageGeneric updates only

    Cadences

    Timelines start at T=0 (incident declared). Adjust for time zones (UTC primary). Use a shared Google Sheet or incident tool (e.g., PagerDuty, Firehydrant) for tracking.

    SeverityInternal (IR/Teams)Internal (All-Employees)External (Customers/Partners)External (Public/Media)
    SEV1Every 15 mins until mitigationEvery 30 minsEvery 30 mins (status page), hourly emailEvery 1 hour (if public-facing)
    SEV2Every 30 minsHourlyHourly (status page)Every 2 hours (status page only)
    SEV3HourlyAs needed (min 2x/day)As needed (status page)None
    ResolvedImmediate "All Clear"ImmediateImmediate + root cause in 24-48 hrsImmediate if applicable

    Milestones (all severities):

    • T=0: "Incident declared."
    • T+30 mins: Initial impact assessment.
    • Mitigation: "Fix deployed."
    • Resolved: "Monitoring post-fix."
    • +24 hrs: Root cause summary.

    Artifacts

    Use templates below. Store in shared repo (e.g., GitHub, Notion). Customize per incident. Tools: Statuspage.io (external), Slack (internal), Google Docs (drafts).

    1. Status Update Template (All Channels)

    Incident: [Short Title, e.g., "Prod API Outage"]
    Severity: [SEV1/2/3]
    Status: [Identified | Mitigating | Monitoring | Resolved]
    Time: [UTC]
    Summary: [1-2 sentences on what/impact]
    Actions: [Bullet list of steps]
    ETA: [To next milestone or resolution]
    Next Update: [Specific time]
    Incident Cmdr: [@handle] | Comms Lead: [@handle]
    

    2. Channel-Specific Artifacts

    ChannelArtifact ExamplesFrequencyOwner
    Slack (#incidents)Pinned status threadPer cadenceIR Lead
    Zoom BridgeVerbal readoutsPer internal cadenceIncident Cmdr
    Email Digest (Internal)HTML summary w/ linksHourly (SEV1/2)Comms Lead
    Status PageAutomated + manual updatesPer external cadenceComms Lead
    Customer EmailPersonalized blast (via Customer.io)Hourly (SEV1/2)Customer Success
    Twitter/LinkedInTweet threadEvery 2+ hours (SEV1)Social Lead (PR approved)
    Press ReleaseFull doc (Google Doc)Post-resolution (SEV1)PR
    Post-MortemPublic/ internal report48-72 hrs post-resolveEngineering + Comms

    3. Escalation & Handoffs

    • No update? Escalate to leadership in 2x cadence.
    • Legal/Regulatory: Flag sensitive incidents (e.g., data breach) immediately.
    • Templates Repo: [Link to your shared drive/Notion page].

    Quick-Start Checklist

    1. Declare incident → Assign Comms Lead.
    2. Post T=0 update to #incidents.
    3. Set calendar reminders for cadences.
    4. Mirror updates to status page.
    5. Resolved → Send all-clear + schedule post-mortem.

    This playbook is living—review after every SEV1. Questions? Ping #comms or the Comms Lead.

    Designed by Sherlock, Trailblazer Labs

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.