PARA Method
Projects, Areas, Resources, Archives. Tiago Forte's organization system reduces the question of "where does this go" from twenty folder choices to one of four buckets, organized by actionability rather than topic.
Created by Tiago Forte, Building a Second Brain (2022).
The basics
PARA is a four-bucket system for organizing every digital file, note, link, and document. The buckets are Projects, Areas, Resources, and Archives, in that order of decreasing actionability. The order matters: the top of the list demands the most attention, the bottom stays quiet but searchable. Every item you save eventually lives in one of these four places, and most items move between them as your relationship with the content changes.
A Project is anything with a clear goal and a defined endpoint. "Finish the Q3 marketing plan by Friday" is a Project. "Renovate the kitchen" is a Project. "Launch the new website by August" is a Project. Projects always end, which is what makes them different from Areas. The defining test: can you state the outcome that means this is done? If yes, it is a Project. If no, it belongs somewhere else.
An Area is an ongoing responsibility without a defined endpoint. "My health", "the apartment", "my finances", "the team I manage", "my marriage". Areas are maintained at a standard rather than completed. The defining test: would I feel a sense of failure if I stopped paying attention to this? If yes, it is an Area. Areas often spawn Projects (a renovation comes from "the apartment"; a fitness plan comes from "my health"), but the Area itself outlives any individual Project.
A Resource is reference material for a topic of interest. "Notes on productivity", "saved articles about AI", "recipes I might try", "design references", "books I want to read". Resources are passive: you do not act on them on any schedule, you reach for them when an active Project or Area calls for them. Most of what people save ends up here. PARA explicitly does not require you to act on Resources; their purpose is to be available, not to demand attention.
An Archive is anything from any of the other three buckets that is no longer active. The Project you finished. The Area you stepped away from (the job you left, the team you stopped managing). The Resource on a topic you no longer follow. Archives are searchable but out of sight, so the active buckets stay clean. The key insight: archiving is the opposite of deleting. The content remains; only its prominence drops. Future-you will thank past-you for not throwing things away too aggressively.
Who it is for
If your Documents folder, Notion sidebar, and Drive look like archeology projects, PARA gives you four buckets that absorb everything. The "where does this go" decision shrinks from twenty folder choices to one of four. The relief is real and immediate. The first month is mostly triage: you walk through existing folders, decide which Project or Area each item belongs to, and archive the rest. The second month, PARA starts paying you back: a new email attachment lands in Projects automatically, a saved article goes into the relevant Resource folder, and you can find things in seconds instead of minutes.
A semester is a folder of Projects (each assignment with a due date) plus an Area (your overall degree progress) plus Resources (saved papers, lecture notes from past terms, the textbook PDFs you might reread). PARA separates the active work from the background material without losing either. When the semester ends, the completed assignments archive automatically; the persistent Area stays alive across terms. The same set of saved papers can power a final project this semester, a senior thesis next year, and a graduate school application after that.
Side projects are Projects. The skills you keep sharp are Areas. The inspiration folder is a Resource. The startup you wound down last year is an Archive. PARA gives a place to every kind of save without forcing you to commit to a topic taxonomy. The creator workflow benefits particularly: a screenshot saved in 2023 because "this layout is interesting" sits as a Resource until you start a new design Project, at which point it surfaces naturally because the Resource is right there in the same system.
PARA replaces topic-based folders ("Marketing", "Engineering", "Personal") with intent-based buckets. The reason this works: you almost never need to find something by topic. You need to find it by what you were trying to do with it. The PDF on B2B marketing is not useful as "marketing reference"; it is useful when you are running a B2B marketing Project. PARA is the structure that matches how memory actually works, which is by action context rather than by subject classification.
The four buckets, in detail
A document about marketing for a project shipping next week belongs in Projects, not in a Marketing folder. The same document a year later, after the project is done, becomes part of Archives. The location follows the actionability, not the subject. This is the core insight, and it is the part most people get wrong on their first try. Traditional folder structures freeze items into topic categories; PARA keeps items moving as their relevance to your active work changes. The folder you saved a doc into three years ago is almost certainly the wrong folder for it today.
A Resource becomes a Project the moment you decide to act on it. A Project becomes an Archive the moment it ships. Areas drift between active and dormant phases. PARA is a flow model, not a filing system. Most note apps treat folders as permanent; PARA treats them as temporary stages. Practically, this means you will be moving items between buckets weekly, not annually. The friction of moving is the price of having an organization system that stays accurate, and PARA is designed so that moves are cheap (drag, drop, done).
PARA works identically in your notes app, your file system, your cloud drive, and your email folders. Tiago Forte explicitly designed it as a cross-tool taxonomy. The benefit: when you switch tools, the structure transfers without re-thinking. The cost: you need to apply it consistently, even in tools where the temptation to make a topic folder is strong (Drive especially). The payoff for consistency is enormous: anything you saved in any tool, you can find by Project name even if you forgot which tool you saved it in.
PARA is flat at the top level (four buckets), with topic-specific sub-folders inside each. You do not stack folders five levels deep. The shallow structure forces you to keep saves visible rather than burying them in nested taxonomies you will never browse. The discipline is uncomfortable at first because deeply-nested filing feels like "real organization", but PARA's flat structure is what makes it sustainable. You never have to remember a path; you only have to remember which of the four buckets an item is in.
Common mistakes
The most common failure: writing a Project called "Stay healthy" or "Manage my team". Those are Areas. The signal is that the title has no completable outcome. The fix: rewrite as "Run a half-marathon in October" (Project) inside the "My health" Area. The Area persists, the Projects come and go.
PARA newcomers often turn every saved item into a Project because Projects feel "important". The Projects folder bloats to fifty items, none of which are really projects. The fix: most items belong in Resources. Save the interesting article as a Resource. It graduates to a Project only when you decide to do something with it.
Active buckets fill up because users feel guilty archiving an "almost finished" Project. Six months later the Projects list has thirty entries, half of which are dead. The fix: archive aggressively. The item is not deleted, just hidden. Archives stay searchable. If you reach for it, the universal search returns it; if you do not, the active list stays clean.
Inside Resources, the temptation is to create subfolders like "Marketing", "Design", "Engineering". After three months you have rebuilt your old topic-based folder structure inside the Resource bucket and lost the whole point. The fix: tag items by topic, do not folder them. Use search and tags to slice across Resources by topic when you need to.
How Mindly fits
Mindly does not force you into PARA, but it implements the same insight underneath. Spaces in Mindly behave like PARA's top-level buckets: create one for each active Project, one for each Area of responsibility, and let everything else flow into the default Resources space. AI tagging makes the cross-bucket connections that pure folder systems lose, so a Resource that becomes relevant to your active Project surfaces in the right place without manual filing. The Archive bucket maps to Mindly's default behavior of keeping completed items searchable without crowding the active library; when you mark a Project done, the items inside become Archive-quality without disappearing. The mind map view lets you see how items connect across buckets, which is the part of PARA that a folder structure cannot show you on its own. A Project that draws on six Resources across three Areas becomes a visible cluster in the map, so you can see the dependencies your work actually has. If you have read Building a Second Brain and want a tool that respects the method without being a copy of it, Mindly is built to be that tool. If you have not read the book, the four buckets are easy enough to absorb from this page and the rest of the workflow takes care of itself once Spaces and AI tagging are doing the underlying organization for you.
Common questions
Tiago Forte, a productivity teacher and author. He developed PARA over a decade of teaching personal knowledge management and formalized it in his 2022 book "Building a Second Brain". The method has been adopted across thousands of knowledge workers, students, and creators.
Projects are short-term efforts with a defined goal and deadline. Areas are ongoing responsibilities without an endpoint. Resources are reference material on topics of interest. Archives hold anything from the other three buckets that is no longer active. The order is intentional: top-of-list buckets get more attention; bottom-of-list buckets stay searchable but quiet.
Regular folders are organized by topic ("Marketing", "Engineering", "Personal"). PARA is organized by actionability. A marketing document for an active campaign sits in Projects, the same document a year later sits in Archives. The structure follows your relationship with the item, not its subject.
Yes. PARA is tool-agnostic by design. You can apply it in Notion, Apple Notes, your file system, Google Drive, Obsidian, or any tool that supports folders. Mindly's Spaces feature implements PARA naturally, but the method itself is independent of any product.
PARA is an organization system for files and notes by actionability. Zettelkasten is a thinking system that emphasizes atomic, linked notes for building knowledge over time. They are not mutually exclusive: many users keep their files in PARA buckets and write their thinking in a Zettelkasten-style linked note structure inside.
PARA and CODE are both from Tiago Forte's Building a Second Brain. CODE (Capture, Organize, Distill, Express) is the workflow. PARA is the organization layer inside the Organize step. CODE describes how to process information through your second brain; PARA describes where the processed information lives.
The structure is simple enough to absorb in five minutes. Actually applying it consistently takes a few weeks of practice as you learn which items belong in which bucket and how to move items as they evolve. Tiago Forte recommends starting small with one Project and expanding from there.
Other methods
Get started
Download Mindly, create a Space per Project, and watch the rest of your library fall into Resources automatically. The PARA structure without the spreadsheet.