--- created: 2026-01-06 type: reference tags: [para, methodology, organization] --- # PARA Method Explained **P.A.R.A.** = Projects, Areas, Resources, Archive A universal system for organizing digital information based on **actionability**. --- ## Core Principle **Organize by actionability, not by category** Traditional filing (by topic) asks: "What is this about?" PARA asks: "How will I use this?" --- ## The Four Categories ### 1. Projects (01_Projects/) **Definition**: Time-bound initiatives with clear completion criteria **Characteristics**: - Has a specific end goal - Has a deadline or completion state - Contains discrete tasks and deliverables - Will eventually move to Archive **Examples**: - Writing a research paper - Planning a presentation - Learning a specific skill - Organizing an event - Building a feature - Planning a trip **Structure**: ``` 01_Projects/[ProjectName]/ ├── README.md # Project overview, goals, timeline ├── Research/ # Background materials ├── Drafts/ # Work in progress ├── References/ # Supporting documents └── Output/ # Final deliverables ``` **When to Archive**: - Project objectives are met - Project is cancelled or abandoned - Project becomes inactive for 30+ days --- ### 2. Areas (02_Areas/) **Definition**: Ongoing responsibilities without end dates **Characteristics**: - Continuous maintenance required - Standards to uphold (not goals to achieve) - No completion date - Generates multiple projects over time **Examples**: - Health & Fitness - Professional Development - Finances - Relationships - Home Management - Career - Personal Growth **Structure**: ``` 02_Areas/[AreaName]/ ├── Overview.md # Area definition and standards ├── Projects.md # Related project links └── Resources.md # Helpful references ``` **Key Insight**: Areas are **standards to maintain**, not goals to achieve. - ✅ "Maintain health" (Area) - ❌ "Lose 10 pounds" (Project) **When to Archive**: - Area is no longer relevant to your life - Responsibility has been transferred - Area has been inactive for 6+ months --- ### 3. Resources (03_Resources/) **Definition**: Topics of interest for reference and learning **Characteristics**: - Not tied to current projects or areas - Reference material for future use - Long-term knowledge building - Curated information by topic **Examples**: - Programming languages (Python, JavaScript) - Historical topics (World War II, Ancient Rome) - Philosophical concepts (Stoicism, Existentialism) - Technical documentation (Git, Docker, APIs) - Book notes and summaries - Research papers - How-to guides **Structure**: ``` 03_Resources/[TopicName]/ ├── Index.md # Topic overview ├── Notes/ # Individual concept notes └── References/ # Source materials ``` **Key Insight**: Resources are **interests, not responsibilities**. - If you're not actively using it → Resource - If you must maintain it → Area **When to Archive**: - Information becomes outdated - Topic is no longer of interest - Superseded by better resources --- ### 4. Archive (04_Archive/) **Definition**: Completed projects and inactive items **Characteristics**: - Completed projects (for reference) - Inactive areas (no longer relevant) - Outdated resources (superseded) - Historical reference only **Structure**: ``` 04_Archive/ ├── Projects/ # Completed projects ├── Areas/ # Inactive areas └── Resources/ # Outdated resources ``` **When to Archive**: - **Projects**: When objectives are met or abandoned - **Areas**: When no longer relevant - **Resources**: When superseded or no longer useful **Archive vs. Delete**: - Archive: May need for reference later - Delete: Clearly useless or duplicates --- ## Decision Flow **Where should this file go?** ``` ┌─ Has a deadline or end goal? │ └─ YES → Projects │ ├─ Ongoing responsibility? │ └─ YES → Areas │ ├─ Just interesting information? │ └─ YES → Resources │ ├─ Completed or inactive? │ └─ YES → Archive │ └─ Not sure? └─ → Inbox (process later) ``` --- ## Common Confusion ### Project vs. Area | Question | Project | Area | |----------|---------|------| | Has deadline? | ✅ Yes | ❌ No | | Can be completed? | ✅ Yes | ❌ No | | Generates tasks? | ✅ Yes | ✅ Yes | | Standard to maintain? | ❌ No | ✅ Yes | **Example**: - "Health" → Area (ongoing responsibility) - "Train for marathon" → Project (specific goal, deadline) ### Area vs. Resource | Question | Area | Resource | |----------|------|----------| | Must maintain? | ✅ Yes | ❌ No | | Accountability? | ✅ Yes | ❌ No | | Just interested? | ❌ No | ✅ Yes | **Example**: - "Professional Development" → Area (responsibility) - "Machine Learning" → Resource (interest/learning) --- ## PARA Benefits ### 1. Fast Capture Don't waste time deciding perfect categories. If unsure → Inbox. ### 2. Context-Based Information is organized by how you'll use it, not what it's about. ### 3. Scalable Works with 10 files or 10,000 files. ### 4. Action-Oriented Focus on what needs attention now (Projects/Areas), not passive information. ### 5. Dynamic Files move between categories as context changes. --- ## PARA in Practice ### Starting a New Project 1. Create folder: `01_Projects/[ProjectName]/` 2. Add README.md with: - Goal and timeline - Success criteria - Next actions 3. Move related notes from Inbox/Resources to project folder 4. Work actively until completion 5. Archive when done ### Maintaining an Area 1. Create folder: `02_Areas/[AreaName]/` 2. Add Overview.md with: - Definition of the area - Standards to maintain - Key metrics or indicators 3. Link to related projects (many projects may support one area) 4. Review during weekly review 5. Archive if no longer relevant ### Building Resources 1. Capture web content, articles, notes to Inbox 2. During processing, ask: "Is this tied to a project/area?" - No? → Move to `03_Resources/[Topic]/` 3. Build topic collections over time 4. Reference when starting new projects --- ## Migration Tips ### From Folder-Based System **Before** (By topic): ``` Notes/ ├── Work/ ├── Personal/ ├── Learning/ └── Reference/ ``` **After** (By actionability): ``` 01_Projects/ ← Active work items 02_Areas/ ← Ongoing responsibilities 03_Resources/ ← Reference materials 04_Archive/ ← Completed items ``` ### From Tag-Based System Keep tags! PARA complements tags: - **PARA**: Primary organization (folders) - **Tags**: Secondary connections (cross-cutting themes) Example: - File: `01_Projects/Website_Redesign/wireframes.md` - Tags: `#design #ux #client-work` --- ## Common Pitfalls ### 1. Too Many Projects **Problem**: 20+ active projects **Solution**: Archive inactive projects. Aim for 5-10 active projects max. ### 2. Areas Become Dumping Grounds **Problem**: "Personal" area has 100+ unrelated notes **Solution**: Break into specific areas or create projects for actionable items. ### 3. Never Archiving **Problem**: Completed projects stay in Projects folder **Solution**: Move to Archive immediately upon completion. ### 4. Over-Organizing Resources **Problem**: Spending hours categorizing resources **Solution**: Quick capture to Inbox, batch organize weekly. ### 5. Treating Areas as Projects **Problem**: Expecting areas to be "completed" **Solution**: Areas are maintained, not completed. Create projects for specific goals. --- ## Weekly Review Integration During weekly review, ask: **Projects**: - [ ] Which projects are complete? → Archive - [ ] Which projects are stalled? → Archive or reactivate - [ ] Do areas need new projects? **Areas**: - [ ] Are standards being met? - [ ] Do any areas need attention? - [ ] Should any areas be archived? **Resources**: - [ ] Are resources still relevant? - [ ] Can resources be consolidated? - [ ] Archive outdated resources? **Inbox**: - [ ] Process all items into PARA --- ## Advanced: Cross-Cutting Themes PARA handles **vertical organization** (by actionability). Use **tags** for horizontal themes: Example: - Project: `01_Projects/Client_Presentation/` - Tags: `#public-speaking #client-work #q1-2026` This creates multi-dimensional organization: - Find by project (folder) - Find by theme (tags) - Find by time (date tags) --- ## Further Reading **Original Creator**: Tiago Forte **Book**: *Building a Second Brain* **Blog**: [Forte Labs](https://fortelabs.com/blog/para/) **Related Methods**: - GTD (Getting Things Done) - Task management - Zettelkasten - Note-taking and connections - PARA - Information organization **Best Used Together**: - PARA for organization - Zettelkasten for linking ideas - GTD for task execution --- ## Quick Reference | Category | Question | Timeframe | |----------|----------|-----------| | **Projects** | What am I working on? | Short-term (weeks-months) | | **Areas** | What am I responsible for? | Ongoing (no end) | | **Resources** | What might be useful? | Long-term reference | | **Archive** | What is completed? | Historical | --- **Last Updated**: 2026-01-06 **See Also**: [[CLAUDE]], [[QUICK_REFERENCE]], [[WEEKLY_REVIEW]]