Why does my decision journal only have bad decisions in it?

Because you only open the journal when something already feels like it went wrong. That is not a discipline problem, and it is not evidence that you make bad decisions more often than good ones. It is a fact about which feelings send you to the page: regret creates a specific itch to explain yourself, and a decision that goes fine never creates the equivalent pull. Nobody sits down to write three lines about the ordinary thing that worked out the way they expected. So the archive fills with post-mortems and stays quiet on every week where things went well, until the whole record reads like a file of your own mistakes — not because that is what happened, but because that is the only category of moment that ever made you reach for the notebook.

Why regret writes and satisfaction doesn't

A decision that goes badly leaves something unresolved: you want to know what you missed, you want to make sure it does not repeat, and there is a specific, nameable feeling driving you toward the page. A decision that goes well resolves itself completely on its own. There is no open question to chase, so there is nothing pulling you toward a blank entry. This is not a character flaw or a bias you can simply notice and correct — it is closer to how a smoke alarm works. It is built to go off for smoke, not for a room that is fine, and a fine room generates no signal for it to react to. Waiting for the same kind of internal alarm to prompt you to log a good call means waiting for a signal that, by design, is never going to fire.

Hindsight hides the good calls before you even get to grade them

There is a second, quieter mechanism working in the same direction. Once a decision turns out well, it tends to stop looking like a decision at all. It gets filed in memory as "obviously the right move," or as something that was never really in question, or as plain luck that did not require judgment on your part. A choice only gets remembered as having been a real decision — something that could genuinely have gone another way — when it fails, because failure is the thing that proves a live alternative existed. Success quietly erases its own difficulty. This means the skew is not only about which moments make you want to write; it is about which moments still look, in retrospect, like they were ever worth writing about. By the time you might think to log a win after the fact, it often no longer registers as one.

What an all-negative archive does to the practice

Reread a journal that is entirely post-mortems and it does not read like a record of how you decide — it reads like an indictment. That framing is exactly the trap decision journaling was supposed to route around: a log of every time you were wrong, checked periodically, is a worse version of the streak-and-failure scoreboard this whole method exists to replace. It also quietly distorts your sense of your own judgment going forward. Rereading a file of nothing but failures trains you to expect the next decision to fail too, not because that is accurate, but because failures are what is available to recall. A record that is unrepresentative does not just feel unfair — it actively teaches the wrong lesson about how good your judgment actually is.

The fix is not "remember to write about your wins"

Telling yourself to log good outcomes too does not work, for the same reason diets built on willpower do not work: it asks you to manufacture a feeling that the moment is not actually producing. The real fix is to change what triggers an entry in the first place, so the outcome stops being the thing that decides whether you write at all. If you log the three lines — what you decided, what you expect, the real reason — at the moment you commit, before you know how it turns out, the trigger is no longer "this went badly." The trigger becomes "this was genuinely uncertain," and uncertainty exists in both directions before the story resolves. A useful cue to watch for is hesitation itself: the pause before you send the message, the moment you notice you are not fully sure, the case where you could describe your confidence as a number instead of a certainty. Write there, regardless of which way you expect it to break, and the archive stops being selected by outcome at all.

What to do with the archive you already have

Do not try to balance it after the fact by adding entries about old wins you now remember fondly — those would be reconstructed with the benefit of already knowing how things turned out, which has the same problem as any other backfilled entry: the honest uncertainty that made it worth recording is no longer available to write down. Instead, relabel what you have for what it actually is — a partial record of the moments that hurt enough to make you open the notebook, not a representative sample of your decisions — and start the uncertainty-triggered habit from here. Within a handful of weeks the record starts including calls that turned out fine, not because you tried harder to be positive, but because you logged them before you could know which way they would go.

CreedOS's daily check-in has a plain note field next to the score, sized for exactly this kind of short entry written in the moment rather than reconstructed afterward — the point is to capture the uncertainty while it is still there, not to grade the outcome once it has already arrived. It is free, with no in-app purchases.