How to keep a decision journal without it turning into a diary
A decision journal has one job: capture what you expected before you found out what happened, so you can later tell whether you were actually right or just got lucky. A diary has a different job, recording how a day felt. Both are worth keeping. The trouble starts when they merge, because a diary that has swallowed a decision journal is comfortable to keep and useless to reread — and a decision journal that has swallowed a diary is exhausting to keep and gets abandoned within a month.
What a decision journal is actually for
The value of the format is narrow and specific: it lets you separate the quality of a decision from the quality of its outcome. Most people never make that separation, so a good decision that happened to go badly gets filed as a mistake, and a reckless decision that happened to work gets filed as good judgment. Neither lesson is true, and both get reinforced anyway, because nothing was written down at the moment you didn't yet know the ending.
An entry written before the outcome exists is a snapshot of your actual reasoning, uncontaminated by what happened next. Read it back after the fact and you are grading the thinking, not the luck. That is the entire mechanism. It does not require much writing. It requires writing at the right moment, about the right things, and almost nothing else.
Where it starts turning into a diary
1. Every decision gets an entry, not just the ones with stakes
The instinct to be thorough is the first thing that kills a decision journal. If you log what you had for lunch, which route you drove, and which reply you sent to a group chat, the file fills with decisions that carried no real uncertainty and cost nothing to get wrong. Skimming for the handful of entries that actually mattered becomes its own chore, and a journal that is a chore to read stops getting read, then stops getting written.
2. It records how you felt instead of what you expected
A diary entry is honest about mood: nervous, hopeful, annoyed. A decision journal entry needs something more specific and less comfortable to write: a stated expectation with a shape you can later check against reality. "I think this will work out" is a feeling. "I expect this to take six weeks and I'm doing it anyway because the downside if it takes twelve is still smaller than the downside of waiting another quarter" is a prediction you can grade. If every entry could be swapped for "nervous but hopeful" without losing anything, it has already become a diary.
3. There is no revisit step, so entries just accumulate
A diary is complete the moment you write it — rereading is optional, and mostly nostalgic. A decision journal is not finished until you come back to a specific entry after the outcome is known and write a short follow-up next to it. Skip that step consistently and you have built an archive of predictions nobody ever checked, which produces none of the calibration benefit and all of the writing effort.
The boundary: what actually earns an entry
A decision is worth logging when at least one of these is true: it is expensive or slow to reverse, the outcome is genuinely uncertain to you right now, or you notice yourself relitigating it in your head at 11pm. That third test catches more than it sounds like it should — a decision you keep circling back to is one where some part of you already suspects the reasoning is thin, and writing it down forces the reasoning into a sentence instead of a loop.
Keep the entry itself to a fixed, small shape so it stays fast enough to survive contact with a normal week:
- What I decided — one sentence, no hedging.
- Why, right now — the actual reasoning and the information you had, not the reasoning you'll wish you'd had.
- What would tell me I'm wrong — a specific, checkable sign, not a vague "if it doesn't work out."
That's the whole entry. No mood, no scene-setting, no paragraph about how the meeting went. If you find yourself wanting to add texture — what someone said, how the room felt — that material belongs in a diary or a note, not in this file. Keeping them physically separate, even just as two different notes, removes the temptation to let one bleed into the other.
The revisit is the part that actually pays off
Set a date to look at the entry again — a fixed number of weeks out, or whenever the "what would tell me I'm wrong" condition would plausibly have shown up. When you get there, write one more line: what actually happened, and separately, whether the original reasoning holds up now that you can see it. The second question is the one people skip, and it's the one that matters. A decision can go well with bad reasoning, and it can go badly with good reasoning that ran into something nobody could have seen. Grading the reasoning instead of the result is the only way the journal makes you better at deciding rather than just better at remembering what you decided.
How this differs from a values review
A decision journal and a weekly review look at behavior from different angles and are easy to conflate. A review asks whether a principle you hold was lived this week, across an ordinary stretch of ordinary days. A decision journal asks whether one specific, high-stakes call was reasoned well, independent of whether it worked. You can use both — a review might surface that a principle keeps losing to a certain kind of pressure, and a decision journal entry is where you work out, in advance, what you'll actually do the next time that pressure shows up.
CreedOS's daily check-in has a field for exactly this kind of narrow entry — a note plus one concrete thing you did or decided — separate from the score, so you can log a real call without it turning into a diary page. It's free, with no in-app purchases.