premortem concept in black and hot pink editorial style, Amelia S. Gagne
Psychology • Updated • 15 min read

The Premortem: Assume the Project Failed, Then Work Backward

A premortem assumes a project has already failed, then asks why. Imagining the failure as settled raises a team's ability to correctly identify reasons for a future outcome by about 30 percent (Mitchell, Russo, and Pennington, Journal of Behavioral Decision Making).

A premortem is a short meeting in which a team assumes its project has already failed and works out why, before any money is spent.

Imagining that a project has already failed raises a team's ability to correctly identify the reasons for a future outcome by about 30 percent, according to research by Deborah Mitchell, Jay Russo, and Nancy Pennington published in the Journal of Behavioral Decision Making. That single finding is the whole case for the premortem: a short, calm ritual you run before a launch, in which the team assumes the plan has died and then explains, out loud, exactly what killed it.

Pink sticky notes clustered on a dark wall beneath one glowing pink bulb, each a reason a premortem says the project failed
A premortem flips the usual risk meeting: the project has already failed, and the team's only job is to say why.

I study behavioral psychology because the most expensive mistakes rarely come from a lack of intelligence. They come from a lack of the right question at the right moment. The premortem is one of the cleanest examples I have found of a question that changes what a group can see.

The short version: a premortem is a thirty-minute meeting held before a big decision, in which everyone assumes the project has already failed and writes down why.

  • Pin the failure to a date and an outcome people would notice.
  • Write causes silently first, then share them one at a time.
  • Rank by likelihood and damage, and keep the top three or four.
  • Give each one an owner, a date and a tripwire you can observe.
  • Nobody defends the plan until the premortem list is finished.

What a premortem actually is

The technique was named and described by research psychologist Gary Klein in his 2007 Harvard Business Review article, "Performing a Project Premortem." A postmortem, in medicine, gathers people after a death to learn what went wrong. Everyone benefits except the patient. A premortem simply moves that same conversation to before the launch, while the patient can still be saved.

Here is the exact move. You gather the people who will do the work. You tell them to imagine it is some months from now and the project has failed completely, not partially, not "mixed results," but a clear, visible failure. Then each person writes down every reason they can think of for why it died.

The grammar is the mechanism. A normal risk meeting asks "what could go wrong?" A premortem asserts that it has already gone wrong and asks "what happened?" The first question invites a shrug. The second one invites a story, and people are very good at telling stories about events they treat as real.

What is premortem thinking?

Premortem thinking is the habit behind the premortem meeting: before you commit to something, you picture the version of the future where it went badly and ask what led there. You can run a premortem alone in five minutes before signing a contract, or with a team before a launch. The question is always the same. It is six months from now, this failed, so what happened?

A solo premortem works for the same reason a group premortem does. Treating the failure as settled turns a vague worry into a specific story with causes, and specific causes are things you can check. A business owner running a quick premortem on a new software vendor might write: "We switched, the data import lost three years of customer notes, and nobody found out until a client called." That one sentence produces three concrete questions for the vendor before anyone signs.

Premortem vs postmortem: what is the difference?

A postmortem happens after a failure and asks what went wrong. A premortem happens before the work starts and asks what will have gone wrong. A premortem and a postmortem are both honest reviews of causes. The difference is timing, and timing decides what you can do with the answers. A postmortem produces lessons for the next project. A premortem produces changes to this one.

Most teams that run postmortems well can run a premortem with almost no extra training, because the skills are the same: blameless language, specific causes and a short list of actions. Running a premortem and a postmortem on the same project is a good check on yourself. If the postmortem names a cause the premortem missed, that gap tells you which kinds of risk your team tends not to see.

Why imagining failure beats brainstorming risk

This is where the 30 percent comes from. Mitchell, Russo, and Pennington called the effect prospective hindsight: you project yourself into a future where the outcome is settled, then look backward to explain it. Their work found that certainty of outcome, not merely the passage of time, produced longer and more concrete causal explanations. People stop hedging and start diagnosing.

Daniel Kahneman found the method useful enough to feature in Thinking, Fast and Slow, framing it as a rare, practical antidote to the overconfidence that sets in once a group has committed to a plan. Once a team has decided, dissent feels disloyal. The premortem legitimizes doubt by assigning it as the task.

There is a social benefit that matters more in small teams than large ones. In a company of two or three, the person raising a concern is often the same person who has to build the thing. Framing failure as a shared assumption lets them flag a weakness without it reading as reluctance. This is the same reason I keep coming back to how much of technology work is really consumer and human behavior wearing an engineering costume.

The bias a premortem is built to defeat

