What the PARA method gets right, where its four folders creak in daily use, and the smaller habit — a live project list — worth keeping either way.
· Note-Taking Methods · 7 min read
Ask the internet how to organize your notes and the answer you hit first, these days, is PARA: four top-level folders — Projects, Areas, Resources, Archive — into which, the pitch goes, anything you will ever save can be sorted in about three seconds. The method comes from Tiago Forte's Building a Second Brain, and its popularity is earned: it replaces the hardest question in filing with a much easier one.
It also ships with a fair amount of ceremony, and most write-ups don't separate the ceremony from the insight. This one tries: what PARA actually says, why its core move genuinely works, where the four folders creak in daily use, and the one piece worth keeping even if you never create a folder in your life.
PARA sorts everything you keep — notes, files, bookmarks — into four containers, ordered by how actionable they are:
The sorting rule is the entire trick. You never ask what is this note about? — the question that makes topic hierarchies miserable. You ask when will I act on this? Soon, toward a specific outcome → the project. Indefinitely, as upkeep → the area. Someday, maybe → resources. No longer → archive.
Topic is ambiguous at the worst possible moment. A note about a client's API plausibly belongs under the client, under engineering, or under the migration — and whichever folder you pick, future-you will look in the other two first. Actionability is usually obvious at that same moment: the note exists because of the migration, so it goes with the migration. PARA works because it swaps a taxonomy question you can get wrong for a scheduling question you mostly can't.
Notice what the four folders actually model underneath the acronym: not subjects but lifecycle — active, ongoing, dormant, done. That happens to be the one job folders are good at. A folder holds a note in exactly one place, which is fatal for topics (most notes belong to several) and perfect for status (a project is either live or it isn't). PARA is less a filing philosophy than a disciplined application of the rule that folders should mark boundaries, not subjects.
It also front-loads the most valuable list you can own: the Projects folder is a list of your current commitments. Most people cannot produce that list on demand. If PARA did nothing but force it into existence, it would still pay for itself.
Projects must end. A project with no deadline and no definition of done is an area wearing a costume, and it will sit in the folder for a year, radiating guilt. The test is blunt: if your project list hasn't changed in two months, it is not a list of projects.
Archive constantly, delete rarely. The archive is what keeps the other three folders small enough to stay legible. Moving a finished project there costs one drag, loses nothing — search still reaches archived notes — and is reversible the day a dead project revives. People who describe PARA as "clean" are really describing an archiving habit.
Organize at the moment of use, not capture. Official PARA blesses lazy filing: capture into an inbox or straight into the current project, and sort something only when you actually need it for real work. Organizing just-in-case is the classic dead-end weekend; organizing just-in-time is a few seconds attached to something you were doing anyway.
The project/area boundary is clean in the book and muddy in a vault. "Run a 10k in October" is a project; "fitness" is the area it serves; the notes feeding both are the same notes. PARA's answer — file by where you'll use it next, move it later — is workable, but "move it later" is doing a lot of quiet work in that sentence.
Resources is a landfill with a nicer name. It is the someday/maybe bucket, and nothing in the method ever brings a resource back to you. Retrieval depends entirely on remembering that the note exists, which is exactly how notes disappear. Search mitigates this; the folder itself contributes nothing.
The shuffle is real maintenance. PARA's legibility is purchased with constant moves: project finishes → archive; interest becomes responsibility → resources to areas; responsibility hands off → archive again. Skip a few weeks and the folders start lying about your life, which is worse than no folders, because now the structure itself is stale information. Every folder scheme rots when upkeep stops — PARA just rots in four places at once.
It organizes doing, not thinking. This is the deepest limit. PARA tells you where a note sits; it does nothing to connect one idea to another. A note filed perfectly under Resources is still an orphan — well stored, never encountered. Filing is not understanding, and no arrangement of four folders produces the collisions between ideas that linking exists to produce.
The two methods are routinely pitted against each other, which is a category error. PARA arranges working material around commitments: it is a desk. A Zettelkasten grows a web of ideas independent of any deadline: it is a library. One optimizes for shipping the current thing, the other for compounding what you learn, and plenty of people run both at once — PARA-shaped structure for deliverables and admin, links for ideas. The combination is coherent precisely because the two systems never claim the same note for the same reason.
If you keep only one, let the choice follow your actual pain. Drowning in active work and losing track of commitments points to PARA. Reading a lot and retaining little points to linked notes. "Both" is a fine answer; "neither, just search" is underrated too.
Strip PARA to its load-bearing element and what remains is small: a live list of your projects, each with one home where its material accumulates, and a way for finished work to leave the view. Everything else — the R, most of the A — is carried perfectly well by search, tags, and links in any modern app.
Folderless PARA looks like this:
#archive tag or a "Done" parent and drops out of daily view; search still reaches it the day it matters again.In an outliner this barely qualifies as a system. In Indenta, for instance, a project is just a note: material indents under it, [[wiki-links]] pull in whatever the project touches, backlinks accumulate on the project note automatically, and the archive is one tag — no folders involved (the User Guide covers the mechanics). The point is not that folders are wrong; it's that the insight — actionability first, archive aggressively — survives without them.
If PARA appeals, resist beginning the way most people do: creating four empty folders and spending a weekend re-filing three hundred old notes. That archaeology is where reorganizations go to die. Begin with ten minutes instead. Write the list of projects you are genuinely committed to right now — it will be shorter than you expect and more clarifying than any folder tree. Give each project one home. Sweep everything older than the list into an archive, unexamined; search will find it if it's ever needed.
That list is the part of PARA that survives contact with real life. The folders are optional — some people find the four boxes calming and should keep them. But the method's actual discovery is smaller and better than its diagram: current work deserves a visible home, finished work deserves to get out of the way, and "what is this about?" was never the right filing question.
Try it in practice: Indenta is a free, offline-first outliner — nested notes, backlinks, tags, and peer-to-peer sync, with no account required. Start writing in your browser, or read the User Guide first.