How does "Score decision quality separately from outcome quality" work?

"Resulting" — Annie Duke’s term for judging decisions by outcomes — is the most common way people learn the wrong lesson. In uncertain domains, a bad process can produce a good outcome by luck, and a good process can produce a bad outcome by bad luck. Scoring the process separately ("was the reasoning sound given what I knew?") breaks this conflation and protects the actual signal from noise.

How does "Run a weekly decision review session" work?

Decisions and their outcomes are separated in time, which means feedback is only useful if you create a deliberate moment to receive it. Without a regular review ritual, entries in a decision journal never get closed, outcomes never get compared to predictions, and the feedback loop — the only reason to keep the journal — never closes. A weekly cadence is frequent enough to keep the reasoning fresh and infrequent enough not to feel onerous.

How does "Classify decisions by reversibility and stakes" work?

Most people apply roughly the same amount of deliberation to all decisions, which means they over-deliberate on trivial ones (analysis paralysis) and under-deliberate on high-stakes irreversible ones (defaulting to intuition). Jeff Bezos’s "two-door" framing captures the principle: reversible decisions (door one) should be made quickly and corrected if needed; irreversible ones (door two) deserve much more deliberation because they can’t easily be undone.

How does "Track your calibration across many predictions" work?

A single decision tells you almost nothing about your decision-making quality — outcomes are too noisy. Calibration — the match between stated confidence and actual accuracy — only becomes visible across many predictions. If you say "80% confident" across 20 decisions and are right only 50% of the time, you are systematically overconfident at that level, and the journal gives you the data to see it.

How does "Log the information you wished you had" work?

Decisions made under uncertainty are limited by information gaps. Most people experience these gaps vaguely ("I just wasn’t sure") without articulating what specifically was missing. Naming the exact information gap does two things: it clarifies how the gap could have been filled before deciding, and it reveals, after the outcome, whether filling it would have changed the decision — which is a direct test of whether the gap actually mattered.

Annie Duke

What is decision journaling and how does it improve decision quality?

How to build a personal feedback loop for the decisions that actually matter

Short answer

A decision journal is a written record of significant decisions — what you decided, why, what you expected to happen, and what actually happened. It counteracts hindsight bias and outcome bias by preserving your actual reasoning before the outcome arrives, and it creates the only feedback loop that produces real calibration: comparing your predictions to results across many decisions over time.

Most people never find out if they’re good at deciding. A single decision rarely produces clean feedback: outcomes are noisy, attribution is murky, and hindsight rewrites what you thought you knew at the time. A decision journal fixes this by creating an external record — before the outcome — that you can score honestly later. Annie Duke calls this "resulting" avoidance: refusing to judge the quality of a decision only by whether it worked out. The practices below build the habit of logging, reviewing, and calibrating from your own decision history.

The practices (6)

Why it works

Hindsight bias overwrites the memory of your pre-decision reasoning with knowledge of what actually happened, making bad decisions look smart in retrospect (if lucky) and good decisions look naive (if unlucky). Writing the reasoning down before the outcome creates an immutable external record that the bias cannot reconstruct. This is the foundational move of decision journaling: without it, you have no ground truth to review.

How to do it

1For any significant decision, write: the decision, the date, your reasoning in 2–4 sentences, and your expected outcome.
2Assign a rough confidence level (e.g., "70% confident this will succeed in the next six months").
3Note what information you do not have that you wish you did.
4Close the entry and do not revisit it until the outcome arrives.

Evidence

Mechanistic

Pre-outcome recording directly counteracts hindsight bias, which is one of the most replicated biases in the judgment literature. The mechanism is simple and structural: you cannot rewrite a written record the way you can rewrite a memory.

Honest caveat: Pre-logging prevents hindsight rewriting; whether the logging habit translates into better future decisions depends on the quality of the review and whether lessons are actually extracted and applied.

— Fischhoff (1975), "Hindsight ≠ Foresight", Journal of Experimental Psychology — establishes the bias that pre-logging counteracts

Common mistake: Logging only the conclusion ("I decided to hire her") without the reasoning, which leaves no material to review when the outcome arrives. The reasoning — not the decision — is what you’re preserving.

Go deeper on this practice →

Practice this with IX Coach

Reading about a practice changes nothing on its own. IX Coach turns these into a guided, adaptive routine — discerning where you are in real time and walking the practice with you, session after session.

Start with IX Coach →