The failure it targets is optimism bias, and the pattern is well documented at scale. Bent Flyvbjerg's research on large projects, summarized by McKinsey, found that nine out of ten megaprojects run over budget, with overruns of 50 percent common, a pattern so durable he named it the Iron Law of Megaprojects.

Small businesses are not building bridges, but the mechanism is identical. Once you have chosen a plan, your mind quietly recruits evidence that it will work and discounts evidence that it will not. You estimate the best case and call it the plan. The premortem forces the opposite motion for thirty minutes.

Flyvbjerg's proposed remedy for large projects is reference class forecasting: instead of estimating from your own optimistic bottom-up view, you base the forecast on how comparable real projects actually turned out. A premortem is the small-team version of the same instinct. You cannot pull outcome data on a thousand past launches, but you can force yourself to reason from failure rather than from hope, which is most of the correction.

This connects to a broader truth I keep writing about: the biases you cannot see are the ones steering the decision. A premortem is one of the few tools that makes an invisible bias briefly visible, which is why I treat it as a sibling to any honest look at cognitive bias in technology decisions and to the sunk cost fallacy that keeps teams pouring money into a plan that has already told them it is failing.

How to run a premortem in thirty minutes

The ritual is small on purpose. A useful premortem for a two-person or ten-person team takes half an hour and needs a wall, some paper, and a rule that no one defends the plan during the exercise.

Diagram of the premortem flow: assume failure, list causes, rank by likelihood and impact, mitigate the top few
The premortem loop: state the assumed failure, list the causes, rank them, then mitigate the few that matter.

State the assumed failure first. Be specific and concrete: "It is October. We shipped the new booking system and customers hated it. Bookings dropped." A vague failure produces vague causes, so pin the scenario to a date and an outcome someone would actually notice.

Then list causes silently. Give everyone a few minutes to write independently before anyone speaks. Silent generation matters because the first person to talk in a group anchors everyone else, and you want the full spread of fears, not an echo of the loudest voice.

Next, rank. Read the causes aloud, cluster the duplicates, and sort them by two axes: how likely each is, and how much damage it does if it happens. Most lists collapse to three or four causes that carry the real weight. The long tail is noise you can note and move past.

Finally, mitigate the top few. For each serious cause, decide one of three things: prevent it now, prepare a response, or accept it with eyes open. Writing "accept" next to a risk is a legitimate answer. Pretending the risk is not there is the one answer that does not count.

What to do with the list once you have it

A premortem that ends in a nice document has failed its own test. The output should be a small set of changes to the plan and a small set of tripwires that tell you the failure is starting, rather than a report.

Tripwires are the underrated half. For each top risk, name the earliest signal you could actually observe. If the fear is "customers found the new flow confusing," the tripwire might be a spike in support messages in week one. Klein noted that a premortem sensitizes a team to pick up early signs of trouble once work is underway, and a named tripwire is how that sensitivity becomes something you can check.

Assign each mitigation an owner and a date, then let the plan proceed. The goal is to walk in with the three things most likely to sink it already handled or already watched, rather than to talk yourself out of the project. This is the same discipline behind building systems before you need them rather than after the emergency.

Where premortems fit in a small team's rhythm

You do not need a premortem for reversible, low-cost choices. Save the ritual for decisions that are expensive to undo: a new customer-facing system, a migration, a pricing change, a partnership. The cost of the meeting is thirty minutes. The cost of the failure it catches can be a quarter.

In our own operations methodology at LTFI, the premortem sits at the front of anything we are about to run in production, next to the less glamorous truth that maintenance, not the launch, is the actual job. Launches get the attention, but the quiet failures that a premortem surfaces are the ones that show up three weeks later, when everyone has moved on.

There is a reason large AI and software efforts stumble at the end rather than the start. As I have written about the last mile of AI projects, the failure usually hides in the boring gap between "it works in a demo" and "it works for a real customer on a Tuesday." A premortem is one of the few habits that reliably drags that gap into the room before you have spent the budget.

How do you do a premortem? Klein's own steps

Gary Klein has kept refining the premortem since 2007. In a January 2021 post on Psychology Today, he describes the premortem as something that "can take as little as 20-30 minutes," and lays out the sequence he uses:

  1. Review the plan. The team needs to know what the premortem is about to judge.
  2. Announce the failure. Klein tells the group to imagine looking into an "imaginary, infallible crystal ball" that shows the plan has failed.
  3. Two minutes of silent writing. Everyone lists reasons the plan failed, on their own.
  4. Round-robin. Each person reads one reason at a time, the leader goes first to show that candor is welcome, and the items go on a whiteboard quickly.
  5. Refinements. In later versions he adds two more minutes per person to suggest actions, and a rating of each problem for likelihood, impact and how easy it is to prevent.

