A business launch can fail long before the first customer complains. A career move can become difficult months after the excitement of accepting an offer has faded. A project can exceed its budget even though everyone approved the original plan.
The warning signs often existed before the decision was made. They were simply never discussed, tested, or translated into practical safeguards.
A pre-mortem analysis template changes the conversation. Instead of asking whether a plan looks convincing today, it asks you to imagine that the plan has already failed—and work backward to discover why.
The goal is not to become pessimistic. It is to find weaknesses while you can still do something about them.
Free Pre-Mortem Analysis Template and Decision Risk Planner
Use the interactive planner below to examine a decision before committing to it. Describe your goal, identify plausible failure causes, assess their relative priority, and create a practical response plan.
The tool supports multiple failure scenarios, likelihood and impact ratings, confidence assessments, early warning signals, preventive actions, contingency plans, and a printable report.
Pre-Mortem Decision Planner
Imagine your decision failed. Identify what went wrong, prioritize the risks, and plan your response before committing.
1. Define the Decision
Describe the choice you are evaluating. Avoid entering sensitive personal or confidential information.
2. Imagine the Failure
Assume the decision has failed at the selected time horizon. Add plausible causes, not just vague fears. Scores are subjective planning aids, not predicted probabilities.
3. Decision Safeguards
4. Analyze and Export
Risk priority = likelihood (1–5) × impact (1–5). Confidence describes how reliable you believe your assessment is; it does not change the risk score.
Your results reflect the information and judgments you enter. The tool does not predict whether your decision will succeed, and its risk scores are not statistical probabilities.
For a useful first assessment, begin with at least three distinct failure scenarios rather than evaluating only the most obvious concern.
What Is a Pre-Mortem Analysis?
A pre-mortem analysis is a structured decision-making exercise in which you imagine that a proposed plan has already failed, identify plausible causes, and develop safeguards before implementation.
Unlike a post-mortem, which examines an outcome after the event, a pre-mortem takes place while there is still time to change the plan.
The method is associated with psychologist and decision researcher Gary Klein, who described its application to project planning in Harvard Business Review in 2007.
Its defining question is not simply, “What could go wrong?”
Instead, the exercise begins with a hypothetical statement:
“It is one year from now. We implemented this decision, and it failed. What happened?”
That change in perspective encourages a more concrete examination of assumptions, operational weaknesses, neglected stakeholders, and unintended consequences.
A pre-mortem does not require a large team or specialized software. It can be performed individually, although involving people with different knowledge and perspectives may reveal risks that one person would miss.
Pre-Mortem vs. Post-Mortem vs. Traditional Risk Assessment
These methods are related, but they answer different questions.
| Method | When to use it | Central question | Primary output |
|---|---|---|---|
| Pre-mortem | Before commitment | Why did our imagined plan fail? | Failure scenarios and safeguards |
| Post-mortem | After an outcome | What actually happened and why? | Lessons and corrective actions |
| Traditional risk assessment | Before and during implementation | What risks exist and how should we manage them? | Risk inventory and response priorities |
| Decision matrix | When comparing alternatives | Which option best fits our criteria? | Comparative option scores |
A pre-mortem complements these methods rather than replacing them.
For example, a weighted decision matrix might indicate that launching a new service is preferable to expanding an existing one. A pre-mortem can then reveal the assumptions that must hold for the preferred option to succeed.
The first method helps compare choices. The second challenges the plan behind a choice.
How to Use the Pre-Mortem Decision Planner
The Summase.org planner organizes the exercise into four stages: defining the decision, imagining failure, designing safeguards, and analyzing the results.
Step 1: Define the Decision and Success Criteria
Start with a specific decision.
“Improve my business” is too broad.
“Launch a monthly website maintenance service for ten existing clients within six months” provides a clearer basis for analysis.
Enter the decision or project name, then describe what success would look like.
A useful success criterion should be observable. It may involve a deadline, a completed deliverable, a customer outcome, or another measurable condition.
For example:
- Decision: Launch a website maintenance service.
- Success target: Acquire ten paying clients within six months.
- Alternative: Test the service with three existing customers first.
- Decision deadline: End of the current planning month.
- Reversibility: Partly reversible.
- Failure horizon: Twelve months.
Reversibility matters because not every failed decision has the same consequences.
An inexpensive experiment may be easy to discontinue. A long-term contract, major relocation, or substantial capital commitment may be much harder to reverse.
The planner asks you to consider this distinction before analyzing the failure scenarios.
Step 2: Imagine the Decision Has Failed
Select a future time horizon and assume the outcome was disappointing.
Then identify plausible reasons.
For the website maintenance service example, potential causes might include:
- Existing customers do not perceive enough value in the monthly fee.
- Support requests require substantially more time than expected.
- The service depends on one person who becomes unavailable.
- Customer acquisition costs exceed the available budget.
- Service expectations are not clearly defined in the agreement.
These are more useful than vague statements such as “the business might fail” or “something unexpected could happen.”
Each scenario should describe a specific mechanism of failure.
If you cannot explain how the failure might occur, the scenario may be too broad to guide preventive action.
Step 3: Assess Likelihood, Impact, and Confidence
For each failure cause, the planner asks you to assign three judgments.
Likelihood describes how plausible you believe the scenario is.
Impact describes how serious the consequences would be if it occurred.
Assessment confidence describes the quality of the evidence supporting your judgment.
The planner uses five-point likelihood and impact scales.
| Rating | Likelihood | Impact |
|---|---|---|
| 1 | Very unlikely | Minor |
| 2 | Unlikely | Limited |
| 3 | Possible | Moderate |
| 4 | Likely | Major |
| 5 | Very likely | Severe |
The displayed priority score is calculated as:
Risk priority = Likelihood × Impact
A scenario rated 4 for likelihood and 5 for impact receives a score of 20 out of 25.
This does not mean there is an 80% probability of failure.
The numbers are ordinal planning ratings, not calibrated probabilities. Multiplying them creates a convenient sorting convention, but the numerical differences should not be interpreted as precise measures of expected loss.
The tool classifies scores into the following planning bands:
| Score | Priority |
|---|---|
| 1–7 | Lower |
| 8–14 | Moderate |
| 15–25 | High |
These bands are conventions used by this planner, not universal or independently validated risk thresholds.
A low-likelihood scenario with catastrophic consequences may still require urgent attention even if its calculated score falls below another risk.
Never use the score as a substitute for judgment about severity, reversibility, or unacceptable consequences.
Step 4: Record Early Warning Signals
A useful risk assessment identifies what you could observe before a problem becomes serious.
For example, “customers may reject the service” is a failure scenario.
An early warning signal might be:
“Fewer than two of the first ten qualified prospects agree to a paid pilot.”
The second statement is more actionable because it identifies something that can be monitored.
Other warning signals may include:
- Repeated missed milestones.
- Unresolved customer complaints.
- Increasing support hours per client.
- Dependencies that remain unconfirmed.
- Rising costs without corresponding progress.
- Critical assumptions that fail during testing.
Choose signals that are relevant to your decision and can realistically be observed.
Avoid creating a monitoring system so complicated that maintaining it becomes another major project.
Step 5: Define Preventive Actions and Contingencies
A warning without a response plan has limited practical value.
For every significant risk, distinguish between two kinds of action.
Preventive action: What can you do now to reduce the likelihood or consequences of the problem?
Contingency action: What will you do if the problem occurs despite your preparation?
For example:
- Failure cause: Monthly support requests become unmanageable.
- Prevention: Define service limits, document recurring tasks, and test actual support demand.
- Early warning: Average support hours per client exceed the planned allowance.
- Contingency: Reassess pricing, adjust service scope through agreed terms, or stop accepting new clients until capacity is restored.
The contingency is not a prediction. It is a prepared response that can reduce confusion if the situation develops.
The planner also includes a field for a review date or responsible person. Use it to make sure the safeguard does not remain an unassigned intention.
Step 6: Check Critical Assumptions
Some risks are symptoms of a deeper problem: the entire decision depends on an assumption that has never been tested.
For a new service, the assumption might be that customers are willing to pay for ongoing support.
For a career move, it might be that the new role offers the responsibilities described during recruitment.
For a software migration, it might be that important data can be transferred without disrupting operations.
Write down the assumptions that would materially change your decision if proven false.
Then identify the least costly credible way to test them.
This is often where a pre-mortem becomes most valuable. Rather than trying to eliminate every possible risk, you discover which uncertainties deserve verification before commitment.
Step 7: Generate and Review the Risk Report
After entering your scenarios, click Generate Risk Report.
The planner organizes the documented failure causes by their calculated priority scores and summarizes the information you provided.
Review the results carefully.
Ask whether the highest-priority scenarios have credible preventive actions, whether the warning signals are observable, and whether important assumptions remain untested.
You can also use Save in This Browser to retain your current entries locally and Restore Saved Work to retrieve them later on the same browser.
The Print / Save PDF function produces a separate decision report for printing or saving as a PDF.
Because the tool works with your own assessments, the report should be treated as a working decision document rather than an independent expert evaluation.
Worked Example: A Small Business Launch That Looks Safer Than It Is
Consider a freelance website developer who wants to introduce a recurring maintenance subscription.
The business case initially looks attractive. Existing clients already trust the developer, recurring revenue could make income more predictable, and the technical work appears familiar.
The plan is to launch within one month.
Before committing, the developer performs a pre-mortem using a twelve-month failure horizon.
The imagined outcome is straightforward: the service launched, but it became financially and operationally unsustainable.
The following example is illustrative. Its scores and scenarios are hypothetical, not observed business data.
| Failure scenario | Likelihood | Impact | Score |
|---|---|---|---|
| Customers reject the subscription price | 4 | 4 | 16 |
| Support demand exceeds available capacity | 4 | 5 | 20 |
| Client responsibilities are poorly defined | 3 | 4 | 12 |
| Critical work depends on one person | 3 | 5 | 15 |
The highest numerical priority is support demand.
But the analysis also reveals a structural problem: the service has not been tested under realistic conditions.
What Changes After the Pre-Mortem?
Instead of immediately offering unlimited support to every customer, the developer decides to:
- Run a small paid pilot with three customers.
- Record the time required for each recurring task.
- Define response times and service exclusions.
- Establish an escalation process for unexpected technical problems.
- Review the pilot before expanding.
The pre-mortem has not proved the business will succeed.
It has changed the initial commitment from a broad launch to a controlled experiment.
That distinction matters.
The best result of a pre-mortem is often a better-designed decision, not a higher confidence score.
When the Highest Score Is Not the First Priority
Suppose the same project includes a lower-likelihood scenario involving accidental loss of client data.
Even if its numerical score is lower than the support-capacity risk, its consequences could be unacceptable.
The developer should therefore examine backup verification, access permissions, recovery procedures, and contractual responsibilities independently of the ranking.
This illustrates a limitation of simple risk matrices: a single score cannot represent every important dimension of risk.
Five Questions That Improve a Pre-Mortem
When the first round of failure scenarios feels predictable, use these questions to challenge the analysis.
1. What Would Someone Outside the Project Notice?
People who designed a plan may overlook assumptions they have become accustomed to accepting.
A customer, colleague, contractor, or experienced outsider may recognize dependencies that the project owner considers normal.
Ask for concrete concerns rather than general approval.
2. What Happens If the Timeline Doubles?
A plan that works only when every milestone is completed on schedule may be fragile.
Examine what happens if approvals are delayed, suppliers become unavailable, or unexpected work consumes the available capacity.
The purpose is not to assume delays are inevitable. It is to identify which delays would make the original plan unworkable.
3. Which Assumption Has the Weakest Evidence?
Not every unknown deserves equal attention.
Focus on assumptions that are both uncertain and consequential.
If customer demand is unverified, refining a website design may be less valuable than testing whether customers will pay.
4. What Would Make Us Stop?
Define a reconsideration trigger before emotional and financial commitment increases.
A trigger might involve repeated missed milestones, an unacceptable operational risk, or evidence that a core assumption is false.
A trigger does not have to require automatic cancellation. It can initiate a structured review.
5. What Is the Smallest Useful Test?
Some decisions can be partially tested before a full commitment.
Examples include a limited pilot, a temporary workflow, a prototype, a short trial, or a small-scale operational test.
The test should produce information that could genuinely change the decision.
A test designed only to confirm what you already believe offers little protection against poor assumptions.
When a Pre-Mortem Is Worth the Effort
Not every decision requires a formal analysis.
Choosing a different note-taking application rarely warrants a detailed failure register.
A pre-mortem becomes more useful when a decision has meaningful consequences, important dependencies, or uncertainty that cannot be resolved by a quick comparison.
| Decision | Useful pre-mortem focus |
|---|---|
| Launching a business service | Demand, pricing, capacity, delivery obligations |
| Changing careers | Role expectations, transferable skills, transition constraints |
| Migrating business software | Data integrity, downtime, training, rollback |
| Hiring a contractor | Scope, deliverables, communication, accountability |
| Starting a long-term project | Resources, dependencies, changing requirements |
| Entering a partnership | Responsibilities, incentives, decision rights, exit conditions |
For significant financial, legal, medical, or safety-critical decisions, this planner can help organize questions, but it should not replace qualified professional assessment.
A subjective risk score is particularly unsuitable as the sole basis for decisions involving personal safety, regulatory compliance, or substantial financial exposure.
Common Mistakes That Make a Pre-Mortem Less Useful
Treating Every Concern as Equally Important
A list of twenty risks without priorities may create more confusion than clarity.
Distinguish between minor inconveniences, manageable operational problems, and threats that could fundamentally change the decision.
Use the score as an initial sorting tool, then examine consequences that require special attention.
Writing Failure Causes That Cannot Be Tested
“Everything goes wrong” does not identify a mechanism.
“Three critical suppliers miss delivery deadlines” provides a more useful basis for prevention and monitoring.
The more specific the failure mechanism, the easier it becomes to develop an appropriate safeguard.
Confusing Confidence With Likelihood
You may believe a scenario is likely while having very little evidence to support that judgment.
That is why the planner asks for confidence separately.
A high-priority risk supported mostly by assumptions may justify further investigation before a major commitment.
Listing Safeguards Without Owners or Review Dates
“Improve communication” sounds reasonable but gives no one a clear responsibility.
A stronger action identifies what will change, who will check it, and when the result will be reviewed.
For personal decisions, the owner may simply be you.
Using the Exercise to Justify a Decision Already Made
A pre-mortem loses value when the participant dismisses every scenario that challenges a preferred outcome.
Try generating failure causes before defending the plan.
If working with a team, consider asking participants to write their concerns independently before group discussion.
Assuming More Analysis Always Produces Better Decisions
A pre-mortem can become counterproductive if it encourages endless speculation.
Set a reasonable time limit, identify the most consequential unresolved risks, and determine which questions require further evidence.
The purpose is to support a decision—not postpone it indefinitely.
A Practical Decision Readiness Checklist
Use this checklist after generating your report.
Check each item after you have verified it for the decision you are evaluating. Your progress updates as you go.
This is a readiness checklist, not a certification of safety or success. Even when every item is checked, your decision may remain uncertain. Checkbox progress is not saved after you leave or reload this page.
A decision may remain uncertain even when every item is complete. What matters is whether the analysis has exposed weaknesses that can be addressed before the commitment becomes difficult to change.
How Pre-Mortem Analysis Fits Into a Broader Decision System
A pre-mortem is most useful when it becomes part of a repeatable decision process.
Before selecting an option, you need to understand the actual problem, available alternatives, and relevant trade-offs.
The Summase.org guide to decision-making frameworks for high-stakes life choices explores how to structure that earlier stage of the process.
Once you have a preferred plan, the pre-mortem challenges its assumptions and prepares responses to potential failure.
After implementation, the next task is monitoring what happens and updating the plan when new evidence appears.
This process fits naturally into a personal operating system that connects decision-making, execution, and periodic review.
You can also explore the broader Life Strategy, Systems Thinking & Long-Term Decisions hub for related approaches to risk awareness, systems thinking, and long-term planning.
The key is to keep the process proportional to the decision.
A small, reversible experiment may need only a few minutes of analysis. A complicated commitment involving multiple stakeholders may require independent assessments, documented safeguards, and professional review.
What Research Supports—and What It Does Not
The pre-mortem method is associated with Gary Klein's work on prospective hindsight.
In his 2007 Harvard Business Review article, Performing a Project Premortem, Klein described how asking people to imagine a completed failure can help surface concerns that might otherwise remain unspoken.
The Public Health Foundation has also published guidance on using pre-mortem analysis to examine significant organizational projects with defined objectives, timelines, and potential consequences.
These references support the method as a structured planning exercise. They do not establish that every pre-mortem prevents failure, that every risk score is accurate, or that this particular online planner has been scientifically validated.
The Summase.org tool is an implementation of the general planning approach, with additional fields for prioritization, confidence, early warning signals, and contingency actions.
Its scoring bands are practical design choices rather than clinical, financial, or engineering standards.
Reference reading:
- Gary Klein, Performing a Project Premortem, Harvard Business Review, 2007.
- Public Health Foundation, Pre-Mortem Analysis, quality improvement resource.
Frequently Asked Questions
Can I use a pre-mortem template for personal decisions?
Yes. A pre-mortem can help evaluate a career change, relocation, educational commitment, or other important choice. Define the decision, imagine a disappointing outcome, and identify plausible causes. Use the results to test assumptions and prepare safeguards rather than treating the exercise as a prediction.
Is a pre-mortem the same as a SWOT analysis?
No. SWOT organizes strengths, weaknesses, opportunities, and threats around a situation or organization. A pre-mortem starts with an imagined failure of a specific plan and investigates how that failure occurred. The methods can complement each other, but their starting questions and outputs differ.
How many failure scenarios should I include?
Start with three to five distinct scenarios covering different failure mechanisms. Add more when the decision involves important dependencies or consequences. Quality matters more than quantity: each scenario should identify a plausible cause, an observable warning signal, and a possible response.
Can I save my pre-mortem analysis as a PDF?
Yes. After generating the report, use the planner's Print / Save PDF button and select your browser's PDF destination. You can also save form entries locally in the same browser. Avoid entering sensitive information on shared devices, especially when saving or printing reports.
Make the Next Decision Easier to Defend
A strong plan is not one that assumes everything will go right. It is one that recognizes where reality could challenge the assumptions behind it.
A pre-mortem analysis template gives you a practical way to examine those assumptions before you commit.
Start with one decision that matters. Identify three credible failure causes, document their warning signs, and choose one assumption you can verify before moving forward.
Then use the free planner above to create a report you can revisit when circumstances change.
You do not need certainty to make a thoughtful decision. You need a clear understanding of what remains uncertain—and a credible plan for responding when new evidence arrives.
