PARA and Folder Methods
PARA is a folder scheme with four top-level buckets: Projects, Areas, Resources, Archive. Everything goes in one of them, and the sorting principle is actionability rather than subject.
It is the most widely adopted organising method in this space, it contains a genuinely good idea, and it addresses a problem most people do not actually have.
A related workplace concept is accountability and responsibility in the workplace, which offers a useful contrast with the personal knowledge-work problem discussed here.
The good idea
Sort by how soon you will act on it, not by what it is about.
Subject-based organisation fails because subjects are ambiguous and overlapping. A note about pricing a website belongs under pricing, business, clients, and web — which means it belongs nowhere, and you spend the filing moment deciding rather than working.
Actionability is far less ambiguous. Is there a project this serves? Is it an ongoing responsibility? Is it neither, but might be useful? Is it done?
For an independent external reference related to this topic, see Forte Labs.
That single reframe removes most of the friction in filing, and it is worth taking whether or not you adopt the rest.
The second good idea is the archive bucket: things move out without being deleted. Lower psychological cost than deletion, and it keeps the active space small.
What it does not address
Retrieval. PARA tells you where to put things. It does not bring anything back.
A well-organised archive and a badly-organised one are equally silent. Nothing in a normal day triggers returning to either, and folders do not change that. Organisation is a capture-side improvement to a problem that lives on the other side.
That is not a criticism of the method for failing to do something it never claimed. It is a warning about what adopting it will and will not fix — because people arrive at PARA feeling that their notes are not working, and reorganising is the fluent, satisfying half of the pair.
Where it works well
Work with real projects. If you have five or six live projects with deliverables, the project folder is genuinely useful and the boundary is obvious.
Files as much as notes. PARA was designed for a mixed environment — documents, references, notes together — and it handles that better than note-specific methods.
People who want less filing, not more. Four buckets is a small decision, and small decisions get made.
Where it strains
Notes that are thinking rather than material. Most notes are thinking, and thinking notes serve no project and are not quite reference. They end up in Resources, which becomes an undifferentiated pile — the same problem in a new folder.
Long-running interests without projects. If you read about something for years without a deliverable, actionability does not classify it usefully.
And the maintenance is real. Projects finish and have to be archived, areas drift, resources accumulate. A scheme that is not maintained decays into folders you no longer trust, which is worse than no scheme because you still have to look in them.
Folders or links
The standing argument, and the honest answer is that it matters less than either side claims.
Folders are good at exclusion — one location, easy to scan, easy to archive wholesale.
Links are good at connection — one note in many contexts, and the connection itself is recorded.
Both are capture-side. Whichever you choose, you still need something that returns a note to you when you were not looking for it, and neither provides it.
For most people the practical answer is a shallow folder structure for containment plus search and good titles for finding — and titles do more work than either scheme.
The recommendation
Take the actionability principle. It is the durable part.
Keep the structure shallow. Four buckets, or three, and no sub-sub-folders. Depth is where schemes go to die.
Archive rather than delete, at first. Deletion gets easier once archiving has proved that nothing was missed.
And do not expect it to fix the problem you actually have. If your complaint is that you never return to your notes, reorganising them will feel productive and change nothing — which I established over four consecutive weekends.
The short version
- PARA sorts by actionability rather than subject, which removes most of the friction in filing
- The archive bucket is the second good idea: things leave the active space without being deleted
- It is a capture-side method and does not address retrieval, which is usually the actual complaint
- It strains on thinking notes and long-running interests without deliverables
- Folders exclude, links connect, and both are capture-side — neither returns anything to you
- Take actionability, keep the structure shallow, archive before deleting, and expect no retrieval benefit