What this fixes
You’re about to commit to a plan - a sprint, a release, a migration, a launch - and asking “what could go wrong?” never surfaces the real risks. Once a team has built a plan, it stops evaluating it and starts defending it, so the doubts people privately hold stay unsaid. Then the post-mortem opens with “I had a bad feeling about that.”
It Already Failed flips the question. You assume the plan has already failed and explain why - which turns defending back into investigating and surfaces the concerns already quietly living in the room while they’re still cheap to prevent.
How this works
Imagine: tomorrow, your team is committing to a major customer migration. Before anyone signs off, imagine it’s six weeks later, and the migration failed badly - and explain why.
Imagine the project has already failed. Now explain why.
That single shift - from predicting to explaining - is the whole tool. Instead of guessing what might go wrong, the team writes the causes of a failure that has “already happened”: what did somebody already suspect, but nobody acted on? Every cause goes up on a wall, one card each, until the room can see just how many ways this could fail.
Then you thin the wall. Keep only causes you could actually have acted on before starting, narrow it down to the top five that matter most, and for each write one preventive move with an owner. The wall is the point: seeing fifty ways to fail is what makes “we can only protect against five” land.
Team: one person acts as the facilitator, running the activity from the Facilitator Guide. Everyone writes causes; the room builds the wall together.
Time required
Team ✓ · About 20–30 minutes, with a facilitator.
The time required is indicative and will depend on the size of the plan and the team.
The facilitator should read the short facilitation guide first - about 8–10 minutes. It is a downloadable PDF on this page.
When to use
Bring one real plan you’re about to commit to - the tool works at the point of commitment, not on a hypothetical.
Use it whenever:
What you get
You’ve done it well when: the team commits with its top failure modes named and prevented - and leaves with owned preventive moves, not just a list of worries.
What you’ll notice
Why this works
Once people invest in a plan, they become its advocates, not its evaluators - so a forward-tense “what could go wrong?” feels like an attack on something they now own, and the risks they suspect stay silent. The past tense removes the need to defend the plan: you’re examining a fictional failure, not criticising a colleague’s plan, so people investigate freely. And the real reason it works: we are far better at explaining failure than predicting it. Forward tense demands prediction, which humans do poorly; past tense demands explanation, which we do well. (Based on the premortem technique.)
What you need
One real plan. A plan you’re about to commit to, with genuine stakes - a sprint, release, migration or launch.
The cause cards and the board. One blank card or sticky note per failure cause, and a whiteboard, wall or large flip chart to build them into a visible wall, then thin to the top five. Supplied with the activity.
Markers. One per person, so everyone writes causes at once - the wall should fill fast.
A facilitator. They hold the obituary frame, keep the wall filling before any sorting, run the actionability filter and the forced cut to five, and make sure every survivor leaves with a preventive move and an owner.
Steps
Output / Takeaways
You leave with:
Important rules
Planning to facilitate this activity? Access the resources below to get started.