NotesNudge the notes you never go back to

The Weekly Review, Smaller

The weekly review, as usually described, is a substantial ritual: process every inbox, review every project, check every list, plan the week ahead. An hour or two, every week, indefinitely.

It is the most-recommended and least-performed practice in this subject. The failure rate is not about discipline.

For a workplace-oriented comparison with this kind of workflow, this overview provides additional context.

Why the full version fails

It is too long to fit in a bad week, and bad weeks are when it would help most. A practice that only survives good weeks does not survive.

It has no minimum. If the standard is complete, then a partial review feels like failing, and one failure usually ends the practice. Nothing about the design allows a small version.

It is mostly maintenance. Processing inboxes and checking lists is administration. Useful administration — and it is not the same activity as returning to your notes, which is what you started for.

For an independent external reference related to this topic, see Getting Things Done.

And the payoff is diffuse. You finish it feeling tidy. Tidy is a real feeling and it is not an outcome you can point at, which is why the habit erodes without any decision to stop.

What to keep

Ten minutes, three parts.

Three notes from the marked set. Attempt recall before opening each one. Fifteen seconds each, then read and compare. This is the part with evidence behind it and it is the part the full ritual squeezes out.

One decision per note. Keep, promote, retire from the set, or delete. Deletion is output.

One written line. What you would do differently, what this connects to, or simply still true. Without an output the session is reading, and reading sessions decay.

That is the whole thing. Everything else in the standard weekly review is either administration that belongs elsewhere or completeness for its own sake.

What to drop, and where it goes

Inbox processing. A real need and a separate activity — do it when the inbox is annoying, not on a schedule tied to reflection.

Project status. Belongs to whatever runs your work, not to your notes.

Planning the week. Also a different activity, and combining it with review means the planning always wins because it is urgent.

Comprehensive coverage. Reviewing everything is arithmetically the same as reviewing nothing. The full version's ambition is the source of its failure rate.

Making it survive

Attach it to something that already happens. Review has no natural trigger and must borrow one. The end of a Friday, a particular train, immediately after something else fixed.

Keep the floor at three notes. On a bad week, three notes and no writing is a completed session. Defining the minimum low enough to hit is what turns it into a habit rather than an intention.

Do not lengthen it when it is going well. The instinct after a good month is to expand to twenty minutes, then to a proper review, and then to nothing. The ten-minute version is the one that survived; leave it alone.

And expect lapses. Restart at three notes rather than resolving to do better.

What it will not do

It will not process your archive. Ten minutes a week on a marked set of forty gives each note a return every couple of months. The other four thousand notes stay unread, and that is the correct arrangement rather than a shortfall.

It will not feel impressive. Three notes and a line is not a system anyone writes a book about. It is roughly ten minutes more than most people manage in a year.

The short version