The Problem: Your File Structure Doesn't Reflect How You Work
You've tried organizing by topic ("Marketing," "Finance," "Research"). You've tried organizing by date, by client, by project. Eventually, every system collapses: the folders multiply, nothing is where you expect it, and you find yourself using search instead of navigation.
The underlying problem is that topic-based organization doesn't match how information is actually used. You don't need to find "all your marketing research" — you need to find the marketing research relevant to the campaign you're launching next month.
The PARA method solves this by organizing information by actionability and time horizon — not by what the information is about, but by where it fits in your current priorities and responsibilities.
Where PARA Came From
The PARA method was developed by Tiago Forte and published in a 2017 blog post before being incorporated into his Building a Second Brain book (2022). PARA is the organizational backbone of Forte's broader BASB methodology, but it can be used independently with any note-taking or file system.
Forte's insight came from frustration with topic-based organization systems (including the Dewey Decimal System and other categorical approaches). The core observation: information in a personal knowledge system isn't used categorically — it's used in the context of active work. A note about marketing psychology is useful when you're working on a marketing campaign; it's background noise otherwise.
PARA stands for:
- Projects — active goals with deadlines
- Areas — ongoing responsibilities
- Resources — reference material for future use
- Archive — inactive material
The four categories cover every piece of information a knowledge worker handles, organized by the time horizon and urgency of its relevance.
The PARA Method, Step by Step
Understanding the Four Categories
Projects:
A project is a series of tasks linked to a goal, with a clear completion criteria and a deadline (even if informal). Projects are your active focus areas.
Examples:
- "Write Q4 Marketing Strategy"
- "Onboard new team member (Sarah)"
- "Research and propose new CRM system"
- "Complete MBA application"
A project has a finish line. When it's done, it moves to Archive.
Areas:
An area is a sphere of ongoing responsibility with no explicit completion date. You maintain areas continuously; you don't "complete" them.
Examples:
- "Health" (ongoing; you don't finish maintaining your health)
- "Team Management" (ongoing responsibility)
- "Finance" (ongoing)
- "Professional Development" (ongoing)
Areas often generate projects (a health area might spawn a project to "Research and select a new gym"), but the area itself persists.
Resources:
Topics or interests that might be useful in the future but aren't tied to a current project or area.
Examples:
- "Machine Learning" (you're interested but not currently working on it)
- "Competitive Analysis — CRM Market" (might be useful; not an active project)
- "Design Systems" (reference material, not an active project)
Resources are organized for potential future use.
Archive:
Completed projects, inactive areas, resources that are no longer relevant. Everything you might want to reference but don't actively use.
The Archive is searchable, not browsable — you don't regularly navigate it, but you can search it when you need to reference something from a past project.
Setting Up PARA: Step by Step
Step 1 — Create four top-level folders (or sections)
In your note-taking app, file system, or cloud storage, create exactly four folders: Projects, Areas, Resources, Archive. These are your only top-level categories.
Step 2 — List your active projects
Write down every active project you're working on: at work, personally, in any domain. A project must have a goal and an implicit deadline. If you can't articulate a finish line, it's probably an area or a resource, not a project.
Create a sub-folder (or note) for each project inside the Projects folder.
Step 3 — List your ongoing areas of responsibility
What ongoing responsibilities do you have? At work: your role's responsibilities (team management, budget ownership, product strategy). Personally: health, finances, relationships, home.
Create a sub-folder for each area.
Step 4 — Move existing notes/files into the structure
Go through your existing files, notes, and bookmarks. For each item, ask: Is this relevant to an active project? → Projects. Is this an ongoing reference for an area? → Areas. Could this be useful in the future but isn't tied to current work? → Resources. Is this inactive but worth keeping? → Archive. Is this trash? → Delete.
Don't aim for perfection in this step — get roughly right.
Step 5 — Use project folders as your active workspace
When you start new work, navigate to the relevant project folder. When you save something relevant to an active project, put it in the project folder. The project folder should contain everything you need for that project.
Step 6 — Archive completed projects
When a project is done (launched, submitted, completed), move the entire project folder to Archive. Don't spend time cleaning it up first — just move it. Archive is searchable; you'll find what you need if you ever need it.
A Worked Example
A consultant, David, adopts PARA to manage his knowledge system:
Active projects at any time:
- "Consulting Proposal — Acme Corp" (due next week)
- "Update Client Onboarding Process" (due end of quarter)
- "Read Good to Great and apply insights" (personal)
Ongoing areas:
- "Client Management" (ongoing — client relationships and communications)
- "Business Development" (ongoing — lead generation, networking)
- "Finance" (ongoing — invoicing, expenses, taxes)
Resources:
- "Consulting Frameworks" (collected frameworks for future use)
- "Industry Research — Retail Tech" (possible future projects)
- "Writing" (techniques and references for future writing projects)
When David reads a good article about pricing strategy:
- Is it relevant to an active project? Yes — the Acme Corp proposal includes a pricing recommendation. → It goes in "Projects > Consulting Proposal — Acme Corp."
When David finishes the Acme Corp proposal:
- The whole project folder moves to Archive. David doesn't have to decide what to keep — everything goes to Archive, searchable if needed.
A year later, David starts a new proposal for a retail client:
- He searches Archive for "pricing" and finds his old notes from the Acme proposal. He reuses the research without starting from scratch.
PARA turns the Archive into a searchable library of past work — not a graveyard of old folders.
Where PARA Shines
For professionals with multiple simultaneous projects: PARA is designed for people who routinely have 5-15 active projects across different domains. The project-centric organization makes information immediately findable in context.
For cross-tool use: PARA's four-category structure can be applied consistently across your file system, note-taking app, email folders, and bookmark manager. Consistency across tools reduces cognitive load.
For managing knowledge accumulation over time: The archive function ensures old material doesn't clog your active workspace while remaining searchable. This is a structural solution to the "old stuff everywhere" problem.
Where PARA Breaks Down
For people with few active projects: If you have one or two ongoing projects, the PARA overhead (maintaining four categories, regularly moving items between them) may not provide enough benefit to justify the setup cost.
The maintenance requirement: PARA requires regular review to remain useful. Projects that aren't archived when complete become noise in the Projects folder. Areas that aren't reviewed drift toward irrelevance. Without regular maintenance (weekly or monthly), the system degrades.
Ambiguous categorization: Some information genuinely belongs in multiple categories. A document relevant to an active project might also be good Resources material. PARA's answer is "put it where you'll use it first" (the project) — but this can feel arbitrary and creates inconsistency.
Not ideal for academic research: PARA doesn't address citation management, systematic literature review, or note interconnection — needs better served by Zettelkasten or dedicated reference managers.
Tools That Support PARA
| Tool | How to implement PARA | Notes |
|---|
| Notion | Four top-level pages as databases | Flexible; allows database views filtered by project |
| Obsidian | Four top-level folders | Works well; search is fast |
| Apple Notes | Four smart folders | Limited; no nested structure |
| Google Drive | Four top-level folders | Good for file-based (not note-based) content |
| Evernote | Four top-level notebooks | Classic PARA implementation; good search |
| WebSnips | Collections organized by project | Clips from the web organized into PARA-aligned collections |
The tool matters less than the discipline of maintaining the four-category structure. Start with whatever tool you already use.
Common PARA Mistakes
Mistake 1: Too many projects.
PARA works with 5-15 active projects. With 30 "active" projects, nothing is truly prioritized. If something has been in Projects without progress for a month, move it to Archive or deliberately deprioritize it.
Mistake 2: Sub-categories within Resources.
Resources is supposed to be flat (or lightly structured). Adding 12 sub-categories to Resources recreates the topic-based organizational chaos that PARA is designed to replace.
Mistake 3: Skipping the Archive step.
Completed projects that aren't archived clutter the Projects folder, making it harder to see what's actually active. Archive immediately when complete — even if the project ended messy.
Mistake 4: Using PARA as a reading system rather than a production system.
PARA's value comes from organizing information for active use, not for passive accumulation. If you're capturing and organizing but never expressing (producing work from your second brain), you're not getting the system's core benefit.
Frequently Asked Questions
How many sub-folders should each PARA category have?
Projects: as many as active projects (typically 5-15). Areas: as many as significant ongoing responsibilities (typically 5-10). Resources: limited; avoid over-categorizing. Archive: grows over time; organized by project/area, not by topic.
What about information that fits multiple categories?
Put it where you'll need it first. If you'll need it for an active project, put it in the project folder. If it's genuinely multi-category, choose one and move it if you need to reference it elsewhere. The goal is fast retrieval, not perfect categorization.
Can PARA work with a physical paper system?
Yes, with adaptations — four folders or sections in a binder, with active project folders and archive folders. The digital advantage is searchability; a physical PARA system sacrifices search but gains tangibility.
Key Takeaways
- PARA method organizes everything by actionability: Projects (active + deadline), Areas (ongoing responsibilities), Resources (future reference), Archive (inactive but searchable).
- Created by Tiago Forte (published 2017) as the organizational backbone of the Building a Second Brain methodology.
- The key principle: organize by what you're working on, not by topic — information is always findable in the context where you need it.
- Archive immediately: when a project is complete, move the whole folder to Archive without cleaning it first; search will find what you need later.
- Maintenance required: regular review (weekly or monthly) keeps Projects current and Areas relevant; an unmaintained PARA system degrades.
- Works across tools: apply the four-category structure consistently in your file system, notes, email, and bookmarks to reduce cognitive overhead.
Conclusion
PARA is elegant in its simplicity and powerful in its discipline. The four categories cover all information a knowledge worker handles, and the project-centric organization ensures that information is always findable when you need it — in the context of active work, not in a topic-based filing cabinet you have to navigate by memory. The maintenance overhead is real, but the return — a system where you can reliably find relevant material for any active project — is one of the most direct productivity improvements available to knowledge workers.
Try WebSnips free — organize your web research into PARA-aligned collections, with each collection mapping to a project or area, so your captured passages are always findable in the context where you need them.