How to have an operational incident a crash course
summary
Clear actionable checklist for getting an incident under control: have reliable monitoring and thresholds, advertise a single assembly Slack channel or conference bridge that stays up, use a dispatcher pattern that will page teams not people, assign an incident commander with sole authority, run 4-hour shifts for responders, log narratives during work for postmortem, prepare playbooks for rollback versus long mitigations, and train engineers to act as incident commanders so decisions happen without freezing.
AI-written summary · about
chapters (11)
- 0:00Introduction and context
- 1:46Defining an emergency
- 4:14Urgent versus important
- 6:22Emergency response frameworks
- 9:30Building an incident system
- 13:45Assembling the response team
- 15:31Role of the incident commander
- 16:55When is the incident over
- 18:41Minimum requirements for response
- 20:06Next steps and communication
- 23:23Q&A session
related talks
30mHow To Have An Operational Incident (a crash course)
28mHow to Have an Operational Incident (A Crash Course)
20mHow to Have an Operational Incident
39mNavigating the Chaos: A Holistic Approach to Incident Management
33mDon't Panic! Effective Incident Response
01h 04mIncident Management - Talk the Talk, Walk the Walk
32mIncident Management - Talk the Talk, Walk the Walk
19mHow to handle incidents at scale