Premortem Template: Find the Failure Before It Happens

I used to think optimism meant believing everything would work out.

It sounds beautiful, doesn't it? Start with hope. Trust the process. Keep moving. The problem is that optimism without inspection can become a very polite form of blindness.

A few years ago, I watched a project begin with that kind of energy. The idea was exciting. The team was capable. Everyone could see the upside clearly. What we did not see clearly were the small cracks: unclear ownership, vague deadlines, assumptions about customer behavior, and the quiet belief that motivation would solve coordination.

It did not fail in one dramatic moment. It became tired first. Then confused. Then expensive.

That is why I like the premortem.

A premortem is simple: before you commit, imagine the decision has already failed. Then you work backwards and ask what caused the failure. It is not pessimism. It is a structured way to make optimism more honest.

This premortem template is useful before a big project, career move, hiring decision, product launch, investment, or any decision where enthusiasm may be louder than evidence.

Here is the template you can copy.

1. Decision or project: What are you about to commit to?
2. Success definition: If this goes well, what will be true?
3. Failure scene: Imagine it is six or twelve months later and this failed. What happened?
4. Top failure causes: List five reasons it failed.
5. Early warning signs: What would show up in the first few weeks if one of those risks was real?
6. Assumptions: What are you treating as true but have not proved?
7. Blind spots: What are you avoiding because it is uncomfortable to discuss?
8. Prevention: What can you do now to reduce the biggest risk?
9. Fallback plan: If the risk appears, what will you do instead?
10. Decision adjustment: After seeing the risks, what should change before you commit?

That is the whole worksheet.

But the value is not in filling every box. The value is in the moment when one answer makes you pause.

For example, imagine you are considering joining an early-stage startup.

Decision: Accept the role and leave a stable job.

Success definition: I learn faster, gain ownership, and help build a product I believe in.

Failure scene: Six months later, I am exhausted, the product direction has changed, and the role is not what I expected.

Top failure causes: The company runs out of funding. The founder and I have different expectations. The job becomes mostly execution with little strategy. I underestimate the emotional cost of uncertainty. I join because I want escape, not because this role is right.

Early warning signs: Slow replies about runway. Vague answers about responsibilities. No clear manager. Current employees seem tired but careful with their words.

Assumptions: I assume the product will find market fit. I assume ownership means influence. I assume my current frustration means I should leave.

Blind spots: I do not want to admit that the startup feels attractive partly because my current role feels stale.

Prevention: Ask sharper questions before accepting. Speak to two current employees. Get role expectations in writing. Compare the decision with a decision matrix, not just excitement.

Fallback plan: If the role becomes misaligned, set a three-month review point and keep enough savings to leave without panic.

Decision adjustment: Do not accept until the runway, manager expectations, and role scope are clear.

Notice what happened. The premortem did not say "do not join." It made the decision more specific. Fear became information. Optimism became testable.

This is the difference between anxiety and preparation. Anxiety says, "What if everything goes wrong?" Preparation says, "If this goes wrong, what would probably cause it, and what can I do now?"

The premortem pairs well with a decision journal. The premortem names the risks before the decision. The journal records why you still chose what you chose. Later, when the outcome arrives and hindsight bias starts rewriting the story, you have a record of what you actually saw at the time.

It also pairs well with a cognitive bias checklist. A premortem asks what would make the decision fail. A bias checklist asks whether your thinking is already being bent by confirmation bias, sunk cost, loss aversion, or a story that feels too neat.

Here is the uncomfortable part: a good premortem may make your exciting idea feel less exciting.

That is not a problem. That is the point.

If the idea only survives while everyone avoids the hard questions, it is not strong yet. If it survives after the hard questions, it becomes calmer. Less shiny, maybe, but more real.

I still believe optimism matters. Without it, we would never start anything. But optimism should not be a blindfold. It should be a lantern.

The goal is not to predict every failure.

The goal is to stop being surprised by the obvious ones.