Imagine it failed: the pre-mortem

Run Gary Klein's pre-mortem with a team before you commit to a plan.

Take a blank sheet and write across the top: "It is a year from now, and this plan has failed." Keep it in front of you while you read, because that sentence is the core of a method for drawing out doubts before you commit to something.

The usual way of checking for doubts doesn't work well. A leader ends a planning meeting with "any concerns?", and real worries almost never come out. The team has put in the effort, the boss is clearly keen, and anyone who speaks up risks looking negative. The pre-mortem gets around this. It is a way of asking why a plan failed before you start, by imagining it already has, while there is still time to act on what you find. It comes from psychologist Gary Klein, who described it in the Harvard Business Review. A post-mortem asks the same question after the failure, when it is too late to change anything.

Hafiz and the Tampines lease

Hafiz, from lesson 6.1, is deciding whether to take a lease on an outlet in Tampines. He and his team are invented examples, as is everything that happens to them here. In lesson 6.1 he concluded the lease was a one-way door and deserved care, so his team spent two weeks on the plan: fit-out, menu, hiring and the launch promotion.

At the final meeting he asked, "Any concerns before we sign?" Nobody spoke for a moment. One person brought up parking, the room agreed it was a small issue, and the plan was approved.

Six months on, the outlet is struggling. At the post-mortem, three people admit they had worried about weekday foot traffic from the start. None of them had mentioned it when it could have made a difference.

Why treating failure as fact draws out better answers

A pre-mortem is for the point when your team has a plan and is close to committing. The leader asks everyone to picture a year from now: the plan went ahead and failed badly. Each person writes down every reason they can think of. Klein's instruction is that the failure has already happened. Nobody is guessing whether it might.

The phrasing changes what people produce. Ask "what could go wrong?" and you get careful, vague replies. Say "it went wrong, explain why" and people start telling a specific story. Klein drew on research into prospective hindsight, the finding that picturing an event as already over makes it easier to name specific reasons for it. Once the failure is fixed in your mind, you search for causes the same way you would after something real.

The larger effect is on the group. In an ordinary planning meeting, raising a doubt can feel disloyal, particularly when a senior person has backed the plan or when challenging the boss in front of others is uncomfortable. Plenty of people in Singapore offices recognise this. A pre-mortem changes what counts as good work. The leader has asked for reasons the plan failed, so coming up with them is doing the job properly. Someone who would never say "I don't think this will work" will readily write: weekday footfall was too low because the office crowd works from home on Mondays and Fridays.

Daniel Kahneman covers the method in his book Thinking, Fast and Slow. Kahneman notes that it counters the groupthink that builds as a team gets closer to deciding. Lesson 5.2, Anchors and confirmation, showed how difficult it is to search for evidence against something you already believe. In a pre-mortem, that search becomes the purpose of the meeting.

Running the session so every voice gets in

Allow fifteen to thirty minutes. The order of the steps is deliberate:

The leader sets up the failure as a fact: "Imagine it is a year from now. We went ahead, and it failed badly. Write down every reason why." Give a few minutes for this. Everyone writes on their own, in silence, for those few minutes. No talking. Go round the table or round the call, one reason per person per turn, until every list is used up. The leader records each reason somewhere the whole group can see. Look over the complete list together and pick out the reasons that seem most likely or would do the most damage.

Silent writing comes first so the most senior or most confident person can't set the direction for everyone else. This is the anchoring problem from lesson 5.2 again. Taking one reason per turn gives everyone a go, so a junior colleague's strongest point is heard before the conversation moves elsewhere. If some people are in a room and others are joining remotely, call on each person by name so the remote ones aren't passed over. Lesson 5.4 of the course Communicate at work, Get heard when you are remote and others are in the room, explains why this matters.

When the group reads the full list, there are usually several reasons on it that nobody had mentioned before. You can do the same exercise on your own for a personal decision by writing out the failure story for yourself.

Deciding what each reason changes

A list that leads to no action is wasted. Take each of the most important reasons and give it one of two responses: change the plan, or set a warning sign to watch for.

Changing the plan means fixing the weakness before you commit. If weak weekday footfall were the most likely cause of failure, Hafiz could negotiate a shorter first lease, adjust the opening hours, or add a weekday office catering service before launch.

Some risks can't be fixed in advance. For those, decide now what early signal would show the risk is happening and what you will do if you see it, then write that trigger down. For example: "If average weekday sales are below our break-even figure for six straight weeks, we review the opening hours and the menu." A trigger written ahead of time is much easier to act on later, because you made the decision while you were thinking clearly. It also protects you from the sunk cost trap covered in lesson 2.3, Sunk costs and other traps in your own head.

Run properly, Hafiz's pre-mortem produces eleven reasons. Most of the team rate three as likely: weekday footfall, a delayed fit-out pushing the opening into a slow month, and trouble hiring a manager for the outlet. Hafiz changes the plan to deal with the first two and sets a warning sign for the third.

Think of a plan you are close to committing to, at work or at home, ideally one where nobody has yet said out loud what worries them. That is the plan to bring to the activity below.

Spend fifteen minutes running a pre-mortem on a plan you have now, alone or with your team. List three changes it points to.

Course

Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).