Sustainable Incident Management
summary
History of wildfires leads to creation of Firescope after the 1970s Laguna fire (about 16 fatalities), giving tech a concrete model: adopt an incident command system so one person funnels orders, reduce duplication, and standardize terminology. Cites a 2019 Catchpoint SRE survey with ~80% reporting stress and common on‑call bands of 2–5 or 6–10 people. Recommends 12‑hour rotations, automated timelines by pulling monitors, disaster recovery and chaos testing, training ramps, and a Datadog+Slack integration that auto‑creates an incident channel.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker background
- 3:08Defining sustainable incident management
- 7:14History of incident command system
- 10:24Pain points in incident response
- 13:37Audience pain points discussion
- 18:28On-call stress and escalations
- 21:15Incident communication challenges
- 22:41Post-incident reviews and training
- 24:49Making incident response sustainable
- 28:40Q&A and audience feedback
related talks
15mSustainable Incident Management for happy SRE teams
43mLearning from Firefighters to Improve Systems Reliability
42mIncident Command at the Edge- 43mLearning from Firefighters to Improve Systems Reliability
19mManaging Fires: Leadership Through Crisis
20mHow to Have an Operational Incident
36mSo You Want a New Incident Commander—Lessons from Building Incident Response...
39mNavigating the Chaos: A Holistic Approach to Incident Management