PARA — Projects, Areas, Resources, Archives — is one of the most useful organizational frameworks in personal productivity. It's also one of the most frequently misused. People discover it, spend an afternoon reorganizing their entire note system, and six months later abandon it because maintaining the taxonomy took more energy than the work itself.
The problem isn't PARA. The problem is what people think PARA is for.
The Failure Mode That Kills PARA
The taxonomy trap: you spend more time deciding whether something is a Resource or an Area than you do actually working. You find an article about project management — is it a Resource, or is it input for the product launch you're planning? You file it in both places, which means you've doubled your maintenance load. Six months later you can't remember which copy mattered.
This is the wrong problem to have. The right question was never "where does this go?" It was "where will I need this at the moment of work?"
If it informs a live project, put it in that project. If it supports an ongoing responsibility, put it in the relevant area. If it is genuinely general, put it in resources. If none of those are true, archive it or drop it. PARA fails when people worship categories instead of using them to move work.
The One Rule That Keeps PARA Alive
PARA only works if you use it at the moment of retrieval. Most people file diligently and then never look at the system again. Filing without retrieval is not organizing — it's burying.
The discipline: when you start a work session, open the project you're working on. When you finish, put new notes, next actions, and decisions there. When you file a link, put it where it will support the next decision, not in a general Resources folder and a project subfolder "just in case."
One copy, in the right place. That's the rule. Two copies is doubling your maintenance. Three copies means you can't remember which one is current.
