Two friends, Anil and Rekha, start the same year with the same ambition: build a disciplined personal money plan. Neither is a professional. Both write down goals, set up a routine and promise themselves they will stick to it. By the autumn, one plan is quietly holding together while the other has been abandoned. The difference was not intelligence, and it was not luck. It was a single evening in January when Rekha did something Anil skipped: she ran a pre-mortem. What follows puts Anil’s method and Rekha’s method in direct contrast. It is informational only and offers no investment advice or recommendations about any security, strategy or product.

What a pre-mortem means for a personal plan

A pre-mortem asks you to imagine, before you begin, that your plan has already failed. You then jot down each cause that occurs to you. Pessimism is not the goal; people are far better at explaining a failure they believe has happened than at predicting one that might. Optimism is the default setting when we make plans, and it quietly hides the obvious weak spots until they cost real money or real motivation.

Anil: the plan written in a hopeful mood

Anil’s plan was neat. He listed his goal, chose a monthly routine, and promised to review his progress each weekend. He wrote it in an upbeat evening after a good day and felt energised. The plan assumed regular income, a calm mind and steady free time.

Then real life arrived. A busy stretch at work crowded out the weekend reviews. An unexpected family expense disrupted the monthly routine and he had no rule for how to handle it. A few weeks later, feeling behind, he made a hasty change to the plan out of frustration rather than reasoning. By autumn he had stopped looking at it. Nothing dramatic had happened; the plan simply had no defence against ordinary disruption.

Rekha: the plan written after imagining its funeral

Rekha started the same way, with goals and a routine. Then she wrote one sentence at the top of a fresh page: “It is next December and this plan has failed. Why?” She gave herself half an hour and listed everything that came to mind.

• I got busy and stopped reviewing.
• An unplanned expense knocked me off the routine, and I felt too guilty to restart.
• I made big changes after a bad week and lost the thread.
• I never wrote down what “on track” looked like, so I could not tell whether I was.
• I took a friend’s confident opinion as if it were a plan.
• The routine required more energy than I really have on weekday evenings.

She then wrote a response to each. A shorter review that takes ten minutes, so busy weeks do not break it. A written rule for what to do when an unplanned expense appears, decided in advance and in a calm mood. A cooling-off period before changing the plan after a stressful stretch. A clear description of what “on track” means. A habit of treating other people’s opinions as input rather than instructions. And a lighter routine that matches her real energy.

Side-by-side comparison

• Mood when written: Anil’s plan reflects a good day; Rekha’s reflects a deliberate look at her worst days.
• Handling of disruption: Anil’s plan assumed none; Rekha’s has pre-agreed responses.
• Reviews: Anil’s review was long and optional; Rekha’s was brief and fixed.
• Changing course: Anil changed things in frustration; Rekha waits and decides in calm.
• Definition of success: Anil had a vague hope; Rekha had a plain description of what on track means.

A closer look at the guilt problem

One of Rekha’s imagined causes deserves more attention: the guilt that follows a missed week. Many plans do not die from the missed week itself but from the feeling that the whole effort is now spoiled. By naming that reaction in advance, she gave herself a script: a missed review is a missed review, nothing more, and the next one simply takes its place. Anil, lacking a script, treated his first missed weekend as proof of failure and drifted away from the routine altogether.

Where the comparison is honest about its limits

It would be easy to turn this into a neat moral, but plans can still fail for reasons nobody could foresee. A pre-mortem does not guarantee outcomes, and it certainly says nothing about what any market will do. What it improves is the part you control: your routines, your reactions and the clarity of your own rules. That is a modest claim, and a true one.

Borrowing from how engineers think

People who build and release software are used to thinking about quiet failure, especially in the automated steps that carry changes into live systems. If you are curious how they frame it, the DevSecOps Now blog is mostly about securing CI/CD pipelines, written for software and security practitioners. The vocabulary will be unfamiliar, but the instinct carries over to personal planning: automated or habitual processes deserve a moment of suspicion before you trust them.

How to run your own in thirty minutes

1. Write down the plan in a few lines, including what you are trying to do and how often you will check on it.
2. Write one sentence stating that it has failed, and set a timer for fifteen minutes.
3. List every cause that comes to mind, including embarrassing ones such as boredom, distraction or overconfidence.
4. Circle the three likeliest and the three most damaging. Where they overlap, start there.
5. For each circled cause, write a small, specific response you can carry out without heroic effort.
6. Put a date in your calendar for a short look-back, and compare your imagined failures with real ones.

Pairing the exercise with routine and discipline

The pre-mortem works best alongside habits you already trust. Readers who like building structure into their days may find it useful to compare it with how a calm morning routine shapes a trader’s day and with a step-by-step approach to staying disciplined with your trades. Those pieces describe routines; the pre-mortem tests whether a routine will survive contact with a bad week. Used together, they make a plan more robust without making it more complicated.

Who ends up better off, and why

By the following spring Anil admitted he had never really failed at the money plan; he had failed to prepare it for ordinary life. Rekha’s version was not perfect. She missed two reviews and revised one rule. But each stumble had a prepared response, so she never reached the point of quitting. Her plan survived because she spent thirty uncomfortable minutes in January imagining it dead.

That is the whole comparison in a sentence: one plan assumed good weather and the other was written for storms. Before committing to your next plan, spend half an hour on the storms. It costs nothing, and it quietly protects the thing every plan depends on, which is your willingness to keep going.