What is the PARA method?

PARA stands for Projects, Areas, Resources, Archives — a filing system created by Tiago Forte. It sorts every note, file, and task by how actionable it is right now, instead of by topic. Projects are things with a deadline; Areas are ongoing responsibilities; Resources are topics of interest; Archives are anything inactive.

What's the difference between PARA and CODE?

CODE is the whole Second Brain workflow: Capture, Organize, Distill, Express. PARA is one specific way to do the Organize step. You can follow CODE without using PARA — and you can use PARA outside a Second Brain system.

Why do PARA systems collapse?

PARA needs constant maintenance. Every note has to be filed into the right bucket, and buckets need to be reviewed weekly as projects finish and interests shift. Most people quit inside a month. The system works for people who genuinely enjoy filing — a small minority.

Do you need PARA to have a second brain?

No. PARA is a filing system; a second brain is any external store of what you know. If a tool can retrieve the right note without you filing it, you don't need PARA. Flowgod is built on that bet: capture without organizing, ask questions to retrieve.

Is PARA better than folders by topic?

For most people, yes — filing by actionability beats filing by topic because you retrieve notes when you're working on something, not when you remember a topic. But 'better' assumes you'll actually keep the system up. If you won't, both fail equally.

Guide · PARA method

The PARA method, honestly.

Projects, Areas, Resources, Archives. Tiago Forte's filing system is clever. It also asks for weekly maintenance most people won't do. Here's the practical version.

What is PARA?

PARA is a filing system that sorts every note, file, and task by how actionable it is right now — not by topic. It comes from Tiago Forte's book Building a Second Brain, and it powers the “Organize” step of the CODE framework.

The idea: when you sit down to work, you don't need every note about “marketing.” You need the notes for the marketing project you're shipping this week.

The four buckets

PARA — Projects, Areas, Resources, Archives.

Projects

Short-term efforts with a deadline and a defined outcome.

Example
Launch the podcast. Ship v2. Plan the wedding.

Areas

Long-term responsibilities you maintain over time.

Example
Health. Finances. The team you manage.

Resources

Topics you're interested in but not actively working on.

Example
Sourdough. Rome in the 3rd century. Rust.

Why most PARA systems die

PARA has a maintenance cost the tutorials rarely mention. Every incoming note needs a home. Projects finish and their notes need to move to Archives. Interests shift and Resources need pruning. Areas need reviewing.

The recommended cadence is a weekly review. For a small percentage of people, that's satisfying. For most, it's the reason the system quietly dies at week three, buried under a Projects folder that has forty “projects” in it, half of which finished a year ago.

PARA works. For the people who file. Everyone else builds a graveyard.

What if you skip PARA entirely?

The goal of PARA isn't filing — filing is the cost. The goal is retrieving the right note when you need it. PARA is one way to solve that. AI retrieval is another.

Flowgod is built on the opposite bet from PARA: you'll never file, and that's fine. Capture everything in one inbox — text, voice, PDF, screenshot. Ask a plain-English question when you need it back. No Projects folder. No Areas. No weekly review.

If you love PARA as a thinking framework — sorting your life by actionability — keep it in your head. You just don't need to enforce it inside the app.

FAQ

Frequently asked

What is the PARA method?: PARA stands for Projects, Areas, Resources, Archives — a filing system created by Tiago Forte. It sorts every note, file, and task by how actionable it is right now, instead of by topic. Projects are things with a deadline; Areas are ongoing responsibilities; Resources are topics of interest; Archives are anything inactive.
What's the difference between PARA and CODE?: CODE is the whole Second Brain workflow: Capture, Organize, Distill, Express. PARA is one specific way to do the Organize step. You can follow CODE without using PARA — and you can use PARA outside a Second Brain system.
Why do PARA systems collapse?: PARA needs constant maintenance. Every note has to be filed into the right bucket, and buckets need to be reviewed weekly as projects finish and interests shift. Most people quit inside a month. The system works for people who genuinely enjoy filing — a small minority.
Do you need PARA to have a second brain?: No. PARA is a filing system; a second brain is any external store of what you know. If a tool can retrieve the right note without you filing it, you don't need PARA. Flowgod is built on that bet: capture without organizing, ask questions to retrieve.
Is PARA better than folders by topic?: For most people, yes — filing by actionability beats filing by topic because you retrieve notes when you're working on something, not when you remember a topic. But 'better' assumes you'll actually keep the system up. If you won't, both fail equally.

The second brain that skips the filing.

Zero setup. No PARA, no folders, no weekly review. Just capture and ask.

Try Flowgod free Read the Second Brain guide →