NotesNudge the notes you never go back to

Quantity Was Never the Problem

The standard diagnosis for a note archive that is not working is that it is too big. Too much captured, too little processed, a backlog to clear.

It is a satisfying diagnosis because it implies a solution: capture less, process more, catch up. And it is wrong, which you can establish without any research at all.

A related workplace concept is handling multiple clients efficiently, which offers a useful contrast with the personal knowledge-work problem discussed here.

People with four thousand notes and people with four hundred make the same complaint. They never go back. If quantity were the cause, the smaller archive would work.

What the count actually affects

Not nothing, and worth being precise so this does not read as a licence to hoard.

Search quality. More irrelevant material means more results to scan past.

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

Random selection. Two thousand notes at one a day returns each about every five years; four hundred returns each every fourteen months.

And avoidance. A collection that feels like a landfill is one you stop opening — which is a size effect, though it is really an effect of undifferentiated size.

Those are real and they are downstream. None of them explains why someone with four hundred notes also never returns.

What is actually missing

A reason to go. Capture has a trigger and review has none. Nothing in an ordinary week says now would be a good time. An archive of any size is silent, and silence at four hundred is the same silence as at four thousand.

A small set worth going to. Most notes were thinking and are not owed a second reading. Without a marked subset, "returning to your notes" means facing everything, which is arithmetically the same as facing nothing.

And a shape for the session. Ten minutes, three notes, one decision each. Without a shape the intention is to review, which is not an action anyone can take.

Those three are missing at every archive size, which is why the complaint is size-independent.

Why the quantity diagnosis persists

It is actionable in a satisfying way. Capture less and process more are both things you can resolve to do this afternoon.

It assigns blame comfortably. You were undisciplined; discipline will fix it.

And it produces a project. Reorganising, purging, migrating — the enjoyable half, with a visible result at the end and no change to the underlying situation.

Whereas the real diagnosis produces a ten-minute weekly appointment, which is unglamorous and permanent.

The test

If you believe quantity is your problem, it is checkable.

Take forty notes you consider your best. Put them somewhere separate. Now you have a four-hundred-times smaller archive of only high-value material.

Do you go back to it?

If yes, quantity was your problem and you have solved it. If no — and for most people it is no — the constraint was never the count, and the next reorganisation will feel excellent and change nothing.

What to do instead

Mark a small set as you capture, rather than filtering a large one afterwards.

Build the trigger. Ten minutes attached to something that already happens.

Delete during sessions, three or four at a time, so the archive shrinks as a by-product rather than as a project.

And stop counting. The number is not measuring anything you care about, and watching it go up is the reward mechanism that produced the imbalance in the first place.

The short version