How to review your values weekly without it becoming a chore
Almost everyone who starts a weekly review quits within two months. The usual diagnosis is discipline. The actual cause is design: the review is too long, it asks questions with no consequences, and it produces a feeling of being graded. Fix those three and ten minutes a week is genuinely sustainable.
Why reviews die
They are too long
An hour-long review requires a protected hour, and protected hours are the first thing a busy week eats. A ten-minute review can be done badly on a bad week and still happen — and a review that happens badly is infinitely more valuable than one that does not happen at all. Design for your worst week, not your best.
Nothing changes as a result
If the review ends with a feeling and no edit, your brain correctly classifies it as optional. Every review must be allowed to produce a concrete change: rewrite a standard, retire a principle, book something into next week. No permitted output, no motivation.
It feels like a performance review
Reviews built around completion percentages invite the same reaction as an appraisal: defensiveness, then avoidance. You start managing the number instead of looking at the week. The way out is to make the review about circumstances rather than scores.
The ten-minute format
Same time every week, timer on, four questions.
1. Which principle did I most clearly live this week? (2 min)
Start here, and be specific — name the moment, not the sentiment. This is not self-congratulation; it is calibration. You are collecting evidence about the conditions under which the good version of you shows up, and those conditions are reproducible.
2. Where did I not live one, and what was happening? (4 min)
The heart of the review. Do not ask "why did I fail," which produces character judgements and no information. Ask what the situation was: the time, the pressure, who was in the room, how much sleep, what you were avoiding. Failures cluster around conditions far more than around traits, and conditions can be engineered.
3. Is anything going quiet? (2 min)
The dangerous category is not the principle you are failing — you can see that one. It is the one you have stopped engaging with entirely, which produces no data and therefore no alarm. Scan for silence explicitly, or you will not notice it for months.
4. One change. (2 min)
Exactly one. Rewrite a standard that was never realistic, or remove a principle you have not consulted in eight weeks, or block time for something you keep deferring. One change a week compounds; five changes a week is just churn, and it means nothing gets a fair trial.
Design rules that keep it alive
- Fixed slot, low ceremony. Same day, same time, no special place required. Friday afternoon or Sunday evening both work; what matters is that it is not a decision.
- Capture during the week, not in the review. The review should be reading, not reconstructing. If you have to remember Tuesday on Sunday, you will invent Tuesday. Two lines a day of raw notes makes the review fast and honest.
- Never review more than eight principles. Past that, ten minutes is impossible and you will start skimming, which is the beginning of the end.
- Let scores be pointers, not verdicts. A number's only job is to direct attention to the thing worth reading about. Once it has done that, ignore it.
- Skip a week without ceremony. Missing one review is not a broken streak; it is a missing data point. Systems that punish absence get abandoned rather than resumed.
What good looks like after three months
You should be able to answer, without checking notes: which principle is currently under the most pressure, and what change you made last. You should have retired at least one principle and rewritten at least two standards. If nothing has been retired or rewritten in three months, the review is not doing anything — it has become a ritual of reassurance, and the fix is to make the questions harder rather than to do it more often.