A weekly review answers one question: what's gone quiet?
It's a good question and the gap number mostly answers it for you. But it has a blind spot, and the blind spot is large enough to lose a year in.
A goal touched every week reads as healthy. It reads as healthy whether it's progressing or whether the same eleven safe tasks are being cycled through indefinitely, and no weekly measure can tell those apart.
The failure a monthly review catches
Sustained activity in the wrong direction.
Someone works on a business weekly for a year and can't name anything that changed. Someone does a course a month for nine months and has built nothing. Someone spends every session on a book reorganising notes and redesigning the outline.
None of that shows up in a gap, because there's no gap. The counter says three days quiet, which is true, and the goal is quietly going nowhere.
The reason a longer range catches it is that the evidence is only visible in aggregate. One session of tidying is a reasonable evening. Twelve in a row is a pattern, and the pattern is the finding.
This is also why you can't catch it by paying more attention week to week. Each individual entry was written by someone who believed it at the time, and each was defensible. The failure exists only in the sequence, and sequences require reading a stretch of them at once.
What a monthly review is
Not a longer weekly one. A different activity with a different instrument.
Weekly, you look at numbers — the gaps, sorted, and you diagnose the top few. Five to ten minutes.
Monthly, you read the notes. One goal at a time, everything written on it since last month, in one sitting. Twenty minutes, three or four goals.
Three questions per goal, and only three.
What was I actually doing — the verbs. Not intentions, not plans. What the entries say happened.
Where did it change — the point at which the character of the entries shifts. That's usually the interesting moment, and it's usually invisible at the time.
And what's missing — the task that appears in none of them. This is the one that pays. People are far better at spotting an absence when reading twenty concrete entries than at any other time, and the absence is where the diagnosis lives.
One practical detail that changes what you see.
Read everything for one goal together, rather than everything from the month in date order. Mixed together, twenty entries across five goals read as a busy month. Separated out, the same twenty might be sixteen on one thing and one apiece on the others, which is a completely different picture and the one worth acting on.
The date-ordered view flatters you. The per-goal view tells you where your attention actually went, which is rarely where you'd have said.
The decisions that belong here
Some things are wrong to decide weekly and right to decide monthly.
Whether a goal is still worth doing. That question asked every week produces churn and a lot of bad revisions made on bad Tuesdays. Asked monthly, it's a reasonable check.
Whether the approach is working. Twenty applications and no interviews. Nine months of courses and nothing built. A year of tidying a business. These need a month's evidence to be visible and they're the highest-value findings available.
And whether the list is the right length. Capacity drifts. A list that was four goals in January is seven by June without anyone deciding, and monthly is about the right frequency to notice.
Where this becomes ceremony
The honest objection, because monthly reviews are a classic thing people design elaborately and then never do.
If nothing changed, don't do it. A month where you touched everything, made progress, and nothing feels off is a month where twenty minutes of reading produces confirmation and no decisions. Skipping is correct, and the habit of doing it out of duty is exactly what makes people abandon the practice within a year.
Keep it small. Three or four goals, not the whole list. Twenty minutes, not an afternoon. The elaborate version — templates, sections, scores out of ten — is a different activity that mostly serves the feeling of being organised.
And be careful when to read. A log read while you're already low becomes a catalogue of failures rather than a record, and the finding you'll reach is about your character rather than about your approach. Read it when you suspect your impression is wrong, and not when you're only looking for evidence that it's right.
Nine months of entries
His goal is learn to code, and it's been touched almost every week since January. The counter reads three days quiet. Everything looks fine.
In September he reads the entries for that one goal in a single sitting. There are about forty.
Finished module 4. Started the databases series. Watched the auth videos. Module 7 done. Started the framework course. Finished section 3.
What's in every entry: a course. What's in none of them: building anything. There is no entry that says stuck on, or couldn't work out, or tried X and it didn't work — which is what learning to code actually consists of, and there are forty entries without a single one.
That's a diagnosis, and no weekly review could have produced it. Weekly, this goal has been green all year.
The response is one thing: build something small that nobody has written a tutorial for. It takes eleven evenings, is thoroughly unpleasant, and produces more capability than the previous nine months.
Two instruments, two failures
The gap catches abandonment. It's fast, it's automatic, and it's in front of you every time you open the list.
The record catches misdirection. It's slow, it requires deliberately sitting down with it, and it's the only thing that can see a goal that's been busy and static.
Most systems only have the first, which is why so many people have the experience of a year in which they worked hard and can't say what changed.
Twenty minutes a month is the price of avoiding that, and it's the best-value thing in this whole practice by a distance — because the failure it catches is measured in years rather than in days.
Related: Review by gap, not by list · Notes as evidence · Quiet quitting your own projects
Share: