The PARA Method for Notes: Tiago Forte's System, Pros and Cons

Tiago Forte's PARA method is the most-implemented information-organization framework of the last ten years. Forte's book Building a Second Brain popularized it. Millions of users have adopted some version. The framework has real value. It also has blind spots, and understanding both makes the difference between adopting it thoughtfully and adopting it as dogma.

What PARA is

Four categories, used as the top-level organization in your notes app, file system, and cloud storage:

• Projects — short-term efforts with a defined outcome and deadline.
• Areas — ongoing responsibilities you maintain indefinitely.
• Resources — topics of ongoing interest or reference material.
• Archives — completed projects, inactive areas, old resources.

The claim: any piece of information fits into one of these four categories, and the boundaries between them are portable across tools.

How to implement PARA

Step 1: Create the four top-level folders in your notes app (Obsidian, Notion, Apple Notes), your file system (Documents / iCloud / Dropbox), and your cloud drives. The consistency is part of the point.

Step 2: Sort your current stuff. Look at your existing notes, files, and folders. For each, ask: Is this active work toward a specific outcome (Project)? Is this an ongoing area I maintain (Area)? Is this topical reference (Resource)? Is this inactive (Archive)?

Step 3: Review regularly. As projects complete, move them to Archives. As resources become projects, promote them. PARA is meant to be a living structure, not a one-time sort.

Where PARA works well

File systems. For organizing files — PDFs, documents, media — PARA is excellent. The four-folder structure is legible, portable, and prevents the "Documents folder with 800 files" problem.

Cross-tool consistency. Having the same four folders in your notes app, file system, and cloud storage makes cross-tool navigation easier. Everything lives in one of four places.

Project-based workflows. Consultants, agencies, and anyone with discrete client or deliverable work will find PARA's project-centric framing natural.

Archiving. The "move to Archives when done" discipline is the best part of PARA. It keeps active workspaces clean without deleting history.

Where PARA falls down

Projects vs Areas is a mushy distinction. Forte defines Projects as having a specific outcome and deadline; Areas as ongoing responsibilities. In practice, many of my "Areas" have implicit outcomes (maintain good health, run my business profitably), and many of my "Projects" have no clear end date. Users waste hours debating which category something belongs in.

Atomic note-taking doesn't fit. For users who take small, linked notes as a thinking practice (Zettelkasten, Obsidian-style PKM), PARA is the wrong frame. Atomic notes don't belong to one project or area; they cut across them.

Deep knowledge management. PARA is organized around actionability — what are you working on. A knowledge base organized around concepts, ideas, and questions doesn't map cleanly onto Projects/Areas.

Overhead. Maintaining PARA consistently across multiple tools requires ongoing discipline. For users whose actual problem is "I don't take enough notes," adding PARA overhead makes the problem worse, not better.

When to use PARA

• Organizing files, documents, and cloud storage
• Consultants and agencies with discrete client work
• Users who feel overwhelmed by unorganized piles of stuff
• Project-heavy workflows with clear deliverables

When to not use PARA

• Deep PKM with atomic linked notes
• Users whose issue is under-capture, not poor organization
• Research and writing work with fuzzy boundaries
• Users who already have a working system

A pragmatic hybrid

In my own setup, I use PARA for files (Documents, Dropbox, cloud storage) and for project-level notes in Notion. I do not use PARA for my Obsidian vault, where notes are organized by tags and backlinks rather than folders. This hybrid works better than trying to apply one framework to every surface.

The honest bottom line

PARA is a good framework for a specific problem: organizing files and project materials across multiple tools. It is an imperfect framework for note-taking, and Forte's book overclaims when it positions PARA as the universal organizing principle for a "second brain." Adopt PARA selectively. Where it fits, it helps. Where it doesn't fit, use something else.