Dana has been offered a job in another city. The salary is better, the title is better, and her current manager has started to feel like weather she has to dress for. She has made a pros and cons list twice. Both times the pros won. Both times she still could not sleep.
A pros and cons list asks what might go right and what might go wrong. That sounds balanced, but in practice it tilts toward the answer we already want. Once we lean toward a choice, our minds get very good at finding reasons for it and very quiet about reasons against it. The premortem is a small tool built to get around that quiet.
Where the idea comes from
The premortem was described by the psychologist Gary Klein, who studies how experienced people make decisions under pressure. He laid out the method in a short 2007 article in the Harvard Business Review titled "Performing a Project Premortem." The idea borrows from medicine. A postmortem explains why a patient died after the fact, when nothing can be done. A premortem imagines the death in advance, while the plan can still change.
Klein's instruction is simple. Imagine it is some time in the future. The plan was carried out, and it failed. Not "might fail." Did fail. Now write down every reason you can think of for why it went wrong.
Daniel Kahneman, the psychologist who won the 2002 Nobel memorial prize in economics for work on judgment and decision making, praised the technique in his book Thinking, Fast and Slow. His point was that a premortem gives doubters permission to speak. In a group that has already fallen in love with a plan, raising objections can feel disloyal. When the exercise itself demands reasons for failure, raising them becomes the job.
Why assuming failure works better than asking "what could go wrong"
The difference sounds small. It is not. "What could go wrong?" invites a defensive answer. You list a few risks, rate them as unlikely, and move on, feeling responsible. "It went wrong; why?" asks for a story. Stories pull out specifics: the commute that turned out to be seventy minutes, the team that was reorganized six months in, the partner who never settled in the new city.
Researchers have a name for part of this effect. In a 1989 study, Deborah Mitchell, J. Edward Russo and Nancy Pennington found that people generated more reasons for an outcome when they imagined it had already happened than when they imagined it only might happen. They called it prospective hindsight. The premortem puts that finding to work.
How to run a premortem on your own
You need fifteen minutes, a blank page and a willingness to be uncomfortable.
- Write the decision in one sentence. "I take the job in Denver and start in March." Keep it concrete enough that failure would be recognizable.
- Pick a date. A year out works for most life decisions. For a project, use the deadline.
- Declare the failure. Write, at the top of the page, "It is a year from now. This went badly." Then describe what badly means for you. Lonely? Broke? Back where you started, but tired?
- Write reasons for five minutes without stopping. Do not judge them. Silly reasons, petty reasons and reasons you are embarrassed to admit all go on the page. The embarrassing ones are often the useful ones.
- Circle the three that feel most plausible. Plausible, not most dramatic.
- For each one, write one thing you could do now. Ask a question before signing. Negotiate a start date. Visit for a weekend in the worst month of the year. Talk to someone who left that team.
Dana's list included the obvious reasons, like cost of living. It also included a less obvious one: "I took the job to get away from my manager, and the new manager turned out to be the same kind of person." That reason changed her next step. Instead of accepting, she asked to speak with two people who report to her future boss.
How to run one with a team or a family
The group version follows the same steps with one important rule. Everyone writes their reasons privately first, before anyone speaks. If people call out reasons in turn, the first loud voice sets the frame and quieter people tune their answers to it.
After the private writing, go around the room and collect one reason per person per round until the lists are exhausted. The person who proposed the plan should go last, or should take notes instead of contributing. That keeps the exercise from turning into a defense.
Then do what the solo version does. Choose the few reasons that matter, and turn each into an action, an owner and a date. A premortem that ends with a long list and no changes was a worry session, not a decision tool.
What a premortem is not
It is not a vote against the plan. Most premortems end with the same decision, made more carefully. Dana may still take the job. If she does, she will do it knowing which risks she is accepting and which ones she has reduced.
It is not a forecast. Writing that the move failed does not make failure more likely, and listing reasons does not measure their probability. You still have to judge which reasons are real.
It is not a cure for anxiety. For people who already ruminate, an open-ended exercise in imagining disaster can feed the loop. The time limit matters for that reason. Five minutes of writing, then a switch to actions. If you notice the exercise is making you spiral rather than plan, stop, and talk the decision through with someone you trust instead.
A small practice for ordinary choices
Not every decision deserves fifteen minutes. For smaller ones, a single line will do. Before you send the email, sign the lease or say yes to the volunteer role, ask yourself: "If I regret this in a month, what is the most likely reason?" Then decide whether that reason is worth a small change now.
Wisdom traditions have long asked people to look at endings before beginnings. The Stoics practiced imagining loss so that they would hold good things more lightly. The premortem is a practical cousin of that habit. It does not ask you to expect the worst. It asks you to look at the worst for a few minutes, on purpose, so that you can walk toward the best with your eyes open.