PARA is an acronym that describes four organisational categories: Projects, Areas, Resources and Archive. It was popularised by Tiago Forte as part of his “Building a Second Brain” methodology, although its principles are older and its application is independent of any specific tool or methodology.

What makes it particularly useful is not that it is the “correct” system (no such thing exists), but that it organises information by usefulness at the present moment, not by topic. And that changes a great deal about how you interact with your own system.

Why topics are not enough

Imagine you have a folder called “Finance”. Inside there are articles on investment, annotations from a book you are reading, a budget for a renovation project that you need to actively track this week, and notes from a conference you attended two years ago.

All of that is “finance”. But its relevance to you right now is radically different. The renovation budget needs immediate attention. The conference notes from two years ago can wait indefinitely.

Topic-based organisation mixes the urgent with the inactive. PARA separates them.

P: Projects

A project is anything that has a concrete outcome and a deadline. “Write the Q2 report”, “organise the August holiday”, “launch the newsletter”, “read the systems book”: if it has a clear end and a defined time horizon, it is a project.

Projects are the most active category and the one that requires the most attention. In your system, projects should be in the most accessible place: they are the ones you will consult and update every day.

A good practice: limit the number of active projects. More than ten simultaneous projects is usually a sign that many of them are not really active.

A: Areas

Areas are responsibilities or dimensions of your life that have no end date, but that require ongoing attention: health, personal finance, relationships, professional development, home. An area does not end; it is maintained.

Areas are less urgent than projects, but more important in the long run. In your system, they live at a second level of accessibility: you consult them less frequently, but regularly.

The key difference between a project and an area: a project has an objective that can be completed. An area has a standard that is maintained.

R: Resources

Resources are reference information that may be useful in the future, but which is not tied to any active project or area. Books you want to read, ideas on a topic that interests you generally, templates and references that might come in handy someday.

Resources are the largest category and the least urgent. You do not consult them frequently, but when you need them, they are there.

Beware of the resource illusion: not everything that does not fit in projects or areas deserves to be a resource. Many things are simply not worth keeping.

A: Archive

The archive is the destination for everything that is no longer active: completed or abandoned projects, areas that are no longer relevant, resources that turned out not to be. The archive is not deleted: it sleeps.

The archive serves a dual function. On one hand, it keeps the main system clean and focused on what is active. On the other, it preserves the history in case you ever need to return to something you thought was definitively past.

The archive is easy to maintain: when something ceases to be active, it goes to the archive. No deliberation, no analysis. Just move.

How information flows between categories

PARA’s categories are not static. Information flows between them:

  • A resource that becomes relevant to an active project moves up to Projects.
  • A completed project moves down to Archive.
  • An area that ceases to be relevant (you changed jobs, moved city) moves down to Archive.
  • A resource idea that becomes a concrete project moves up to Projects.

This dynamism is what keeps the system useful over time.

What PARA does not solve

PARA is an organisation system, not a processing system. It tells you where to put things, but not how to turn them into your own knowledge. For that you need the next link: notes and processing.

It also does not tell you how to capture. Or how to review. It is just a structure. A very useful structure, but only one part of the complete system.

In the next chapter we talk about something finer: personal taxonomy, how to name things consistently so you can find them when you need them.