Skip to content
BodhiProtocol

A Good Decision Can Still Lose

Surya · 3 min read

Decision Makingprobabilityjudgment
DECISION QUALITY × OUTCOME
GOOD OUTCOMEBAD OUTCOMEGOOD CALL
Deserved Win
Bad Beat
BAD CALL
Dumb Luck
Deserved Loss
2 OF 4 GET MISJUDGEDGRADE THE PROCESS

A decision and its outcome are two different things, separated by everything that was genuinely unknown at the moment you made the call. The instinct is to grade the decision entirely by how it turned out anyway — because the outcome is the only part you can actually see, and the reasoning that led there is easy to forget once you know the ending. That instinct has a name, and it's quietly one of the most expensive habits in judgment.

Poker players have a word for the trap you don't

Poker players call it resulting: treating the outcome as proof of the decision's quality. A player who goes all-in holding the statistically correct hand and loses to a lucky card on the river made a good decision with a bad outcome. A player who calls a terrible bet on a hunch and happens to win made a bad decision with a good outcome. Confuse the two — grade the decision by the outcome alone — and you learn exactly the wrong lesson from both of them: punish good judgment for bad luck, and reward bad judgment for good luck.

Two axes, not one

The honest way to evaluate a decision needs two separate axes: was the decision itself sound given what was knowable at the time, and did the outcome happen to be good or bad. Cross them and four cases appear, and only two of them are what they look like on the surface. A good decision with a good outcome is a deserved win — no surprise there. A bad decision with a bad outcome is a deserved loss — also no surprise. But a good decision that still loses is a bad beat, not proof the decision was wrong. And a bad decision that happens to win is dumb luck, not proof the decision was right. Those middle two cases are where almost all bad self-evaluation lives.

Most of a single outcome isn't yours to claim

Under genuine uncertainty — not a labeled deck where you can calculate exact odds, but a real unknown future — even the right decision only shifts the odds in your favor. It doesn't guarantee the result. A sound process can still land in the unlucky 20% of outcomes; a careless one can still land in the lucky 20%. One event tells you almost nothing reliable about whether the reasoning behind it was good, because a single draw from a probability distribution was never designed to reveal the distribution itself.

Grade the process, not the scoreboard

The practical discipline is to write down the reasoning and the odds you believed before the outcome is known, then evaluate the decision against that written reasoning specifically — not against how things happened to turn out. If you only review a decision after you already know the ending, you're not evaluating judgment anymore. You're rationalizing a result that's already fixed, and calling it analysis.

The one-question check

Before calling a decision good or bad based on how it turned out, ask: would I have made the same call if I'd made this decision a hundred times, most of which I'll never get to see the ending of? If the honest answer is yes, a bad outcome doesn't retroactively make it a bad decision — and if the answer is no, a good outcome doesn't retroactively make it a good one either.