What it is
A prospective-hindsight exercise: the team imagines it is the future and the project has failed, then brainstorms why, surfacing risks and blind spots that optimism usually suppresses.
When to use it
During Initiate and before committing to a plan or launch, whenever risk and overconfidence are concerns.
Why (value)
Legitimizes dissent, counters groupthink and optimism bias, and turns vague worries into concrete risks you can mitigate.
How to run it
- Set the scene: “It is launch day and this failed badly.”
- Everyone independently writes why it failed.
- Share and cluster the failure causes.
- Assess likelihood and impact.
- Turn top risks into mitigations and owners.
Inputs and outputs
- Inputs: A plan or decision and the team behind it.
- Outputs: A prioritized list of risks with mitigations.
Time and effort
Low. Thirty to sixty minutes.
Evidence and limitations
Surfaces hypothesized risks, not evidence. It improves planning; the risks still need judgment and, where possible, validation. See Evidence and limitations.
Tips and pitfalls
- Have people write independently first to avoid anchoring.
- Make it safe to voice pessimism.
- Convert risks into concrete mitigations, not just a worry list.
Variations
Prospective hindsight, failure brainstorming, risk premortems.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
- Gamestorming.
Explore related methods
- Assumption mapping — Surface the beliefs a plan depends on and sort them by risk so you test the scariest ones first.
- Five whys — Ask "why" repeatedly to move from a surface symptom to a root cause.
- Lean hypotheses — State beliefs as testable predictions so you can learn quickly instead of debating opinions.
