The PARA Method: Organize Notes by Action, Not Topic

PARA is an acronym for Projects, Areas, Resources, and Archives — four categories that every note, file, and document you keep drops into. Forte describes it as a 'simple, comprehensive, yet extremely flexible system for organizing any type of digital information across any platform.' That last part is the appeal: the same four buckets are meant to structure your notes app, your file system, and your cloud storage identically, so you're not learning a new scheme for every tool.

The method comes out of Forte's broader work on what he calls a 'second brain' — an external system for storing and using the information you encounter. PARA is the organizing layer of that idea, laid out in his book 'Building a Second Brain' (Atria Books, 2022).

What makes PARA worth understanding isn't the four labels themselves — plenty of systems have categories. It's the rule for which bucket something goes in, and that rule is the opposite of how most of us were taught to file things.

Forte's central observation is that most of us first learned to organize information in school — sorting it, as he puts it, 'by academic subject, such as Math, History, or Chemistry.' We carry that habit into adult life and build topic folders for everything. The problem is that a topic tells you nothing about whether you need that information now, next month, or possibly never.

PARA's principle is to organize information instead 'according to the projects and goals you are committed to right now' — what Forte calls organizing by actionability. The four categories form a rough gradient from most actionable to least: Projects are what you're actively pushing on, Areas are what you maintain, Resources are what you might reference, and Archives are what's done.

The practical payoff is focus. When you sit down to work, the material tied to your current commitments is grouped where you can see it, while interesting-but-not-urgent reference material is filed out of the way rather than competing for attention. You stop scrolling past a 'Marketing' folder that contains a 2019 webinar, this quarter's launch plan, and an article you half-read — three things at completely different levels of urgency.

Here are Forte's own definitions of the four buckets, in order of how actionable they are:

Because PARA is platform-agnostic, setup is the same wherever you keep things: create four top-level folders — Projects, Areas, Resources, Archives — in your notes app, your file system, and your cloud drive, and use the identical structure in each.

A common way to start, without a daunting cleanup day, is to sweep your entire existing mess into the Archives folder first. Nothing is lost, but you get a clean slate. Then you pull items back out into Projects only as you actually need them for current work — which means your live folders fill with what's genuinely relevant rather than with everything you've ever saved.

From there, give each active project its own subfolder under Projects, and add Area and Resource folders only when you actually have something to put in them. Creating empty category folders 'just in case' is how PARA slowly turns back into the topic-folder sprawl it was meant to replace. Keep it shallow: four buckets at the top, a thin layer of project and area folders inside, and not much more.

PARA is genuinely useful, but it isn't magic, and it's worth knowing where it gets awkward. Even Evernote — which supports the method — publishes a fair critique noting its 'potential for oversimplification, where complex and overlapping projects might not fit neatly into one category,' and warning that 'creative projects with evolving structures might outgrow the rigid confines of these categories.' Real work is often messier than four buckets.

The second friction is the Areas-versus-Resources judgment call. Is your reading on a subject a Resource (a topic you're learning) or part of an Area (an ongoing responsibility)? The honest answer is that it's often genuinely ambiguous, you'll classify the same thing differently on different days, and you'll re-sort. PARA tolerates this, but it doesn't eliminate the small decision tax of filing.

Third, PARA needs maintenance. Its clarity depends on you actually moving finished projects to Archives and keeping current commitments in Projects. Neglect that for a few weeks and it quietly drifts back into a pile — a tidier pile than before, but a pile. And there's a deeper limit worth naming: PARA tells you where to put a note, but not how to find it later when you can't remember which bucket you chose. For that, the structure matters less than being able to search the contents.

PocketNote isn't a folder system, and it won't make you sort everything into Projects, Areas, Resources, and Archives. But it removes the friction PARA leaves untouched: finding a note later when you can't remember which bucket you filed it in. You upload PDFs, slides, lecture videos, web pages, and your own notes into one searchable space, and its source-grounded chat answers from that material and shows you exactly where each answer came from — so retrieval doesn't depend on remembering your own filing decisions.

If you do run PARA, the two work well together: keep your four-bucket structure wherever you like it, and use PocketNote as the layer that actually reads and connects the material you've collected. A 'Resources' pile of saved readings stops being a graveyard and becomes something you can ask questions of directly.