Decision Frameworks

I can slow down and use a real tool to think through a hard decision, instead of just going with my gut and hoping it works out.

• Sort any hard decision into 'reversible' or 'irreversible' and match how much thinking-effort it deserves to that classification.
• Use the question 'what would have to be true for this to turn out to be a mistake?' to surface hidden risks before deciding on something irreversible.
• Explain why a decision should be judged by the reasoning behind it at the time, not by how it later turned out.

When a hard decision lands in front of you, the real problem usually isn't a lack of thinking — it's thinking in the wrong shape. Most people give every decision the same nervous energy, whether it's picking a grocery brand or quitting a job. That's backwards. The amount of thinking a decision deserves should depend on one simple thing: how hard it would be to undo.

That's the first tool — the Reversibility Filter. Ask yourself: if this goes wrong, can I fix it easily and cheaply? A reversible decision is one you can walk back — trying a new grocery brand, switching a small SIP amount. These deserve light thought, because even a wrong call costs you almost nothing to correct. An irreversible decision is hard or costly to undo — quitting a job, taking a large loan, signing a long lease. These deserve careful, deliberate thought, because a mistake here sticks around.

Once it's flagged irreversible, gut feeling alone isn't enough anymore.

Once a decision is flagged as irreversible, gut feeling alone isn't enough — you need a way to pull hidden risks out into the open before you act. That's the second tool: the Pre-Mortem Question. Before deciding, ask, "What would have to be true for this to turn out to be a mistake?" Answer it honestly and specifically. This question forces you to imagine failure in advance and list the real conditions that could cause it — things your gut, focused on how excited or anxious you feel right now, would skip right past.

Here's the part that makes both tools usable without fooling yourself: judge the decision by the reasoning you did at the time, not by how it later turned out. This is Process vs Outcome. A carefully reasoned decision can still fail — the startup can run out of money, the market can turn — and that failure doesn't mean your thinking was bad. Likewise, a reckless decision can get lucky, and that luck doesn't mean it was wise. If you only score yourself on outcomes, you'll learn the wrong lessons: you'll get overconfident from lucky wins and needlessly scared of good bets that happened to lose.

None of this promises you'll be right. What it does is put you in a position to say, honestly, "I thought this through" — and that's the one part of the decision you actually control.

Vikram has a stable job, but a friend has just asked him to join a new startup — for less pay in year one, but with equity if it works out. His gut says "exciting, go for it." Instead, he stops and runs it through the Reversibility Filter first: quitting his job means losing steady income, and with rent and EMIs to cover every month, undoing that decision quickly isn't realistic. It's clearly irreversible. That alone tells him this isn't a decision to make on excitement — it deserves careful thought.

So he asks the Pre-Mortem Question: "What would have to be true for this to turn out to be a mistake?" Sitting with it honestly, he lists three things: the startup running out of funding within six months, him having no emergency fund to cover an income gap, and the actual role turning out different from what was described in the interview.

None of those three thoughts showed up when he first felt excited about the offer. Because he named them, he now knows exactly what to check before saying yes: the startup's runway, a written role description, and time to build a three-month emergency fund first.

Vikram might still join, and the startup could still fail — the framework never promised it wouldn't. But whatever happens next, he'll be able to trace the decision back to real reasoning, not a leap of faith.

Point: Applying the Reversibility Filter and the Pre-Mortem Question changes the depth and content of a person's thinking before they decide — surfacing risks a gut call would have missed — even though it cannot guarantee the outcome will be good.

These two tools aren't a formula that spits out the "correct" answer — they're reusable questions you bring to any hard decision. Reversibility and stakes work together: a decision can be technically reversible but still high-stakes (like undoing a big investment at a painful loss), so use judgment, not just the reversible/irreversible label, to decide how much care it deserves. And this unit deliberately stops here — combining multiple frameworks, running formal decision trees, or reviewing a string of past decisions to sharpen your judgment over time are real skills, but they build on this foundation later. For now, the goal is just to reach for one of these two questions instead of pure gut feeling.

