On the night you decide to change your life, the plan is always flawless. You will wake at 6:30, write for forty minutes, stretch, and eat something with protein in it. You can see the whole thing, calm and well lit, like a photograph of a person you are about to become.

Then Thursday happens. A child is up with a fever, or a deadline moves, or you simply slept badly. By Friday the photograph has curled at the edges, and by the following week you are quietly explaining to yourself why the plan was probably too ambitious anyway.

Here is the uncomfortable part. Thursday was not a surprise. You have had Thursdays your whole life. You just did not let them into the room while you were planning.

Why plans are written by your best self

We make habit plans in a particular mood: hopeful, rested, a little inspired. In that state, the future feels clean. Psychologists who study construal level, notably Yaacov Trope and Nira Liberman, have shown that events far away in time tend to be represented abstractly, in terms of the big why, while near events are represented concretely, in terms of messy how. A routine that starts next Monday is still abstract. It has no traffic, no tiredness, no inbox.

Add the well-documented planning fallacy, our tendency to underestimate how long and how hard things will be, and you get a plan built entirely from the best-case scenario. It is not a lie exactly. It is a plan with the weather left out.

The usual fix is to "be realistic," which is advice nobody can follow, because realism is exactly what the abstract mind cannot produce on demand. You need a method that forces the concrete details to show up.

The pre-mortem

A medical post-mortem happens after the patient has died, to find out why. The psychologist Gary Klein proposed turning that around for projects: a pre-mortem. Before you begin, you imagine the project has already failed, and you ask what went wrong.

The idea rests on a finding from Deborah Mitchell, J. Edward Russo, and Nancy Pennington in 1989. They found that when people imagine an event has already happened and then explain why, they generate more and better reasons than when they merely consider what might happen. Their work on what they called prospective hindsight reported roughly a 30 percent improvement in the ability to identify reasons for future outcomes. Klein popularized the technique for teams, and Daniel Kahneman later called it one of the few debiasing methods he was genuinely enthusiastic about.

Why does a small change in grammar do this? Two things shift at once.

First, certainty changes the task. "What could go wrong?" invites a shrug and a vague answer. "It went wrong; explain it" asks your mind to do what it is superb at, which is telling a causal story about something that already happened.

Second, it gives you permission. In a hopeful planning mood, naming a weakness feels disloyal, like jinxing it. The pre-mortem reframes doubt as the assignment, so pessimism becomes useful rather than defeatist.

Applying it to a habit, not a company

Klein's method was built for teams and big projects, but a habit is a small project with a single stakeholder who is very good at excuses. The adaptation is simple.

Pick the habit. Then write the sentence: It is six weeks from now and I have completely stopped. What happened?

Do not edit. Let your future self, the one who failed, be specific and a little petty. The useful answers are almost never "I lacked motivation." They tend to look like this:

  • The 6:30 slot collided with the school run on Tuesdays and Thursdays, and I never decided what to do about it.
  • I got sick for four days, and restarting felt like admitting the streak was dead.
  • The habit depended on my laptop being open, and my laptop lives in the other room.
  • I put it right after a coffee I don't always make.
  • I started at forty minutes. By week three, forty minutes felt like a verdict.

Notice what these are. They are not character flaws. They are scheduling collisions, missing contingencies, and design errors, and every one of them is fixable in advance, which is the whole point.

From failure story to design change

A list of ways to fail is only half the work. A pre-mortem pays off when each failure gets a response, a specific change to the plan.

There are really three kinds of fix:

Remove the cause. If Tuesday and Thursday mornings are structurally taken, don't schedule the habit there. A routine that is honest about the calendar beats one that is ambitious about it.

Shrink the commitment. If the failure story says "the full version felt like a verdict," build a floor, a version so small you can do it on your worst day. Five minutes counts. The floor protects the identity of someone who shows up, even when the ceiling is out of reach.

Pre-decide the response. For failures you can't prevent, such as illness or travel, write the restart rule now: If I miss a day, the next day I do the floor version, no discussion. This is the logic behind implementation intentions, the if-then plans studied by Peter Gollwitzer, aimed at the exact moment you are most likely to spiral.

That last one matters more than it looks. Much of what we call "falling off" is not the missed day but the story we tell about it. A pre-mortem moves that conversation to a moment when you are calm and kind, instead of leaving it to a guilty Friday.

One caution

This is not a license to catastrophize. The point is not to feel dread; it is to extract information. Give yourself ten minutes, write down five or six plausible failure stories, and stop. If the exercise starts to make you feel that you will certainly fail, you have drifted from planning into rumination. Close the notebook and make the fixes.

Also, don't mistake it for mental rehearsal of success. Imagining the triumphant version tends to feel good and teach nothing. The pre-mortem is deliberately the opposite: unglamorous, specific, and mildly uncomfortable. That discomfort is the sign it is working.

Your next moves

Try this today, with a habit you're starting or have already quietly abandoned:

  • Write the failure date. On paper, write: "It is six weeks from now and I've stopped [habit]. Here is exactly what happened." Set a ten-minute timer and write at least five specific causes. Specific means a day, a place, or a moment, not "I got busy."
  • Circle the two most likely. Don't try to fix everything. Pick the two stories that felt most uncomfortably familiar. Those are your real risks.
  • Make one design change per risk. Move the time, change the location, attach it to a more reliable cue, or put the needed object where you will trip over it. Write the change beside the risk.
  • Define your floor. Write the smallest version of the habit that still counts, and commit that on your worst day you will do only that.
  • Write your restart rule. Complete this sentence and keep it where you will see it: "If I miss a day, then tomorrow I will ______." Decide the answer now, while you are calm.

Where a tool can help

A pre-mortem is a one-time insight, but its fixes need to live somewhere you actually look. The weak points it finds are usually about sequence and timing: what comes right before the habit, and how much room you've left for it. That is the part Tally is built around. It pairs habit stacking, anchoring a new behavior to an existing one, with a Pomodoro-style focus timer, so the small floor version of your habit has a trigger and a boundary rather than relying on a good mood. If you're curious, you can see how it works at tally.lumenlabs.works. But the exercise above works with a pen and a bad memory of last January, and it's worth doing either way.