The PARA Method: Organize Your Digital Life with Tiago Forte's Four Folders

Introduction

Every solo founder has the same junk drawer. Bookmarks saved and never opened. Screenshots of ideas that made sense at midnight and none the next morning. Half-written notes scattered across three apps, a desktop full of files named final-v2-really-final.pdf, and a head full of open loops. The problem is not that you forget things. The problem is that you have nowhere to put them where you can find them again when they matter.

Tiago Forte's answer is called PARA. It is a filing system with exactly four folders — Projects, Areas, Resources, Archives — and one rule: file everything by how actionable it is, not by what it is about. Forte did not invent it in a laboratory. He built it because a chronic illness that began when he was twenty-two left him unable to rely on his own memory, so he built an external one out of notes, software and habit. He then taught the system live, cohort after cohort, starting with 25 students in January 2017, and eventually wrote it up in his 2022 book Building a Second Brain, published by Atria Books on 14 June 2022. The book has sold 250,000 copies. The method below is his, distilled into a form a solo founder can set up in half an hour.

Why topic folders fail

Most people organise their notes the way a library organises books: by subject. A folder called Marketing, one called Finance, one called Health, one called Ideas. It feels sensible, and it fails in the same way every time. Subject folders grow forever and never tell you what to do next. A folder called Marketing holds a tweet you liked in 2023, a half-finished launch plan, a competitor's pricing page and a quote you meant to use somewhere. When you open it to work on next week's launch, you have to re-read all of it to find the three items that matter. The folder answers the question "what is this about?" and nobody working on a deadline ever asks that question. The question they ask is "what do I do next?"

PARA replaces the subject question with an action question. Every note, file, bookmark and idea goes into one of four folders, decided by a single test: what is this for, and when will I act on it? Something with a finish line goes in Projects. Something you maintain indefinitely goes in Areas. Something interesting with no deadline goes in Resources. Something finished goes in Archives. The folders are not a taxonomy of knowledge. They are a map of your commitments, and commitments change, which is why the system stays useful: when a project ends, you drag the whole folder into Archives and it disappears from view without being deleted.

Step 1: The four folders, and what goes where

Start by understanding the four buckets precisely, because every filing decision you will ever make in this system is a choice between them.

Projects are active efforts with a defined outcome and a finish line. Launching a product, planning a trip, writing a proposal, preparing for an exam. A project has a deadline, even a soft one, and a moment when you can say it is done. Only projects go at the top of the system, because only projects tell you what to do today. If you are working on a launch, the notes that serve that launch live inside the launch's folder, not in a folder called Marketing. When the launch ships, the whole folder moves to Archives in one drag.

Areas are ongoing responsibilities with no finish line, only a standard to maintain. Health, finances, career, parenting, a business you run. You never complete an area; you tend it. The test is simple: if it has no end date but still needs your attention every week, it is an area. Most people have four to six areas, and that is enough. An area with nothing in it is not a failure; it is a reminder of a responsibility you have chosen to keep.

Resources are topics you find interesting or useful, with no current obligation attached. Articles on storytelling, research on pricing, recipes, investment theory, a language you might learn one day. Resources are the drawer where curiosity lives, and the rule for resources is honesty: if nothing in your current projects or areas needs it, it is a resource, not a project. Calling a curiosity a project is how to-do lists grow into guilt lists.

Archives hold everything that is no longer active. Completed projects, areas of life that have changed, resources that stopped being relevant. Archives are not a bin. Nothing is deleted; it is just out of the way. The archive is what makes the other three folders trustworthy: you can file aggressively, because nothing is ever truly lost, and you can look at your projects folder and believe that everything in it is genuinely live.

The filing test, in one sentence, is this: which active project does this move forward? If the answer is a live project, file it under that project. If the answer is an ongoing responsibility, file it under the area. If the answer is "maybe one day", it is a resource. If the answer is "nothing any more", archive it.

Step 2: Set it up in 30 minutes

