PARA method
PARA method is an organizational system developed by Tiago Forte that categorizes all information into four containers: Projects, Areas, Resources, and Archives. The system provides a universal structure applicable across any digital platform, enabling consistent organization of notes, files, and tasks while supporting natural information flow as context changes over time.
The method's power lies not in the categories themselves but in how information moves between them. Static organization creates stale systems; PARA embraces the reality that a piece of information's relevance shifts as circumstances evolve.
The four categories
Projects represent discrete, time-bounded efforts with defined outcomes. Each project has a deadline and a concrete deliverable — launch a website, complete a report, plan an event. The key distinguishing feature is temporality: projects end. When a project completes, it moves to Archives, and any reusable material gets distributed to other categories.
Areas represent ongoing responsibilities with standards to maintain rather than deliverables to complete. Health, finances, professional development, home maintenance — these persist indefinitely. Areas don't have completion dates; they have maintenance requirements. The difference between a project and an area is the difference between "plan the family vacation" (project with an end date) and "manage family activities" (ongoing responsibility).
Resources contain generally useful information organized by topic. Unlike Areas, which contain personally relevant material tied to specific responsibilities, Resources hold information valuable for reference or sharing with others: industry research, recipes, design inspiration, technical documentation — material useful beyond immediate personal application.
Archives contain inactive items from all other categories. Completed projects, dormant interests, ended responsibilities — anything no longer active but potentially useful for future reference moves to Archives. This category prevents clutter while preserving institutional memory.
Information flow patterns
The real operational logic of PARA emerges in how information flows between categories as context shifts.
Resources often seed new Projects. An interest in blockchain technology, tracked casually for years through collected research and news, might suddenly become a project to create an educational course. The accumulated resource material provides a foundation rather than starting from scratch.
Resources can also elevate to Areas when casual interest becomes ongoing responsibility. A recipe collection (resource) might support a new commitment to cooking healthier meals for family (area).
Areas frequently spawn Projects. Travel planning (area) generates specific trips (projects). Professional development (area) creates specific learning initiatives (projects). The ongoing responsibility identifies opportunities; discrete projects execute on them.
Projects naturally distribute their outputs when complete. Before archiving a finished project, a quick scan identifies material useful elsewhere. Intermediate work — brainstorms, research, diagrams — might enrich Resources. Decisions or processes might inform Areas. Only a small percentage of project material deserves redistribution, but that material creates immense future value.
Archives aren't dead storage but dormant potential. Past project materials resurface when new projects touch similar domains. Background research from a consulting engagement might inform a future project in that industry. The archive preserves accumulated intellectual capital for future leverage.
Just-in-time organization
A crucial operational principle: organizational work should happen opportunistically rather than on strict schedules. Dedicated reorganization sessions rarely survive busy periods — there's no line item in budgets for "getting organized."
Instead, PARA encourages making small adjustments when already working with notes. While searching for project material, move a note that belongs elsewhere. During routine review, notice and adjust misclassified items. This approach distributes organizational overhead across natural workflow moments rather than concentrating it in sessions that get perpetually postponed.
The goal is preventing organizational breakdown through continuous small maintenance rather than periodic heroic efforts. Systems degrade gradually then fail suddenly; just-in-time adjustment prevents the gradual degradation.
Related pages
- progressive-summarization — Note-taking technique that works within PARA structure
- compound-engineering — Philosophy of building reusable knowledge systems