There is a particular kind of meeting that most people have sat through at least once, the post-mortem. A project has gone badly. People are tired, perhaps a little raw, and the group assembles to examine what went wrong. Insights emerge that are often sharp and accurate. The supply chain assumption that was always fragile. The stakeholder whose concerns were noted and then quietly set aside. The timeline that everyone privately knew was optimistic but no one said out loud. The post-mortem is valuable. It is also, inevitably, retrospective. The project has already failed. The insights arrive after the cost has been paid.
The pre-mortem runs the same exercise in the opposite direction. Before a project begins, or at an early enough stage that changes are still possible, you imagine the project has already failed and ask the question: how did this happen? What went wrong? The results can be surprisingly confronting, and that is exactly the point.
Contents
The Concept and Its Origins
The pre-mortem technique was developed by psychologist Gary Klein, who published it in a 1998 book called Sources of Power and brought it to a wider audience through a 2007 Harvard Business Review article. Klein had spent years studying how experts make decisions under pressure in high-stakes environments including firefighting, military command, and medical care. He was interested in the conditions that allowed experienced practitioners to recognize problems early, before they had become critical, and the pre-mortem was partly an attempt to systematize that capacity for ordinary teams and organizations.
The technique draws on a concept Klein called prospective hindsight, the idea that imagining a future event as though it has already happened improves your ability to identify the specific causes that would have led to it. Research by Deborah Mitchell and colleagues at the Wharton School found that prospective hindsight increased the ability to identify correct reasons for a future outcome by approximately thirty percent compared to standard foresight. Imagining failure as an accomplished fact, rather than a possibility to be hedged against, unlocks a different and more honest mode of analysis.
Why It Works When Standard Risk Assessment Does Not
Standard risk assessment asks people to identify what might go wrong. The pre-mortem asks people to explain what already went wrong. This sounds like a minor reframing, but the psychological difference is significant. When asked to identify risks in a plan they have helped develop and are emotionally invested in, most people experience a pull toward confirmation rather than critique. They think of the reasons the plan will succeed, or they identify mild risks that do not challenge the core assumptions. Genuine skepticism requires swimming against the current of group momentum, and most people in most organizations are reluctant to do that explicitly.
The pre-mortem dissolves this by changing the premise. You are no longer asked to criticize a plan that the group has endorsed. You are asked to explain a failure that has already, hypothetically, occurred. The permission to be negative is built into the exercise. No one is attacking the plan. Everyone is forensically examining wreckage. This framing tends to unlock concerns that would not have surfaced in a conventional risk discussion, including the concerns that team members have been quietly carrying but not voicing.
The Planning Fallacy and Why Teams Need This
The pre-mortem is also a direct response to the planning fallacy, the well-documented human tendency to underestimate the time, costs, and risks associated with future plans while overestimating the benefits. The planning fallacy operates at the individual level and becomes considerably more powerful at the group level, where social dynamics amplify optimism and suppress dissent. Teams that have worked hard to develop a plan are collectively invested in it, and that investment creates pressure toward optimism that individual members find difficult to resist without a structured occasion to do so.
The pre-mortem creates that occasion. By making the failure vivid and concrete rather than abstract and hypothetical, it short-circuits the optimism bias long enough to surface the concerns that the planning process had been generating in people’s heads without routing them into the room.
How to Run One
The mechanics are simple enough to apply in any team setting with minimal preparation. At the outset of a project, or at a significant planning milestone, gather the relevant team members and begin with a specific instruction: assume that it is now a year from now, and the project has failed. Not merely underperformed, but failed clearly and significantly. Take a few minutes and write down, individually, all the reasons you can think of for why it failed.
The individual writing step is important. It prevents the group dynamics of a live discussion from narrowing the range of concerns that surface. People write down what they actually think rather than what they feel comfortable saying in front of the group. Once everyone has written their lists, go around the room and collect one item from each person, working through the lists until all the distinct concerns are on the table.
The output is a map of the project’s failure modes as seen by the people most familiar with it. Some of these will be familiar risks that are already in the project plan. Others will be concerns that had not been formally articulated. A few will be genuine blind spots, assumptions so deeply embedded in the project’s design that they had not previously been recognized as assumptions at all. Those last ones are the most valuable findings the pre-mortem produces.
What to Do with the Results
The pre-mortem is a diagnostic tool, not a decision-making framework. Its output is a set of concerns that the project team now has a shared, explicit understanding of. What to do with those concerns is a separate conversation, but it is one that is considerably more productive for having the explicit map rather than the unspoken collection of private worries.
Some concerns will be addressable with specific planning changes. Others will be structural risks that cannot be eliminated but can be monitored. A few may be serious enough to prompt a reconsideration of the project’s scope, timeline, or fundamental premises. That reconsideration, if it is warranted, is far less costly before the project has started than after it has run for several months in the wrong direction.
The post-mortem will always have a place. Some lessons genuinely can only be learned from what actually happened. But the pre-mortem offers the rare opportunity to learn from a failure that has not occurred yet, which is a form of institutional intelligence that most organizations underuse and almost all of them could benefit from building.