NotesNudge the notes you never go back to

Revisiting

This is the half of the subject that nobody builds for.

Capture has a trigger and review has none. You encounter something interesting and the impulse to save it arrives with it. Nothing in an ordinary Tuesday says now would be a good time to read something you wrote in March. That is a design problem, not a discipline problem, and resolving to review more is the approach that fails.

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

Reviewing everything is arithmetically the same as reviewing nothing. Two thousand notes at ten minutes a week is a cycle measured in years, by which time most have expired. The useful question is which small fraction earns a place — and for most archives that is a few dozen notes, marked at capture as things you will want without looking them up.

Fifteen seconds converts the whole practice. Read the title, attempt to recall what the note said, then open it. That single step turns being shown something into attempting to recall it, which is the difference between the operation the evidence supports and the one it does not.

And deletion is the output, not a failure. A session that removed four notes improved the archive; one that added four did not. Every note you look at gets a decision — keep, promote, retire, delete.

For an independent external reference related to this topic, see The Learning Scientists.

The whole practice fits in a sentence: ten minutes, attached to something that already happens, three notes from a marked set, one written line at the end.

Expect most sessions to be unremarkable — three notes, two of which are no longer interesting. That is the normal case rather than a failure. The value sits in the small number of returns that land, and you cannot know in advance which those will be.