NotesNudge the notes you never go back to

When to Delete

Almost nobody deletes notes. The resistance is strong, it feels like caution, and it is the main reason archives become unusable.

Worth taking the resistance seriously before dismantling it, because it is not irrational — it is just aimed at the wrong risk.

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

What you are actually afraid of

That you will need it. The obvious one, and the least justified: most notes are never revisited, so the probability of needing any particular one is very low, and it is low in a way that is easy to check by looking at what you have actually retrieved in the last year.

That the effort will have been wasted. This is the real fear, and it rests on a misunderstanding. The encoding benefit was delivered when you wrote it. Writing did its work whether or not the file survives. Deleting a note does not un-think the thought.

That the archive is a record of you. Sometimes true, and if that is what you want, say so — a journal is a legitimate thing to keep entire. But a journal and a working archive are different objects with different rules, and treating one as the other makes both worse.

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

What keeping everything costs

Paid continuously and never attributed.

Search gets worse. Every irrelevant note is a result you scan past.

Random selection gets worse. With two thousand notes, one surfaced a day returns each about every five years; with four hundred, every fourteen months.

Review becomes impossible. Reviewing everything is arithmetically the same as reviewing nothing, and the larger the archive the more obviously true that is.

And you avoid it. The strongest cost and the least visible. An archive that feels like a landfill is one you stop opening, at which point its size is irrelevant because you are getting nothing from any of it.

Four rules that make it easy

Delete during review, never in purges. Three or four notes a session, no ceremony. Purges are large, dreaded, and postponed indefinitely — and a postponed purge is just an archive with anxiety attached.

Use the arrival test. If this surfaced at random tomorrow, would I be glad? If the honest answer is that you would skim and move on, it is expired. This works because it asks about the future rather than about the effort already spent.

Archive before deleting, at first. Move it somewhere out of the active set. Lower psychological cost, and after a few months of never once retrieving anything from it, deletion gets easy. Actionability-based schemes get this right.

And delete by cause, not by age. Old is not a reason. Superseded, wrong, no longer relevant, or written about a problem you no longer have — those are reasons, and they are visible on reading.

What not to delete

Anything with a record function. Decisions and why you made them, agreements, medical or financial notes, anything you might need to demonstrate rather than remember.

Writing you did for its own sake. If a note is a piece of thinking you value as writing, it is not archive material and the rules here do not apply.

And things about other people, which should be handled as a separate question — some of that material should never have been saved, and deleting it is the correct action rather than a filing decision.

The reframe that makes it possible

Deletion is the output of review, not a failure of it.

A session that removed four notes improved the archive. A session that added four did not. Once that lands, the resistance mostly dissolves, because you stop experiencing deletion as loss and start experiencing it as the thing you came to do.

It also fixes the ratio problem. Capture is over-rewarded and review under-rewarded, and giving review a visible output — a number of notes removed — is the cheapest available correction.

The short version