Managing Fires: Leadership Through Crisis
summary
Declares that crisis requires a prechosen incident commander with authority to make business decisions, then coordinates via runbooks, automation and chat ops; delegates tasks (database recovery, DNS first) so teams work in parallel; uses visible boards like Trello and status pages for frequent external updates; gives a concrete case: faced with a failing single-server client, the choice is 16 hours of recovery or 16 hours of migration and the migration yields a better, working high‑availability outcome; leader manages people, food and rotations, not just tech fixes.
AI-written summary · about
chapters (10)
- 0:00Managing Fires: Leadership Through Crisis
- 1:04use your tools for little fires
- 2:09WATCH AND ACT
- 2:49crisis requires a team and leadership
- 6:01Troubleshooting 101
- 9:13what will make it work?
- 12:58leaders handle human problems
- 14:17manage your bench
- 15:50public communication
- 18:12empower your team, remove barriers
related talks
06mIgnite - Crisis Communication Breakdown
30mThe Perfect Storm - How We Talk About Disasters
43mLeading teams through times of uncertainty and upheaval
30mHow to have an operational incident a crash course
18mStaying in your lane: incident response for leaders
30mHow To Have An Operational Incident (a crash course)
20mHow to Have an Operational Incident
32mSustainable Incident Management