You do not need a new app. Forte's system is deliberately tool-agnostic: it works in Notion, Obsidian, Evernote, Apple Notes, or a plain folder on your desktop. The structure is the same everywhere, and that is the point. Pick the tool you already open every day, and create four top-level folders: Projects, Areas, Resources, Archives.

First, list your active projects — three to five, no more. If you have twelve "active" projects, you have twelve open loops and no priorities; pick the five that genuinely have deadlines and move the rest to Resources or Archives. Each project gets its own folder inside Projects, named for its outcome: "Launch pricing page", not "Website stuff".

Second, list your areas — four to six ongoing responsibilities. Health, Finances, Business, Family, Career. One folder each, inside Areas.

Third, list three to five resource topics you actually collect material on: AI tools, copywriting, investing, cooking. One folder each, inside Resources. Leave Archives empty for now; completed projects will fill it later.

Then do a rough sort of what you already have. Do not organise perfectly — move your existing notes, files and bookmarks into the nearest folder in one pass, and accept that the sort will be imperfect. The system's value does not come from a perfect first filing. It comes from the fact that from today onwards, every new thing you save has exactly one obvious home, and you can find it by asking what it is for instead of what it is about. Thirty minutes, four folders, and the junk drawer has an address system.

Step 3: CODE — the workflow that feeds PARA

PARA is where things live. CODE is how things move. It is the four-step workflow that information follows from something you noticed to something you made, and it is the reason PARA does not become another graveyard of well-filed notes.

Capture means saving only what resonates. Not everything you see — only the notes, highlights, ideas and images that strike you as surprising, useful, personal or inspiring. The test is a feeling, not a rule: if it makes you stop scrolling, save it. Capture is cheap and fast, and it should be: the longer capturing takes, the less you will do it.

Organise is the PARA step you have just set up. File by actionability, by which project it serves, not by topic. This is the step most systems skip, which is why their capture piles up into a second junk drawer.

Distill means extracting the essence, so that future-you can grasp a note's value in seconds instead of re-reading it. Forte's technique for this is Progressive Summarization, covered in the next step.

Express means turning what you stored into finished work: a post, a proposal, a product, a plan. This is the step that justifies the other three. Forte's measure of a second brain is not how much goes in; it is what comes out. If you are not producing more finished work a month after setting the system up, the setup is too complicated, and the fix is to simplify it until expressing is easy again.

Step 4: Progressive Summarization — distill in layers, just in time

Distilling is where most note-taking systems die, because people try to summarise everything the moment they save it. Forte's rule is the opposite: never distill a note until you reopen it to do actual work. Distillation happens just in time, in layers, each layer only when a real project demands it.

Layer one is the raw captured material: the article, the quote, the screenshot, saved as it is. Layer two, on the first revisit, is bolding the key passages — the sentences that actually matter. Layer three, on a later revisit when you are building something, is highlighting within the bold: the best of the best. Layer four is a short executive summary at the top of the note, written in your own words, two or three bullets that tell future-you what this note is good for. Some versions of the method add a fifth layer: remixing the summary into new creative output.

The point of the layers is that each pass costs less than the last. A note you never revisit stays at layer one, and that is fine — it cost you nothing to keep. A note you revisit five times, because five projects needed it, arrives at layer four almost by itself, compressed to the few lines that earned all that attention. The alternative — writing a perfect summary of everything you save — guarantees you will stop saving things, because the tax on each capture is too high. Summarise on demand, not on arrival.

Step 5: Intermediate Packets and the weekly review

The final piece of the system is what makes it compound. Forte calls them Intermediate Packets: small, reusable pieces of finished work — an outline, a draft paragraph, a research summary, a set of slides, a checklist — saved as building blocks instead of being buried inside one finished document. When you write a proposal, the pricing section you wrote becomes a packet. When you research competitors, the comparison table becomes a packet. The next time a project needs a pricing section or a competitor table, you start from the packet instead of from zero. Every project benefits from everything you have ever made, because the work is stored in reusable pieces, not in single-use documents.

