Notes You Will Never Reread
Most people who take notes carry a low, persistent sense of failure about them. Thousands captured, almost none revisited, a backlog that grows.
The last thing worth saying on this site is that the ratio is not the problem, and for most of what you write it is not even a shortfall.
A related workplace concept is work hours in a year, which offers a useful contrast with the personal knowledge-work problem discussed here.
Two kinds of writing, one word
Writing to think. You work something out by putting it in sentences. The value is delivered during the act — this is the encoding function, and it is the best-established benefit in the whole subject. The file that remains is residue.
Writing to store. You are putting something somewhere to get it back later. The value depends entirely on retrieval, and without a mechanism it is not delivered at all.
Both produce a note. Only the second creates an obligation. And most of what most people write is the first, which means most of the guilt is about material that already did its job.
For an independent external reference related to this topic, see Heptabase.
Where the guilt comes from
The deposit metaphor. Second brain, external memory, knowledge base — every framing implies storage, and storage implies withdrawal. Under that description an unread note is an unrealised asset.
The visible count. The number goes up and nothing goes down, which reads as an accumulating debt.
And the advice. Every guide is about capturing well and processing thoroughly, which presupposes that everything captured is destined for processing.
None of those is a fact about notes. They are framings, and dropping them removes the feeling without changing anything you do.
What a healthy practice actually looks like
A large majority written and never reopened. Ninety per cent or more, and this is fine.
A small marked set that genuinely returns. Perhaps forty notes and a ten-minute weekly session.
Regular deletion, three or four at a time, so the residue does not become sediment.
And no backlog, because nothing was ever queued for processing. Unprocessed captures get deleted rather than promoted.
That practice produces roughly the same archive as an anxious one and none of the accompanying feeling, which is most of what changes when you stop treating the collection as a debt.
The one thing that is a real shortfall
Not the ratio. Having no mechanism at all for the small part that should come back.
If ninety per cent of your notes were thinking and ten per cent were meant to be retrieved, and nothing retrieves them, then ten per cent of your writing was wasted — and it is the ten per cent you deliberately chose.
That is the actual problem, it is small, and it is fixable with ten minutes a week. Everything else on this site is refinement of that one point.
What to do with the rest
Leave it. Searchable, unread, untroubling. If something surfaces at random, that is a small bonus and not a rebuke.
Delete when you happen to see it and it has expired.
And stop counting it. The number was never measuring anything you wanted, and watching it rise is the mechanism that produced the imbalance.
The end of the argument
The whole site reduces to two sentences.
Writing things down is worth doing on its own, and most of what you write is finished when you finish writing it.
A small part of it should come back, and something has to bring it — because nothing in an ordinary week will.
Everything else — the methods, the tools, the evidence, the arguments about linking and folders — is detail hanging off those two. If you only act on the second sentence, the site has done its job.
The short version
- Writing to think delivers its value during the act; writing to store depends entirely on retrieval
- Most notes are the first kind, so most of the guilt concerns material that already did its job
- The deposit metaphor, the rising count and the standard advice all manufacture a debt that does not exist
- A healthy practice: ninety per cent never reopened, a small marked set that returns, regular deletion, no backlog
- The real shortfall is having no mechanism for the small part you deliberately meant to keep
- Ten minutes a week fixes it, and everything else is detail