How long should a weekly principles review actually take?
Ten minutes, on an ordinary week. Not because round numbers are inherently correct, but because that is roughly the length that survives contact with a week that already had a dentist appointment and a deadline in it. A review that needs an open hour gets protected the first two weeks and then quietly stops being scheduled. A review you can do in ninety seconds gets done every week and tells you nothing, because ninety seconds is not enough time to notice a pattern — only enough time to notice a number.
Where the ten minutes actually goes
The number is not a vibe, it is a budget, and the budget only works if you know what it is buying. A weekly review that is worth doing has to do three things: notice what went well enough to repeat, look honestly at what did not and why, and decide on one change. Each of those needs real minutes, not a glance. Notice what went well is fast — two minutes, maybe three. Looking at what did not go well and asking what was actually happening, rather than judging yourself for it, is the part that needs the most room, because "what was going on" is a real question with a real answer, not a box to tick. Deciding on one change is fast again, because you are picking one thing, not drafting a plan. Ten minutes is what is left when you refuse to shortcut the middle part, which is the part doing all the work.
The length should scale with how many principles you hold, not with how bad the week was
This is the mistake that quietly wrecks most reviews: treating a rough week as a reason to spend longer, and an ordinary week as a reason to rush. It should work the other way. The thing that legitimately changes how long a review takes is how many principles you are actually reviewing that week — three principles take less time to look at honestly than eight, regardless of whether the week itself was calm or chaotic. A bad week is not more principles; it is the same handful, with more to say about one or two of them. If a review is consistently running long, the fix is almost never "give it more time." It is "you are reviewing more principles than ten minutes can hold," which is a sign to retire one, not to book a longer slot.
Under two minutes: fast enough to always happen, honest enough to say nothing
A review that only asks "did I hit my numbers this week" can be answered in under two minutes, every week, without fail — and after three months you will have a string of percentages and no idea what actually happened on the weeks that dipped. Speed and honesty are pulling in different directions here, and a review compressed past a certain point stops being able to do the second thing at all. If your review reliably takes under two minutes, it is very likely not reviewing anything — it is glancing at a summary screen and calling that done.
Past thirty minutes, it has quietly become something else
The opposite failure looks more virtuous while it is happening. Thirty, forty, sixty minutes of writing feels like taking the thing seriously, and for the first few weeks it might even be true. But a review that long is no longer a weekly review — it has become journaling with extra steps, and journaling is a fine practice with a very different time budget and a very different purpose. The tell is what the extra time is actually spent on: if it is spent rereading and reflecting on the week in general, that is journaling, and it deserves its own slot rather than eating the review's. If it is spent going deep on one specific principle that is clearly under pressure, that is worth doing, but it belongs in that principle's own space — a decision journal entry, or a longer look the next time you sit down to revise it — not folded into the ten minutes that are supposed to cover everything.
The one week ten minutes is not enough
Some weeks genuinely have more in them — a decision you are still turning over, a principle that just broke in a way that matters, a conversation that changed how you think about something you have held for years. The instinct is to let that week's review run long, and the mistake is letting the following week inherit the new length as the default. A week that needs more time gets more time, once, deliberately, and the review returns to ten minutes the week after unless something equally large has happened again. If you notice the review has crept up to twenty minutes and stayed there for a month, that is not a sign you finally found the right length — it is a sign something that belongs elsewhere, probably a specific decision worth its own record, has been living inside the weekly review by default because nowhere else was built for it.
How this relates to the daily check-in
The daily check-in and the weekly review are different time budgets doing different jobs, and the size difference between them is the point, not an accident. A daily check-in stays under a minute because its only job is to record whether, once, honestly. A weekly review gets ten minutes because its job is to look at several of those whether-points together and ask why — a question that a single day's entry was never built to answer on its own. Trying to make the daily check-in do the weekly review's job stretches it past a minute and it stops happening. Trying to make the weekly review as short as a daily check-in means it can only ever repeat the taps back to you, never explain them.
The review inside CreedOS is built around that same ten-minute shape — a short read of the week's trend and category performance, an issue queue that surfaces what is going quiet before you would have noticed on your own, and an AI coach available if you want to talk through what to change first. It is free, with no in-app purchases, and nothing about it asks for more time than an ordinary week actually has.