para-method

# PARA Method - Organize Your Digital Life

The PARA Method is a universal organizational system developed by Tiago Forte for
organizing every piece of information in your digital life across any platform.

## When to Use This Skill

- Setting up a new note-taking system (Notion, Obsidian, Evernote, etc.)
- Organizing digital files and folders
- Categorizing notes, tasks, or projects
- Migrating from other systems (GTD, Zettelkasten, etc.)
- Conducting weekly reviews of your productivity system
- Deciding where to store or move information
- Maintaining an organized Second Brain

## Core Principle

**Organize by actionability, not by topic.**

```
Traditional (Topic-Based)     PARA (Actionability-Based)
─────────────────────────     ──────────────────────────
📁 Work/                      📁 Projects/
📁 Personal/                  📁 Areas/
📁 Reference/                 📁 Resources/
📁 Archive/                    📁 Archives/

❌ Where do I file this?      ✅ What is this for?
❌ No clear answer             ✅ Clear answer every time
```

The PARA system organizes information based on how actionable it is right now.

## The Four Categories

### 1. Projects - Active Endeavors with Deadlines

**Definition:** Short-term efforts with a clear endpoint and deadline.

```
Projects have:
├── Specific goal/outcome
├── Clear deadline or timeframe
├── Series of tasks/actions
└── Defined "done" state
```

**Examples:**
- "Complete Q4 financial report by December 15"
- "Launch new website by March 1"
- "Plan summer vacation in July"
- "Write article draft by Friday"
- "Prepare presentation for conference"

**How to identify:**
```
Question: Can I cross this off my list when done?
Answer: YES → It's a Project

Key Test:
- Does it have a clear finish line?
- Would you throw a party when it's done?
- Will it definitely end?
```

### 2. Areas - Ongoing Responsibilities Without Deadlines

**Definition:** Spheres of responsibility requiring continuous attention.

```
Areas have:
├── No deadline (ongoing)
├── Standard to maintain
├── Never "completed"
└── Requires regular attention
```

**Examples:**
- Health & Fitness
- Finances
- Career/Professional Development
- Relationships
- Home Environment
- Personal Growth
- Team Management
- Client Relations

**How to identify:**
```
Question: Is there a clear endpoint?
Answer: NO → It's an Area

Key Test:
- Will this continue indefinitely?
- Is there no "done" state?
- Does it require ongoing maintenance?
```

### 3. Resources - Topics of Ongoing Interest

**Definition:** Topics, themes, or interests you want to reference in the future.

```
Resources have:
├── No action required now
├── Potential future value
├── Topics of interest
└── Reference material
```

**Examples:**
- Marketing Strategies
- Cooking Recipes
- Design Inspiration
- Programming Tutorials
- Writing Tips
- Travel Guides
- Mental Models
- Leadership Frameworks

**How to identify:**
```
Question: Is this useful/interesting but not directly actionable?
Answer: YES → It's a Resource

Key Test:
- Would you reference this later?
- Is it educational/informative?
- Does it support your interests?
```

### 4. Archives - Inactive Items

**Definition:** Completed or inactive items from other categories.

```
Archives have:
├── No current relevance
├── Historical value
├── Potential future reference
└── Storage for completed/deferred items
```

**Examples:**
- Completed Projects
- Inactive Areas (past jobs, ended relationships)
- Old Resources (no longer relevant)
- Past reference materials

**How to identify:**
```
Question: Is this inactive but worth keeping?
Answer: YES → It's an Archive

Key Test:
- Project completed? → Archive it
- Area no longer relevant? → Archive it
- Resource outdated? → Archive it
```

## Actionability Spectrum

```
Most Actionable ←────────────────────────────→ Least Actionable

┌─────────┐   ┌────────┐   ┌───────────┐   ┌──────────┐
│PROJECTS │ → │ AREAS  │ → │ RESOURCES │ → │ ARCHIVES │
└─────────┘   └────────┘   └───────────┘   └──────────┘
    │              │              │               │
Active now    Important but    Useful for       Inactive
must focus    ongoing         future ref       storage
```

