Pre-mortems: Identify Risks When Building Your MVP

A pre-mortem is a structured planning technique that helps product and project teams surface the most likely failure points in an MVP before development begi…

Topic: Decision Making & Analysis

Why It Matters

When a product launch fails, the post-mortem almost always surfaces the same uncomfortable truth: the failure was visible in advance, at least to someone on the team. The customer problem was narrower than assumed. The technical dependency was underestimated. The competitor had already announced a similar feature. Someone knew. Fewer people said anything. And almost no one asked.

The pre-mortem is a structured technique that addresses exactly this dynamic. Rather than waiting for failure to generate its own lessons, it asks teams to simulate failure in advance, while there is still time to act. Used well, it changes the quality of the conversation that precedes an MVP launch in ways that few other planning tools can match.

Consider whether any of these situations feel familiar. Has your team shipped something that failed in a way someone privately suspected it might, but never raised? Do planning sessions tend to reach consensus quickly, with dissenting views emerging only once work is already underway? Do post-launch reviews consistently surface risks that were technically visible before the build began? If any of these resonate, a pre-mortem is worth understanding in depth.

Origin and Underlying Logic

The pre-mortem was developed by research psychologist Gary Klein, whose work on naturalistic decision-making explored how experienced practitioners identify and respond to risk in high-stakes environments. Klein observed that most planning processes are optimised for commitment: teams build momentum around a plan, and the social dynamics of group settings make it progressively harder for individuals to raise doubts. The pre-mortem was designed as a structural antidote to that pressure.

The technique draws on a principle called prospective hindsight. Research in cognitive psychology shows that imagining a specific outcome as though it has already occurred significantly improves the accuracy of causal reasoning. In practice, this means asking "what went wrong?" is more productive than asking "what might go wrong?" The shift from hypothetical to assumed failure changes how people engage with the question, and what they are willing to say aloud.

The pre-mortem sits within a broader family of anticipatory risk tools. It shares some characteristics with scenario planning and red teaming, though it is faster and less resource-intensive than either. It also complements formal risk registers, but serves a different function: where a risk register catalogues and tracks known risks, a pre-mortem is designed to surface the risks a team has not yet named.

Structure and Application

A pre-mortem session follows a consistent sequence. The facilitator opens by framing a specific scenario: the project has launched, and it has failed. Not partially underperformed. Failed. Participants are then given five to ten minutes to write down, independently and in silence, the reasons they believe led to that outcome. This individual reflection phase is critical: it protects minority views from being anchored by the first voice in the room.

Once individual lists are compiled, the group shares and works through them. The facilitator clusters themes, identifies the risks that appear most frequently or generate the strongest response, and helps the group prioritise which concerns are most urgent and most addressable before launch. The session typically closes with a small number of agreed actions tied to the highest-priority risks. The tool itself takes the form of a facilitated group session, and can be run equally well on a physical whiteboard with sticky notes, or in a shared digital document for distributed teams.

Before reading further, try this: in your next planning session, before reviewing the project plan, ask your team one question. "If this MVP were to fail in six months, what would be the single most likely reason?" Note which answers come quickly and which take longer. Note also what is not said, and by whom. That question, and the silence around it, will tell you more about your risk exposure than the plan itself. What it will not tell you is how to act on what you learn. That is where the premium content begins.

FAQ

The following questions address what managers most commonly ask when encountering a pre-mortem for the first time.

Q: What is a pre-mortem?
A: A pre-mortem is a planning technique in which a team imagines a project has already failed and identifies the most likely reasons why. Developed by research psychologist Gary Klein, it applies the principle of prospective hindsight: imagining a specific failure scenario produces more accurate and candid risk identification than asking what might go wrong in the abstract.

Q: How is a pre-mortem different from a post-mortem?
A: A post-mortem is conducted after a project concludes and examines what went wrong. A pre-mortem runs the same analysis in advance. The practical difference is timing: risks identified in a pre-mortem can be acted on, while risks identified in a post-mortem can only inform the next project. Both have value, but the pre-mortem is the more preventive of the two.

Q: How do I know if a pre-mortem is right for my situation?
A: A pre-mortem is most valuable when a team is about to commit meaningful resources to an initiative with genuine uncertainty. It is particularly useful when stakeholders may be privately doubtful but reluctant to say so openly, or when past projects have consistently produced "we knew that" observations in retrospect. For low-stakes or highly reversible initiatives, a lighter risk review may be more proportionate.

Q: How long does a pre-mortem session take?
A: For an MVP-scale initiative, a focused pre-mortem typically runs 60 to 90 minutes. Larger or more complex initiatives may require additional time or a follow-up session. The session requires a skilled facilitator, a clearly framed failure scenario, and protected time for individual reflection before group discussion begins. Compressing the individual phase significantly reduces output quality.

Q: Can a pre-mortem work with a small team or a solo founder?
A: A pre-mortem works best with four or more participants, where diversity of perspective adds genuine value. With smaller teams, the facilitator needs to be deliberate about creating space for every voice. The technique can be adapted for solo use by working through the failure scenario in writing, but it loses its most distinctive strength: surfacing risks that are visible to some team members but invisible to others.