• Treating a decision framework like a formula that guarantees the right outcome. — Frameworks are often presented as neat checklists, so it's easy to expect them to work like a formula that always gives a correct answer. Fix: Remember a framework only sharpens your thinking under uncertainty — the outcome can still go wrong even when the process was sound.
• Judging a past decision as 'bad' just because it turned out badly (or 'good' just because it worked out). — The outcome is visible and immediate, while the reasoning behind it is invisible, so it's the easiest thing to judge by. Fix: Separate process from outcome — ask what you knew and how you reasoned at the time, not just what happened afterward.
• Giving every decision, big or small, the same amount of careful deliberation. — People assume being 'responsible' means always thinking hard, so they either overthink small choices or rush big ones out of habit. Fix: Check reversibility first — let light decisions stay light, and save the Pre-Mortem Question for the ones that are hard to undo.

• Before deciding, ask: how hard would this be to undo? Reversible decisions deserve light thought; irreversible ones deserve careful thought.
• For irreversible decisions, ask: 'What would have to be true for this to turn out to be a mistake?' — it surfaces risks gut feeling misses.
• Judge a decision by the reasoning behind it at the time, not by how it later turned out — that's what you actually control.
• Frameworks sharpen judgment under uncertainty; they never guarantee a good outcome.
• These two tools work on any hard decision, not just financial ones.

Q1. What is the 'Reversibility Filter' used for?

• Sorting a decision as reversible or irreversible to decide how much thinking-effort it deserves
• Calculating the exact financial cost of a wrong decision
• Predicting whether a decision will turn out well or badly
• Choosing between two investment options based on returns Answer: Sorting a decision as reversible or irreversible to decide how much thinking-effort it deserves — The Reversibility Filter simply asks how hard a decision would be to undo, so you know whether it deserves light thought or careful thought.

Q2. The Pre-Mortem Question asks: 'What would have to be true for this to turn out to be a mistake?' Answer: True — That's exactly the sharpening question used before an irreversible decision — it helps surface hidden risks a gut call would miss.

Q3. Rohan carefully thought through a decision to switch jobs, listing possible risks and checking his savings first. The new job didn't work out due to a company shutdown a few months later. What does this unit's Process vs Outcome idea say about Rohan's decision?

• His process was still sound; a bad outcome doesn't mean his thinking was bad
• His process must have been flawed since the outcome was bad
• He should have skipped thinking and just trusted his gut instead
• The framework failed him, so frameworks don't work Answer: His process was still sound; a bad outcome doesn't mean his thinking was bad — A good decision process can still lead to a bad outcome because of factors outside anyone's control, like a company shutting down. Judge the reasoning, not just the result.

Q4. Priya is deciding whether to sign a 3-year rental lease for a shop versus trying a new flavor at her small food stall for a week. According to the ideas in this unit, how should she think about these two decisions?

• Give the lease careful thought and a pre-mortem check since it's hard to undo; give the flavor trial light thought since it's easy to reverse
• Give both decisions the exact same amount of careful thought, since both involve her business
• Skip thinking about the lease entirely since frameworks can't guarantee the shop will succeed
• Give the flavor trial more thought since it happens sooner Answer: Give the lease careful thought and a pre-mortem check since it's hard to undo; give the flavor trial light thought since it's easy to reverse — The lease is hard and costly to undo, so it deserves careful thought and the pre-mortem question. The flavor trial is cheap and easy to reverse, so light thought is enough — matching effort to reversibility.

Q5. Kabir is about to co-sign a friend's business loan: "It's not a big deal, I can always ask the bank to remove my name later if he's late on payments." Is this actually a two-way door? Reveal: Weak: agrees — he can just ask to be removed later. Strong: recognizes co-signing isn't reversible on his own timeline — the bank has no obligation to release him, so his liability stays exposed regardless of his friend's promises. A decision that feels reversible can still be a one-way door.