NotesNudge the notes you never go back to

A Review Habit You Will Keep

Capture has a trigger: you encounter something interesting and you write it down. Review has none. Nothing in an ordinary Tuesday says now would be a good time to read something you wrote in March.

That is the entire problem, and it is a design problem rather than a discipline problem. Resolving to review more is the approach that fails; supplying the missing trigger is the one that works.

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

Four decisions determine whether the habit survives past week three.

One: what triggers it

Attach it to something that already happens. The last ten minutes of a Friday. The train home on a particular day. Immediately after a weekly planning session you already do.

Or let something hand it to you. A scheduled email, a tool that surfaces a note, a recurring reminder. Lower effort and lower quality, because being shown a note is not the same as attempting recall — but a weak habit that happens beats a strong one that does not.

For an independent external reference related to this topic, see James Clear.

Never "when I have time." You will not have time. Nobody has ever had time.

Two: how long

Ten minutes. Not thirty, not an hour.

The instinct is to schedule a substantial session because the archive is large, and that instinct kills more review habits than anything else. A long session is easy to postpone and postponing once is usually terminal.

Ten minutes is short enough that skipping it feels absurd, and it is enough for three or four notes read properly — which is more than most people manage in a month.

Three: what you look at

The decision people skip, and the one that determines whether the session feels worthwhile.

Not everything. Most notes do not need reviewing and spreading finite attention across an entire archive dilutes it to nothing.

A small marked set, plus something random. The marked set is the twenty or thirty notes you decided at capture time you wanted back. The random element is what produces the occasional surprise, which is what keeps the habit interesting.

Or one project. If you are working on something, review is most obviously useful when it is aimed at the current problem rather than at the archive in general.

Four: what you do with what you find

A review with no output is a reading session, and reading sessions decay because they produce nothing you can point at.

Give it one required output. A single line: what you would do differently, what this connects to, or simply still true or no longer relevant.

Delete or mark. Every note you look at gets a decision — keep, delete, or promote to the marked set. Deleting is part of the practice and an archive that only grows becomes unusable at a rate proportional to its size.

And attempt recall before opening. Fifteen seconds. This is the step that converts the session from resurfacing into something the evidence actually supports, and it is free.

What to expect

Most sessions will be unremarkable. Three notes, two of which are no longer interesting. That is the normal case and it is not failure — the value is in the small number of returns that land, and you cannot know in advance which those are.

The habit will lapse. Everyone's does. The recovery matters more than the streak: restart at ten minutes rather than resolving to do better, because the version that lapsed was already the ambitious one.

And it will feel less productive than capturing. Capture produces artefacts; review produces decisions and deletions. That asymmetry is why the capture bias exists and why review needs the structure that capture does not.

The minimum that works

If you take one thing: ten minutes, attached to something you already do, on a small marked set, ending with one written line.

Everything else on this site is refinement of that. The refinements matter, and none of them matters if the session never happens.

The short version