People are bad at foreseeing risks. Psychological research has shown this for decades — and still the standard practice in organizations remains classic risk analysis: hold a workshop asking everyone for possible problems. The result is usually thin, polite, and harmless. Gary Klein developed the Pre-Mortem method that systematically bypasses this weakness. Instead of asking 'what risks could arise?', the Pre-Mortem asks: 'assume the project has failed in six months — why?'. This reversal is the key trick: people recognize risks significantly more easily in hindsight than in foresight. This article shows how to conduct Pre-Mortems, when they work especially well, and how they combine with classic analysis tools.
Pre-Mortem
The Pre-Mortem works in four steps. First: the team gathers before project start or before an important decision. Second: the facilitator sketches the failed scenario — 'we failed six months ago, the project was canceled.' Third: each participant notes for themselves for 10 minutes the reasons for this failure. Fourth: the reasons are collected, grouped, and prioritized. The key difference to a classic risk workshop: the prospective question 'what could go wrong?' creates politeness and superficiality. The retrospective question 'why did it go wrong?' creates honesty and depth. Studies show Pre-Mortems produce significantly more relevant risks than standard methods.
View DetailsDEFINITION
Prospective hindsight is the psychological principle Pre-Mortem rests on: people are better at recognizing causes when they imagine an event as already having happened. The method uses this cognitive peculiarity to produce better risk insights than direct risk questioning makes possible.
PRO TIP
Formulate the failure concretely. 'The project failed' is too abstract. Better: 'It's March 2027, the project was canceled after nine months, the CEO decided not to continue the initiative.' The more concrete the scenario, the deeper the answers. A general failure produces general answers — a specific one produces specific ones.
Fishbone Diagram
The Fishbone Diagram is the classic complement to the Pre-Mortem. After the Pre-Mortem has collected reasons for possible failure, a Fishbone Diagram structures these reasons systematically: which categories of causes appear? People, processes, technology, external factors? The Fishbone helps recognize patterns not immediately apparent from the raw Pre-Mortem list. If three out of five named causes concern 'unclear roles', that's a strong signal. Without systematic structuring, Pre-Mortem results remain a loose list from which priorities only painfully emerge.
View DetailsProblem Tree
The Problem Tree extends the analysis with causal depth. While the Pre-Mortem collects reasons and the Fishbone groups them, the Problem Tree distinguishes between symptoms, causes, and root causes. That matters because not every named failure reason sits equally deep. 'The team was overloaded' is a symptom — the root cause could be 'unrealistic deadlines from unclear project brief'. The Problem Tree helps identify root causes that should be prioritized in follow-up actions. Pre-Mortems without this deepening often lead to countermeasures fighting symptoms without fixing causes.
View DetailsSCAMPER
SCAMPER is the creative counterpart to the Pre-Mortem. When the Pre-Mortem has shown which aspects of the plan are most at risk, SCAMPER helps generate alternatives. The seven SCAMPER questions — Substitute, Combine, Adapt, Modify, Put to other use, Eliminate, Reverse — force the team not to just accept the first solution for each risk point. 'How could we eliminate this risk?' is a different question from 'how could we mitigate this risk?'. The combination Pre-Mortem + SCAMPER produces plans that are more robust because the countermeasures were thought through more creatively.
View DetailsCAUTION
The most common Pre-Mortem trap: the collected risks aren't translated into concrete actions. A Pre-Mortem producing a list that then falls into oblivion is a waste. Rule: every top-5 risk gets an owner, a timeline, and a countermeasure. After six weeks it's checked whether the measures are working. Without this discipline the Pre-Mortem remains a ritual without effect.
Pre-Mortem, Fishbone, Problem Tree, and SCAMPER cover the full risk process. Pre-Mortem collects honest risks. Fishbone structures them. Problem Tree identifies root causes. SCAMPER generates alternative countermeasures. A good project setup uses all four — not in every detail, but in sequence. The investment is moderate — half a day for a substantial Pre-Mortem with follow-up. The benefit is enormous: projects that have gone through this sequence fail less often on the typical, predictable risks.
KEY TAKEAWAY
The question 'why did it fail?' is psychologically more productive before the start than the question 'what could go wrong?'. Pre-Mortem is the disciplined use of this asymmetry.
CONCLUSION
Pre-Mortems are among the most effective tools for risk-aware planning. They produce in two hours more honest risk insights than many formal risk workshops in a day. The reason is psychological: people are braver when talking about already-happened failures than when asked to prospectively voice criticism. Those who systematically deploy this method before important decisions — product launches, organizational changes, large investments — have a significantly higher success rate. Combined with Fishbone, Problem Tree, and SCAMPER, a risk management process emerges that's neither bureaucratic nor superficial but substantial and manageable.