Leadership insight

A 15-minute premortem for a decision your team is rushing

A short, practical premortem your team can run in 15 minutes to slow a rushed decision, surface assumptions and set a simple check-and-review trigger.

By Andy Nunn4 min read
Andy Nunn holding a phone while standing among delegates seated at round tables

Andy Nunn interacting with delegates at an event.

Before your team commits to a rushed business decision, imagine the plan has failed and ask why. A premortem gives people a specific way to raise concerns before the decision is locked in.

The 15-minute agenda below is a suggested starting point for an ordinary, limited business change. It is not a validated time limit or a guarantee of a better result. Use a more thorough review when the consequences warrant it. For emergencies or safety-critical work, follow established procedures.

Why a premortem for rushed decisions

Gary Klein’s 2007 article, Performing a Project Premortem, describes imagining that a planned project has failed and generating plausible reasons. His publisher’s summary explains how this can bring concerns into the discussion before execution.

You are not predicting failure. You are asking which assumptions deserve a closer look. That connects with the focus on questioning assumptions in Andy Nunn’s The Human Advantage. The exercise below is a practical adaptation for discussion.

Consider a fictional team deciding whether to launch a customer onboarding change next month. Their task is to identify one important uncertainty to check before confirming the date.

1. Set the frame (2 minutes)

State the decision out loud and write it where all can see: “Launch the onboarding change next month.” Define success in one sentence: “Faster first‑value for new customers without increasing support load.” Now ask everyone to imagine it is two months after launch and the change has clearly failed.

Prompt to group: “It failed. What happened?” Make it clear this is about the plan and its assumptions, not people or blame.

2. Silent writing: reasons it failed (3 minutes)

Ask each person to write possible reasons for failure before the group discusses them. Give everyone the same quiet writing time, including people who might otherwise wait for a senior colleague to speak.

For the fictional onboarding change, someone might worry that the mobile flow times out. Another might question whether sales promises match the new steps, whether support can handle extra enquiries, or whether older accounts will transfer correctly. These are possibilities to investigate, not established facts.

3. Share and cluster the risks (4 minutes)

Invite each person to share one concern, then group similar notes. Describe each group as an assumption you can examine. “Mobile usability holds up under real conditions” is more useful than “the technology is bad”.

Other assumptions in the fictional example could concern the sales handover, support capacity or migration of older accounts. Avoid solving every problem immediately. First agree which concern could materially change the decision.

4. Choose one material assumption to check (3 minutes)

Choose an assumption that would meaningfully affect the outcome if it were wrong. Suppose the fictional team chooses support capacity during the first fortnight.

Agree a proportionate check before confirming the launch date. The team could compare its available capacity with recent support demand, then ask a support lead what the new process would add. Record what the check can establish and what will remain uncertain. One quick check cannot prove that the whole launch will succeed.

5. Nominate an owner and a review trigger (3 minutes)

Give one person responsibility for the check, with a deadline before the final decision. In the fictional example: “Priya will review support capacity and report back by Thursday afternoon.”

Then agree a condition that will reopen the decision if the team proceeds. For example, support waiting times exceeding the team’s agreed threshold could trigger a review before any further rollout. Choose the threshold and response time for your context rather than borrowing arbitrary numbers.

Record the owner, check, deadline and review trigger where the team can find them.

A practical takeaway

At the next decision meeting, write down the proposed action, imagine it has failed and give everyone time to name a possible reason. Choose one important assumption to check, appoint an owner and agree when the decision will be reconsidered. For the fictional onboarding team, the support lead would review capacity before launch and reopen the decision if waiting times crossed the agreed threshold.

Explore further

Sources

Audience Feedback

Open video in a new tab