A Weekly Review That Doesn't Feel Like Bureaucracy

The short answer: fifteen minutes, three prompts, no spreadsheet

David Allen's GTD methodology (source) puts the weekly review at the centre of the system because the rest of the system silently rots without it. But the version most readers try — a 90-minute audit of all projects, contexts, and trigger lists — is what kills the practice within a month. The honest minimal weekly review is fifteen minutes, three questions, no templates: what got done, what's drifting, what's the one thing for next week. That's enough to do the load-bearing work of the review without becoming the bureaucratic monument that no one actually maintains.

Why the maximalist version fails

A 90-minute weekly review requires a specific kind of attention that most weeks don't have. The reviewer needs energy, a clear head, no immediate deadlines bleeding into the window. Those weeks are rare. When they don't arrive, the review gets skipped — and one skipped review starts the slide toward two months without one. The maximalist design also implies that the review has to surface everything, which makes it feel like a major event rather than a hygienic check. A lighter design is more sustainable, and sustainable beats thorough by a wide margin when the alternative is nothing.

The three-question version

• What got done this week? Scan calendar, inbox, done-list. Five minutes. The point isn't to congratulate yourself; it's to see what the actual shape of the week was. Most weeks contain more output than the felt memory suggests, and naming that output corrects the next-week framing.

• What's drifting? Five minutes. Glance at the open projects and ask which one hasn't moved. Drifting is fine for one week; two weeks is signal. The review catches drift early enough to either resume or formally park; without the review, drift becomes silent abandonment.

• What's the one thing for next week? Five minutes. Pick one outcome that, if it happened, would make the week feel successful. Not a list — one thing. The plan beneath it can be three lines or twenty; the headline is one item, and it does most of the work of focusing the week.

When to do it

The traditional advice is Sunday evening, which works for some readers and ruins the weekend for others. Friday afternoon is often a better fit — the work is fresh, the week-end transition is clean, and Monday isn't carrying any planning load. Pick whichever time you can defend; the time of day matters less than the consistency of the slot. Tie it to an existing anchor (after lunch on Friday, before the last meeting, etc.) so the cue is environmental rather than willpower-dependent.

Why this pays double for ADHD

ADHD weeks are unusually shapeless without external scaffolding. Without a weekly review the felt experience drifts to "I did nothing," regardless of actual output; with one, the visible reminder of what happened anchors the narrative. The other ADHD-specific gain is the one-thing question — it converts the typical too-many-priorities anxiety into a single decision that the next week's planning can flow from. The light cadence is also what keeps the practice surviving past month one, where the maximalist version reliably dies.

Where it fails (and the repair)

• Letting it sprawl. Once you start adding sub-questions, the 15 minutes becomes 30, then 45, and you've recreated the maximalist version that fails. Set a timer; when it goes off, the review is done even if you didn't finish the third question.

• Doing it as performance. If the review starts producing impressively-formatted notes that no one (including you) reads, it's become a ritual instead of a tool. The output is for you; if it's not changing how next week unfolds, the format is too heavy.

• Skipping a bad week. The week when nothing got done is the week the review matters most. Doing it on a bad week takes more courage but produces the most signal — and the next week is structurally better for having faced the bad one.

FAQ

Where should I record the review?

Wherever you'll re-read it. A plain text file, a paper notebook, a notes app. The format should be uniform across reviews so a quick scan of last month's reviews surfaces patterns — projects that drift repeatedly, themes that keep recurring as next-week priorities, etc. The format doesn't need to be fancy; it needs to be consistent.

What if I miss a week?

Skip it cleanly and do the next one. Don't backfill — the value of a review is in current orientation, not historical archaeology. Two missed weeks in a row is the signal to look at whether the slot has stopped working; one is just life.

Should the review include personal life or just work?

Mixed reviews — work + life + body + relationships — outperform work-only ones because they reflect how a week actually goes. The questions stay the same; the answers cover more ground. The mixed format is also what keeps the review from feeling like an extension of the workday.

Do I need a monthly or quarterly version too?

Eventually useful, not urgent. A weekly review running for six months will quietly surface the patterns that a quarterly review would also catch — and you'll have caught them earlier. Add the longer cadence only after the weekly one has been running consistently for several months.

Is fifteen minutes really enough?

For most readers, yes. The thoroughness of the review matters less than the consistency of the practice. A 15-minute review every week for a year produces dramatically better orientation than a 90-minute review you actually did three times. The compounding is in the cadence, not the depth of any single session.