How to combine a weekly review and a decision journal into one session

If you have tried keeping both, you already know the failure mode: a weekly review with a fixed slot on the calendar, and a decision journal with no slot at all, competing for the same ten spare minutes on a Sunday. The journal usually loses, because nothing forces it to happen. The fix is not to find more time. It is to notice that a decision journal and a weekly review are not two habits — they are two halves of one loop, and treating them as separate is what makes each of them harder than it needs to be.

Why running them side by side doubles the friction

Each one, on its own, is designed to be light. A decision journal entry is a few sentences written at the moment you decide. A weekly review is ten minutes read back at the end of the week. Neither is the problem. The problem is that kept as unrelated systems, they still ask for two separate sits: one to write the entry, and later, unconnected to it, one to sit down and "do the review" from scratch — which usually means trying to remember the week rather than reading it. Two open loops compete for the same scrap of spare attention, and a system that competes with itself for time loses pieces first, then loses the person keeping it.

What each one is actually for

They are not the same task performed twice. A decision journal entry is written before you know the outcome, about one specific choice — what you expect to happen, the real reason, what would change your mind. A weekly review looks back across an entire week and asks a different question: which principles did you actually live, and where did you not. One is about a decision. The other is about a pattern of decisions and behaviour across seven days. Confusing them is what causes people to either journal every small decision, which nobody sustains, or to try to reconstruct specific decisions from memory during the review, which is exactly the hindsight-bias problem the journal exists to prevent.

Why they are already solving each other's weak point

A weekly review with nothing written down during the week runs entirely on memory, and memory reorganises itself around how things turned out — the same distortion a decision journal is built to defeat. A decision journal that never gets reread, on the other hand, is just a stack of private entries with no pattern extracted from them; the insight a journal promises only shows up on reread, and reread is exactly what a weekly review already is. Put the two together correctly and the decision journal stops being a second obligation sitting on top of the review — it becomes the material the review reads.

The order that makes it one session

The combination only works in one direction: capture during the week, read on review day. Never the reverse.

1. During the week, when a decision actually happens: write the short entry — the choice, what you expect, the real reason, what would change your mind. This takes a few minutes and happens in the moment, not later.
2. On review day, start by reading, not writing. Open whatever decision entries landed this week before you do anything else. You are not reconstructing the week from memory anymore — it is already sitting there, and the review's first ten minutes get faster and more honest for it.
3. Do the outcome pass for anything that resolved. If one of this week's entries was about something that has now played out, read your prediction before you write your verdict. The gap between what you expected and what you now remember expecting is usually the most useful sentence in the whole session.
4. Then run the normal review questions — which principle did you most clearly live, where did you not and what was happening, is anything going quiet — grounded in what you just read rather than what you can currently recall.
5. One change. Same rule as a review run alone: exactly one edit gets made as a result, whether that is a rewritten standard or a decision you flag to revisit next week.

Done this way the combined session is not much longer than a review alone, because the expensive part — writing down what actually happened — was already done in small pieces across the week. Review day is reading, and reading is fast.

Where the two still need to stay separate

Do not let review day become the moment you write decision entries for the first time. An entry written after you already know how something turned out is not a decision journal entry — it is a story that has been quietly edited by the outcome, and it will not catch anything the next time you reread it. If a decision this week never got written down in the moment, let it go rather than backfilling it under review-day pressure. Likewise, do not journal every decision just because the review is now the place you read them — the journal is still for choices that are hard to reverse, genuinely uncertain, or a repeating type, not a transcript of the week.

What the combination catches that either one misses alone

Run only a review and you can see that you lived a principle this week without ever seeing the specific, close call where it almost went the other way. Run only a decision journal and you can see individual choices clearly without ever stepping back to ask whether they add up to the person you are trying to be. Together, a pattern shows up that neither one surfaces by itself: a principle you kept in every decision that touched it, but at a cost you only notice once you read the reasoning back — or a case where you broke a principle on purpose, for a reason that, reread a week later, still holds up.

CreedOS's daily check-in already has a note field for exactly this moment — log the one concrete thing you did or broke, or the reasoning behind a call you just made, in a sentence, while it is still fresh. The review page reads that history back as a weekly trend instead of asking you to reconstruct the week from scratch, which is most of what makes running both together practical instead of one more system to maintain.