Mastering incident communications
summary
Argues that customer support should own the liaison role during major incidents, translating engineering terms into customer-facing updates and feeding customer symptoms back into the incident. Recommends concrete practices: use Slack channel + PagerDuty + Jira and a 20-minute cadence for early updates, maintain both external and internal status pages, keep templateable message skeletons, map internal components to customer-facing features, run public postmortems, and formalize the liaison role so communications actually work.
AI-written summary · about
chapters (10)
- 0:00Incident communications intro
- 1:27Customer language in updates
- 4:58Customer-facing teams' role
- 8:25Stakeholder communications
- 12:42Terminology for clarity
- 16:13Communication toolkit
- 19:19Drafting incident updates
- 21:47Update cadence & expectations
- 23:57Improving communication processes
- 25:52Q&A on postmortems
related talks
26mMastering Incident Communications
37mMastering incident communication
20mHow to Have an Operational Incident
27mIncidents: the customer empathy workshop you never wanted
28mHow to Have an Operational Incident (A Crash Course)
06mIgnite - Crisis Communication Breakdown
30mHow to have an operational incident a crash course
05mDevOps and incident management: A recipe for success