Public preview
Post-Incident Review
After major incident: full review — timeline, causes, improvements, no blame.
Goal
Turn incident from regret into org learning — prevent recurrence.
Steps
-
1
Within 7 days: gather participants.
Expected Outcome
Immediate
You find 3-5 systemic causes that'd be ignored.
Evidence base
School: Etsy Blameless Post-Mortems
Founders: John Allspaw · Etsy (2012)
Allspaw — Code as Craft blog 2012 "Blameless PostMortems and a Just Culture"; Dekker — Just Culture (2007) as philosophical source.
Keywords
#post-mortem#aar#allspaw#etsy#5-whys#لماذا#crisis#blameless#timeline#learning#sidney-dekker#مراجعة ما بعد الحادث#خط زمني دقيق#تعلم مؤسسي من الأزمة#سبعة أيام كحد أقصى#نشر التقرير داخليا#ثلاثة إلى خمسة أسباب نظامية#just-culture-2007#2012-etsy-code-as-craft-blog#جودة المعلومة فوق اللوم#متى علمنا متى تصرفنا متى حل#متى آخر حادث كبير بلا مراجعة#تحويل الحادث من ندم إلى تعلم#منع تكرار الحادث#مراجعة كاملة بعد أي حادث كبير
Frequently asked questions
How long does "Post-Incident Review" take?
This exercise takes about 90 minutes, practiced in a group in a Social format.
When will I notice the effect of "Post-Incident Review"?
You find 3-5 systemic causes that'd be ignored. In the short term: After 3 PMs, first incident type doesn't recur.
Is "Post-Incident Review" evidence-based?
Yes — it draws on Etsy Blameless Post-Mortems (John Allspaw, Etsy (2012)). Allspaw — Code as Craft blog 2012 "Blameless PostMortems and a Just Culture"; Dekker — Just Culture (2007) as philosophical source.
Is "Post-Incident Review" suitable for beginners?
Its difficulty level is: Advanced. No external tools required — it can be practiced directly inside the app.
Subscribe for full access
Subscribe to Plus for full access to this practice and the whole catalogue, or try first — free, no sign-in, no commitment.
7 complete practices (one per domain) are free forever, no sign-in.