Organize by What You'll Do With It, Not What It's About

Most people, me included, instinctively organize by topic. A folder per subject, everything about a thing in one place. It feels obviously correct and it slowly strangles you, because “what something is about” is a poor predictor of “what you need to do with it.” The reorganizing idea that actually changed how I keep notes — and, it turns out, files and projects generally — is to sort by actionability instead of subject. The framework that names this well is PARA, and its core move is worth stealing even if you never adopt the rest.

Topic folders mix the live and the dead

Here’s the problem with a subject folder: a single topic contains material at wildly different stages of usefulness. Under one heading you’ll have an active project you’re shipping this month, an ongoing responsibility with no end date, a pile of reference you might consult someday, and a graveyard of finished work you’ll never touch again. Filing all of that together by subject means your most active material is buried among inert archives, and “where is the thing I’m working on” becomes a dig every single time.

Topic tells you what a note is about. It doesn’t tell you whether you’ll ever open it again — and that’s the thing you actually navigate by.

PARA sorts by actionability, in four buckets

PARA — from Tiago Forte — sorts everything into four top-level buckets defined by how active it is, not what it concerns:

• Projects — efforts with a goal and an end date. Things you’re actively pushing to done.
• Areas — ongoing responsibilities with no end date. Things you maintain.
• Resources — reference material and topics of interest, useful across many projects.
• Archives — anything inactive from the other three.

The names matter less than the axis: a thing’s place is decided by what you’ll do with it, not by its subject. The same topic naturally scatters across all four buckets — and that’s the point, because you almost never want “everything about X.” You want “the active work,” and that lives in Projects regardless of subject.

Why this is the better axis

Two properties make actionability a stronger organizing principle than topic:

• It’s a ladder, not a silo. Material flows Projects → Areas → Resources → Archives as it cools off. A finished project’s notes move to Archives; reference promotes to Resources when it proves broadly useful. Things have an obvious next home as their status changes, instead of calcifying in a topic folder forever.
• It puts the live stuff up front. The things demanding action — Projects and Areas — are separated from the things that are merely about something. Your attention lands on what’s current without wading through the archive every time.

Topic-first organization optimizes for “file it somewhere sensible.” Actionability- first optimizes for “find what I need to act on,” which is what you’re actually doing most days.

Only a few top-level buckets, on purpose

A quiet benefit: four buckets is few enough that placing something is fast. Deep topic hierarchies make you agonize — does this go under networking, or infrastructure, or that project? Actionability collapses the decision to “is this active, ongoing, reference, or done?” which you can usually answer in a second. The structure stays shallow, and shallow structures are the ones people actually maintain. An organizing scheme you abandon because it’s fussy is worse than a simple one you keep.

Steal the principle even without the framework

You don’t have to adopt PARA by the letter to get the win. The transferable idea is just: when you organize anything, ask “what will I do with this?” before “what is this about?” It applies to notes, to project directories, to a backlog, to the tabs you refuse to close. Sort by activity and the things you need stay reachable while the things you’re done with get out of the way — without being deleted, just demoted. It pairs naturally with building a knowledge system that compounds and compiling your notes instead of re-reading them. If you’ve reorganized around actionability and felt the difference, tell me what it changed.

Sources

• The PARA Method — Tiago Forte’s original framework. Content was rephrased here; the four-bucket model is his.