Concepts & methods

The PARA method: what it solves, and what it cannot do

Tiago Forte's four folders organise notes by actionability instead of topic, and the idea genuinely works. A reference entry on what PARA fixes, the maintenance it quietly demands, and the job it was never built for.

Aleem O'BalogunBy Aleem O'Balogun|Updated |4 min read

The short answer

PARA is Tiago Forte's method for organising notes and files into four folders by actionability: Projects (active, with an end), Areas (standards to maintain), Resources (topics of interest), and Archives (everything inactive). It solves the filing problem elegantly. It is a storage architecture, though, not a planning system: it holds work, it does not run it.

What it is, and who made it

PARA is the organising scheme Tiago Forte introduced on his blog in 2017 and canonised in Building a Second Brain (2022): four top-level folders, Projects, Areas, Resources, Archives, applied identically across every tool you use. The insight is the sort key. Filing by topic asks a question with no urgent answer (“where does this belong in the tree of knowledge?”); filing by actionability asks the only question that matters at speed: how soon will I act on this? A project has an end date and current momentum; an area is a standard you maintain indefinitely; a resource is interest without obligation; the archive is everything cooled. The canonical write-up is at fortelabs.com.

What it actually solves

PARA kills the two classic filing failures at once: the forty-minute taxonomy session that produces a beautiful tree nobody retrieves from, and the single “notes” pile where everything is technically captured and practically lost. Because the categories are defined by action rather than subject, the system self-prunes: finished projects roll to the archive, and what remains in view is, by construction, what is live. The projects-versus-areas distinction is the sleeper hit; realising that “health” is not a project you can finish but a standard you maintain reframes more than filing.

Where it breaks

The honest cost is that actionability decays. Projects stall, areas blur, and the sort that was supposed to be instant becomes a small standing tax of re-filing; skip it for a month and PARA degrades into topic folders with confident names. The deeper limit is scope. PARA tells you where a thing goes, never when anything happens. There is no cadence in it, no review, no mechanism by which a note in an area folder ever interrupts your week to say the renewal is due. Forte is straightforward that the method organises information for action; the acting is left entirely to you.

How it maps to the notice loop

On the notice loop's verbs, PARA is the organise half of capture and nothing else, by design. What lands gets a home fast, and the home signals its own urgency, which genuinely helps the later verbs. But nothing in PARA notices, shapes, reviews, or learns; the folders hold what you put in them until you come back. The practical pairing writes itself: PARA (or any storage scheme you already trust) underneath, and a weekly rhythm on top that reads the projects list and turns it into an actual week. Storage architecture and operating rhythm are different layers, and the folders were only ever the first one.

Sources

Primary sources for the method as described; the assessment is editorial.

  • Tiago Forte, The PARA Method (2017) and Building a Second Brain (2022; buildingasecondbrain.com). The four categories, the actionability sort key, and the organise-for-action scope.
← All guides