Weekly Review: The 30-Minute Habit That Actually Sticks

Somewhere in your system there's a project that quietly stalled three weeks ago, and you don't know which one. That low hum of "I'm probably forgetting something" is the tax you pay for not looking at your commitments regularly — and the weekly review is the 30 minutes that cancels it. The practice comes from David Allen's Getting Things Done, where he calls it the habit that keeps the whole system trustworthy. He's right, which is why every productivity method since has borrowed it.

The catch: most people who start doing weekly reviews stop within a month. So this guide covers a checklist that fits in an actual half hour, the two reasons reviews die, and how the shape of your notes decides whether the review is a glance or an excavation.

A realistic 30-minute weekly review checklist

The classic GTD version has a dozen steps. Honest advice: start with three. A modest review you do every week beats a thorough one you did twice in March.

1. Clear your inboxes (~10 minutes)

Everything that piled up during the week — quick-capture notes, starred emails, screenshots, that idea you typed into your phone at a red light. For each item, one decision: does it belong to a project, an area of responsibility, or the bin? File it or delete it; don't do it (two-minute replies excepted). If you use the PARA method, this step is one question per item: how actionable is this?

Empty inboxes aren't the point. Trusting that nothing is lurking in them is.

2. Scan your active projects (~10 minutes)

Open your project list and walk it top to bottom, asking one question per project: does this have a concrete next step? Not a status report — a scan.

• No next step? Write one now, or admit the project is stalled and mark it.
• Actually finished? Archive it. This is satisfying and you'll skip it if you don't do it here.
• Doesn't deserve your time anymore? Kill it deliberately instead of letting it haunt the list.

This step is where the "am I forgetting something?" hum stops — because you just looked at everything, and now you know.

3. Pick three priorities (~5 minutes)

Not ten. Three. Write "This week: X, Y, Z" somewhere you'll see on Monday. The constraint is the value — choosing three forces the ranking your future self needs when Tuesday goes sideways and only one thing is getting done.

That's 25 minutes, with five of slack. Stop there.

Why weekly reviews fail

Two failure modes account for nearly every abandoned review habit.

Perfectionism. You treat the review as a full system overhaul — reorganize the folders, process every note, plan the quarter. It takes two hours, so you start dreading it, so you skip one, and a skipped "sacred ritual" feels like failure in a way a skipped 30-minute scan doesn't. The fix is scope: the review maintains the system; it doesn't rebuild it. Tag the messes you find and move on.

No fixed slot. A review that happens "when I get a chance" happens never — it's important-but-not-urgent, the exact category that always loses to whatever's on fire. The fix is boring: a recurring calendar appointment, same time every week, defended like a meeting with your best client. Friday afternoon works for closing the week while it's fresh; Monday morning works as a launch ritual. Which one matters far less than picking one.

Make the review a glance, not an excavation

Here's the part most guides skip: how long your review takes is mostly decided by how your notes are shaped the other six days.

If meeting outcomes live in scattered docs and projects have no single home, the review becomes archaeology — twenty minutes of finding state before you can assess it. If every project is one page that collects its own activity, the review is reading, not digging.

Two structures do most of the work. Links — especially backlinks, links that work in both directions so a page knows what points at it — mean that when your meeting notes link to their project, the project page automatically lists everything that happened to it this week. You open one page and the week reports itself. Databases — pages with structured fields like status, owner, and next step — turn the project scan into a filtered view: every active project and its next action in a single table, stalled ones visible as blank cells. In a workspace like Stacy, that project database plus backlinks is the whole setup; a good starting structure is covered in how to organize notes, and if you're building a fuller second brain, the weekly review is the maintenance loop that keeps it alive.

None of this requires fancy tooling — a paper list works. But every minute of excavation you remove is a minute of resistance removed, and resistance is what kills the habit.

The takeaway

Thirty minutes, three moves: clear the inboxes, scan the projects, pick three priorities — at the same time every week, scoped small enough that you'll actually repeat it. Credit David Allen for the insight underneath: a system you don't review is a system you can't trust. The weekly review is how you keep trusting yours.