None of this maintains itself, and that is what the weekly review is for. Once a week, open your notes and ask of each live item: which project that I am actively working on does this serve? If the answer is a live project, keep it there. If the answer is "maybe one day", move it to Resources. If a project is finished, drag its whole folder into Archives. Anything that has sat untouched for a month gets archived without a second look. The review takes twenty minutes, and it is the only maintenance the system needs — but it is the whole system, in a sense. Without it, Projects fills up with finished work, Resources fills up with guilt, and you are back to the junk drawer with better labels.

Does it actually work?

The honest answer is that PARA has never been tested in a controlled study. What it has is something rarer for a productivity method: a decade of public use, taught live, with the teacher's own numbers on the table. Forte taught the first live cohort of Building a Second Brain in January 2017 to 25 students. By 2022 the biggest cohort had 1,000 students paying a base price of around $1,500 — up to $1.5 million of revenue for a single five-week course, by a calculation published by Creator Science. The book, published in June 2022, sold 250,000 copies within two years. Forte has taught the method to employees at Google, Toyota and the World Bank, and his work has been featured in the New York Times, The Atlantic and the Harvard Business Review. Tens of thousands of people have paid to learn a filing system with four folders.

There are two caveats worth stating plainly. First, the method's real test is whether you are still using it in week four. Forte's own account of the book project shows he is honest about what his systems do and do not deliver: the book cost $1.13 million to make and promote and was still about $146,000 in the red two years after publication, by design — a loss leader that bought an audience. A method that survives is one whose maintenance cost stays below the value it returns, and the weekly review is where that bargain is either kept or broken. Second, the system only works if you express. If a month passes and you have beautiful folders but no more finished work than before, the system is a hobby, not a tool — simplify the setup until producing is easy again.

The evidence, in the end, is not a study. It is that a man who could not trust his own memory built a system out of four folders, taught it to tens of thousands of strangers, and watched the ones who kept the weekly review keep the system for years. The folders are not the achievement. The review is.

Lessons

The method compresses into three mechanisms a solo founder can reuse, whatever tool they use:

1. File by the next action, never by the topic: Topic folders answer a question nobody asks while working. The executable version is the filing test, asked every time you save something: which active project does this move forward? If you can name the project, file it there. If you cannot, it is a resource or an archive item, and admitting that is the system working, not failing. The guardrail is a count: if your Projects folder holds more than five active projects, you do not have five priorities, you have no priorities — move the rest to Resources until one of the five finishes. A note's home should tell you what to do with it, and if it does not, it is in the wrong folder.

2. Distill only on demand, in layers, never on arrival: Summarising everything you save is a tax that kills capturing. The executable version is Forte's layer rule with a hard timing rule attached: when you save something, save it raw and move on. The first time you reopen it for a real project, bold the key passages. The second time, highlight the best of the bold. The third time, write two or three bullets at the top in your own words. A note that reaches layer four has earned its compression by being used three times; a note that never leaves layer one cost you nothing. If you find yourself writing summaries for notes no project has asked for, stop — that is organising as procrastination, and the cure is to go and express something instead.

3. Run a twenty-minute weekly review, and let the archive do the forgetting: A filing system without a review rots, because finished work stays visible and live work drowns in it. The executable version is a fixed weekly slot with three moves only: anything finished moves to Archives in one drag; anything untouched for a month moves to Archives without debate; anything that serves no live project moves to Resources. The archive is what makes the whole thing safe: nothing is deleted, so the review can be ruthless. The review is also where Intermediate Packets get harvested — when a project ends, pull out the reusable pieces (the outline, the table, the checklist) before archiving the rest. Four folders, one review, and the system maintains itself.

Closing

The PARA method will not make you smarter, and it will not read the articles for you. What it does is smaller and more useful: it gives every idea you save exactly one address, decided by what you will do with it, and it gives you a weekly habit that keeps that address honest. Most knowledge systems fail not because the folders are wrong but because nobody ever empties them. Four folders, a filing question, a layer rule, and twenty minutes a week — that is the whole method, and the whole method is the maintenance.

So the question is not which note-taking app to buy. It is whether you can name your three to five active projects right now, without looking. If you can, the folders are already half built. If you cannot, no app will save you — but four folders and thirty minutes might.