Think of the last big thing you were sure about. It might have been a move, a new job, a project, or a promise to yourself that this was the year. You probably remember the feeling most: the lift in your chest, the clear picture of how it would go. Now think about the part you didn't picture. Months later, something went sideways in a way that seems obvious in hindsight. It's the kind of thing a friend might have named in one sentence if you'd asked.

You didn't ask, and that's not because you're foolish. Planning feels good, and the feeling works against you.

Why a good plan feels safer than it is

Behavioral scientists have a name for this. Daniel Kahneman and Amos Tversky described the planning fallacy in the late 1970s. People predict how long a task will take, and how well it will go, by picturing the best-case path. They then ignore what happened the last several times they tried something similar.

The problem isn't a lack of information. You have plenty of it. When you imagine the future, your mind builds a smooth story, and a smooth story has no room for the flat tire, the sick kid, the colleague who goes quiet, or the week your motivation just leaves.

Optimism has its uses, and we'd probably get little done without it. But optimism alone doesn't check the plan. At the moment you commit, the only voice in the room is the one that wants this to work.

The trick: pretend it already happened

In 1989, the researchers Deborah Mitchell, J. Edward Russo, and Nancy Pennington ran studies on what they called prospective hindsight. People were asked to imagine that an event had already happened, then explain why. In their results, this framing helped people generate more, and more specific, reasons for the outcome than people who were simply asked what might happen. The improvement was roughly 30 percent in the figures usually cited from that work.

The change in wording looks small. "What could go wrong?" is a question about a cloudy maybe. "It went wrong. What happened?" is a question about a fact, and your mind is good at explaining facts. It reaches for causes, sequences, and details.

The psychologist Gary Klein turned this into a practical tool called the premortem and described it in the Harvard Business Review in 2007. A team about to start a project imagines it has failed, spectacularly, then each person writes down why. Because the failure is assumed, nobody is being negative or disloyal by naming a problem. They're only helping with the story.

Kahneman has praised the idea, partly because it gives permission to doubt. Once a group has settled on a plan, doubters tend to go quiet. A premortem makes doubt part of the exercise.

The tool was built for teams. It works just as well alone, on paper, about your own life.

Why it works better on a page than in your head

You can do a premortem in your head, but you'll probably do a weak version. You'll think "well, it might not work out," feel a small flinch, and move on. The flinch is the whole problem. The mind prefers to leave the uncomfortable thought vague, because vague thoughts don't have to be acted on.

Writing forces the sentence to finish. You can't write "something went wrong" for long. You have to write what went wrong, who was involved, and what you did or didn't do the week before. A vague dread turns into a particular risk, and a particular risk can be handled.

There's a second benefit that people don't expect. It makes the plan feel less scary, not more. Once the worst version has been written down in plain words, it stops lurking. This isn't a claim about any one study. It matches what many people report when they put a worry into specific words.

A word of care, though. The goal isn't to talk yourself out of things. Research by the psychologist Gabriele Oettingen on mental contrasting suggests that pairing a wished-for future with a clear look at the obstacles tends to produce more realistic commitment than dreaming alone. The premortem sits in that same family. It doesn't kill the dream. It gives the dream a route around the rocks.

What a premortem page looks like

Take a real plan you've just started or are about to start. Write the date at the top. Then:

First, write the plan in one plain sentence. For example: "I'm going to finish the first draft of my book by March, writing before work."

Second, write this sentence, in the past tense: "It's next March. The draft isn't done. Here is what happened."

Third, write the story, not a list of vague worries. Let it run. "By February I'd missed eleven mornings. It started when the early meetings moved up to 8:30. I told myself I'd write at night, but I'm useless at night. I got embarrassed about the missed days and stopped opening the file."

Notice how much that contains. There's a schedule conflict, a bad fallback, and a shame spiral. Each of those has a fix that you can only design once you've seen it.

Fourth, circle the two causes that feel most likely, not the most dramatic. Beside each, write one change you could make now.

Your next moves

  • Pick one plan that's still soft. Choose something you've committed to in the last month or are about to start. Skip the big existential ones for now. A new routine, a trip, a hard conversation, or a work project is enough.
  • Set a ten-minute timer and write the failure story in past tense. Start with "It didn't work. Here's what happened." Don't stop to judge it. Let at least one cause be a human one, such as your own habits, a person's mood, or your energy.
  • Underline the cause that made you wince. That reaction usually points at the one you've been avoiding. Write it again in a single sentence at the bottom of the page.
  • Turn two causes into one if-then plan each. For example: "If an early meeting lands on a writing day, then I write for 15 minutes at lunch." Specific if-then plans, which Peter Gollwitzer calls implementation intentions, are better supported by evidence than general resolve.
  • Set a date to reread it. Put a note on your calendar for one month out. When it arrives, check which failures started showing up. Some will, and you'll have a head start.

When to use it, and when not to

A premortem is best at the start, when you can still change things. It's less useful in the middle of a crisis, when what you need is action, and less useful for things you can't influence. Don't use it to stew over events outside your control. That's closer to rumination, which is a different loop.

It also shouldn't be your only page. Pair it with the opposite: a few lines on why it could work, and what you'll be proud of if it does. A premortem is a check on enthusiasm, not a replacement for it.

One more thing deserves saying. Many of the plans that fail do so quietly, without a dramatic collapse. You just stop. The failure story you write today is partly a portrait of that quiet stopping, and naming it is how you make it harder to slide into.

The page remembers what your confidence forgets

The most useful part of a premortem comes later, when you open the page and read it. You'll find that some of what you predicted happened, and some of it didn't, and you'll learn something about how your own mind guesses. People who do this a few times begin to notice their patterns: they underestimate transitions, they overestimate their evening energy, they forget that other people have bad weeks.

That's the kind of knowledge a single page a day is good at storing. In Inkdays, you write one page each day, in ink, and the pages pile up into a record you can check against what you believed at the time. A premortem page fits there naturally: dated, short, and waiting for you to come back and see how right you were. If you'd like a place for that kind of honest page, you can look at Inkdays at https://inkdays.lumenlabs.works. The method works on any paper, though, so start with whatever you have in front of you.