Log the information you wished you had
In every decision entry, write: what would I want to know that I don’t?
Why it works
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.
How to do it
- In your decision log entry, write: "What I wished I knew that I didn’t" in one or two sentences.
- Note whether that information was available and you didn’t seek it, or genuinely unavailable.
- After the outcome, revisit: would having had that information changed your decision?
- If yes, build a checklist of information to gather before similar decisions in the future.
Evidence
Explicitly naming decision-relevant unknowns aligns with research on prospective memory and with intelligence analysis practices, where structured protocols for identifying information gaps are standard. The practice converts vague uncertainty into actionable questions. (mechanistic)
This is a principled practice derived from structured analytic techniques rather than a tested personal-decision intervention. Its value is in building the habit of knowing what you’re estimating versus what you’ve verified.
Common mistake
Listing information you didn’t have that turned out not to matter, rather than the gaps that actually determined the outcome. The retrospective check — "would it have changed my decision?" — is what makes the log useful.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Decision Journaling: Learning to Decide Better Over Time
- Log the decision before the outcome
Write what you decided, why, and what you expect — before you know how it turns out.
- Score decision quality separately from outcome quality
Judge the process you used — not whether it worked — when you review a past decision.
- Run a weekly decision review session
Set aside 20 minutes each week to score past decisions and extract one lesson.
- Classify decisions by reversibility and stakes
Sort decisions into low-stakes/high-stakes and reversible/irreversible before deciding.
- Track your calibration across many predictions
Score your confidence levels against outcomes over dozens of predictions to find your systematic biases.
Related concepts
- Hindsight Bias: Why Everything Seems Obvious in Retrospect
How "I knew it all along" corrupts judgment — and the practices that correct it
- Survivorship Bias: Learning from What You Can’t See
The invisible graveyard of failures — and how to reason from the full distribution
- Thinking, Fast and Slow, Made Usable
Two systems, the biases they create, and when to slow down