The thirty-minute premortem earlier in this article follows the same shape. The detail worth copying is the leader speaking first. If the person who owns the plan names a weakness in it, everyone else in the premortem feels free to do the same.

A premortem template you can copy

A row of brass bells strung on a taut wire across a dark floor in hot pink light, the early tripwires a premortem names
A premortem ends with owners, dates and tripwires: the earliest signals that the imagined failure is starting for real.

Paste this into a shared document before the premortem and fill it in live. It keeps a premortem short and makes sure it ends in decisions rather than worry.

  1. The plan in one sentence: what we are about to do and by when.
  2. The failure: "It is [date]. [Project] failed. The sign was [an outcome someone would notice]."
  3. Silent list: each person writes five or more reasons it failed. Two to five minutes.
  4. Shared list: one reason per person per round until the lists are empty. Merge duplicates.
  5. Ranking: score each cause 1 to 3 for likelihood and 1 to 3 for damage. Multiply. Keep the top three or four.
  6. Response for each top cause: prevent, prepare or accept, in one line.
  7. Tripwire for each top cause: the earliest signal you could see, and who checks it.
  8. Owner and date: one name and one date per action.

If your team records meetings, the qurtoo.com playbook for a meeting notes prompt that pulls out decisions and action items uses the same "owner, task, by date" format, which makes it a good way to turn the premortem transcript into the last two rows of the template.

A worked premortem for a small business

Illustrative example: here is what a premortem looks like for a six-person dental office near Worcester that is moving to a new practice management system in March.

The premortem failure statement: "It is April. The new system is live and the front desk hates it. Two hygienists' schedules double-booked in the first week, and we went back to paper for a day."

Causes the team wrote down in the premortem: old appointments imported in the wrong time zone; nobody trained the part-time receptionist; the insurance lookup works differently and claims stalled; the old system's notes field did not migrate; the vendor's support line closes at 5 p.m. and the office runs until 7 two nights a week; the one person who understands the old system is on vacation the week of the switch.

Ranked top three: the notes field (likely and damaging), the evening support gap (certain and damaging), and the vacation timing (certain and easy to fix).

Responses and tripwires: test the notes import on fifty real records before go-live, with the office manager as owner; agree written after-hours support with the vendor, or keep the old system readable for thirty days; move the vacation. The tripwire for the import is simple: any patient chart without its history in week one stops the rollout.

That premortem took twenty-five minutes, and none of it required special tools. When we run this with clients through advisory work, the premortem is often where the real requirements show up for the first time. Brian makes a related point about software requests in the client who wanted a dashboard actually wanted a decision: the failure you imagine usually tells you what the project was for.

What does the research say about premortems?

The finding behind the premortem, prospective hindsight, comes from the 1989 Mitchell, Russo and Pennington work cited at the top. The premortem itself has been tested more directly. In 2010, Beth Veinott, Gary Klein and Sterling Wiggins tested the premortem with 178 college students who reviewed a plan for keeping students safe during a hypothetical H1N1 outbreak, under several conditions. Klein's summary of the result: "The students in the pre-mortem condition showed the greatest reduction in (over)confidence," compared with simple critiques or listing pros and cons.

Two honest caveats about the premortem evidence. That study measured confidence, not project outcomes, and the participants were students reviewing a hypothetical plan. What it shows is that a premortem makes people less sure of a plan than other review methods do, which is the intended effect, since the starting problem is too much certainty.

The scale of that certainty problem has only become clearer. In How Big Things Get Done (2023), Bent Flyvbjerg and Dan Gardner report that in his database of more than 16,000 projects, only 8.5 percent came in on budget and on time, and only 0.5 percent came in on budget, on time and with the promised benefits. A premortem will not fix that on its own. It is a cheap way to make your plan argue with the base rate before the money is spent.

Bar chart: in a database of 16,000+ projects, 8.5% came in on budget and on time, and 0.5% also delivered the benefits
Only 0.5 percent of the projects in Flyvbjerg's database hit budget, schedule and benefits together, the base rate a premortem asks your plan to argue with.
How many big projects deliver what they promised (Bent Flyvbjerg and Dan Gardner, How Big Things Get Done, 2023)
OutcomeShare of projects (%)
On budget and on time8.5%
On budget, on time and with the promised benefits0.5%

The ltfi.ai project planning skill ends with a list of questions to settle before building begins, and those questions make a good input to a premortem.

Common ways teams get the premortem wrong

The first mistake is running it too late. If the decision is already emotionally final and the launch is tomorrow, the premortem becomes theater. It works when there is still time and appetite to change the plan.

