The PARA method is an organizational framework created by Tiago Forte as part of his Building a Second Brain methodology. It classifies all information into exactly four top-level categories based on actionability, not topic: Projects, Areas, Resources, and Archive.
The Four Categories
Projects are short-term efforts with a clear goal and deadline. Examples: "Launch website redesign," "Write Q2 report," "Plan vacation." A project has a finish line; when it is done, it moves to Archive.
Areas are ongoing responsibilities with standards to maintain but no end date. Examples: health, finances, professional development, home maintenance, parenting. Areas persist indefinitely and require continuous attention.
Resources are topics of ongoing interest or reference material. Examples: PKM methodology, cooking recipes, design inspiration, programming languages. Resources have no accountability attached; they are useful but not obligatory.
Archive is the catch-all for inactive items from the other three categories. Completed projects, deprecated areas, and outdated resources all land here. The archive is not a graveyard; it is searchable and items can be reactivated.
Organizing by Actionability
PARA's core insight is that organizing by topic creates systems that look tidy but fail under real usage. Organizing by actionability means the most urgent and relevant material is always at the top of the hierarchy: projects first, then areas, then resources. This mirrors how knowledge workers actually think about their work.
Fluid Movement Between Categories
Items are not permanently assigned. A "Resources" topic like "machine learning" becomes a "Project" when you enroll in a course. A completed project's reference material moves to "Archive" or gets extracted into "Resources." This fluidity is a feature, not a bug; it keeps the system reflecting current reality.
PARA and Folder Structure vs Tags
PARA was originally conceived as a folder-based system, and Forte recommends mirroring the same PARA structure across every tool (file system, note app, task manager, cloud storage). In tools like Obsidian that support tags and links, PARA can also be implemented as metadata rather than literal folders. The Obsidian Starter Kit, for instance, draws inspiration from PARA's zone concept while adapting it into a more granular folder and tag hierarchy.
PARA Across Tools
PARA's simplicity makes it tool-agnostic. Implementations exist in Notion (databases with a PARA property), Obsidian (folder structure or Dataview queries), Apple Notes (folders), Google Drive (folder hierarchy), and even physical filing systems. The key constraint is maintaining the same four categories everywhere to reduce cognitive overhead when switching contexts.
Common Mistakes
- Too many Areas. If your Areas list exceeds 10-12, some are probably Resources in disguise. Areas carry accountability; if you are not maintaining a standard, it is a Resource.
- Not archiving enough. The psychological cost of stale projects cluttering your active workspace is underestimated. Aggressive archiving keeps the system honest.
- Confusing Projects with Areas. "Health" is an area. "Run a 5K by June" is a project. Failing to distinguish these leads to vague, unfinishable items.
PARA vs Johnny Decimal
Johnny Decimal imposes a strict numerical classification (categories 10-19, 20-29, etc.) that caps at 100 items per level. PARA is simpler (four buckets) but less precise. Johnny Decimal works better for people who want rigid, predictable structure; PARA works better for people who want minimal overhead. Some practitioners combine both: PARA at the top level with Johnny Decimal numbering within each category.
When PARA Breaks Down
At scale, PARA's simplicity becomes a liability. With hundreds of projects and dozens of areas, the four-bucket model does not provide enough granularity for retrieval. People managing multiple life domains (personal, freelance, day job, side business) may find themselves wanting sub-areas or cross-cutting tags that PARA does not naturally accommodate. At that point, practitioners typically augment PARA with Maps of Content, tags, or a more sophisticated zone system.
Key Points
- PARA organizes by actionability (project urgency), not by topic
- Items move fluidly between categories as their status changes
- The system is tool-agnostic and designed to be mirrored across all tools
- Common failures include too many areas, insufficient archiving, and project/area confusion
- PARA works best at moderate scale; large systems often need supplementary structures
Open Questions
- How well does PARA adapt to team environments where multiple people share the same project and area definitions?
- Does AI-assisted organization reduce the need for rigid top-level categories like PARA's four buckets?
- Can PARA coexist with graph-based knowledge systems, or does its folder-centric origin create friction?
References
- Tiago Forte, Building a Second Brain (2022)
- Forte Labs, "The PARA Method: A Universal System for Organizing Digital Information"
- Vault notes: PARA method, Obsidian Starter Kit - Theory