5.9 KiB
PARA Method Reference
Source: Tiago Forte - fortelabs.com/blog/para
Table of Contents
- The Core Principle
- The Four Categories
- The Key Distinction: Projects vs. Areas
- Why Breaking Areas into Projects Matters
- Why PARA Works
- Common Mistakes
- The PARA Workflow
- Integration with GTD
The Core Principle
"Instead of organizing information according to broad subjects like in school, organize it according to the projects and goals you are committed to right now. This is what it means to organize by actionability." — Tiago Forte
The ideal organizational system leads directly to tangible benefits. It should:
- Be incredibly easy to set up and maintain
- Be flexible across different seasons of life
- Be comprehensive across all platforms
- Pull actions closer and make them easier to start
PARA is actionable - it organizes by "when will I use this?" not "what is this about?"
The PARA Definition
PARA stands for Projects, Areas, Resources, and Archives - four top-level categories that encompass every type of information you might encounter in your work and life.
The Four Categories
Projects
Definition: A series of tasks linked to a goal, with a deadline.
Examples:
- Complete app mockup
- Develop project plan
- Execute business development campaign
- Write blog post
- Finalize product specifications
- Attend conference
Key Characteristics:
- Has a clear end state
- Has a deadline (explicit or implicit)
- Requires multiple tasks to complete
- Can be "finished"
Areas
Definition: A sphere of activity with a standard to be maintained over time.
Examples:
- Health
- Finances
- Professional development
- Travel
- Hobbies
- Friends
- Apartment
- Car
- Productivity
- Direct reports
- Product development
- Writing
Key Characteristics:
- Ongoing responsibility
- No end date
- Requires consistent attention
- Has standards to maintain
Resources
Definition: A topic or theme of ongoing interest.
Examples:
- Habit formation
- Project management
- Transhumanism
- Coffee
- Music
- Gardening
- Online marketing
- SEO
- Interior design
- Architecture
- Note-taking
Key Characteristics:
- Topics you're interested in
- Reference material
- May or may not be actionable
- Collected over time
Archives
Definition: Inactive items from the other three categories.
Examples:
- Completed projects
- Areas no longer active
- Resources no longer relevant
Key Characteristics:
- Not currently needed
- Preserved for potential future use
- Keeps other categories clean
The Key Distinction: Projects vs. Areas
This is where most people struggle:
| Projects | Areas |
|---|---|
| "Run a marathon" | "Health" |
| "Publish book" | "Writing" |
| "Save 3 months expenses" | "Finances" |
| "Plan vacation" | "Travel" |
| "Buy new car" | "Car" |
The test: Can you finish it? If yes → Project. If no → Area.
Why Breaking Areas into Projects Matters
"As long as you view your work through the lens of areas, you'll never quite know just how much is on your plate." — Tiago Forte
1. You Can't Know Your Commitments Without Projects
Looking at an area like "Hiring" - how much work does it represent? Could be anything from a part-time hire every 6 months to filling 50 positions this quarter.
Break it down:
- Review 10 engineering candidates
- Conduct final interviews for Marketing Manager
- Onboard new DevOps hire
Now you can actually see the workload.
2. You Can't Connect Efforts to Goals Without Projects
Areas never end - they continue indefinitely. Imagine waking up week after week to the same list of never-ending responsibilities:
- Health
- Finances
- Career
- Relationships
This kills motivation. No matter how hard you work, the endless horizon never gets closer.
Projects create victories. When you break areas into bite-sized projects, you get a cadence of regular wins:
Complete marathon training plan✓Hit savings goal for Q1✓Finish certification course✓
Each completion is a dopamine hit that sustains motivation.
3. The Practical Test
Look at your area list. For each one, ask:
"What's the next project I could define that would move this forward?"
If you can't answer, you're probably stalled in that area.
Why PARA Works
1. Universally Applicable
Works across any platform, tool, or medium:
- Digital notes
- Files and folders
- Cloud storage
- Task managers
- Email folders
2. Actionability-Based
Organizes by "when will I use this?" not "what is this about?"
3. Flexible
- Projects come and go
- Areas evolve
- Resources grow
- Archives preserve
4. Cross-Platform
Same structure everywhere creates consistency.
Common Mistakes
1. Too Many Folders
Keep it to 4-6 items per level maximum. If you have more, you probably need sub-projects.
2. Confusing Projects and Areas
"Get healthy" is not a project - it's an area. "Lose 10 pounds by March" is a project.
3. Over-Organizing Resources
Resources don't need perfect organization. They just need to be findable.
4. Fear of Archiving
Archive liberally. You can always retrieve things.
The PARA Workflow
- Capture everything to Inbox
- Clarify what it is and what it means
- Organize into P, A, R, or A
- Review regularly (weekly)
- Engage with your system daily
Integration with GTD
PARA complements Getting Things Done:
| GTD Concept | PARA Location |
|---|---|
| Next Actions | Within Projects |
| Waiting For | Within Projects |
| Someday/Maybe | Resources or Areas |
| Reference | Resources |
| Projects | Projects |
Reference compiled from Tiago Forte's official PARA methodology documentation.