Why does my weekly review always focus on the negative?

Because a broken principle is an event and a kept one is usually nothing. When you slip — snap at someone, skip the thing you said you would do, spend the money you told yourself you wouldn't — there is a moment, a specific scene, a reason you can half-remember by Friday. When you keep a principle, most of the time nothing happens at all: you just live the ordinary version of the day, the version where the hard moment either never came up or you handled it so automatically you didn't notice you were handling anything. One of those leaves a story behind. The other doesn't. By the time you sit down to review the week, you are not reading a balanced transcript of what happened — you are reading whatever was distinctive enough to leave a trace, and distinctive, for most people most weeks, means "went wrong."

The review can only work with what you handed it

A weekly review is not a camera that recorded your week and now plays it back evenly. It is a reconstruction built from whatever you happened to notice, remember, or write down in the moment — and noticing is not neutral. A slip pulls your attention toward itself; it usually comes with a flash of guilt or frustration right when it happens, which is exactly the kind of thing memory is built to hang on to. A day where you simply did the thing you meant to do rarely produces that flash. It feels like nothing, because functioning the way you intended to function is supposed to feel like nothing — that is what it means for a principle to have become ordinary rather than effortful. So when Sunday comes and you try to reconstruct the week, the slips arrive pre-loaded with detail and the kept days arrive as a vague, correct-but-empty sense that "the week was fine." Vague and empty loses to specific and vivid every time you're deciding what to write about.

This is not the same as pessimism

It's worth separating this from a personality trait, because the two get treated as the same problem and they aren't. Being a pessimist means you interpret ambiguous or good events negatively. What's happening in a review that only finds problems is narrower and more mechanical: the good events were never ambiguous, they just never got recorded in the first place, so there is nothing left to interpret one way or the other by the time you're looking back. You don't need to be pessimistic at all for this to happen — you just need a system that only prompts you to write something down when something goes wrong, which describes most people's weekly reviews by default, including ones run with real self-compassion and good intentions. The fix for pessimism is reframing. The fix for this is capturing more of the week in the first place.

An issue queue does exactly what it says, no more

If your review process has any kind of "what needs attention" view — a list of the principles you're slipping on, the areas that have gone quiet, the ones trending down — that view is useful precisely because it is narrow. It is supposed to surface problems; that's its entire job, and it would be a worse tool if it also tried to be a highlight reel. The mistake is not that the issue queue exists. The mistake is treating the issue queue as if it were the review, when it was only ever meant to be one section of it. A queue of what needs fixing, read on its own, will always look like an indictment, because you built it to only contain things that need fixing.

What to actually log so the good days stop being invisible

The asymmetry is fixable, but not by trying to "think more positively" during the review itself — by then the week's data is already lopsided and no amount of reframing recovers detail that was never captured. It has to happen earlier, at the point where you'd normally only reach for a note when something goes wrong:

• Write down the close call that went well. The moment you were about to snap and didn't, the purchase you almost made and talked yourself out of, the deadline where the old pattern would have had you cutting the corner and this time you didn't — these are exactly as specific and rereadable as a slip, but almost nobody writes them down, because nothing "happened."
• Name the day that was ordinary on purpose. Not "nothing to report" — the specific ordinary thing. "Handled the thing that usually derails me and it genuinely wasn't a big deal" is one sentence, and one sentence is enough to survive to Sunday. The absence of drama is the data point; you just have to say so instead of letting it pass as nothing.
• Separate "no note" from "went well." If your check-in only has room for a score, a low-effort perfect score and a hard-won perfect score look identical in the record, and only one of them is worth remembering. A one-line note that says which kind of day it was is what makes the good days competitive with the bad ones when you reread the week.

Read the good days back with the same seriousness

Once you've started logging them, the second half of the fix is in how you review, not just what you logged. It is easy to skim past a line that says a day went fine on the way to the line that says a day went badly, because the badly line still reads as more urgent. Give the kept days equal reading time on purpose — not to manufacture positivity, but because a pattern of quiet, specific wins across several weeks is exactly the kind of thing a review is supposed to catch, and it is invisible if you only ever stop to read the parts that are flashing red.

What this is not asking you to do

This isn't an argument for writing everything up as a win or softening real slips so the week reads better. A principle you broke five times this week did get broken five times, and a review that hides that from you is worse than a lopsided one, not better. The goal is accuracy, not balance for its own sake — and right now, for most people's reviews, the honest, accurate correction runs toward including more of what actually happened, because what actually happened includes a lot of ordinary, uneventful keeping that never made it onto the page.

CreedOS's daily check-in has a note field next to the score for exactly this reason — a place to log the close call or the ordinary day that held, not just the day something broke — and the weekly review reads the trend across the whole stretch, not just the issue queue of what's slipping. It is free, with no in-app purchases.