Run a premortem before committing
Imagine the project has already failed and work backwards to find why.
Why it works
The premortem (Klein, 1989) exploits prospective hindsight: when people are told an outcome has occurred, they generate more and better causes for it than when asked to imagine possible futures. By assuming failure before starting, you bypass the motivated reasoning that suppresses uncomfortable scenarios during forward planning. The premortem surfaces specific failure modes that get averaged out by optimistic group planning, without requiring individuals to publicly dissent.
How to do it
- After completing a plan, announce: "Imagine it is six months from now and this project failed badly. What happened?"
- Have every team member (or your future self) write down two to three causes of that failure.
- Gather the list, look for recurring themes, and adjust the plan or add explicit mitigation.
- Run a separate "pre-parade" for potential successes to preserve motivation.
Evidence
Prospective hindsight research (Mitchell, Russo & Pennington, 1989) found that imagining an event as already having occurred increased the generation of correct reasons by about 30% compared to forward projection. Klein popularized the premortem as a practical application; direct RCT evidence for the premortem specifically is limited. (observational)
Most evidence is on reason generation in lab settings, not on whether premortem-adjusted plans actually complete faster.
Sources
- Mitchell, Russo & Pennington (1989), Back to the future: Temporal perspective in the explanation of events, Journal of Behavioral Decision Making
Common mistake
Treating the premortem as a brainstorm for edge cases rather than a systematic audit — the exercise requires genuine imagination of central failure, not just catastrophizing.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for The Planning Fallacy — Why Your Estimates Are Always Wrong
- Reference class forecasting
Before estimating, look up how long similar past projects actually took — not how they felt.
- Decompose tasks and sum the pieces
Estimate each sub-task independently, then add them up — the sum is closer to truth than a top-down estimate.
- Schedule buffers as first-class commitments
Add explicit slack time to your schedule and treat it as non-negotiable white space, not a reserve to fill.
- Set external accountability deadlines
Announce a completion date to someone who will notice if you miss it.
- Log actual vs. estimated time for every task
Build a personal database of your own estimation errors so you can calibrate future predictions.
- Separate the planning session from the execution day
Do your planning in a dedicated session, never on the day you intend to start.