The Organizational Pre-Mortem

In 1989, psychologist Deborah Mitchell and her colleagues published a study demonstrating that “prospective hindsight”: mentally projecting to a future state and then reasoning backward about how it came to be: increased the ability to identify reasons for a future outcome by approximately 30 percent compared to standard foresight analysis. Gary Klein, the cognitive psychologist who developed the pre-mortem technique, built on this research to create a structured method for applying prospective hindsight to organizational decisions: before a project begins, imagine it has already ended in failure, and ask the team to explain why.

The pre-mortem has been written about, taught in business schools, and endorsed by decision scientists for more than two decades. Most organizations have never conducted one.

This is not because the technique is difficult. It is not. It is because doing it well depends on organizational conditions that most teams have not built, and because the absence of those conditions means that what gets called a pre-mortem in most organizations is not actually one.

The Mechanism: Why Prospective Hindsight Works

Standard risk identification asks people to answer the question: what could go wrong? This framing triggers a well-documented cognitive bias, optimism bias, sometimes called planning fallacy, which causes people to systematically underestimate the probability and impact of negative future events in projects they are personally committed to. The bias is particularly strong in organizational contexts where expressing doubt about a project that leadership has endorsed can be read as disloyalty, negativity, or insufficient commitment.

The pre-mortem bypasses this bias through a simple reframing. It does not ask what could go wrong. It asserts that things have gone wrong, completely, visibly, and without ambiguity, and asks the team to explain how. The shift from possibility to fait accompli changes the cognitive task. The question is no longer “what might happen?” It is “what did happen?” And reasoning backward from an established failure is cognitively easier, and socially safer, than predicting negative outcomes about a project that the room is committed to delivering.

The social dynamic is equally important. When failure is stipulated as the starting condition, raising concerns is no longer a vote against the project. It is participation in a shared analytical exercise. The team member who has been privately worried about the third-party dependency, or the technical assumption in the architecture, or the timeline that assumes no regulatory delay: all of them now have permission to name what they know, in a format that the organization has explicitly sanctioned.

The pre-mortem does not create new knowledge. It releases knowledge that the team already had but had no safe way to express.

What a Real Pre-Mortem Looks Like

The mechanics of an effective pre-mortem are simple but specific. The session works as follows.

First, the facilitator states the stipulation: “It is eighteen months from now. This project has failed: significantly and visibly. Not a partial setback, but a genuine failure: missed objectives, missed timeline, leadership dissatisfied, outcomes not delivered. You are here to understand why.” The specificity of the failure matters. A vague negative outcome, “things didn't go as planned”, gives participants too much latitude to imagine minor setbacks. A vivid, unambiguous failure forces a more complete reckoning.

Second, each participant writes independently, in silence, for five to ten minutes: every reason they can identify for why the failure occurred. The independent writing step is not optional. Group brainstorming is dominated by whoever speaks first and loudest, and in an organizational context, that is usually the most senior person or the most confident one. The concerns of the quieter, more junior, or more skeptical participants do not survive the social dynamics of a group brainstorm. Independent writing captures what the group actually knows, not what the group is comfortable saying aloud.

Third, the facilitator collects the reasons, round-robin, one per participant per turn, until all unique concerns have been captured. This step is designed to prevent any single participant's frame from dominating the analysis. Each concern goes on the list without immediate discussion or evaluation. The evaluation comes later.

Fourth, the group reviews the collected concerns and identifies which are highest priority for risk response: most likely to occur, highest impact if they do, and least addressed by the current plan. These become the inputs to the risk register: not as items generated by a checklist or a brainstorm, but as items surfaced through prospective hindsight, which the research suggests will include concerns that no structured identification exercise would have caught.

The Organizational Conditions the Pre-Mortem Depends On

The mechanics are simple. What makes the pre-mortem rare, and what distinguishes organizations that get genuine insight from it from those that conduct a ritual that looks like one: is the organizational conditions it requires.

The first condition is psychological safety: the genuine belief, held by participants, that naming a concern about the project will not be held against them. This is the condition that most organizations most consistently overestimate. Leaders routinely believe their teams feel safe raising concerns when the teams do not. The pre-mortem creates a temporary structure that can help: the stipulated failure gives cover to concerns that would otherwise feel risky to name. But if the baseline organizational culture treats skepticism as disloyalty, participants will self-censor even in the pre-mortem format. They will raise concerns that are safe to raise, while keeping to themselves the concerns that matter most.

The second condition is independent generation before group discussion. This is the most commonly violated structural requirement. Many organizations conduct “pre-mortems” that are actually group discussions about potential failure: facilitated brainstorms where the first participant to speak sets the frame and the rest respond to it. This format captures the concerns of the most vocal participants and suppresses the concerns of everyone else. The research on prospective hindsight that motivates the pre-mortem technique specifically involves independent generation. Organizations that skip this step are not conducting pre-mortems. They are conducting facilitated discussions with a provocative framing.

The third condition is facilitation by someone without a stake in the project's success. The most invested person in the room is the last person who should lead the analysis of why the project failed. They will, consciously or not, steer the discussion toward concerns they already have plans to address and away from concerns that implicate their own assumptions or decisions. An effective pre-mortem requires a facilitator who is genuinely neutral: someone who can hear that the plan has a fundamental flaw without defending it.

The quality of a pre-mortem is determined almost entirely by the conditions in the room before it begins: not by the technique applied during it.

The Adaptability Connection

In the Four A's of Organizational Readiness™ framework, Adaptability is the condition that determines whether an organization can learn, from feedback, from experience, from changing conditions, faster than the environment changes around it. Most discussions of adaptability focus on learning from failure after it has occurred: the post-mortem, the after-action review, the lessons-learned session. These are valuable. They are also retrospective: they capture what the organization failed to prevent.

The pre-mortem is an adaptability tool that operates in the other direction: it uses prospective learning to surface, before the project begins, the knowledge that post-mortems typically reveal after it ends. It is the organizational equivalent of a vaccine: introducing a controlled exposure to failure in order to build the immune response before the real threat arrives.

Organizations that conduct pre-mortems consistently develop a specific capability over time: the ability to name failure modes in advance, before optimism bias and sunk cost have made the conversation difficult. They also develop a culture in which raising concerns early is treated as a form of organizational stewardship: a contribution to the project, not a challenge to it. This is the adaptive condition the pre-mortem builds: not just better risk identification on a single project, but a progressively more honest organizational conversation about the gap between what is planned and what is actually likely.

What Pre-Mortem Findings Reveal About the Organization

There is one more use of the pre-mortem that most organizations overlook: the pattern analysis. Over time, the concerns surfaced in pre-mortems across multiple projects reveal the recurring failure modes in the organization's approach to risk. If the same concerns appear in every pre-mortem: the same vendor dependency assumptions, the same schedule optimism, the same underestimated integration complexity: those are not individual project risks. They are systemic organizational conditions that the project-by-project risk management process cannot see and cannot fix.

The pre-mortem that reveals a recurring pattern is more valuable than the one that improves a single project. It points to the underlying conditions, in planning norms, in vendor management, in estimation practice, that are producing consistent risk exposure across the portfolio. Addressing those conditions is the builder's work: not managing risks project by project, but diagnosing and fixing the organizational architecture that keeps generating the same risks.

That is what turns pre-mortem practice from a risk tool into an adaptability tool. The question it eventually answers is not just “what could go wrong with this project?” It is “what does the pattern of what keeps going wrong tell us about the organization we have built?”