The second is letting the plan's owner defend it in the room. The moment someone says "well, that would not really happen," the exercise reverts to a normal optimistic meeting and the effect evaporates. Defense comes after, when you decide what to mitigate.

The third is treating every listed cause as equally urgent. A premortem generates a lot of material precisely because it lowers the bar for speaking up. The ranking step is what turns that raw fear into a plan. Skip the ranking and you get anxiety instead of foresight, which, like an unexamined default, quietly shapes the outcome anyway.

Related reading

Frequently asked questions about premortems

What is a premortem in simple terms?

A premortem is a short exercise you run before a project launches. You imagine the project has already failed completely, then everyone lists the reasons it died. It is the opposite of a postmortem, which happens after failure, and it lets you fix problems while there is still time.

Does a premortem actually work, or is it just a nice idea?

The core research holds up. Mitchell, Russo, and Pennington found that imagining an outcome as already settled improved people's ability to identify reasons for it by about 30 percent, a mechanism called prospective hindsight. Gary Klein built the premortem on that finding, and Daniel Kahneman later endorsed it as a practical decision tool.

How long should a premortem take?

For most small teams, thirty minutes is enough. Spend a few minutes framing the assumed failure, a few minutes on silent writing, then the rest ranking the causes and assigning mitigations. If it stretches past an hour, you are probably debating the plan instead of diagnosing its failure.

When should I not bother running one?

Skip it for small, reversible, low-cost decisions where the downside of being wrong is minor. Reserve the premortem for choices that are expensive or hard to undo, such as a migration, a new customer-facing system, a pricing change, or a partnership.

Who should be in the room for a premortem?

The people who will actually do the work, plus anyone who will feel the consequences. Diversity of role matters more than seniority, because the person who spots the fatal flaw is often the one closest to the messy detail, not the one who approved the plan.

What does pre mortem mean?

In project work, pre mortem (or premortem) means a review held before a project starts, in which the team imagines it has already failed and lists the causes. The name borrows from the medical postmortem, which examines a death after it happens.

Does pre mortem have a medical meaning too?

Yes. In medicine, "pre mortem" or "antemortem" simply describes something that happened before death, such as a pre mortem injury. The business premortem borrowed the word and turned the idea toward projects, where the "death" is imaginary and can still be prevented.

Is the premortem a project planning technique?

Yes. The premortem is a planning technique that assumes failure and works backward to the causes, usually run after a plan is drafted and before it is approved. It fits beside the risk register, not in place of it: the premortem finds the risks, and the register tracks them.

Can you run a premortem with a remote team?

Yes. A remote premortem needs a shared document or whiteboard. Give everyone the silent-writing minutes with cameras on and microphones off, then take turns reading one cause each. Remote premortems often surface more, because quieter people write before anyone can steer them.

How is a premortem different from a risk assessment?

A risk assessment usually asks what might go wrong and rates each item. A premortem asks people to explain a failure that has already happened. The ranking at the end looks similar, but the premortem tends to produce more specific causes, which is the prospective hindsight effect at work.

How many people should join a premortem?

A premortem works well with between three and about ten people. Fewer than three and you lose the range of views. More than ten and the round-robin takes too long, so split into groups and merge the lists.

What should a premortem template include?

A one-sentence plan, a dated failure statement, space for silent lists, a ranking by likelihood and damage, and a row for each top cause with a response, a tripwire, an owner and a date. The premortem template above fits on one page, which is the right size.

Psychology Sep 11, 2026 • 11 min

Decision Architecture Beats Sales Tactics

Decision architecture in B2B is the default. When one company made 401(k) enrollment automatic, participation among new hires rose from 37% to 86% (NBER, 2000). Fix the form before the deck.

Psychology Jul 24, 2026 • 18 min

Survivorship Bias Is Distorting Every Best Practice You Copy

Survivorship bias overstates the typical U.S. stock fund's reported returns by roughly 1.6 percentage points a year, per CRSP: surviving U.S. stock funds averaged 8.8% over the decade ending 2003, and 7.2% once dead funds were counted. Every best practice you copy carries the same tilt.

Psychology Jul 22, 2026 • 7 min

The IKEA Effect: Why You Overvalue What You Built In-House

In a set of experiments published in 2011, people who assembled a plain IKEA storage box valued it 63 percent higher than an identical prebuilt one. The IKEA effect, named by the researchers who ran that study, is the bias that makes you overvalue what you built yourself. It quietly...

Work With Us

Need help building this into your operations?

Kief Studio builds, protects, automates, and supports full-stack systems for businesses up to $50M ARR.

Newsletter

New writing, straight to your inbox.

Strategy, psychology, AI adoption, and the patterns that actually compound. No spam, easy to leave.

Subscribe