**Key principle:** Information flows from left to right as actionability decreases.

## Decision Framework

### The PARA Test

Ask these questions in order:

```
1. Is it active right now?
   YES → Projects (has deadline) or Areas (ongoing standard)
   NO → Continue

2. Does it have a deadline?
   YES → Projects
   NO → Areas

3. Is it useful/interesting reference material?
   YES → Resources
   NO → Archives

4. Is it inactive but worth keeping?
   YES → Archives
   NO → Delete/doesn't belong in system
```

### Quick Decision Tree

```
                        Where does this go?
                               │
                               ▼
                      ┌────────────────┐
                      │  Active now?   │
                      └────────────────┘
                         │         │
                        YES        NO
                         │         │
                         ▼         ▼
                  ┌──────────┐  ┌────────────┐
                  │ Deadline?│  │ Useful ref?│
                  └──────────┘  └────────────┘
                    │      │      │      │
                   YES     NO    YES     NO
                    │      │      │      │
                    ▼      ▼      ▼      ▼
                Project  Area  Resource Archive
```

## Implementation Guide

### Phase 1: Quick Setup (First Hour)

```
1. Create four top-level folders:
   📁 1-Projects/
   📁 2-Areas/
   📁 3-Resources/
   📁 4-Archives/

2. Number them (1-4) for:
   ✓ Sorting by actionability
   ✓ Quick visual reference
   ✓ Consistent ordering across platforms

3. Don't create subfolders yet
   → Let structure emerge naturally
```

**Why numbering matters:**
```
Without numbers, alphabetizing gives:
Areas, Archives, Projects, Resources
      ↑         ↑
   Wrong order - breaks actionability principle

With numbers (1-4), always correct:
1-Projects, 2-Areas, 3-Resources, 4-Archives
```

### Phase 2: Initial Sorting (First Day)

```
Process existing items:

1. Create "To Sort" temporary folder
2. Move ALL existing notes/files to "To Sort"
3. Start with empty PARA structure
4. Sort items one by one using decision tree
5. Ask: "Is this active now?"

Benefits:
├── Clean slate
├── Forced reconsideration of every item
├── Prevents hoarding in wrong category
└── Ensures intentional placement
```

### Phase 3: Detailing (First Week)

```
Add subfolders as needed:

1-Projects/
├── Q4 Financial Report/
├── Website Redesign/
├── Summer Vacation/
└── Conference Presentation/

2-Areas/
├── Health & Fitness/
├── Finances/
├── Career Development/
├── Relationships/
├── Home Maintenance/
└── Personal Growth/

3-Resources/
├── Marketing Strategies/
├── Writing Tips/
├── Design Inspiration/
├── Programming/
├── Mental Models/
└── Productivity/

4-Archives/
├── Completed Projects/
├── Old Jobs/
├── Past References/
└── Inactive Areas/
```

## Categorization Examples

### Real-World Scenarios

```
Item: "Meeting notes: Marketing sync, Dec 5"
Decision: Where does this go?

Analysis:
├── Actionable now? → Check if follow-ups needed
├── Meeting itself: Informational → Resource (if valuable)
├── Has action items? → Create Project for each
└── Just reference? → Archive or delete

Placement:
└── Extract action items → Projects
    Save key insights → Resources: Marketing
    No value? → Archives or delete
```

```
Item: "Reading list of business books"
Decision: Where does this go?

Analysis:
├── Currently reading? → Project: "Read [Book Title]"
├── List of books to read → Areas: Learning & Development
└── Book notes/summaries → Resources: Book Notes

Placement:
└── Split into multiple locations based on actionability
```

```
Item: "Vacation photos from 2023"
Decision: Where does this go?

Analysis:
├── Part of active project? → No
├── Ongoing responsibility? → No
├── Reference material? → Maybe (Resources: Travel)
└── Just storage? → Archives: Vacations/2023

Placement:
└── Resources (if you reference for future trips)
    OR Archives (if purely historical)
```

