Para Method

---
name: para-method
description: Organize everything with PARA: Projects, Areas, Resources, Archives across any tool. Use when information is scattered and you need one simple universal organizing system.
category: productivity
---

# PARA Method

## Overview

PARA organizes all information into four categories: Projects (active, goal + deadline), Areas (ongoing responsibilities), Resources (topics of interest), Archives (inactive).

Created by Tiago Forte as the universal component of Building a Second Brain — it works in any tool, from Notion to plain folders.

The key insight: organize by actionability, not by topic. What you're doing now (Projects) stays front and center; the rest waits its turn.

Simple enough to apply everywhere consistently — which is exactly why it works.

## When to use

- Information scattered across apps with no consistent structure
- Setting up a new notes app, file system, or task manager
- Unifying organization across multiple tools (notes + files + tasks)
- Teams needing a shared, obvious filing convention
- Simplifying an over-complicated folder taxonomy

## Core concepts

- **Projects.**
  Active endeavors with a goal and deadline. 'Website redesign,' 'Q3 launch.' The only category with urgency — this is where daily work lives.
- **Areas.**
  Ongoing responsibilities with no end date: health, finances, team management, home. Maintained indefinitely, reviewed regularly.
- **Resources.**
  Topics of interest for future use: design inspiration, recipes, research topics. No action required — reference material.
- **Archives.**
  Inactive everything: completed projects, paused areas, outdated resources. Nothing is deleted; it's just put to rest, searchable.
- **Actionability ordering.**
  Projects > Areas > Resources > Archives. Attention flows down the hierarchy; most time is spent in Projects.
- **Universal application.**
  Same four folders in notes, files, bookmarks, tasks. One mental model everywhere means zero relearning per tool.
- **Project completion flow.**
  Done project -> Archive (or its assets split: lessons to Areas/Resources, rest to Archive). The Archive is the memory.
- **Area vs. project test.**
  'Does it have a deadline and a done state?' Yes -> project. No -> area. This single question resolves most filing debates.

## Practical workflow

1. **Create the four folders.**
   In your notes app AND file system: 01 Projects, 02 Areas, 03 Resources, 04 Archives. Same names everywhere.
2. **List active projects.**
   Every current endeavor with goal + deadline. Cap at ~10 active; the rest are parked in Archives until activated.
3. **Define your areas.**
   Ongoing responsibilities: health, money, career, home, key relationships. 8-12 areas is typical.
4. **Seed resources lightly.**
   Only topics you actually reference. Don't pre-build a library of 50 empty topic folders.
5. **Migrate as you touch.**
   Don't big-bang reorganize years of files. New items go to PARA; old items move when touched. Legacy stays searchable.
6. **Run project closeouts.**
   Completed project: extract lessons to Areas/Resources, move the rest to Archive. Five minutes, huge long-term value.
7. **Review weekly.**
   Projects: still active? Areas: anything neglected? Promote/demote between categories as reality changes.
8. **Archive quarterly.**
   Sweep for dead projects and stale resources. Archives keep everything findable without cluttering the active view.

## Common pitfalls

- **Too many projects.**
  25 'active' projects means none are. Cap active projects; park the rest in Archives honestly.
- **Areas as projects.**
  Putting deadline work in Areas where it rots without urgency. Deadline + done state = project, always.
- **Resources hoarding.**
  50 topic folders, 45 never opened. Resources should be lean — only what you actually reference.
- **Deleting instead of archiving.**
  Deleting completed work destroys future value (templates, lessons, evidence). Archive; storage is cheap.
- **Inconsistent naming.**
  'Projects' in one app, 'Active' in another. Same four names everywhere — the universality is the point.
- **Filing by topic in Projects.**
  Project folders organized by subject instead of by project outcome. PARA sorts by actionability, not taxonomy.
- **Never archiving.**
  Completed projects lingering in Projects for years. The closeout ritual keeps the active view truthful.
- **Over-nesting.**
  Projects/Areas/Resources/Clients/Website/2024/... Deep hierarchies defeat PARA's simplicity. Two levels max.