NotesNudge the notes you never go back to

The Capture Bias

Everything in this subject is shaped by one asymmetry, and once you see it the rest of the field becomes legible.

Capturing is pleasant, immediate, and produces an artefact. Reviewing is effortful, delayed, and produces deletions.

A related workplace concept is being more proactive at work, which offers a useful contrast with the personal knowledge-work problem discussed here.

Every incentive in the practice, in the tooling, and in the writing about it points at the first. That is why almost everyone has an archive and almost nobody has a habit.

How the bias operates

Capture has a trigger and review does not. You encounter something interesting; the impulse to save it arrives with it. Nothing produces a comparable impulse to return.

Capture produces something visible. The note count goes up. Reviewing produces judgements, most of which are "no longer relevant," and the count goes down.

For an independent external reference related to this topic, see Nielsen Norman Group.

Capture feels like progress on the underlying goal. Saving an article about a problem feels like working on the problem. It is not, and the feeling is convincing enough to substitute.

And capture is where the tools compete. Faster capture, capture from anywhere, capture with one keystroke. Reviewing is harder to build, harder to demo, and harder to sell, so it gets a scheduling feature and a settings page.

What it produces

Archives that grow past usefulness. A collection's value does not scale with its size; past some point the noise grows faster than the signal, and the archive becomes something you avoid rather than consult.

A persistent sense of failure. People with thousands of notes generally feel bad about them. Not because they are doing something wrong — because they were sold a deposit-and-withdraw model and only the deposits happened.

And an industry aimed at the wrong half. Most methods, most tools and most writing address capture and organisation. The retrieval problem gets a schedule and an assumption.

The bias in myself

Worth admitting, since this site is written by someone with the same problem.

I capture more than I review, by a large margin, and I know precisely why it is the wrong ratio. Knowing has not fixed it. What has helped is structural rather than motivational: a short scheduled session attached to something that already happens, and a rule that every note I look at gets a decision.

Ten minutes a week is not an impressive practice. It is roughly ten minutes more than I managed for several years, and it is the only part that has survived.

What follows

Raise the cost of capture deliberately. One sentence of context at capture time filters as much as it records. Notes not worth twenty seconds were mostly not worth saving.

Lower the cost of review. Ten minutes, small marked set, attached to an existing routine.

Stop counting notes. It is the metric that rewards the behaviour already over-rewarded, and there is no version of it that measures anything you want.

And treat deletion as output. A review session that removed forty notes did more for your archive than one that added them. This is the hardest reframing here and the most useful.

The version that is not a problem

One qualification, because the argument above can tip into guilt, which is not the intention.

A large share of note-taking is thinking, and the value was delivered at the moment of writing. Those notes have done their job. You are allowed to have an archive that is mostly residue — the failure is not the ratio of reread to written, it is having no mechanism at all for the small part that should come back.

The capture bias is a problem because it means nobody builds that mechanism, not because writing things down and not rereading them is a moral failing.

The short version