Don't Panic! Effective Incident Response
summary
Exact claims and concrete tools: a reproducible Incident Command System that codifies when an event is a major incident (severity boundary at sev3→sev2), how anyone can trigger an incident from Slack or PagerDuty, and a minimal role set — incident commander, scribe, deputy, liaisons, SMEs — with handoff timing and checklists. Also specific practices: automated preemptive responses, runbooks, regular drills like chaos/failure-friday exercises, postmortem templates and the decision rule are there any strong objections.
AI-written summary · about
chapters (13)
- 0:00Effective incident response
- 1:14Defining incidents
- 3:44Incident command system
- 6:11Major incidents severity
- 8:38Triggering incidents tooling
- 9:39Switching from peace time to war time
- 12:05Incident lifecycle roles
- 18:42Incident commander duties
- 23:41New IC tips
- 25:25Scribe deputy roles
- 30:22Preparing response teams
- 31:24Postmortems importance
- 32:06Summary resources
related talks
30mHow To Have An Operational Incident (a crash course)
20mHow to Have an Operational Incident
30mHow to have an operational incident a crash course
28mHow to Have an Operational Incident (A Crash Course)
33mDon’t be a bystander, be an Incident Commander!
28mEverything I know about incident response
39mNavigating the Chaos: A Holistic Approach to Incident Management
15mIncident Ready: Chaos Engineer Your Incident Response