PARA Method

PARA is an organizational system from Tiago Forte's Building a Second Brain that sorts all digital information into four categories ranked by actionability:

Projects are short-term efforts with a specific goal and deadline. A blog post you're writing, a feature you're shipping, a trip you're planning. They end.

Areas are ongoing responsibilities with no end date. Your health, your team, your finances, a codebase you maintain. They require standards, not completion.

Resources are topics you're interested in but aren't actively working on. Programming languages you want to learn, recipes you collect, research areas you follow. They might feed a future project.

Archive is cold storage for anything that drops out of the other three. Completed projects, areas you no longer manage, resources that lost their relevance. Nothing gets deleted — it just moves here.

The sorting heuristic is simple: for any new item, ask "which project does this support?" first. If none, try areas, then resources. If it doesn't fit any active bucket, archive it. Forte recommends not overthinking placement — search handles retrieval even if something ends up in the wrong spot.

The key design choice is organizing by what you're doing rather than what something is about. A note about database indexing goes in your "Optimize Search API" project folder, not in a "Databases" topic folder. When the project ends, the whole folder moves to Archive. This keeps your active workspace clean and focused.

PARA works across any tool — file systems, note apps, email folders, bookmarks. The same four categories apply everywhere, which means you only learn one system.

The trade-off: PARA is project-centric, so it's weaker for building a long-lived knowledge graph where connections between ideas matter more than current projects. Topic-based or link-based systems (Zettelkasten, wikis) handle that better. Huashu's obsidian-ai-complete-guide presents PARA as "Template B" for vault architecture — good for managing multiple parallel projects, but notes he independently evolved into nearly the same structure before learning the name.

PARA can be extended pragmatically. Rumproarious's file-system-as-graph-database setup keeps the four PARA buckets but adds /people/{slack_handle} for per-person notes and /daily/{year}/{month}/{day}/ + /meetings/{year}/{month}/{day}/ for temporal logs. Vanilla PARA has no natural home for either category; the extensions give both a predictable path without breaking the actionability sort.