Process, Not Outcome
A good decision can lead to a bad result, and a reckless one can get lucky. Judging your choices only by how they turned out — “resulting” — teaches exactly the wrong lessons.
Under uncertainty, the decision and the outcome are two different things. You control the process — what you knew, how you weighed it, the odds you faced. You don't control which branch of the future actually arrives. A sound bet can lose; a foolish one can win.
Separating the two makes you a better decider over time. If you grade every choice by its result, you'll punish good decisions that got unlucky and reward bad ones that got lucky — slowly training yourself toward whatever happened to work last time.
The trap is called resulting: reading the quality of a decision backward from its outcome. It feels like accountability but it's just hindsight. The real question after any result is not “did it work?” but “given what I knew then, was it a good bet?”
Grade the decision, not the dice
Reconstruct what you knew at the time
Before judging a past choice, rebuild the information you actually had when you made it — not what you learned afterward. A decision can only be graded fairly against the fog it was made in.
Ask if it was a good bet, then
With that information restored, ask whether the odds and stakes justified the choice at the moment. A losing result from a favorable bet is bad luck, not a bad decision.
- Was the reasoning sound with what I had?
- Or am I just reacting to how it landed?
Keep the two ledgers separate
Track decision quality and outcome quality as different columns. Praise good process even when it loses, and stay suspicious of good results that came from bad process — those are the ones that ruin you next time.
Luck decides the outcome of any single bet. Only your process decides the outcome of a thousand of them.