Staying in your lane: incident response for leaders
summary
Defines incidents and insists leaders mostly stay out of the way, stepping in only when asked, when protocol demands, or to correct a clear major mistake; institutes an incident commander with final authority and a named communications liaison; uses Slack channels or an internal status page plus stakeholder notifications for 20–30 minute updates; provides playbooks and operations guides teams follow; calls out the testable script for handling the executive swoop and poop—ask “would you like to take command?” to restore clarity.
AI-written summary · about
chapters (9)
- 0:00Introduction and Speaker Background
- 0:47Personal Anecdote: Lessons from the Kitchen
- 2:24Defining Incident Response at PagerDuty
- 3:23Leadership in Incident Response
- 4:48Empowering Your Team
- 7:42The Executive Swoop and Poop
- 9:33Effective Communication During Incidents
- 15:30Recap and Final Thoughts
- 16:31Resources and Q&A
related talks
26mStaying in your lane: incident response for leaders
26mIncident Commanders to Incident Analysts: How We Got Here
32mIncident Management - Talk the Talk, Walk the Walk
19mManaging Fires: Leadership Through Crisis
36mSo You Want a New Incident Commander—Lessons from Building Incident Response...
44mPanel: Peak Performance Under Pressure: Building Cross-Functional Resilience in Incident Response
13mThe Incident Is The Way: Using Your Incidents to Win...
23mMotivational Leadership Driving Change Through Empowered Eng