Post-mortems: Building better software together.
summary
Argues for post-mortems that identify what prevented safe probing and accurate sensing rather than chasing a single root cause, and shows a concrete process: use trained analysis facilitators, wait a 24-hour delay, run a video conference to co-edit a timeline with UTC timestamps, capture cross‑role evidence, create JIRA action tickets, and have facilitators follow up and iterate the facilitator handbook so the process improves as the software and company change.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:56Complicated Machine
- 2:21Complicated Problems
- 7:13Cynefin Framework
- 8:14Complex software
- 11:48Complex analysis
- 14:02How should I run my own post-mortem process?
- 14:50Analysis != Response
- 15:36Analysis facilitators
- 18:13Call time!
- 21:37Call: systems analysis
- 23:43Call: Action items
- 25:42Communication & improvement
- 27:22References
