Incident Management: Lessons from Emergency Services
summary
Compares incident workflows between a platform serving reporters and a missing-hiker search, showing concrete practices: decouple alerting and notification so low-severity DB-load blips go to Slack while critical load pages wake engineers; triage a 500 internal server error caused by changed X API response by graying-out frontend features and rolling back integrations; narrow searches using a Strava route to narrow search and public alerts (Nixle/Nextdoor); run handoffs as 12‑hour operational periods, keep pocket checklists and timestamped documentation, and focus debriefs on learning not blame.
AI-written summary · about
chapters (16)
- 0:00Introduction to incident response
- 2:49History of Incident Command System
- 4:54Key concepts in IC
- 6:59Incident process overview
- 9:05Case study technical system
- 10:30Case study missing person
- 12:15Pre-planning and preparation
- 13:40Alerting vs notification
- 15:03Establishing command
- 17:09Initial assessment and planning
- 20:46Stopping the bleed
- 23:19Taking action
- 24:21Assignment and debrief
- 25:25When is the incident over
- 27:29Debriefing and learning
- 29:14Q&A session
related talks
20mHow to Have an Operational Incident
39mNavigating the Chaos: A Holistic Approach to Incident Management
15mIncident Ready: Chaos Engineer Your Incident Response
45mIncident Management - Talk the Talk, Walk the Walk
30mHow to have an operational incident a crash course
57mThe Curious Incident in your Software in the Day Time
37mManaging incidents in microservices
29mComposing the Response: Building an Incident Pipeline from Scratch