Mastering Pre-Mortem Analysis for Success
summary
Claims that 74% of IT projects fail and that a premortem outperforms “what could go wrong” prompts by forcing teams to set a hypothetical failed future date (example: treat launch as if it already flopped) then list causes. Describes a two‑step group protocol, favors small diverse teams, forbids problem‑solving during ideation, and shows the workflow: clean and cluster items, assess likelihood and impact, produce a prioritized mitigation plan and a follow‑up to close the loop.
AI-written summary · about
chapters (9)
- 0:00intro
- 0:14introduction and welcome
- 0:29understanding project failures
- 1:36introduction to premortem technique
- 1:58steps to conduct a premortem
- 3:06best practices for effective premortem
- 4:39common pitfalls to avoid
- 8:32post-premortem actions
- 11:50conclusion and final thoughts
related talks
28mPost-mortems or How to Walk Away Happy from a Carnage
45mThe human nature of failure & resiliency
07mDia de los Muertos - Postmortems that save lives
43mPostmortems, Learning & Blameless Culture
57mIntroducing Threat Modelling To Established Teams
44mThe role of catastrophic failure in software design
40mStars Aligned and Software Development Adrift - Why Can We Predict Planets but Not Deadlines?
30mLearning From Failure: Post Mortems