Both of these exist to kill the same moment: the pause before you save a file, when you realise it could sensibly live in three places, and you pick one at random that your future self will not think of.
They answer that pause in opposite ways. PARA says the location should follow the item's status, so it moves as your life moves. Johnny.Decimal says the location should follow a fixed map you design once, so it never moves at all.
Which is right for you depends almost entirely on whether your material is churning or accumulating.
Side by side
| PARA | Johnny.Decimal | |
|---|---|---|
| Filing question | "What is this for, and how soon?" | "Which numbered category is this?" |
| Structure | Four buckets: Projects, Areas, Resources, Archive | Up to 10 areas, 10 categories each, numeric IDs like 22.04 |
| Depth | Shallow, two levels in practice | Strictly two levels, by rule |
| Items move | Constantly, as things start and finish | Almost never |
| Setup cost | Ten minutes | An afternoon, plus revisions |
| Maintenance | Ongoing sorting as status changes | Almost none once the map is right |
| Best material | Live work with deadlines | A stable archive of documents |
| Fails when | Everything is a Resource and nothing gets archived | Something genuinely does not fit the map |
PARA: the location tells you the status
PARA's real trick is that it refuses to file by topic. Topics are infinitely divisible and every item belongs to several of them, which is why topic folders multiply until they are useless. Actionability has one answer per item at any given time.
The four buckets in short: Projects have an end date, Areas are ongoing responsibilities, Resources are things you might want later, Archive is everything finished.
Its underrated property is self-cleaning. Because finished projects move to the Archive, your working view stays roughly the size of your actual commitments, without you ever running a cleanup. Time does the tidying.
Its failure mode is equally predictable. Resources becomes a landfill. Everything ambiguous lands there, nothing ever leaves, and after a year you have a bucket you cannot search meaningfully and a vague sense of guilt. That is the collector's fallacy with a nicer folder name.
Johnny.Decimal: the number is the answer
Johnny.Decimal takes the opposite bet. Instead of following status, you draw a map of your whole life once, cap it at ten areas and ten categories per area, and give every item an address like 22.04.
Its underrated property is that the map is memorable. After a few months you know that anything tax-shaped is in the twenties, the way you know your own phone extension. Folder paths never achieve this. Numbers do, because there are deliberately few of them.
It also travels across systems in a way PARA does not. The same 22.04 can be a folder on disk, a prefix in a note title, and a sticker on a physical binder, giving you one index across everything you own.
Its failure mode is the exception. When something genuinely does not fit any category, you are choosing between forcing it somewhere wrong and redesigning the map, and neither is cheap. The rule against a Miscellaneous bucket is what makes the system work and also what makes that moment painful.
The real question: churn or accumulation
Forget which is more elegant. Ask what your material does over time.
If your material churns, meaning projects start and finish, priorities shift quarterly, and most of what you touch this month is irrelevant next year, PARA is the better fit. Its whole design assumes movement, and a fixed numeric map would need constant renegotiation to keep up.
If your material accumulates, meaning tax records, contracts, house documents, reference material, manuals, scans, then Johnny.Decimal is the better fit. This stuff does not change status. It just needs one permanent home you will remember in five years, and PARA's Resources bucket is a poor answer for it.
Most people have both kinds. Which is why the combination below is more common than either purist version.
Running both
They stack cleanly, because they operate on different material:
- PARA governs live work. Projects and Areas hold what you are actively doing.
- Johnny.Decimal governs the archive. Numbered categories inside the Archive, or as a separate reference library, give the long-lived documents a stable address.
- The junction is a status change. When a project finishes, it does not just move to the Archive; it gets an address there.
The cost of running both is one extra decision at the moment of archiving, and it is worth paying only if your archive is large enough to get lost in.
The uncomfortable question neither answers
Both systems assume that you must remember where you put something. That assumption was correct when search was bad. It is much weaker now.
Full-text search finds a note by what it said. AI search finds it by what you meant. Under those conditions, meticulous filing is no longer the difference between finding and losing something; it is a preference, and often an expensive one. The evidence is in most people's own history: the elaborate structure built in January, abandoned by March, while the messy searchable pile from the same period is still perfectly usable.
Which is the bet Clair Mind makes. Capture in one tap with no filing prompt, and get things back by asking rather than by navigating. That is the right trade for fast personal capture on a phone. It is the wrong trade for a shared team drive full of contracts, where a human-legible structure that other people can navigate is worth real effort. Be honest about which situation you are in.
Choosing in one line
Churning commitments, low patience for setup: PARA. A large stable archive you will hold for years: Johnny.Decimal. Both, at different layers, if you have both problems. Neither, if your notes are mostly thoughts and your search is good, in which case how to organize your notes is the lighter path.
And if what you actually want is for ideas to connect rather than to be filed, neither of these is that system. That is Zettelkasten vs PARA territory. More in personal knowledge management.