Is a pre-mortem the same as being negative?

No. It names failure modes early so you can test them cheaply. Pessimism without tests is theater; pre-mortem plus experiments is discipline.

Thirty minutes sounds arbitrary.

It is a forcing function: enough to surface top risks, not enough to write a novel. Extend only if you already have interview or usage data to attach.

Do I need an AI board for this?

You can run this worksheet solo or with a co-founder. A simulated board adds parallel objections and synthesis — useful after you have a filled worksheet.

Where does Lumor fit?

Use our [stress-test hub](/en/stress-test-business-idea) when you want structured specialist pressure on the same assumptions — before or after this worksheet.

Kill It in 30 Minutes: A Founder Pre-Mortem Worksheet

A tight pre-mortem you can finish before lunch: imagine failure, extract kill criteria, and leave with one experiment — without drowning in theory.

Why founders skip pre-mortems (and pay for it)

Most teams poster-mortem: they explain failure after budget and morale are gone.

A pre-mortem does the opposite: you pretend it is twelve months later and the bet failed — then you steal the clarity before you ship the wrong roadmap.

This worksheet fits one concrete bet: a wedge, a pilot, a pricing move, or a fundraise narrative — not “the whole company forever.”

Before you start (two minutes)

Pick one sentence that defines the bet:

“We believe _________ will pay for _________ because _________.”

If you cannot fill that without sweating, stop polishing decks and fix the sentence first.

Timer on: 30 minutes.

Block A — Failure headline (5 minutes)

Imagine a sober headline twelve months out:

“We shut down / pivoted hard because _________.”

Write five completions. No filtering for fairness:

Force diversity: at least two causes must be outside product (budget, procurement, channel, timing, competitor behavior).

Block B — Inside vs outside failure (8 minutes)

For each headline, tag it:

Tag	Meaning
I	We built or positioned wrong
O	Market or buyer reality refused to cooperate

Mark each line I or O.

Then answer:

Which O risks would survive even if engineering shipped perfectly?
Which I risks are fully under your control this quarter?

If everything is I, you probably framed the problem too narrowly. If everything is O, you might be dodging accountability.

Block C — Kill criteria (10 minutes)

Translate the top three risks into observable signals.

Bad: “Customers don’t get it.”
Better: “Fewer than X of Y qualified calls say the same pain in their words.”

Bad: “Pricing is wrong.”
Better: “Zero paid pilots after N conversations at proposed ACV band.”

Fill:

Risk	Kill signal (numbers or dates)	Owner
1
2
3

If you cannot specify X/Y/N, your next step is discovery — not roadmap expansion.

Block D — One falsifiable experiment (7 minutes)

Pick one kill criterion and design the smallest test:

Hypothesis:
Evidence you will collect:
Timeline:
Cost cap (time + money):

You pass the worksheet only if someone could disprove you — not if they could applaud you.

What to do with this page

Share with a co-founder who is allowed to be annoying.
Schedule the experiment before you add headcount or scope.
Optional: feed the same brief into a stress-test session on Lumor to see how specialist roles tear at the same seams — parallel pressure, structured verdict.

When not to use this worksheet

Skip it when the decision is trivially reversible and cheap — just ship and measure.

Use it when wrong hurts: hiring, positioning lock-in, pricing architecture, compliance-sensitive verticals, or anything you would defend to an investor next month.