Organize by Actionability
The organizing principle behind Forte's PARA method (Projects, Areas, Resources, Archives), as presented by the source article: organize knowledge by how actionable it is, not by abstract topic. Projects hold what has a deadline and a goal; Areas hold ongoing responsibilities; Resources hold reference material; Archives hold the inactive rest. The rationale is retrieval friction: organization exists to make information findable while work is already in motion, and action-oriented buckets keep the system tethered to reality, whereas strict topic taxonomies decay into maintenance work (the over-structuring failure mode of Capture-Organize-Distill-Express (CODE)).
This is a sibling of Query-Shaped Storage: both design storage backwards from use rather than from how data arrives. Query-shaped storage fixes the constraint at the question you will ask; organize-by-actionability fixes it at the action the material serves. For a store whose reader is an agent, the query is usually the sharper constraint; for a store driving a human's active work, actionability is.
Claims
- Organize by actionability rather than abstract topic: action-oriented buckets keep a personal store tethered to active work, while strict category trees decay into maintenance work. (best practice — context: a personal knowledge store supporting active projects, per the source; a shared reference corpus that must converge on stable naming — a wiki — has the opposite need)
- Organization's job is retrieval with low friction while work is in motion, not taxonomy perfection. (principle — as asserted by the source)
Related
- Query-Shaped Storage — the sibling design-backwards principle: from the query there, from the action here.
- Capture-Organize-Distill-Express (CODE) — the Organize stage this method implements; its over-structuring failure mode is the anti-pattern PARA is built to avoid.
- AI Second Brain — the store this organizes.
- Distillate: Second Brain Explained for Engineers and Knowledge Workers