Hard decisions need a process, not more agonising
A hard decision is a choice between options where the route across is not obvious and the stakes are real. Under that pressure, most people either freeze or lunge at the first option that relieves the discomfort. Neither is thinking. What actually helps is a repeatable process that makes your reasoning visible — to others, and to yourself later, when you have forgotten what you actually knew at the time. Here is one you can reuse.
1. Define the real decision
Most poor decisions go wrong here, before any weighing begins, because the question itself is malformed. Write down the current state, the desired state you want, and the constraints any answer must respect. Then check for a solution in disguise: a decision framed as "should we do X?" when the real question is "how do we achieve the underlying goal?" Framing it as X has already thrown away every other option. Ask what problem this decision is actually meant to solve, and let that reopen the field.
2. Generate options before judging them
Separate generating options from evaluating them; doing both at once kills the good ideas early. Push for more than the two that first present themselves — a binary is usually a sign the framing is too narrow. And always include doing nothing as an explicit option. The status quo is a choice with its own costs, not the neutral absence of one, and it is the option that never gets scrutinised unless you force it onto the list.
3. Set your criteria before you score
Decide what a good answer looks like before you compare options, so the standard is not quietly bent to justify a choice you have already fallen for. Distinguish objectives — things you want more of, measured in more-or-less — from constraints, which any option must simply pass or fail. For a weighted decision matrix, give each criterion a weight reflecting how much it matters. The weighting is where the real thinking happens: deciding that learning matters twice as much as salary is itself the decision, and making it explicit lets someone disagree with that rather than with your conclusion.
4. Weigh the trade-offs honestly
Every option gives something up. If you cannot name the trade-off, you have not understood the option. Watch for the "we will do both" evasion — occasionally true, but usually it just means the cost has moved somewhere less visible, into timelines, quality, or people's attention. Account for opportunity cost too, especially attention: the scarcest resource and the least tracked. Every project you accept is several you have declined, whether or not anyone says so.
5. Handle uncertainty deliberately
Separate risk (how likely the bad case is) from downside (how bad it is). The useful question is not "how likely is failure?" but "what happens if it fails, and can I continue?" Some outcomes are ruinous — they end your ability to keep going — and you cannot average your way out of them, so cap the downside first, then optimise the upside. Expected-value reasoning is useful for repeated, modest-stakes bets, but it is blind to ruin: a positive-value bet that can end the series is not a good bet. Before committing to anything hard to reverse, run a premortem: imagine it is a year later and the decision failed badly, then write the story of why. That question surfaces the quiet doubts that "what could go wrong?" never does.
Match the effort to the stakes. A cheaply reversible, two-way-door decision deserves speed — decide, try it, adjust. A one-way door that is hard to undo deserves the full treatment, plus a written record.
6. Judge the decision, not just the outcome
Two traps quietly corrupt this. Sunk cost is continuing because of money or effort already spent; but past spending cannot be recovered by either choice, so only future costs and benefits should count. Resulting is judging a decision by how it turned out. It is intuitive and wrong: under uncertainty, sound decisions sometimes get unlucky and reckless ones sometimes get away with it. A good decision is one made well with the information available; a good outcome is what happened. Keeping them apart is what lets you learn from reasoning rather than from luck.
The fix for both is a decision journal. Before the outcome is known, write down what you decided, why, what you expect, and what would tell you it was wrong. When the result arrives, compare against what you actually predicted — not against a reconstruction, because hindsight quietly rewrites what you believed. It takes about three minutes and is the highest-return habit in the whole subject.
Keep learning: work through MegaMaester's Problem Solving and Decision Making lessons to practise building criteria, running premortems, and keeping a decision journal.