Retrospectives for Humans
summary
Seattle’s Lacey V. Murrow bridge story anchors the talk: crews store hydrodemolition runoff in pontoons, eight pontoons sank in a storm after leaks and schedule failures, damage totals about $69 million, and rebuilt pontoons are subdivided to limit cascades. The concrete claim is clear: incident reviews must be blameless retrospectives that uncover contributing factors not root-cause myths, produce concrete remediation items, track who actually did pumping and trucking, practice facilitation, rotate note-taking, and measure whether fixes change outcomes.
AI-written summary · about
chapters (32)
- 0:00Introduction
- 1:12Seattle Floating Bridge
- 6:51A Giant Disaster
- 8:43The Social Problem
- 10:09The Bridge
- 10:50Crash Course
- 11:21Millers Law
- 12:27Blame
- 13:10Why
- 13:53Other
- 15:05The Last Time
- 15:46Better Things
- 16:56Remediation
- 17:39Human Error
- 18:10Fallacy
- 18:50How to Have a Great Meeting
- 20:54Practice Interrupting
- 22:33Look at Whos Talking
- 24:05Humor
- 24:48Jokes
- 25:11Bad jokes
- 25:37Things I shouldnt mention
- 25:53Fat jokes
- 26:41How to lessen the mood
- 26:57When things go wrong
- 27:09When you mess up
- 28:08When you blame yourself
- 28:46Critical thinking
- 29:23A bad joke
- 30:27Whats the point
- 31:28Acknowledgements
- 31:59How do you approach it
related talks
37mRetrospectives for Humans (the short form)
22mComplex System Failures and Blameless Retrospectives
01h 30mRunning Excellent Retrospectives: Talking for Humans
31mThe Blameless Cloud: Bringing Actionable Retrospectives to Salesforce
38mRetrospectives Antipatterns Avoid my Mistakes
29mLearning from incidents: how things went right
59mRetrospectives Antipatterns
40mBuilding Resilience: How to Learn More from Incidents