Elephant in the Blameless War Room—Accountability
summary
Shows that blamelessness and accountability coexist: hold people only after exhausting systemic fixes and clear prerequisites (were expectations documented, was feedback provided), and separate incident response from performance management. Uses a real outage where an engineer hit production instead of test and the team builds a big flashing production banner plus restrict edit permissions and oversight, implements a two‑week contributing‑factor analysis and action plan, sequences persuasion (ethos/logos/pathos), and reports hiring is usually costlier than training.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:10Blameless Culture & Developer Velocity
- 2:26Interpreting Chaos
- 7:19on the incident
- 15:21Stakeholder Trust
- 24:57Blamelessly Accountable
related talks
29mElephant in the Blameless War Room - Accountability
05mWho's to Blame?
22mBlame, shame and panic - how not to respond when things go wrong
20mBeyond Blameless
28mBlameless Postmortem Culture
48mOf Elephants, Mooses and other problems in the Room
19mBlame, Shame and Panic - What not to do when things go wrong
06mIgnite: Failure and the Third Way