Ignites- Don't be a Bystander, be an Incident Commander!
summary
Claims that nontechnical staff can lead incidents, backed by a concrete training pipeline used at PagerDuty: define the incident commander as coordinator not solver, run incident commander office hours, require shadowing then scribe duties, then “reverse shadow” with primary and secondary IC on-call so a deputy can send tips. The process produces more on-call leaders, spreads load off senior engineers, and yields documented incidents for faster postmortems.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:30Something is broken!
- 0:45Major Incident Incident Response Incident Commander
- 1:30Inclusive Incident Response
- 1:45Coordinate and delegate
- 2:15Office Hours
- 3:00Scribe
- 3:30Reverse Shadow
- 4:00Celebrate
- 4:46#DevOps
- 5:15Recording and Production Confreaks
related talks
33mDon’t be a bystander, be an Incident Commander!
26mStaying in your lane: incident response for leaders
48mIncident Management - Talk the Talk, Walk the Walk
33mDon't Panic! Effective Incident Response
06mIgnite - Crisis Communication Breakdown
12mBetter Incident Management to Reduce MTTR
20mHow to Have an Operational Incident
30mHow to have an operational incident a crash course