The Decision Journal Advantage: Write It Down Before You Decide

Why Writing a Decision Down Changes the Thinking Behind It

Decision journalling brings clarity.

Writing pressures you to find the right words. The clarity you thought you had disappears the moment you have to defend it in writing.

Jargon and loose thinking hold up in conversation. On a page, they don't.

Shane Parrish captures it precisely in Clear Thinking: writing makes the invisible visible.

A decision journal also creates a gap. It sits in the space between stimulus and response — between the pressure to act and the moment of choosing. Writing a decision down means you respond with intention rather than react in haste.

That habit of writing before deciding is the foundation of reflective decision making — and it compounds over time. As a leader, your best decisions are the ones you understand. Writing is how you get there.

What the Evidence Says About Decision Journalling

Most leaders believe they are thinking clearly when they decide. The research suggests otherwise.

Daniel Kahneman's work on fast and slow thinking shows why. Under pressure, the brain defaults to System 1 — fast, automatic, and pattern-driven.

It feels like reasoning. It rarely is.

Engaging the slower, more deliberate System 2 requires effort, and that effort needs a trigger. Writing is one of the most reliable triggers available.

Philip Tetlock's research on forecasting accuracy points in the same direction. Across studies involving thousands of forecasters and millions of predictions, one habit consistently separated better judgment from worse: writing predictions down before an outcome is known, then returning to measure them against what actually happened.

Tetlock found that accountability to your own written record — not intelligence, not experience — was the practice that improved judgment over time. A decision journal is how a leader builds that accountability into their own process.

What the evidence shows is straightforward: decision journalling improves decision making not by making you smarter, but by making your thinking visible before it hardens into a choice. That's a discipline, but not every leader maintains it.

How to Keep a Decision Journal — What One Entry Looks Like

Most leaders know what they decided, but few know what they were actually thinking when they made it.

A single entry changes that. It doesn't need to be long, but it does need to be honest.

Start with the decision itself — stated plainly, in a sentence your managing director could read and immediately understand. In that peak season entry, it was one line: the problem is capacity, not quality. If you can't write it that cleanly, you don't yet understand what you're deciding.

Then write what's at stake — not in the abstract, but specifically. Who is affected, what changes, and what doesn't change if you get this wrong.

For decisions that can't easily be undone, that question deserves more weight than it usually gets. Reversibility shapes how much time a decision deserves — and most leaders skip that question entirely.

Next, write the alternatives you considered — not just the one you're leaning towards, but the ones you dismissed and why. The option you rejected quickly is often the one that reveals most about your assumptions.

Write your reasoning — why you're leaning in a particular direction, what information you're relying on, and what you're assuming to be true. What uncertainty are you deciding into, and are you being honest about how much you don't yet know?

Note your emotional state and the external pressures present. In that peak season entry, it was the weight of years of failed fixes, a managing director who had run out of patience, and the fear of the same conversation repeating next year.

These factors shape decisions more than leaders care to admit. Writing them down keeps them from disguising themselves as logic.

Then write your prediction. Don't do what most leaders do and skip it — make a considered one on what you genuinely think could happen.

A prediction isn't a conclusion. It's a hypothesis.

Before the modelling began, the entry captured a specific suspicion: our engineers were working at roughly six jobs per day — that was the baseline. During peak season, the top 20% of service providers — the ones handling 80% of the volume — were running at double that rate. If that held, the problem wasn't engineer quality but volume no one could absorb.

The journal captured that reasoning before the data confirmed it. When the modelling came back and proved the hypothesis, the entry already existed as an honest record of what had been thought, and why, before the answer was known.

That's what separates a prediction from a rationalisation. Writing it down before the outcome is known is the whole discipline — without it, the review that follows has nothing honest to measure against.

A complete entry looks like this:

Decision: What I am deciding, in one sentence.
Stakes: What changes, and for whom.
Alternatives: Options considered and why they were set aside.
Reasoning: Why I'm leaning this way, and what I'm assuming.
Uncertainty: What I don't yet know that could change this.
Emotional state: What external pressures are present.
Prediction: My hypothesis, stated specifically, before the outcome is known.

The entry is only half the practice. What you do with it next is where the real work begins.

The Review — Where the Journal Pays Off

Most leaders make decisions. Fewer review them. That gap is where experience stops compounding.

The journal entry is not the practice. It's the raw material.

Set aside time — monthly works for most, quarterly at minimum — to go back through what you wrote. Not to judge the outcomes. To compare what you predicted with what actually happened, and to ask whether the gap between the two was luck, circumstances, or something in your reasoning you haven't yet named.

Jim O'Shaughnessy, investor and founder of O'Shaughnessy Asset Management, has kept written journals throughout his career for precisely this reason. With a written record, he has noted, hindsight bias cannot take hold — because there, in your own hand, is what you actually thought at the time. Memory cannot revise what the page already holds.

That's the protection the review offers. Without it, every decision you look back on will seem more inevitable than it was. The reasoning you actually used gets quietly replaced by the reasoning you wish you'd used.

What to look for when you review: decisions made under time pressure that went wrong in a predictable direction. Predictions that were consistently optimistic, or consistently cautious. Alternatives you dismissed quickly that turned out to be right. These aren't random errors — they're patterns, and patterns are learnable.

The discipline of reviewing your decisions is what turns a journal into a learning system. Without the review, you're keeping a record. With it, you're building judgment.

Over time, the review does something else. It changes how you write the entry in the first place.

Knowing you will return to it — knowing your future self will compare prediction against outcome — makes the entry more honest. You stop hedging. You write what you actually think, not what sounds reasonable.

That shift is what separates leaders who keep improving from those who simply accumulate years.

The next significant decision you make — do you have somewhere to write it down before you make it?