PARA Method Explained: How to Organize Notes by Action

You have hundreds of notes and no idea where anything is. You've tried elaborate folder trees organized by topic — Work, Personal, Health, Ideas — and they always rot. The PARA method is a different answer: organize by how actionable something is, not what it's about. It was created by Tiago Forte, who popularized it through his Building a Second Brain course and book, and it has become one of the most widely used systems in personal knowledge management because it's small enough to actually maintain.

What the PARA method actually is

PARA gives you exactly four top-level buckets. Everything you capture lands in one of them.

Projects

Short-term efforts with a clear finish line and (roughly) a deadline. The test: you'll know when it's done.

Examples: Launch the spring newsletter, Plan the Lisbon trip, Redesign the pricing page, File 2025 taxes.

Areas

Ongoing responsibilities with a standard to maintain but no end date. You never "finish" an area — you keep it healthy.

Examples: Health, Finances, Team management, Apartment, Professional development.

Resources

Topics you're interested in that aren't tied to a current responsibility. This is where curiosity lives.

Examples: Sourdough baking, Typography, Woodworking, AI research papers, Recipes.

Archives

Anything inactive from the other three: finished projects, areas you've exited, resources you've gone cold on. Nothing gets deleted — it just gets out of the way, and search still finds it.

Examples: Launch the spring newsletter (shipped), Old job, Wedding planning.

Here's the whole system at a glance:

Bucket	Time horizon	The test
Projects	Weeks to months	Has a finish line
Areas	Indefinite	A standard to maintain
Resources	Indefinite	Interesting, no obligation
Archives	Past	Inactive, kept for reference

Why actionability beats topic

Topic-based systems fail for a sneaky reason: most notes plausibly belong in several topics. A note about negotiating your hosting contract — is that Work? Finances? Vendors? You hesitate, pick one, forget which, and eventually stop filing at all. Filing by topic forces a hard decision at the worst possible moment: capture time.

Actionability makes the decision nearly automatic. Is this for a current project? File it there. Serving an ongoing responsibility? Area. Just interesting? Resource. Done with it? Archive. One question, asked in order, answers itself in seconds.

The deeper benefit: your Projects folder becomes an honest mirror of your commitments. If there are fourteen folders in it, you have fourteen active projects — a fact most people discover with mild horror, and exactly the kind of thing worth confronting in a regular review. Compare that with a topic tree, which tells you nothing about what you're actually doing this month. If you're building toward a full second brain, PARA is usually the organizational layer underneath it.

Migrating a messy vault in one afternoon

The classic mistake is trying to sort every old note into its proper place. Don't. Forte's own advice is more ruthless, and it's why the migration fits in an afternoon:

1. Create the four folders. Projects, Areas, Resources, Archives. That's the whole structure.
2. Move everything you have into Archives. Yes, everything. Date the batch (e.g. Archive/2026-06 old vault) so you can find it. This feels wrong and is the entire trick — your old mess becomes searchable storage instead of a guilt pile.
3. List your actual current projects from memory. Not from your notes — from your calendar, your inbox, your anxieties. Make a folder per project. Most people have 5–15.
4. Add areas as they occur to you. Don't brainstorm them exhaustively; the important ones (health, money, your team) surface within a week.
5. Pull notes out of Archives on demand. When a project needs an old note, search for it and move it. Notes earn their way back into the active system by being used.

That's it. Two hours, mostly spent on step 3, which is really a review of your life — no bad thing. For the ongoing habits that keep the structure honest, see our guide on how to organize notes without creating a filing system you'll abandon.

A tool note: PARA is deliberately tool-agnostic. It works in plain folders, in Notion, in Obsidian — and in Stacy, where nested pages give you the four buckets and backlinks — links that work in both directions, so a page knows what points at it — let a note in Resources surface inside the project that cites it, without moving anything.

Where PARA struggles

Honesty time: PARA is optimized for doing, not for knowing, and it shows in reference-heavy work.

• Deep research doesn't fit. If you're an academic, analyst, or writer whose raw material is notes on topics, "Resources" becomes a junk drawer of hundreds of notes with no internal structure. PARA has no opinion about what happens inside a folder.
• Cross-cutting ideas get orphaned. An insight that connects three projects belongs in all of them and lives in none. Folder systems can't express that; you need links. The Zettelkasten method was built for exactly this connection-first work, and backlinks patch the gap inside PARA.
• Archives-first migration assumes good search. If your tool's search is weak, "just pull it from Archives" turns into dread.

A common and sensible hybrid: PARA for your working life, plus a linked, topic-dense zone for long-term research. The two coexist fine.

The takeaway

Four folders, one question — how actionable is this? — and a migration that starts by archiving everything. The PARA method won't structure your deepest research, but for keeping projects, responsibilities, and interests from blurring into one anxious pile, it remains the simplest system that actually survives contact with a busy life.