Habits & Routines · Career

The Second Brain: Why The PARA Method Beats Folder Trees

Tiago Forte's PARA system sorts everything by how close it is to action, not by topic. A folder tree guarantees a graveyard of notes you'll never find again. PARA actually solves the retrieval problem.

By Hank · · Editorial standards

https://taskcoach.ai/blog/second-brain-para-method/

Folder trees are where notes go to die

Picture the average knowledge worker's file system: a folder tree nested eight levels deep, organized by topic. Work, then Project X, then Research, then Articles, then 2024, then Industry, then Competitive Analysis, then Notes. Two hundred files sitting in that last folder, waiting.

The system promises you'll find things later. It doesn't deliver. Getting a note back out costs more than putting it in did, because retrieval means reconstructing a categorization decision you made months ago and have since forgotten.

Tiago Forte's PARA method, laid out in his book Building a Second Brain, fixes this by changing what you sort by. Instead of topic, you sort by how close something is to action. And instead of infinite folders, you get exactly four.

The four buckets

Projects. Time-bound outcomes with a clear finish line. "Launch the new website by Q3." "Finish thesis chapter 3 by April 30." Projects end.

Areas. Ongoing responsibilities with no end date, standards you maintain rather than outcomes you achieve. "Health." "Finances." "Managing the team." Areas don't end, they just continue.

Resources. Topics you're interested in, reference material you want on hand. Neutral until you need it. "Productivity." "Machine learning." Anything worth keeping around without being tied to something you're actively doing.

Archives. Everything inactive. Finished projects, resources you no longer care about. Still searchable, just out of sight.

That's the whole system. Four buckets, and every note lives in exactly one of them.

PARA: four buckets, sorted by action distance, not topic.

Why sorting by distance to action beats sorting by topic

Take a note about exercise. Where does it belong? That depends entirely on your life right now, not on the topic itself.

If you're training for a marathon, it's a Project. If it's just part of how you live day to day, it's an Area. If you're generally curious about exercise science but not doing anything with it, it's a Resource. If you used to run and don't anymore, it's an Archive.

Notice the topic never told you where to file it. Your current relationship to the topic did, and that's a fast decision because it depends on your life, not on some taxonomy you have to remember.

Compare that to a folder tree: "I think it was under Work, or maybe Personal, definitely from 2024..." Twenty guesses, most of them wrong.

Projects are the bucket that actually runs your day

Projects drive daily attention. Areas show up weekly. Resources stay passive until needed.

Here's the part people miss: Projects should get most of your daily attention, because they're the most active bucket by design. Areas move slower. Resources sit passively until you need them. Archives almost never come up at all.

Your day-to-day workflow should mostly live in Projects. Areas get checked weekly. Resources get pulled up when something specific calls for them. Archives you basically forget exist, until you need to dig something up.

What happens when a project finishes

Reusable assets to Resources. Standards to Areas. Specifics to Archives. The active workspace stays small.

When a project wraps up, it doesn't just vanish. It splits three ways:

  1. Anything reusable, templates, frameworks, moves to Resources.
  2. Any standard or practice that emerged from the work moves to the relevant Area.
  3. Everything else, the specifics that only mattered to that one project, moves to Archives.

After that split, Projects only contains what's actually active. The workspace stays small on purpose.

Where people trip up

Treating aspirations as projects. "Write a book" isn't a project, it's a fantasy with no finish line. "Finish the first draft of chapter one by February 15" is a project.

Mixing up Areas and Projects. "Get healthier" is an Area. It never really ends. "Run a half-marathon by May" is a Project. It has a date.

Turning Resources into a junk drawer. Be picky about what goes in. If you wouldn't deliberately reread it a year from now, it belongs in Archives instead.

Where TaskCoach.AI fits in

Spaces in TaskCoach.AI are basically PARA's Projects bucket made into a first-class feature: each Space bundles the goals, tasks, calendar, focus sessions, and notes tied to one specific project.

Habits live in the Areas layer, ongoing standards rather than outcomes with a deadline. Notes cover the Resources layer through its knowledge graph. And Archive quietly moves finished Spaces out of your way once they're done.

None of that overlap is an accident. The whole structure runs on the same logic PARA does.

The bottom line

Four buckets, sorted by how close something is to action, not by what it's about.

Projects are outcomes with a deadline. Areas are standards with no deadline. Resources are things worth keeping around. Archives are everything you're done with.

If your notes feel like a graveyard right now, the topic tree is probably why. Sort by action distance instead, and the graveyard turns back into something you can actually use.

Frequently asked questions

What is the PARA method?

Tiago Forte's system for organizing notes into four buckets: Projects (time-bound outcomes with a clear finish line), Areas (ongoing responsibilities with no end date), Resources (reference material and topics of interest), and Archives (everything inactive). Every note lives in exactly one bucket, sorted by how close it is to action rather than by what it's about.

Why does sorting by action beat sorting by topic?

A topic-based folder tree promises you'll find things later, but retrieval means reconstructing a filing decision you made months ago, which mostly fails. A note about exercise could belong in Projects if you're training for a marathon, Areas if it's an ongoing habit, Resources if you're just curious about the science, or Archives if you used to run and stopped. The topic never tells you where it goes. Your current relationship to it does.

How do I switch from a folder tree to PARA without redoing everything?

Don't reorganize everything at once. Dump the old folder tree into Archives, then start filing new notes into the four PARA buckets from today forward. When you need something old, find it with search and refile it into PARA at that point. Most of the old tree will never get touched again, which itself tells you how much of it was worth organizing in the first place.

What happens to a project's notes once it's finished?

Anything reusable, like templates or frameworks, moves to Resources. Any standard or practice that came out of the work moves to the relevant Area. Everything else moves to Archives. After that split, Projects only holds what's actually active, which keeps the whole workspace small.