Imagine the project has already failed

Most risk reviews don't surface the real risks. They surface the risks everyone already knew. The supply chain question, the budget question, the resourcing question, the ones that have been discussed in every meeting since the project started.

The risks that actually take projects down are usually the ones nobody quite wanted to raise. The thing the team lead suspects but doesn't want to be the one to say. The dependency that everyone is privately worried about. The assumption that hasn't been tested because testing it might be inconvenient.

There's a 10-minute exercise that gets these into the room. The cognitive move behind it is small and specific.

It's called a pre-mortem.

How it works

Sit down with your team. Tell them this. Imagine it's a year from now. The project has failed. Not "might fail." Has. The launch was a disaster, the deliverable didn't work, the customer fired you, the regulator blocked it. Whatever failure looks like for this project, that's what happened.

Then ask: why?

Each person, on their own, writes down as many specific reasons as they can. 5 minutes. Then around the table, each person shares one new reason at a time, until you've exhausted the list. 5 more minutes.

That's the exercise. 10 minutes, properly run.

Why it works

The mechanism is the grammatical shift.

When you ask a team "what could go wrong?" they answer from a posture of optimism and uncertainty. The plan still might succeed. Raising concerns feels like undermining it. People hedge. They name the risks they think are safe to name.

When you tell them the plan has already failed, the posture flips. They're no longer guarding the plan. They're explaining a failure. People get forensic instead of diplomatic. The risks they privately suspected, the ones that felt impolitic to raise, now feel obligatory to name. The failure has happened. The question is just why.

The research on this is reasonably old. In 1989, Deborah Mitchell at Wharton, Jay Russo at Cornell, and Nancy Pennington at the University of Colorado published a study showing that imagining an event has already occurred (they called it "prospective hindsight") improves your ability to correctly identify reasons for future outcomes by 30%. Gary Klein, a cognitive psychologist, built the pre-mortem on that finding and published the method in Harvard Business Review in September 2007. Daniel Kahneman has cited it as one of the simplest de-biasing techniques available.

A few practical notes

Run it before the plan is locked, but after it's detailed enough that people can reason about specific failures. Too early and the failure modes are generic. Too late and the changes are expensive.

Make people write privately before they share. Social proof contaminates the list if the loudest person speaks first.

Don't combine it with a normal risk meeting. The whole point is the shift in posture. Putting both in one session means the team defaults back to defending the plan.

And take it seriously when something uncomfortable comes up. The risks the pre-mortem surfaces are usually the ones someone privately suspected and didn't want to be the one to say. If your team has trusted you with that, the worst response is to bat it away.

A 10-minute exercise won't save a bad plan. It will tell you where the real failure lines run. Most planning sessions never get that far.