Result ≠ Decision

Say this

Good decision, or just a good result?

Do this now 3 min

Pick a recent decision. Write two columns: "What I controlled (process)" and "What I didn't (luck/context)." Judge yourself only on the first column.

Use when

You're evaluating a past choice and feeling either smug or regretful about the outcome.

Avoid when

The outcome clearly resulted from a process failure — don't use this to excuse sloppy thinking.

Why it works

Judging decisions by outcomes teaches you to be lucky, not skilled — separating process from result is how real calibration happens.

A perfect decision can produce a terrible outcome. A reckless decision can produce a great one. If you judge yourself by results alone, you’re training yourself to be lucky rather than skilled. The two-column exercise — what I controlled vs what I didn’t — separates signal from noise. Over time, this builds something rare: the ability to trust your own judgment regardless of short-term variance. It also protects against the opposite trap: taking credit for good outcomes that were mostly luck.

Go deeper · 8 min read

Outcome Bias: Why Judging Decisions by Results Teaches You to Be Lucky, Not Skilled

A bad result makes a sound call look reckless, and you feel the contempt before you can stop it. Knowing luck was involved barely helps. Here is what to do about the part you can still control.

Result ≠ Decision

One tool a week

One tool a week