The PARA Method: A Pragmatic Guide to Organizing What You Know
You have notes in three apps. Meeting summaries in a Google Doc that nobody remembers sharing. Slack messages you sent to yourself at 11 pm because you were afraid you would forget something by morning. A PDF somewhere on your desktop, maybe in Downloads, maybe in a folder called "Misc" that you created six months ago and never looked at again.
The problem is not that you are disorganized. The problem is that you never had a system that tells you where things belong. So every new piece of information becomes a small decision: Where do I put this? And every retrieval becomes a small search party: Where did I put that?
PARA is a system that answers both questions with the same logic. Four categories. One organizing principle. No specific tool required. It was developed by Tiago Forte as part of his Building a Second Brain methodology, and it has become one of the most widely adopted approaches to organizing digital information. I started using PARA about a year ago, after reading Forte's book (which I cover in my PKM book recommendations). This article is a deep dive into one of the four methods covered in What Is a Second Brain?, where you can see how it compares to Zettelkasten, Johnny.Decimal, and Linking Your Thinking.
What follows is how PARA actually works, where the system is strong, where it runs into real problems, and what a year of using it has taught me about adapting it to fit.
-
PARA stands for Projects, Areas, Resources, and Archives. These are the four categories into which all your digital information can be sorted. The system was created by Tiago Forte and first published as a blog post in 2017, later expanded into a standalone book in 2023. The organizing principle behind all four categories is actionability: how actively are you using this information right now?
The Four Categories: Projects, Areas, Resources, Archives
PARA sorts everything you store digitally into four categories, ordered by how actionable they are.
Projects are short-term efforts with a clear goal and a deadline. They have a beginning and an end. "Launch the Q2 campaign" is a project. "Prepare the board presentation by March 15" is a project. When it is done, it is done.
Areas are ongoing responsibilities that you maintain over time. They do not have an end date. "Marketing" is an area. "Health" is an area. "Direct reports" is an area. You do not finish an area; you keep it at a certain standard.
Resources are topics or interests that might be useful at some point but are not tied to any current commitment. You read an article about negotiation tactics and save it. You collect notes on a programming language you want to learn eventually. These go into Resources.
Archives hold everything from the other three categories that is no longer active. A completed project, a role you no longer hold, a topic that stopped being relevant. Nothing gets deleted. It just moves out of your active view.
The logic that ties all four together is a single question: How actionable is this right now? Projects sit at the top because they need your attention today. Archives sit at the bottom because they do not. Everything in between falls along the same spectrum.
This is what makes PARA different from organizing by topic or subject. A traditional folder system might have you put everything about "Marketing" into one folder. Six months later, that folder contains active campaign briefs mixed with outdated brand guidelines, a presentation from a project that ended last year, and three versions of a template nobody uses. PARA separates these by what you are actually doing with them, not what they are about.
-
A project has a deadline and a specific outcome. An area is an ongoing responsibility without an end date. "Hire a senior developer" is a project. "Team management" is the area it belongs to. The distinction matters because projects create momentum (you can finish them and move on), while areas require sustained attention. In practice, the boundary between the two can blur, especially in digital environments where moving files between categories can break shared links.
How PARA Looks on a Normal Workday
It is 11 am. You have already been in two meetings. Your inbox has 14 new messages. Here is what landed on your plate this morning:
Meeting notes from a sprint review, with three action items and a design decision that needs documentation
A Slack thread where someone shared a competitor analysis
An email from your manager with feedback on the Q2 roadmap draft
A research paper on user onboarding patterns that a colleague recommended
A link to a conference talk you want to watch later
Without a system, you know exactly what happens. The meeting notes go into whatever app was open at the time. The Slack thread gets bookmarked or forgotten. The email sits in your inbox. The research paper lands in Downloads. The conference link becomes one of 47 open tabs.
With PARA, you run each item through one question: Is this for an active project, an ongoing area of responsibility, a topic I might need later, or nothing I need right now?
Here is where each item goes and why:
| What came in | Where it goes | Why |
|---|---|---|
| Sprint review notes | Projects → "Q2 Product Launch" | Active project with a deadline |
| Roadmap feedback email | Projects → "Q2 Product Launch" | Same project, same folder |
| Competitor analysis | Areas → "Product Strategy" | Ongoing responsibility, not tied to one project |
| Research paper on onboarding | Resources → "User Research" | Interesting, no immediate use |
| Conference talk link | Resources → "Learning Queue" | Same: useful later, not actionable now |
The whole process takes about two minutes. No deliberation about folder names, no tagging, no "I will organize this later."
The real payoff comes three months down the road, when Q2 is done and the entire project folder has moved to Archives. A new colleague asks about the decisions that shaped the Q2 launch. Instead of digging through old Slack threads and email chains, you open the archive, find the project folder, and have everything in front of you within seconds.
Where does this information belong?
The Cognitive Logic Behind Four Categories
If you have read the guide to building a second brain, you already know two of the key findings: working memory holds roughly four items at a time (Cowan, 2001), and poorly organized information drains cognitive resources that would be better spent on actual thinking (Sweller's Cognitive Load Theory, 1988). PARA builds on both, but there is a third piece of research that explains why four categories specifically works so well.
Fewer options, faster decisions
In 1952, psychologist William Edmund Hick published a finding that has since become one of the most replicated results in experimental psychology. Hick's Law states that the time it takes to make a decision increases logarithmically with the number of options. Double the options and you do not double the decision time, but you do measurably increase it. The more choices, the slower you move.
Applied to file organization: a system with twelve topic-based folders, three levels of subfolders, and a tagging scheme forces a decision every time you save something. Where does this go? Is it "Marketing" or "Q2 Campaign" or "Strategy Documents"? Each option adds a small delay. That delay is what Sweller would call extraneous cognitive load: mental effort that produces no useful work.
PARA cuts the option set to four. That is not a round number someone picked for simplicity. It is genuinely close to the minimum viable set of categories that can capture all types of information without collapsing into a single pile. Four options means the decision "where does this go?" takes seconds, not minutes. Over the course of a day filled with meetings, messages, and context switches, those saved seconds add up to something real.
Organized by urgency, not by topic
Forte uses a kitchen analogy that gets at PARA's second cognitive advantage. You do not organize your kitchen by the material things are made of (putting wooden spoons next to the cutting board next to the salad bowl). You organize by how often you use things. Daily items go on the counter. Weekly items go in the cabinet. Seasonal items go in the back of the pantry.
PARA applies the same logic to information. Projects sit at the front because you need them today. Archives sit in the back because you do not. This means the things you reach for most often are always the most accessible, and the things you rarely need are out of your way but never gone.
The combination of these two mechanisms, fewer options for filing and proximity-based access, is what makes PARA feel effortless once you start using it. You are not fighting your brain's limitations. You are designing around them.
-
No. PARA is a knowledge organization system. It helps you sort and find your notes, files, and reference material. It does not tell you what to do next, how to prioritize, or how to manage your time. For that, you need a productivity method like GTD or one of the other productivity methods covered on this site. PARA and productivity systems are complementary: one manages your knowledge, the other manages your action.
Setting Up PARA: A Realistic Starting Point
Most PARA guides make setup sound like a weekend transformation. It does not have to be. Here is a stripped-down version that works.
Start with a clean slate. Take everything currently in your note-taking app, file system, or wherever you store things, and move it into a single folder called "Archive." You are not deleting anything. You are clearing the workspace so you can start with an uncluttered view. If that feels too radical, create the four new folders alongside your existing structure and let the old stuff sit until you need it.
List your active projects. Open a blank note and write down everything you are actively working on that has a clear end point. Aim for 5 to 15 items. If you have more than 15, some of them are probably areas disguised as projects. For each project, create a folder or notebook.
Identify your areas of responsibility. These are the parts of your work and life that require ongoing attention: your role at work, your health, your finances, your home. Create folders for the ones where you actually have or expect to have notes and files. Do not create empty folders for areas you think you should be tracking.
Let Resources emerge naturally. Do not pre-build a library of topic folders. When you come across something worth saving that does not belong to a project or area, create a Resource folder for it then. This is what Forte calls "just-in-time organization," and it is one of the best parts of the system. An empty folder structure is just optimism with labels.
Keep the same logic across your tools, but not necessarily the same content. This is worth pausing on. Forte recommends using the PARA structure everywhere: your notes app, your file system, your cloud storage. The logic should be consistent. But you do not need the same files in every tool. More on this in my personal experience section below.
-
Any tool works with PARA, because the system is tool-agnostic. It does not require any specific app or feature. You can use it with Notion, Obsidian, Apple Notes, Google Drive, your computer's file system, or even physical folders. This is one of PARA's genuine strengths, especially if you work in an organization where your tools are dictated by IT policy. Whether you are stuck with Microsoft OneNote or you use Google Workspace, PARA works the same way.
Where PARA Works and Where It Doesn't
After reading through dozens of PARA guides and using the system for a year, here is the honest picture.
What PARA does well
Low maintenance by design. Unlike systems that require daily reviews, tagging schemes, or complex folder hierarchies, PARA runs on a single decision: is this a Project, Area, Resource, or Archive? That low overhead is why people actually stick with it.
It forces you to think in projects. One of Forte's best observations is that most people confuse areas with projects. They put "Marketing" on their to-do list instead of "Write the Q3 campaign brief." Separating projects from areas forces you to define what done looks like, and that alone can change how you approach your work.
It works across tools without requiring a single perfect app. This matters more than most guides acknowledge. If you are a freelancer, you can pick your stack. If you work in a 5,000-person organization, you cannot. PARA does not care whether you use Notion or OneNote or a combination of both. The structure is the same.
It cleans up beautifully. The Archive mechanism means completed projects do not clutter your active workspace. You always see only what is current, and everything else is one folder away if you need it.
Where PARA runs into friction
The Projects-Areas boundary is blurrier than it looks. On paper, the distinction is clean: projects have deadlines, areas do not. In practice, things shift. A project becomes an ongoing responsibility. An area spawns a time-limited initiative. Forte recommends regular reviews to move items between categories. But in a digital environment, moving folders changes file paths, breaks shared links, and creates exactly the kind of friction that the system was supposed to eliminate.
It organizes by location, not by connection. PARA tells you where to put things, but it does not help you connect ideas across categories. If you are working on a product launch (Project) and you come across a research insight in your Resources that is relevant, PARA does not have a built-in way to surface that connection. Systems like the Zettelkasten method are designed specifically for this kind of networked thinking. PARA is not.
There is no built-in mechanism for refining what you store. You can file a 20-page report and a two-sentence insight in the same project folder, and PARA treats them equally. It does not encourage you to extract the parts that matter or condense information over time. If you want that, you need to layer another practice on top.
For creative or research-heavy work, it can feel too rigid. If your work involves exploring ideas that do not yet belong to any project, or connecting themes across domains, the four categories can feel like forcing round pegs into square holes.
Three mistakes that trip people up early
Building the library before reading the books. The instinct is to create folders for every area and topic you can think of before you start. Do not. Empty folders create the illusion of organization while adding noise to your workspace. Only create a folder when you have something to put in it. Forte calls this "just-in-time organization," and it is one of the best ideas in the whole system.
Trying to mirror everything across tools. Some guides suggest replicating your exact PARA structure identically in every app. In practice, that creates more maintenance than it saves. Your notes app and your file system hold different types of content. What matters is that the same logic applies everywhere, not that every folder exists in every tool. You should always be able to answer "where would I find this?" without hesitation. That is enough.
Enforcing the Projects-Areas boundary too strictly. On paper, the split is clean: projects end, areas do not. In a digital workspace, moving items between the two categories can break links, confuse collaborators, and create busywork. If you find yourself constantly shuffling things between Projects and Areas, consider merging them. I did, and I explain why in the section below.
PARA vs. Zettelkasten vs. Johnny.Decimal: Choosing the Right System
The right system depends on the problem you are actually trying to solve. If your main challenge is finding files and staying on top of projects, that is a different problem than connecting ideas across domains or making a shared drive navigable for a team of 20. Each of these three methods was built for a different version of that problem.
Here is how they compare:
| PARA | Zettelkasten | Johnny.Decimal | |
|---|---|---|---|
| Core Principle | Organize by actionability | Connect ideas through atomic, linked notes | Assign every item a unique number within categories |
| Best For | Managing projects, files, and responsibilities | Writing, research, and building on ideas over time | Team file management with clear, shared structure |
| Setup Time | 30 minutes | 1–2 hours (plus ongoing learning) | 1–2 hours |
| Maintenance | Low. Organize as you go. | Medium. Each note needs deliberate linking. | Low to medium. Structure is fixed once built. |
| Idea Networking | None built in | Core feature. Notes connect across topics. | None built in |
| Learning Curve | Low | Moderate to steep | Low to moderate |
| Tool Requirements | Any tool (folders, tags, apps) | Needs linking support (Obsidian, Notion, paper) | Any tool with folder/numbering support |
| Scales To | Individual or small team | Individual (personal knowledge base) | Teams and shared drives |
Try PARA if you need a simple, low-maintenance system for organizing files and notes across multiple tools, and your primary goal is to stay on top of active projects and responsibilities. It is the best starting point for most knowledge workers.
Try Zettelkasten if your work involves writing, research, or any kind of thinking that benefits from connecting ideas across topics. The learning curve is steeper, but the payoff for creative and intellectual work is substantial. Read the full guide: The Zettelkasten Method.
Try Johnny.Decimal if you work in an environment with large volumes of files that need to be shared across teams, and you need a numbering system that makes every file findable by anyone. It is less about personal knowledge and more about team-wide file management.
You do not have to choose only one. Many people use PARA as their top-level structure and borrow linking practices from Zettelkasten for their notes. The methods are not mutually exclusive.
-
Yes, and many people do. A common approach is to use PARA as the top-level structure for organizing projects, areas, and files, while using Zettelkasten principles (like atomic notes and bidirectional linking) within your notes. PARA handles the "where does this belong?" question. Zettelkasten handles the "how does this connect to other ideas?" question. They solve different problems.
What a Year with PARA Actually Taught Me
I started using PARA about a year ago, after reading Forte's book. I set it up both at work and for personal use, and I have run it long enough to see what sticks and what needs adapting.
Stop looking for the perfect tool
The first thing I noticed is that you do not need to find a single app before you start. This sounds obvious, but it was a genuine relief. I had spent time before trying to find a tool that could handle everything: notes, files, task management, reference material. That search is a trap, especially if you work in a large organization where IT decides your stack.
My setup is simple. I use Notion for notes and thinking. My desktop file system handles large files and downloads. Both follow the PARA logic, but they hold different content. I am not trying to mirror everything between them. What matters is that I know where to look: if it is a note or an idea, it is in Notion. If it is a file or a download, it is on my desktop. The categories are the same, the contents are different.
Forte makes this point himself. The principle is not identical copies everywhere. It is that you should always know where something lives. As long as you can answer "where would I find this?" without hesitation, the system is working.
This is especially relevant if you are a knowledge worker in a large organization. You probably have no choice about your tools. Your company runs Microsoft 365 or Google Workspace, and that is what you get. PARA works anyway, because the structure does not depend on any specific feature. Four folders in OneDrive work just as well as four folders in Google Drive or four notebooks in OneNote.
Why I merged Projects and Areas
This is my biggest departure from the original system, and it came from a specific problem.
I had a clear project, something with a defined scope, that gradually evolved into an ongoing responsibility. By Forte's definitions, it should have moved from Projects to Areas. But when I tried to move the folder, all the links I had shared with colleagues broke. Every document I had linked in a Slack message or an email now pointed to a location that no longer existed.
That was the moment I realized that the Projects-Areas separation, while clean in theory, creates real friction in digital environments. Physical boxes do not change their address when you relabel them. Digital folders do.
So I stopped separating them. My active work now lives in a single category that I think of as "Active." Whether something has a deadline or is an ongoing responsibility, it lives in the same place as long as I am working on it. When it is done or no longer relevant, it moves to Archive. The functional difference between a project and an area still exists in my head, but I do not need separate folders to enforce it.
Resources and Archives, on the other hand, work exactly as Forte describes them. Resources is where I collect things I might need later. Archives is where completed or inactive work goes to rest. Those two categories have never given me trouble.
What I would tell someone starting out
Start with the four categories as Forte describes them. Give the system a few weeks. Then pay attention to where friction shows up. If the Projects-Areas split works for you, keep it. If it does not, merge them. The point is not to follow the method perfectly. The point is to always know where your stuff is.
If you also want a system for managing your tasks and priorities (which PARA is not built for), take a look at my pragmatic GTD setup. The two complement each other: GTD tells you what to do next, PARA tells you where the material for that work lives.
Getting Started This Weekend
If you want to try PARA, here is a minimal setup that takes about 30 minutes.
Saturday (20 minutes). Create four folders in your primary notes app or file system: Projects, Areas, Resources, Archives. Move everything that currently exists into Archives. Then list your active projects and create a subfolder for each one. If you are not sure what counts as a project, here are some typical knowledge worker examples:
Q2 product launch
Hire a junior designer
Migrate team documentation to new platform
Prepare quarterly business review
Redesign onboarding flow
Aim for 5 to 15 active projects. If you have more than 15, some of them are probably areas in disguise.
Sunday (10 minutes). Identify your ongoing areas of responsibility and create folders for the ones where you already have material. These are responsibilities without a finish line:
Product strategy
Team management
Professional development
Health and fitness
Personal finances
Do not create folders for areas where you have nothing to file yet. They will emerge when you need them.
Monday (ongoing). Work normally. When you create or receive a new piece of information, ask yourself: is this for an active project, an ongoing area, a topic of interest, or nothing I need right now? File accordingly.
If the system feels too rigid after a few weeks, simplify. If it feels too loose, add structure. PARA is a starting point, not a destination.
-
Forte recommends "just-in-time organization," meaning you organize as you go rather than scheduling dedicated review sessions. In practice, a brief monthly check is worth doing: scan your Projects folder for anything that is done (move it to Archive), check if any new areas have emerged, and clear out Resources you no longer care about. This should take about 15 minutes.
-
Yes. Even if all your information lives in a single app like Notion or Obsidian, the PARA structure gives you a clear framework for deciding where to put new information and where to look for old information. The system becomes even more useful when you apply the same logic across multiple tools, but it works perfectly fine with just one.
Sources
Forte, T. (2022). Building a Second Brain: A Proven Method to Organize Your Digital Life and Unlock Your Creative Potential. Atria Books.
Forte, T. (2023). The PARA Method: Simplify, Organize, and Master Your Digital Life. Atria Books.
Forte, T. (2017). "The PARA Method: A Universal System for Organizing Digital Information." Forte Labs Blog.
Miller, G. A. (1956). "The Magical Number Seven, Plus or Minus Two." Psychological Review, 63(2), 81-97.
Cowan, N. (2001). "The Magical Number 4 in Short-Term Memory." Behavioral and Brain Sciences, 24(1), 87-114.
Sweller, J. (1988). "Cognitive Load During Problem Solving." Cognitive Science, 12(2), 257-285.
Hick, W. E. (1952). "On the Rate of Gain of Information." Quarterly Journal of Experimental Psychology, 4(1), 11-26.
