The folder you never open
Every filing system eventually collapses under its own neatness. A look at why folders fail on their own, and what to do instead of reorganising them again.
Somewhere in your bookmarks there is a folder called Read Later, or Resources, or To Sort. You made it with real intent. You have not opened it in a year. You will not delete it either, because deleting it would mean admitting the sixty things inside were never going to be read.
This is not a discipline problem, and the answer is not a better folder structure. It is a structural property of folders themselves.
Why folders collapse
A folder forces one decision at the worst possible moment: where does this belong, decided at the instant you save, before you know why you will want it.
An article about pricing psychology written by a designer you follow, which you are saving because of one paragraph about onboarding — which folder is that? Pricing? Design? Onboarding? That person? You will pick one. In four months you will look in a different one.
Folders ask you to predict the future reason you will want something, using only the present reason you noticed it.
So the structure grows. You add folders to resolve ambiguity, which creates more places to look, which makes finding harder, which prompts more folders. The system gets more elaborate and less useful at the same time — and the elaborateness feels like progress, which is what makes it hard to stop.
What folders are genuinely good at
None of this means folders are useless. They are excellent at one specific thing: bounded contexts with an end date. A client. A trip. A house move. A course you are taking.
These work because the boundary is real and external. You are not guessing where something belongs — it belongs to the client or it does not. And when the project ends, the folder stops growing, which is the property "Read Later" will never have.
Tags are a different shape of answer
A tag does not ask you to choose. That article can be pricing and design and onboarding and that-person, all at once, and it will surface from any of those directions later.
In Trezio these are called charms, and the naming is deliberate — they are meant to feel lighter than filing. You can add several without the sense that you are committing to a taxonomy, because you are not.
Tags have their own failure mode, and it is worth naming: left unchecked you end up with four hundred of them, half near-duplicates, which is just the folder problem wearing a different hat. The guard against that is to keep them few and reusable — tags for how you will look for something, not for what it is about.
Search changes the arithmetic
The strongest argument against elaborate filing is simply that search got good. When search reads the full text of your own notes, transcripts of anything you recorded, the cost of filing something imperfectly drops close to zero.
That is a real shift. Filing systems were designed for a world where an unfiled thing was a lost thing. That has not been true for some time, but the habits survived it.
What to do instead
- Save without deciding. Getting it in beats getting it in the right place. An unsorted item is findable; an unsaved one is gone.
- Make folders only for bounded things — a client, a project, a trip. If it has no end, it should probably be a tag.
- Keep a small, reusable set of tags. Ten you use constantly beat two hundred you used once.
- Star the few you actually return to. This is the most underrated organising act available, and the shortest list you own.
- Let the rest sit unsorted. Search will find it. That is what it is for.
And leave the folder you never open exactly where it is. Not as a task, and not as guilt — just as evidence of a moment when something looked worth keeping. That is all a saved thing ever needs to be.