Simplify your postmortems and focus on scaling
summary
Advocates a concrete process: templatize and bookmark the page so every postmortem uses the same sections, schedule within three to five days after incidents to capture facts, and push action items into biweekly sprints and track them. It names three tool categories — collaboration (Confluence), incident management/communication, and observability — and recommends checking alerts versus anomaly detection, running 3–4 month retrospectives to spot rising SLO violations, and celebrating wins while fixing missed alerts.
AI-written summary · about
related talks
15mPragmatic Incident Response: Lessons Learned from Failures
28mPost-mortems or How to Walk Away Happy from a Carnage
22mData-driven Postmortems
31mPost-mortems: Building better software together.
34mIncidents are new normal
29mShrinking the Impact of Production Incidents
27mPostmortem Action Items: Plan the Work and Work the Plan
07mDia de los Muertos - Postmortems that save lives