Name the real decision
Many bad decisions are really good answers to the wrong question. Before you decide anything, it is worth making sure you have named the decision you are actually facing.
The decision that first presents itself is often a surface version of a deeper one. Should I take this job can really be, what kind of life am I trying to build.
When you solve the surface question without seeing the real one beneath it, you can get exactly what you asked for and still feel you chose wrongly.
Naming the real decision means asking, what am I actually trying to decide here, and what larger question is this a single piece of.
It also means separating the decision from the first solution that came attached to it. I need to move house may really be, I need to feel less trapped, which has many possible answers.
A decision well named is already half made, because the right question points toward the options that actually matter and away from the ones that do not.
Watch for decisions that arrive pre-packaged as a single yes or no. That framing often hides the real, wider choice underneath it.
Spend a moment, before deciding, getting the question right. It is the cheapest and most overlooked step in deciding well.
What decision are you facing, and what deeper question might it really be a piece of?
- What am I actually trying to decide here?
- Is this the real decision, or a surface version of it?
- What larger choice is this part of?
Take a decision you are weighing. Write it as a question, then ask what deeper question it is really part of.
A good process can have a bad outcome
It is tempting to judge a decision entirely by how it turned out. But outcomes are shaped by luck as well as by choices, so a good decision can end badly and a poor one can end well.
Judging a decision only by its result is a trap. It rewards recklessness that got lucky and punishes wisdom that got unlucky, teaching you precisely the wrong lessons.
A decision can only ever be made with the information available at the time. Its quality lives in how well you used what you knew, not in facts that arrived later.
This is freeing. You do not control outcomes, which depend partly on chance. You do control your process: how you framed the choice, gathered information, and weighed the options.
Separating the two lets you take sensible risks. A well-reasoned bet that happens to fail was still a good decision, and treating it as a failure would only make you too timid next time.
It also keeps you honest about wins. A careless choice that happened to work is not vindicated by its luck. The process was still poor, and next time the luck may not hold.
The habit is to ask, of any decision, was this a good way to choose given what I knew, kept firmly apart from how it eventually turned out.
Deciding well over a lifetime means investing in the process you control, and making peace with the outcomes you do not.
Where are you judging one of your past decisions by its outcome rather than by how you chose?
- Was this a good way to choose, given what I knew then?
- Am I crediting or blaming luck as if it were judgment?
- What in my process could I actually control?
Take a decision that ended badly. Judge whether the process was sound given what you knew, apart from the result.
Know when the choice must be made
Every decision has a timing question hidden inside it: when does this actually need to be decided. Answering it wrongly, in either direction, causes much of the trouble.
Decide too early and you throw away information that was still arriving. Decide too late and you lose options that quietly expired while you waited.
Many decisions feel more urgent than they are. The pressure to decide now often comes from discomfort with uncertainty rather than from any real deadline.
Others feel less urgent than they are. A choice with a slowly closing window can be delayed until the good options have all gone, without any single moment ever feeling like the deadline.
The move is to find the last responsible moment: the latest point at which you can still decide well, and to keep gathering information right up until then.
Naming that moment turns anxious rushing into patient waiting. You know you have until then, so you can hold the uncertainty without panic and without drift.
It also reveals when to act now. If the window is genuinely closing, hesitation is itself a choice, and usually the worst one available.
Deciding well is partly deciding when to decide: not so early that you waste information, not so late that you waste options.
What decision are you rushing, or quietly letting expire, without asking when it truly must be made?
- When does this actually need to be decided?
- Is the urgency real, or discomfort with uncertainty?
- Am I losing options by waiting, or information by rushing?
Take a pending decision. Identify the last responsible moment to decide it, and plan what to learn before then.
There are usually more than two options
Decisions often arrive framed as two choices: this or that, yes or no, stay or go. That framing feels complete, but it is almost always narrower than reality.
When you feel trapped between two options, the trap is frequently the framing, not the situation. There are usually third, fourth, and fifth options you have not yet let yourself see.
The two-option frame is comfortable because it is simple, and because someone, sometimes you, has already done the work of narrowing. But the narrowing may have cut the best choice.
A reliable move is to force more options: if I could not do either of these, what would I do. The imagined constraint often surfaces possibilities the easy frame hid.
You can also combine, split, or delay. Options are not always mutually exclusive. Sometimes the best choice is part of one and part of another, or a smaller version of both.
Generating options is a separate step from choosing among them, and it works better done separately. Judge nothing while you are still listing. Widen first, narrow later.
More options are not always better to decide among, but they are almost always better to have considered. You cannot choose a path you never let yourself imagine.
Before deciding between two things, spend a little while making sure two is really all there is.
Where do you feel trapped between two options that might be hiding others?
- Is this really only two choices, or just framed that way?
- What would I do if I could not pick either?
- Could the best option combine or delay parts of these?
Take a two-option decision. Force yourself to generate three more options before choosing among any of them.
Every yes spends something
Every choice to do one thing is also a choice not to do everything else you could have done with that time, money, or energy. The cost of a yes is the best no it required.
This hidden cost is easy to ignore because it is invisible. Saying yes to a commitment feels free in the moment, until you notice all the things that yes has quietly displaced.
The real question about any option is not just, is this good, but, is this better than what I am giving up to have it. A good option can still be the wrong choice if it costs a better one.
This is why busy, capable people can still feel their lives are off course. They said yes to many good things, each of which spent the room a better thing needed.
The move is to make the cost visible: for each yes, ask what am I saying no to by doing this. The answer often changes the decision.
It also clarifies priorities. If you cannot bear what a yes would cost you, that is useful information about what actually matters most to you.
This is not an argument against commitment. It is an argument for choosing commitments knowing their true price, so your yeses go to the things worth their cost.
Deciding well means counting not just what an option gives you, but what saying yes to it quietly takes away.
What has a recent yes quietly cost you elsewhere in your life?
- What am I saying no to by saying yes to this?
- Is this better than what it displaces?
- Can I bear what this yes would cost?
Take something you are considering saying yes to. Write down explicitly what that yes would cost you, and weigh it.
Match analysis to reversibility
Not every decision deserves the same amount of care. The right amount of analysis depends heavily on one question: how easily could this be undone.
Reversible decisions can be made quickly and fixed later if wrong. Agonising over a choice you can reverse in a week wastes the very time and energy that hard choices deserve.
Irreversible decisions are the ones worth slowing down for. Where a wrong choice cannot easily be undone, the care you invest before deciding is care you cannot add afterward.
Much decision-making misery comes from getting this backwards: rushing the choices that will stick and endlessly deliberating the ones that could be changed at any time.
The move is to ask early, is this reversible, and roughly how costly to undo. Then set your level of analysis to match, quick for the easily fixed, careful for the permanent.
Treating reversible decisions as experiments is often better than trying to get them perfect. You learn more by choosing, watching, and adjusting than by analysing in the abstract.
For truly irreversible choices, the extra care is not anxiety but respect: you gather more information, imagine failure, and take the time the permanence deserves.
Deciding well means spending your limited attention where it changes things, on the choices you cannot take back.
Where are you over-thinking a reversible choice, or under-thinking an irreversible one?
- Is this decision reversible, and how costly to undo?
- Am I matching my care to its permanence?
- Could I treat this as an experiment instead?
Take a decision. Judge how reversible it is, then set your level of analysis to match, quick or careful.
Use criteria before preference takes over
When we evaluate options, a favourite usually emerges early, and from then on our reasoning quietly works to justify it rather than to test it. Preference arrives before analysis and then hijacks it.
The fix is to decide what matters before you look closely at the options. Name your criteria, what a good choice must deliver, while you are still relatively neutral.
With criteria set in advance, you can hold each option against the same standard, instead of inventing standards on the fly that happen to favour the one you already like.
This is the difference between choosing and rationalising. Rationalising picks the winner first and finds reasons after. Choosing sets the standard first and lets it pick the winner.
Writing criteria down matters, because an unwritten standard drifts to fit your preference without your noticing. A written one holds still and can catch you tilting.
It also reveals what you actually value. Sometimes, listing your criteria, you discover that the thing you were leaning toward does not serve what you say matters most.
This does not banish preference or intuition, which carry real information. It just stops them from doing all the work in secret before the evaluation has even begun.
Deciding well means knowing what a good choice looks like before you fall for a particular one.
Where has a favourite option quietly shaped the standards you used to judge the rest?
- What does a good choice need to deliver here?
- Did I set these criteria before or after picking a favourite?
- Is my leaning serving what I actually value?
Take a decision. Before comparing options, write the criteria a good choice must meet, then judge each against them.
Look at downside, not only possibility
When an option excites us, we tend to picture how well it could go. We rarely spend equal time on how badly it could go, and that imbalance quietly warps the choice.
Possibility is seductive. The best case is vivid and pleasant to imagine, so it fills the mind, while the downside stays abstract and easy to wave away.
But a wise choice weighs the downside honestly: not just whether it could go wrong, but how badly, how likely, and whether you could live with the worst plausible result.
The key question is not, could this succeed, but, if it fails, can I survive the failure. An option with a wonderful upside and a ruinous downside is often a bad bet, however tempting.
This is not pessimism. It is completeness. You are simply looking at the whole range of outcomes rather than only the cheerful end of it.
A useful test is to picture the realistic worst case in detail and ask, could I accept that. If yes, the risk may be worth taking. If no, no upside makes it wise.
Protecting against catastrophic downside matters more than chasing marginal upside, because you have to survive each decision in order to make the next one.
Deciding well means looking clearly at how bad it could get, not only at how good, before you choose.
Where are you drawn to an option's upside without honestly weighing its downside?
- If this fails, how badly, and could I survive it?
- Am I picturing the best case more than the worst?
- Is the downside one I could actually accept?
Take an option that excites you. Describe its realistic worst case in detail and ask whether you could accept it.
Ask what happens after what happens
Most decisions are judged by their immediate result, but the important effects often come later, in the second and third steps that the first one sets in motion.
A choice that solves today's problem can create tomorrow's. Asking only, does this work now, misses the chain of consequences that follows the obvious first effect.
The habit is to ask, and then what. You make the choice, the first thing happens, and then what does that lead to, and then what does that lead to after it.
This simple, repeated question surfaces consequences that first-level thinking misses entirely: the reactions of others, the new situation created, the door this closes or opens.
Many tempting options look good only at the first step. A cut that helps this month but weakens next year, a shortcut that solves one task and creates three, all pass a one-step test and fail a two-step one.
It also finds hidden benefits. Some options look modest at the first step but set off a chain of good second and third effects that the immediate view cannot see.
You do not need to trace the chain forever. Even asking and then what two or three times catches most of the consequences that actually matter.
Deciding well means looking past the first effect to the situation each choice will actually leave you standing in.
Where have you chosen for the first effect without asking what it would lead to next?
- And then what happens after that?
- Does this solve now but cost later, or the reverse?
- What situation will this choice actually leave me in?
Take a decision. Ask and then what three times in a row, following the chain of effects past the first one.
Use probabilities as honest language
Most decisions are made under uncertainty, yet we speak as if outcomes were certain: this will work, that will fail. Probabilities are simply a more honest way to talk about what we do not know.
Saying there is a good chance this works, rather than this will work, is not weakness. It is accuracy. It states how confident you actually are instead of pretending to a certainty you lack.
You do not need exact figures. Rough probabilities, likely, even odds, a long shot, already sharpen thinking far beyond the false certainty of a flat will and will not.
Probabilistic language changes how you decide. A plan you would stake everything on if it were certain looks different once you name it as, say, a two in three chance.
It also protects you from being fooled by outcomes. If you named something a long shot and it failed, you were not wrong to try. The improbable was simply improbable, as expected.
Attaching a probability to your beliefs and predictions makes them checkable. Over time you learn whether your confident calls come true as often as your confidence claimed.
This is not about turning life into arithmetic. It is about replacing false certainty with honest uncertainty, which is a far better basis for deciding.
Deciding well under uncertainty starts with admitting the uncertainty out loud, in the language of probability rather than false guarantee.
Where do you speak in certainties about outcomes that are really uncertain?
- How likely is this, honestly, rather than will it or will it not?
- Am I claiming a certainty I do not have?
- Would a rough probability change how I decide?
Take a prediction behind a decision. Restate it as a rough probability rather than a certainty, and see if the decision shifts.
Expected value compares repeated bets
When choosing between uncertain options, one useful lens is to weigh each outcome by how likely it is, not just how good or bad it would be. A large prize at tiny odds can be worth less than a modest one at good odds.
This is the idea of expected value: the size of an outcome considered together with its probability. It gives a single, comparable sense of what an option is worth on average.
The point is not exact calculation. It is the habit of not being dazzled by a big possible payoff without asking how likely it actually is, or frightened by a rare risk without asking the same.
Expected value thinking is strongest for decisions you make many times. Over many repetitions, the option with the better expected value wins, even if any single instance can go either way.
For one-off decisions it needs care. If a bet has good expected value but a small chance of ruin, the average hides a risk you cannot take, because you only get one try at it.
So pair it with the earlier lesson on downside: a good expected value with a survivable worst case is a sound bet. A good expected value that risks catastrophe is not.
Used well, this lens quietly corrects two common errors: chasing unlikely jackpots and avoiding unlikely disasters, both of which ignore how probability weights the stakes.
Deciding well under uncertainty means weighing outcomes by their odds, while never letting a good average blind you to a ruin you could not come back from.
Where are you drawn to a big payoff, or scared of a rare risk, without weighing how likely each is?
- How large is this outcome, and how likely?
- Is this a decision I make once or many times?
- Does the good average hide a risk of ruin?
Take an uncertain choice. Roughly weigh each outcome by its size and its likelihood, then check the worst case is survivable.
Intuition is compressed experience
Intuition is not the opposite of good decision-making. In the right conditions it is a form of it: the fast, wordless output of experience your mind has compressed into a feeling.
An expert's snap judgment in their own field is often excellent, because it draws on thousands of past cases they can no longer consciously recall but have genuinely learned from.
The catch is that intuition is only as good as the experience behind it. In a field where you have deep, well-tested experience, trust it more. In an unfamiliar one, trust it far less.
Intuition earns its reliability from feedback. Where you have made similar judgments many times and seen how they turned out, the feeling has been trained. Where you have not, it is just a guess dressed as a hunch.
So the question is not, should I trust intuition or analysis, but, is this a domain where my intuition has actually been trained by repeated, honest feedback.
Even trained intuition works best paired with a check. Use the fast judgment to generate an answer, then use slower analysis to test it, especially when the stakes are high.
Be most wary of confident intuition in areas that are new to you, rare, or where feedback is slow or misleading. There the feeling is strong but uneducated.
Deciding well means knowing when your intuition has earned its confidence, and when it is only pretending to.
In which areas has your intuition been trained by real feedback, and in which is it untested?
- Do I have deep, tested experience in this domain?
- Has my intuition here had honest feedback?
- Should I check this fast judgment with slower analysis?
Take an intuitive judgment you are making. Ask whether your experience in this exact area has actually been tested by feedback.
Keep a decision journal
The hardest part of learning from decisions is that memory rewrites them. Once you know how something turned out, you misremember what you actually thought beforehand. A decision journal fixes this.
The practice is simple: before an important decision, write down what you are choosing, why, what you expect to happen, and how confident you are. Then set it aside.
Later, when the outcome is known, you return to what you actually wrote. This is the only reliable way to see whether your reasoning was sound and your confidence was calibrated.
Without a record, learning is corrupted. You will remember predicting whatever came true and forget the rest, so your judgment never really improves however many decisions you make.
The journal turns vague experience into real feedback. Over time it shows your patterns: where you are overconfident, what you consistently overlook, which kinds of choices you handle well.
It does not need to be elaborate. A few honest sentences per important decision, written before you know the outcome, is enough to begin correcting your judgment.
The act of writing also improves the decision itself, because putting your reasoning and expectations into words exposes the gaps that stayed hidden while it circled in your head.
Deciding better over a lifetime depends on honest feedback, and a decision journal is the simplest way to give your future self the truth about your past thinking.
How would your judgment change if you had an honest record of what you actually predicted?
- What do I expect to happen here, and how confident am I?
- Would I remember this accurately once I know the result?
- What would a record teach me over time?
Before your next important decision, write what you expect and how confident you are. Revisit it when the outcome is known.
Do not let the result rewrite the reasoning
Once you know how a decision turned out, a strange thing happens: it starts to feel as though you knew it all along. The outcome quietly rewrites your memory of what you actually thought.
After a success, you remember being sure. After a failure, you remember having doubts. Both memories are usually false, edited by the result to make the outcome seem predictable.
This hindsight makes it nearly impossible to learn honestly, because it hides your real reasoning behind a tidy story in which you saw it coming all along.
It also makes you unfair, to yourself and to others. Judging a past decision as obvious in hindsight ignores that, at the time, the outcome was genuinely uncertain.
The defence is to reconstruct what you actually knew and thought at the moment of deciding, before the result arrived, rather than trusting your reshaped memory of it.
This is exactly what a written record protects, but even without one, you can consciously resist the it was obvious feeling and ask what was really knowable then.
The same care applies when judging others. What looks like a clear mistake now was often a reasonable call under the uncertainty they actually faced at the time.
Deciding well over time means learning from what you truly thought, not from the confident story the outcome writes over it afterward.
Where have you told yourself you knew it all along about an outcome you could not really have predicted?
- What did I actually know at the moment of deciding?
- Is the outcome making this feel more predictable than it was?
- Am I judging a past call fairly, given its real uncertainty?
Take a past outcome you feel you saw coming. Reconstruct what you genuinely knew beforehand, and check whether that is true.
Improve the method, not your self-attack
When a decision goes wrong, there are two responses. One turns on the self: I am foolish, I always get this wrong. The other turns on the method: what in how I decided could be better.
Only the second one actually helps. Self-attack feels like accountability, but it produces shame, not improvement, and shame makes you avoid looking closely at exactly what you most need to examine.
Improving the method is specific and forward-looking. It asks, what step failed, what would catch this next time, rather than passing a verdict on your worth.
This distinction is the difference between people who grow wiser from mistakes and people who just grow more discouraged by them. Same errors, opposite directions.
Harsh self-judgment also distorts future decisions. Afraid of being wrong again, you become either recklessly avoidant or paralysed, neither of which is better deciding.
Treat each poor outcome as information about your process, the way an engineer treats a failure: not who is to blame, but what in the system let this through, and how to fix it.
This is not letting yourself off the hook. It is a higher standard, because improving the method actually reduces future errors, while self-attack just performs regret and changes nothing.
The whole practice of deciding better rests here: review honestly, adjust the method, and treat yourself as someone worth teaching rather than someone to punish.
When a decision goes wrong, do you attack yourself or examine your method?
- What step in how I decided could be better?
- Is this shame, or actual improvement?
- Am I treating myself as someone to teach or to punish?
Take a decision that went wrong. Instead of self-criticism, name one specific improvement to your method for next time.