## Maintenance & Reviews

### Weekly Review (15-30 minutes)

```
Weekly PARA Check:

Projects (5 min):
├── [ ] Review active projects
├── [ ] Move completed projects → Archives
├── [ ] Check deadlines are still relevant
├── [ ] Update project status
└── [ ] Identify stalled projects

Areas (5 min):
├── [ ] Review areas needing attention
├── [ ] Check systems/spreadsheets are updated
└── [ ] Note any neglected areas

Resources (5 min):
├── [ ] Brief scan for misfiled items
└── [ ] No action typically needed

Archives (5 min):
├── [ ] Usually minimal action
└── [ ] Clean up if needed
```

### Monthly Review (1-2 hours)

```
Monthly PARA Maintenance:

1. Review All Projects
   ├── Close completed projects
   ├── Assess stalled projects
   ├── Prioritize active projects
   └── Check alignment with areas

2. Audit Areas
   ├── Are all areas still relevant?
   ├── Any new responsibilities emerged?
   └── Standards being maintained?

3. Clean Resources
   ├── Remove obsolete items
   ├── Merge duplicate topics
   └── Reorganize if needed

4. Purge Archives
   ├── Delete truly unnecessary items
   ├── Compress old files
   └── Check for items to reactivate
```

### Quarterly Deep Clean (Half day)

```
Quarterly PARA Overhaul:

1. Complete PARA audit
   ├── Every folder examined
   ├── Every item reconsidered
   └── Structure refined

2. Update systems
   ├── Templates refreshed
   ├── Processes documented
   └── Tools evaluated

3. Set quarterly goals
   ├── Major projects identified
   ├── Area focus areas defined
   └── Resource gaps addressed

4. Archive management
   ├── Major archival
   ├── Cleanup completed
   └── Storage optimized
```

## Migration Guide

### From GTD (Getting Things Done)

```
GTD Structure          →  PARA Structure
───────────────────        ───────────────
Next Actions           →   Projects (with next actions)
Projects               →   Projects
Areas of Focus         →   Areas
Reference              →   Resources
Someday/Maybe          →   Archived Projects
Tickler                →   Archive with dates
Waiting For            →   Project notes

Key difference:
├── GTD: Action-focused (what to do next)
└── PARA: Actionability-focused (when to engage)
```

### From Zettelkasten

```
Zettelkasten Structure  →  PARA Structure
────────────────────        ───────────────
Main notes (Zettels)    →   Split by actionability:
├── Permanent notes     →   Resources (concepts, ideas)
├── Project notes      →   Projects (active work)
├── Structure notes    →   Areas (topic overview)
└── Literature notes   →   Resources (source material)

Key integration:
├── Keep Zettelkasten principles for note-taking
├── Use PARA for overall organization
└── Zettelkasten lives within Resources
```

### From Folder Chaos

```
Common folder mess → PARA migration:

1. Start fresh (don't try to sort in place)
   └── Create clean PARA structure

2. Create "To Sort" folder
   └── Move everything there

3. Sort items using decision framework
   └── One by one, deliberate placement

4. Resist creating subfolders initially
   └── Let structure emerge from needs

5. Trust new categories
   └── Items will flow where they belong
```

## Platform-Specific Implementation

### Notion

```
Para Structure in Notion:

Workspace
├── 📊 Dashboard (linked views)
├── 📁 Projects (database)
│   ├── Status: Active/Completed
│   ├── Due Date
│   └── Related Area
├── 📁 Areas (database or pages)
│   ├── Area template
│   └── Linked to Projects
├── 📁 Resources (database)
│   ├── Tags for topics
│   └── Related Projects/Areas
└── 📁 Archives (database)
    ├── Original location field
    └── Date archived
```

**Notion-specific tips:**
- Use databases for Projects (filterable by status)
- Create templates for each project type
- Link Resources to active Projects
- Use relations between databases

### Obsidian

