AI On Your Team · No. 1

Run a pre-mortem before you commit to a plan

A pre-mortem is one question asked before you commit: assume the plan already failed, then write down every reason why. It takes one honest reviewer.

A blue magnifying glass casting yellow light on a stack of paper, beside a red rubber stamp that has not been used yet, on a warm white background.

We have caught ourselves nodding along with our own recommendation more times than we would like to admit. Everyone in the room already agreed with the plan, because agreeing was how the room produced the plan in the first place.

So we added a step. Before a recommendation becomes a plan, we hand it to someone who was not in the room and ask one question: assume this already failed, now tell me why.

A pre-mortem is one question you ask before committing to a plan. Imagine it has already gone wrong, then write down every reason why. It takes one colleague, and it catches the mistake before the mistake costs anything.

The short answer

  • Ask someone with no stake in it to assume the plan went wrong, and listen to what they say happened.
  • Ask what has changed since the argument for the plan was first made.
  • Run it even on plans you feel good about, especially on those.

A pre-mortem, in one look

Example
  1. Assume this already failed.
  2. Read the whole list first.
  3. Same objection, different words.
  4. Fix the few, let the rest go.

A shift in where the ad budget goes

Assume this already failed. Now tell me why.

Fix

  • An assumption that went stale
  • Blank card
  • Same objection, different words

Let go

  • Blank card Speculation
  • Blank card Speculation
An example. Most of the list will be speculation.

The exercise itself is not new. A 2007 Harvard Business Review article described the same premise: assume the project has failed, then explain why. Ours differs in one way: the reviewer was never in the room.

It has reached classrooms too: a prompt published in Microsoft's prompts-for-edu repository coaches a student to imagine that their project has failed and list the reasons (the pre-mortem coaching prompt).

Why the room agrees with itself

Maybe the plan is a push into search visibility or a shift in where the ad budget goes. Whatever it is, the people who built it spent hours convincing themselves it would work. That effort does not disappear once the plan is finished. It turns into a mild resistance to hearing that the plan might be wrong, right when hearing that would help the most.

The mistake a pre-mortem catches is usually a good idea built on an assumption that went stale without anyone noticing, like a channel that used to convert. The plan can be well built and still fail, because the ground under it moved before anyone checked. The check is simple: ask what has changed since the argument for the plan was first made. If the answer is nothing, the plan probably still holds.

A pre-mortem works because it changes the question, and because the objections arrive before you have defended the plan out loud. Instead of asking whether the plan will work, which invites everyone to defend the plan they already like, it asks what went wrong. That question gives people permission to criticize a plan without criticizing whoever wrote it. Nobody has to admit they were wrong. They just have to imagine a future where the plan failed and describe it.

Ask: will this plan work?

  • You get defenses of the plan
  • Doubts stay vague, if anyone voices them
  • The room leaves more sure of itself

Ask: it failed, why?

  • You get a list of concrete failure stories
  • Each story names what went wrong and when
  • The room leaves with a few things to fix

How to run one with a colleague

A pre-mortem

  1. Write the plan in one sentence

    Not the deck version. The one sentence you would say if someone stopped you in the hallway.

  2. Hand it to someone who was not in the room

    A colleague who has not heard the reasoning yet gives an honest first reaction, not a rehearsed one.

  3. Ask them to assume it went wrong

    Six months from now, the plan did not work. Ask them to write down why, in as much detail as they can.

  4. Read the whole list before you argue with any of it

    The point is coverage, not correctness.

  5. Fix the reasons that would happen

    Most of the list will be speculation. Find the few reasons that would really happen, fix those, and let the rest go.

Once you have defended a plan in front of someone, you tend to stop hearing objections to it. Notice when the same objection turns up again in different words. That repetition usually means the plan has a real weak point.

Assume this already failed. Now tell me why.
The one question we ask

The reviewer needs no stake in the plan

We run this at the point where a recommendation is about to become a plan. The same principle runs this blog: before a post like this one publishes, someone who did not draft it reviews it.

Our reviewer, the one in the callout above, is an AI assistant with no memory of the draft. The sign off is a person's. Google's guidance on helpful content suggests that when automation plays a substantial part in making content, readers should be able to see that, along with background on how and why it was used (Google's guidance on creating helpful content).

Why the pre-mortem goes to someone who did not build the plan.
QuestionA reviewer from the roomA reviewer who was not there
Has heard the reasoningMany timesNot yet
First reactionRehearsedHonest
Stake in the planHelped build itNone

Run it even on plans you feel good about, especially on those. Confidence is not evidence that a plan will work. Most of the time, it is evidence that we already talked ourselves into it, which is exactly the condition this exercise exists to catch. It is the same reason we read a relaunched campaign back instead of trusting the confirmation, and the same reason an AI-assisted draft gets a human edit pass before it goes anywhere.

  • Same objection twice You notice It turns up again in different words
    Same objection twice What it tells you That repetition usually means the plan has a real weak point.
  • Stale assumption You notice A good idea built on an assumption that went stale
    Stale assumption What it tells you Ask what has changed since the argument for the plan was first made.
  • Confidence You notice You feel good about the plan
    Confidence What it tells you Confidence is not evidence that a plan will work.
  • A long list You notice Most of the list will be speculation
    A long list What it tells you The point is coverage, not correctness.

What a pre-mortem turns up, and what it tells you.

The next time a plan is ready to leave your desk, skip the question of whether it is good. Ask someone with no stake in it to assume the plan went wrong, and listen to what they say happened. If the plan survives that conversation, sign off. If it does not, you just found out what would otherwise have cost a great deal more.

After your first pre-mortem

Ready to commit

Talk to Offer before you decide anything.

You'll talk with Offer, not a sales rep. A short call, no pitch deck.

Talk to Offer

This post was drafted with AI tools from our own project records, anonymized, and checked by us before it published. Read our editorial standards.

Related Articles

Want to talk through your marketing?

Tell us where things stand and we'll tell you plainly what we'd do next.