A startup pre-mortem is a structured exercise in which a team assumes that a future outcome was unsuccessful or disappointing and works backward to identify what could have caused it. The purpose is not to predict failure, but to surface fragile assumptions and risks before their consequences occur.
Startups naturally spend a great deal of time thinking about how things will work. Founders create plans, define milestones, forecast growth, develop products, raise capital, and organize teams around an expected future.
A startup pre-mortem temporarily reverses that perspective.
Instead of asking what needs to happen for the plan to succeed, the team imagines that it has reached a future point and the expected outcome did not happen. The product failed to gain adoption. The expansion underperformed. The fundraising round did not close. The company missed its growth targets. The project took significantly longer than expected.
The team then asks:
“What happened?”
By working backward from an imagined disappointing outcome, founders can identify assumptions, dependencies, and risks that may be difficult to discuss while everyone is focused on making the current plan work.
A Pre-Mortem Is Not a Prediction of Failure
The purpose of a pre-mortem is not to determine exactly how the startup will fail. Startups are too uncertain and too dynamic for that level of prediction.
Nor is the exercise intended to make founders pessimistic.
The assumption that the future outcome was unsuccessful is temporary. It creates a different perspective from which the team can examine the plan.
Instead of asking:
“Do we think this will work?”
the team asks:
“If this did not work, what would probably have caused it?”
That small change can produce very different answers.
When people evaluate a plan they already support, they naturally focus on execution. When they temporarily assume that the plan failed, they have permission to search for weaknesses in the underlying assumptions.
Pre-Mortems Surface Fragile Assumptions
Every startup plan depends on assumptions.
A growth plan may assume that customer acquisition costs remain relatively stable. A hiring plan may assume that revenue develops according to forecast. A product launch may assume that customers behave as expected. An international expansion may assume that what worked in one market transfers to another.
These assumptions can remain hidden inside the plan because the team is discussing what it intends to do rather than what must be true for the plan to work.
A startup pre-mortem brings those assumptions into the conversation.
For example, imagine a startup planning an aggressive expansion. The team assumes it is twelve months later and the expansion significantly underperformed. Working backward, possible explanations might include:
- Customer demand was weaker than expected.
- Acquisition costs increased significantly.
- The product required more localization than anticipated.
- Hiring took longer than planned.
- Operational complexity increased faster than the team could manage.
- Existing customers received less attention.
- Burn increased before the new market produced meaningful revenue.
The objective is not to declare that these things will happen. It is to identify which possibilities would materially affect the company and which assumptions deserve additional validation.
Pre-Mortems Make Risk Easier to Discuss
Risk discussions inside startups can be surprisingly difficult.
A founder questioning an ambitious growth plan may appear less committed. An employee raising concerns about a launch may feel that they are being negative. A team member who repeatedly challenges assumptions may worry about becoming the person who always says no.
Momentum can create social pressure to support the plan.
The pre-mortem changes the context of the conversation. Everyone is explicitly asked to identify what could go wrong.
Concerns that might otherwise remain private become legitimate inputs to the exercise.
This is one reason the pre-mortem is important within Juan Damia’s De-Risking Startups Framework™. It creates a structured moment in which discussing risk is part of doing the work rather than an argument against moving forward.
It Helps Counter Optimism Bias
Startups require optimism. Founders pursue opportunities precisely because they believe they can create an outcome that does not yet exist.
But optimism can become dangerous when it protects assumptions from scrutiny.
Teams can interpret evidence in ways that support the existing plan, underestimate execution difficulty, assume positive trends will continue, or discount uncomfortable possibilities because they conflict with the desired outcome.
A pre-mortem does not attempt to eliminate optimism. It introduces a temporary counterweight.
By assuming the plan has already produced a disappointing result, the team can examine possibilities that may otherwise receive too little attention.
The question changes from defending the plan to explaining the imagined outcome.
A Pre-Mortem Moves Learning Forward
The most important value of a startup pre-mortem is temporal.
Imagine a company preparing to launch a new product. Six months after launch, it might discover that customers do not use an important feature, onboarding creates excessive friction, or the product is too expensive to support economically.
At that point, the company has real evidence—but it has also spent six months learning it.
A pre-mortem asks whether some of those potential problems can be surfaced before the commitment is made.
If the team identifies onboarding as a fragile assumption, it can test onboarding earlier. If customer willingness to pay appears critical, pricing can be validated before scaling. If the economics depend on an uncertain support requirement, the company can test that assumption with a smaller group of customers.
The pre-mortem does not provide the answer.
It identifies where the startup should look for evidence before consequences harden.
From Possible Failure to Action
A useful startup pre-mortem should not end with a long list of everything that could possibly go wrong. That would create anxiety rather than better decisions.
The team needs to prioritize.
For each meaningful risk, founders can ask:
- How consequential would this be?
- What assumption is behind it?
- Is there already evidence that the risk may be emerging?
- Can we validate the assumption before making a larger commitment?
- Is there an early warning signal we should monitor?
- Can we reduce the exposure now?
- What options would remain if this actually happened?
Some risks will justify immediate action. Others may require an experiment, a contingency, or simply continued monitoring.
The purpose is not to prevent every possible negative outcome. It is to bring important risks into the decision-making system while the startup can still respond proportionally.
Pre-Mortems Preserve Optionality
This connects the startup pre-mortem directly to another principle of the De-Risking Startups Framework™: optionality.
A risk identified before a decision is made usually leaves more alternatives available. A risk discovered after capital has been spent, employees have been hired, technology has been built, or customer commitments have been made leaves fewer.
The pre-mortem deliberately moves the risk conversation earlier.
It asks founders to confront potential failure while those risks are still hypothetical rather than waiting until they become operational, financial, or existential.
That timing is what gives the exercise its value.
Invite Risk Into the Room Early
Rocketbeet incorporates the logic of Juan Damia’s De-Risking Startups Framework™ around a broader principle: startup risk should be surfaced before the consequences make it impossible to ignore.
A pre-mortem is one mechanism for doing exactly that. It gives founders and teams permission to challenge assumptions, surface private concerns, identify dependencies, and decide which uncertainties deserve attention before making larger commitments.
The goal is not to predict failure.
It is to make potential failure useful before it happens.
A startup pre-mortem moves the discovery of risk forward in time, when the company still has more options to do something about it.