```
Para Structure in Obsidian:

Vault
├── 1-Projects/
│   ├── Project A.md
│   └── Project B.md
├── 2-Areas/
│   ├── Health & Fitness.md
│   └── Career.md
├── 3-Resources/
│   ├── Marketing/
│   ├── Writing/
│   └── Mental Models/
└── 4-Archives/
    ├── Completed Projects/
    └── Old Resources/

+ Daily Notes (linked to projects)
+ Dataview queries for active items
+ Tags: #project, #area, #resource
```

**Obsidian-specific tips:**
- Use Dataview plugin for queries
- Create MOCs (Maps of Content) for Resources
- Link daily notes to active projects
- Use tags sparingly (folders do heavy lifting)

### Evernote / OneNote / Apple Notes

```
Para Structure in Traditional Note Apps:

Notebooks/Sections:
├── 📓 1-Projects
│   └── One notebook per active project
├── 📓 2-Areas
│   └── One notebook per area
├── 📓 3-Resources
│   └── Topic-based notebooks
└── 📓 4-Archives
    └── Stacked notebooks by category

Tags (secondary organization):
├── Project-specific tags
├── Area tags
├── Topic tags in Resources
└── Date tags in Archives
```

## Templates & Examples

### Project Template

```markdown
# Project: [Name]

## Overview
- **Status:** [Planning/Active/On Hold]
- **Start Date:** [Date]
- **Target Completion:** [Date]
- **Area:** [Which area this supports]

## Goal
[Clear outcome - what does "done" look like?]

## Success Criteria
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]

## Key Tasks
- [ ] Task 1
- [ ] Task 2
- [ ] Task 3

## Resources Needed
- [List resources from Resources folder]

## Notes & Progress
[Running notes]

## Links
- [Related resources]
- [Reference materials]

---
Created: [Date]
Last Updated: [Date]
```

### Area Template

```markdown
# Area: [Name]

## Definition
[What does this area encompass?]

## Standards
[What does "good enough" look like in this area?]

## Current Projects
- [Active Project 1]
- [Active Project 2]

## Key Metrics
- [Metric 1]
- [Metric 2]

## Regular Actions
- [Daily/Weekly/Monthly actions]

## Resources
- [Links to relevant Resources]

## Notes
[Running thoughts and observations]

## Last Review
[Date: Summary of status]
```

### Resource Template

```markdown
# Resource: [Topic Name]

## Summary
[Quick summary of what this contains]

## Key Concepts
- [Concept 1]: [Brief explanation]
- [Concept 2]: [Brief explanation]

## Related Areas
- [Area 1]
- [Area 2]

## Active Projects Using This
- [Project 1]
- [Project 2]

## Notes Collection

### [Subtopic 1]
[Notes, quotes, insights]

### [Subtopic 2]
[Notes, quotes, insights]

## Links & References
- [Source 1]
- [Source 2]

---
Created: [Date]
Last Updated: [Date]
```

## Best Practices

### Do's ✓

```
✓ Start simple, let structure emerge
   └── Don't over-engineer from day one

✓ Use numbering (1-4) for consistent ordering
   └── Ensures most actionable items first

✓ Move items freely between categories
   └── PARA is dynamic, not static

✓ Create new project folders for active work
   └── Projects are temporary homes

✓ Review weekly to maintain system
   └── Prevents buildup and misfiling

✓ Keep "To Sort" folder for quick capture
   └── Sort later during reviews

✓ Archive completed projects immediately
   └── Keeps Projects folder clean

✓ Link related items across categories
   └── But don't duplicate - reference instead
```

### Don'ts ✗

```
✗ Don't organize by topic
   └── "Work" and "Personal" are topics, not actionability levels

✗ Don't create too many subfolders
   └── Max 3 levels deep

✗ Don't duplicate items
   └── Link/reference instead

✗ Don't skip weekly reviews
   └── System degrades quickly without maintenance

✗ Don't let Projects become Areas
   └── Projects must have deadlines

✗ Don't hoard in Archives
   └── Delete truly useless items

✗ Don't overthink placement
   └── Better to place and adjust than procrastinate

✗ Don't create "Miscellaneous" folders
   └── Everything has a place in PARA
```

