The 60-second startup pre-mortem

A pre-mortem is a thought experiment popularized by psychologist Gary Klein: imagine the project failed catastrophically; now explain why. The technique works because humans are systematically better at identifying reasons something already failed than reasons something might fail. By assuming the failure has already happened, you bypass your own optimism bias.

The full version of the exercise takes a structured 45-90 minutes. Here's a compressed version — one minute, six questions — that I run on every new idea before doing any more work on it.

The 60-second version

Set a timer. Imagine it's 24 months from today, and the company you'd build around this idea has shut down. Answer:

1. What was the single biggest reason it failed? Write one sentence. Don't think — first instinct.
2. Who was the customer who never showed up? Be specific about the ICP that you assumed would buy but didn't.
3. What did the competitor that crushed you do? Specific company or company type, and the specific move.
4. What was the metric that never crossed its kill threshold? Retention? CAC? Conversion? Be specific about the number.
5. What did the team disagreement that broke us look like? Even if it's just you, you have an internal version of this — name it.
6. What's the one thing we'd have done differently if we'd known on day one? Be ruthlessly honest.

What good answers look like

Bad pre-mortem answers are vague ("we just didn't get traction", "the market wasn't ready", "we ran out of money"). Good answers are concrete and uncomfortable.

1. The category was a feature, not a company. After 18 months Notion shipped it and the comparison was over.

2. The mid-market ops director we assumed had budget actually needs IT approval, and IT defaults to the platform they already own.

3. Asana, by integrating it into their existing workflow product, made the switching cost too high for our 30%-cheaper price to overcome.

4. Net Revenue Retention never crossed 100% — every cohort churned faster than expansion could compensate.

5. My co-founder and I disagreed about whether to pivot to enterprise; we delayed the call for six months and missed the runway window.

6. We'd have niched into one vertical (legal ops) instead of trying to be horizontal.

That's a useful pre-mortem. Each line is something the founder can do something about today: validate IT approval workflows in their discovery calls (#2), check whether their leading metric is NRR-shaped (#4), and pre-commit to a single vertical to avoid the horizontal trap (#6).

When to run it

• Before you start. Always.
• Before every fundraise. The pre-mortem changes; the changes are signal.
• Before every major pivot decision. Compare the pre-mortem of the current idea vs. the pivoted one.
• Every Sunday for the first six months. It takes five minutes and surfaces drift early.

Why this works

The pre-mortem reverses the framing of the question your brain wants to answer. "Will this work?" activates your motivated reasoning. "Why did it fail?" activates your causal reasoning. The same brain produces dramatically different output depending on which question you ask it.

It also makes your kill criteria concrete. Question 4 in particular — "what was the metric that never crossed its kill threshold?" — is literally how you write your kill criteria. The pre-mortem is the kill-criteria generation engine.

If you want a pre-mortem rendered by five hostile experts simultaneously, in 60 seconds, with specific numerical kill criteria attached, that's literally what PivotProof is. The framework above is the manual version; we built the tool to compress it.