Bratha

Part 4.0 — PARA

7 min read

This is Part 4 of 7 in the Productivity Enhancement Series

Table of Contents

The knowledge layer's one job

The workflow handles things you’ll do. The knowledge layer handles things you’ll consult: notes, references, research, saved articles, documents. Its one job is retrieval: getting the right thing back into your hands the moment you need it. A knowledge base you can’t retrieve from is just a hoard. PARA is the organising scheme that makes retrieval automatic, and it’s one of the terms this series keeps from the original framework1 because it’s genuinely the best answer to “where does this go?”

Why organise by actionability, not topic

The instinct everyone has is to organise notes by topic: a folder for “marketing,” one for “health,” one for “finance.” It feels logical and it fails, for one reason: ==a topic-based system can’t tell you what’s relevant right now.== Your “marketing” folder mixes the campaign that’s due Friday with an article you saved two years ago and will never reopen. They’re the same topic and completely different in urgency.

PARA’s insight is to organise by how soon you’ll act on something instead. The result is that the things connected to your active work float to the top automatically, and the dead weight sinks out of sight without being deleted. You file by actionability, and retrieval sorts itself out.

The four buckets

PARA is four buckets, ordered from most to least actionable. Everything you save goes in exactly one of them.

P · A · R · A

  • Projects — active, with a deadline and an outcome. Things you’re working on now that will end: “launch the Q3 page,” “renew the lease,” “write Part 4.” Each maps to a project in your workflow. This is the hottest, most-touched bucket.
  • Areas — ongoing responsibilities with no end date. Standards you maintain indefinitely: health, finances, a role you hold, a property you own. No deadline, but they need attention forever.
  • Resources — topics of interest, for future reference. Things you’re not acting on but want available: saved articles, research, a technique you might use someday. This is where most saved content actually belongs.
  • Archives — done or dormant. Completed projects, areas you no longer hold, resources gone cold. Not deleted (you might want them), just out of the way.

The order is the point. The closer to the top, the more often you touch it and the more visible it should be. Projects are in your face daily; Archives you should almost never see.

How things move between buckets

PARA isn’t a static filing cabinet; it’s a flow. Items move as your life moves, and the movement is most of the value.

  • A Resource becomes part of a Project the moment you start acting on it (that negotiation article you saved becomes live reference when you’re actually negotiating a contract).
  • A Project drops to the Archive the day it’s done. This is the satisfying one: finishing a project means sweeping its whole folder into Archives in one move, and your active space gets cleaner every time you complete something.
  • An Area spins off Projects continuously (the “health” area spins off “book the annual blood panel,” which is a project with a deadline).
  • An Archive item can resurrect into a Resource or Project if it becomes relevant again.

The same scheme everywhere

Use PARA identically across all your tools: your notes app, your file system, your cloud drive, your bookmarks. The power is that “where does this go?” has the same four-answer shape no matter what you’re filing, so the decision becomes automatic. One scheme, every tool.

Running PARA in practice

A few rules that keep it working:

  • When you save something, ask only: “which of the four, and for which project or area?” That’s the entire filing decision. No deep folder trees, no agonising. Four buckets, then a name.
  • Default to Resources. If you’re not sure, most saved content is a Resource. It’s better to under-categorise and let it move up than to build an elaborate home for something you’ll never open.
  • Archive aggressively. A finished project sitting in your active space is noise (the enemy). Sweeping it out is how the system stays fast.
  • Let Projects here mirror Projects in your workflow. The PARA “Projects” folder and your workflow’s project list are two views of the same thing: one holds the material, the other holds the actions. Keep their names matched.

The AI multiplier on PARA

Two wins. First, filing: an assistant can read a saved item and propose its bucket and the project or area it attaches to, so even the small filing decision is drafted for you. Second, and far bigger, retrieval by meaning: instead of remembering which folder something is in, you ask your knowledge base a question and it finds the relevant note regardless of where it’s filed. That’s RAG over your own vault, built in Part 5.0, and it’s why the filing matters less than it used to while the capturing matters more. The next article, Progressive Summarisation, makes each note worth retrieving in the first place.

Part 4 Takeaways

  • The knowledge layer’s one job is retrieval. A base you can’t retrieve from is a hoard.
  • Organise by actionability, not topic. Topic folders can’t tell you what matters now; PARA can.
  • The four buckets, hottest to coldest: Projects (active, deadlined), Areas (ongoing responsibilities), Resources (future reference), Archives (done or dormant).
  • PARA is a flow: things move up when you act on them and drop to Archives when done. Archive aggressively.
  • Use the same four-bucket scheme in every tool so filing becomes an automatic decision.
  • AI makes filing easier and retrieval semantic, so good capture now matters more than perfect folders.

Your PARA Task List

This week

  • Create the four top-level buckets (Projects, Areas, Resources, Archives) in your main notes app and your file system.
  • List your current active Projects; give each a folder. Match the names to your workflow’s project list.
  • List your ongoing Areas (health, finances, each role you hold). These rarely change.
  • Sweep everything finished into Archives. Notice how much lighter the active space feels.
  • For the next week, file every new save with the one question: which bucket, which project or area?

Sources & references

Footnotes

  1. Tiago Forte, Building a Second Brain (2022), and “The PARA Method” (2023). PARA (Projects, Areas, Resources, Archives) is kept from the source framework because organising by actionability rather than topic is, in practice, the most reliable answer to where information should live. This series departs from the source mainly at Part 4.2, where the “second brain” goal of storage is replaced with building tools that act. ↩

Graph View

Backlinks