Weekly reviews fail for a predictable reason: the review depends on a structure, and the structure itself needs maintenance. When the dashboard goes stale, the review dies with it. But if your week is already captured as notes, voice memos, and detected tasks, a review needs no apparatus at all—just three questions.
Question one: what happened?
Scroll the week’s captures once, top to bottom. You are not organizing—you are re-reading your own week. This takes five minutes and routinely surfaces the thing you swore you would not forget on Tuesday.
Question two: what is open?
Look at open tasks and detected commitments—especially the ones that came out of this week’s notes. Close what is done, drop what has expired, and pick the few that matter next week.
- Anything promised to another person gets checked first.
- A task with no source or reason is a candidate for deletion.
- ‘Waiting for’ items deserve one nudge or one more week, decided now.
Question three: what is unclear?
Answer the clarification questions the system asked during the week—the ambiguous ‘ask him on Friday’ notes. Two minutes of answers now is what keeps this week’s notes readable in six months.
Ask rather than tally
Recurring topics, growing piles of postponed items, an unusually loaded week—none of that needs counting by hand. Ask the archive instead: ‘what did I keep coming back to this week?’, ‘what has been sitting untouched the longest?’ Your job in the review is judgment, not bookkeeping.
Where the fifteen minutes actually go
A time budget is what keeps this from expanding into an afternoon and then being abandoned. Roughly:
- Five minutes re-reading the week's captures, top to bottom, changing nothing.
- Five minutes on open tasks and detected commitments—close, drop, or carry forward.
- Two minutes answering the clarification questions raised during the week.
- Three minutes deciding what next week actually requires, written as one short note.
Why weekly reviews usually die
The standard failure is structural rather than motivational. A review built on a dashboard, a template, or a set of tracked projects depends on that structure being current—so the week you are too busy to update it is the week the review becomes useless, and the review after that never happens. The system requires maintenance precisely when you have none to give.
Building the review on raw capture removes that dependency. The material accumulated whether or not you were organized, so a review skipped in a chaotic week costs you exactly one review, not the practice.
Two honest limits remain. This works only if you actually captured something during the week—a week with no notes produces a review with nothing to read, and no method fixes that. And a fifteen-minute pass is a maintenance ritual, not a planning session: it tells you what happened and what is open, but deciding what a quarter should look like is a different exercise that deserves its own hour.
A review is three questions—what happened, what is open, what is unclear—asked over material that captured itself. Fifteen minutes, no system to maintain.