## Common Questions

### What if something fits multiple categories?

```
Place where you'll LOOK for it first.

Example: "Health insurance documents"
├── Actively needed? → Projects (if switching plans)
├── Ongoing reference? → Areas (Health & Fitness)
└── Pure storage? → Resources (Insurance)

Rule: One home, link elsewhere if needed
```

### How detailed should project folders be?

```
Match complexity to project:

Simple Project:
└── Single note or document

Complex Project:
└── Folder with:
    ├── Project brief
    ├── Research
    ├── Drafts
    ├── Assets
    └── Final deliverables
```

### When should I archive?

```
Archive immediately when:
├── Project completed
├── Project cancelled
├── Area no longer relevant
├── Area ended (job ended, relationship ended)
└── Resource no longer useful

Don't wait for "review" - archive now
```

### How many projects should I have?

```
No strict limit, but consider cognitive load:

Healthy range: 5-15 active projects
├── Too few: May lack progress on goals
└── Too many: Split focus, stalled projects

If > 15 projects:
├── Some may be Areas mislabeled
├── Some should be archived
└── Some need delegation/declining
```

## Integration with Other Methods

```
PARA + Other Systems:

GTD (Getting Things Done):
├── PARA organizes WHERE items live
├── GTD defines HOW to process items
└── Use GTD for task execution, PARA for organization

OKRs (Objectives & Key Results):
├── Objectives → Areas
├── Key Results → Projects
└── Initiatives → Project tasks

Agile/Scrum:
├── Sprints → Short-term Projects
├── Epics → Larger Projects
├── Backlog → Resources + Archives
└── Product Areas → Areas

Zettelkasten:
├── Lives within Resources
├── Knowledge work goes here
└── Active thinking remains in Projects
```

## Quick Reference Card

```
THE PARA QUICK GUIDE

PROJECTS (Active + Deadline)
├── Specific endpoint
├── Clear success criteria
├── Has due date
└── Can be "completed"

AREAS (Ongoing Responsibilities)
├── No endpoint
├── Standards to maintain
├── Requires attention
└── Never "completed"

RESOURCES (Reference Material)
├── Topics/interests
├── Educational/informative
├── Potential future value
└── No immediate action

ARCHIVES (Inactive Items)
├── Completed projects
├── Inactive areas
├── Old resources
└── Anything not current

DECISION ORDER:
1. Active? → P or A
2. Deadline? → P
3. No deadline? → A
4. Reference? → R
5. Inactive? → Archive
6. Useless? → Delete
```

## Troubleshooting

### "My Projects folder is overwhelming"

```
Diagnosis: Likely mixing Projects and Areas

Solution:
├── Check each "project" for deadline
├── Move ongoing work to Areas
├── Break large projects into smaller projects
└── Archive stalled projects
```

### "I never look at Resources"

```
Diagnosis: Resources too disconnected from active work

Solution:
├── Link Resources to Projects/Areas
├── Create "quick reference" sections
├── Review Resources during project planning
└── Consider: Is this truly useful? Delete if not
```

### "I don't know where to put X"

```
Decision paralysis → Use the PARA test:

1. Does this require action? → Projects/Areas
2. Does it have a deadline? → Projects
3. Is it ongoing? → Areas
4. Is it reference? → Resources
5. Is it inactive? → Archives

Still unsure? → Put in "To Sort" and decide during review
```

## Resources

For detailed implementation guides, platform-specific setups, and advanced techniques, see [REFERENCE.md](./REFERENCE.md).

- [Building a Second Brain - Tiago Forte](https://www.buildingasecondbrain.com/)
- [The PARA Method - Tiago Forte](https://fortelabs.com/)
- Official PARA Method Book (2023)
- BASB Course by Tiago Forte