“Second Brain Method (PARA): A Beginner’s Guide”

What is the second brain method, exactly?

The second brain method is an external system for holding ideas, notes, and references so your head is free for thinking rather than storage. Forte’s argument is blunt: your brain is for having ideas, not for holding them. A second brain is the place where captured material waits, organized so it can be used.

The method has two layers, and beginners usually learn one and skip the other.

The workflow is CODE: Capture what resonates, Organize it where it will be useful, Distill it down to the parts worth rereading, and Express it by making something. The fourth step is the point. A note you never use is a hoarded object, not knowledge.

The structure is PARA: four top-level categories, described below. Forte published PARA on the Forte Labs blog in 2017, expanded it as the organizing layer of *Building a Second Brain* in 2022, and gave it a standalone book, *The PARA Method*, in 2023.

What the method is not matters just as much. PARA tells you where a file lives; it does not tell you what to do on Tuesday morning. Expect it to replace your task list and you will end up with beautiful folders and the same unfinished work.

> Important note: Forte’s own framing is that the system should give you more time than it takes. That is the test to apply to any customization. If your folder structure needs a monthly redesign, it is failing the test.

What are the four PARA categories?

PARA has four categories because, in Forte’s model, all digital information falls into one of them when you sort by how soon you will act on it.

The categories are ordered by actionability, and that ordering is the whole design. Projects sit at the top because you touch them this week. Areas come next because they need attention continuously but have no finish line. Resources are reference. Archive is where things go to stop distracting you without being destroyed.

Three practical rules make the structure hold:

1. Only active projects get a folder. If a project is paused indefinitely, it belongs in Archive, not in Projects. A Projects folder with 40 entries is a to-do list nobody reads.
2. Areas are standards, not tasks. “Marketing” is an area. “Publish the Q3 case study” is a project inside it. When an area has no active projects, the area is either healthy and quiet or quietly neglected.
3. One note, one home. If a note serves two projects, keep it in the project where it was created and link to it from the other. Duplicates are how systems rot.

How is PARA different from organizing by topic?

PARA organizes by actionability; almost everyone else organizes by topic. That is the entire difference, and it explains why the method feels strange for the first week.

School taught you subject folders: Math, History, Chemistry. You carried that habit into work and produced folders called Marketing, Strategy, Research, and Ideas. Those folders are enormous, they never close, and they tell you nothing about what you were doing when you saved something.

A topic folder answers “what is this about?” An actionability folder answers “what was I working on when I needed this, and will I need it again?” At 4 p.m. on a deadline day, the second question is the only one that saves you.

The cost of the wrong axis is measurable. Harvard Business Review reported a study of 20 teams and 137 users at three Fortune 500 companies: workers toggled between applications and websites roughly 1,200 times a day, and spent just under four hours a week just reorienting after those switches, about 9% of their work time. Some of that is unavoidable. A meaningful share of it is searching for something you already own.

Concretely: a file called `pricing-v4-final.xlsx` inside a folder called `Marketing` is invisible. The same file inside `Q3-pricing-page-launch` appears the moment you open the project you are actually working on. Same file, different retrieval time.

How do you set up PARA in one afternoon?

Setup is a sorting exercise, not a research project. Block two and a half hours, work at the level of titles rather than contents, and do not open files to decide where they go.

Step 1 — List active projects (25 minutes). Write every piece of work that has an end state and a date. Not “Marketing.” Instead: “Rewrite the onboarding email sequence by 15 March.” Aim for 8 to 15 items. If you have 30, you have areas mixed in.

Step 2 — Create four folders and one subfolder per project (20 minutes). Top level: `1 Projects`, `2 Areas`, `3 Resources`, `4 Archive`. Numbering is optional, but it keeps the intended order when a file browser sorts alphabetically.

Step 3 — Move what serves an active project (45 minutes). For each file or note, ask one question: which active project does this serve right now? If the answer is instant, move it. If it takes more than four seconds, skip it.

Step 4 — Group the remaining work by area (30 minutes). The leftovers are usually responsibilities rather than projects: invoices, hiring notes, performance reviews. Give each area a folder and a one-line standard, such as “Invoices: nothing older than 30 days unpaid.”

Step 5 — Park reference material in Resources (20 minutes). Articles, courses, templates, and research that no current project needs. Keep this folder shallow, because Resources grows without limit if you let it.

Step 6 — Archive the rest in one move (10 minutes). Everything inactive goes into Archive, undated, unsorted, and out of sight. You are not deleting anything, only removing noise.

Two rules protect the result. Do not create a “Misc” folder, because it becomes the largest folder within a month. And accept imperfection: a file in the wrong folder costs thirty seconds, while a filing system you abandoned costs the investment.

Worked example: 1,840 files in a consultancy Drive

A two-person consultancy audited its shared drive before starting. It held 1,840 items: client deliverables, invoices, research PDFs, screenshots, and three years of duplicates. Average time to locate a known file was 3.5 minutes, measured across 20 trial searches. The team ran about five searches a day, 210 working days a year.

• Before: 5 × 210 = 1,050 searches a year. At 3.5 minutes each, that is 3,675 minutes, or 61.3 hours.
• After the sort: 11 active projects, 6 areas, one Resources folder, and 62% of the drive in Archive. Average find time dropped to 25 seconds.
• After: 1,050 × 0.42 minutes = 441 minutes, or 7.4 hours.
• Gross saving: 61.3 − 7.4 = 53.9 hours a year.
• Maintenance cost: a 25-minute weekly review, 52 weeks, equals 21.7 hours.
• Net saving: 53.9 − 21.7 = 32.2 hours a year, roughly four working days.

That is the honest arithmetic, and it includes the part most guides omit: the review is not free, and it is not optional.

How do you tell a project from an area?

Ask whether the item can be finished. If you can imagine crossing it off permanently, it is a project. If crossing it off would mean you stopped doing your job, it is an area.

Forte’s argument for splitting them is motivational as much as organizational. An area-only list never changes, so no amount of effort produces the feeling of completion. A project list turns over, which creates a cadence of small wins. That turnover is also how you see whether the area is actually moving.

The practical consequence is that Areas need a second look during the weekly review. If “Hiring” has had no projects for five months, either you are fully staffed, or the area is being quietly avoided. Both are worth knowing.

What are the trade-offs, and where does PARA break down?

PARA is simple by design, and simplicity has costs. These are the four places it usually fails.

It assumes you can name your projects. For deadline-driven work, that is easy. For researchers, writers, and explorers whose work is continuous reading and thinking, the line between Area and Resource blurs, and everything drifts into Resources. A workable fix is to define a “project” as any inquiry with a deliverable, even a self-imposed one: “Draft the literature review by 1 May.”

It struggles with many parallel clients. An agency with 40 live engagements produces 40 project folders at the top level, which is as unusable as the topic folders you started with. Add one intermediate level, such as `Projects/Clients/Harlow/2026-rebrand`, and stop there.

It depends on the review. Left alone, PARA decays in about six weeks. Folders fill with finished projects, the inbox becomes a second Archive, and the system reverts to search. The weekly review is the load-bearing habit; everything else is decoration.

The trade-off is real: PARA buys speed and low friction by giving up richness of connection. Most people are better served by speed.

How do you keep the system running?

The weekly review is a 20 to 25 minute appointment that does five things: empty the capture inbox, move completed projects to Archive, confirm every active project has a next action, promote one note into something you actually produce, and delete ten items.

Twenty minutes a week is 17.3 hours a year. That sounds like a lot until you compare it with the 32 hours the consultancy above recovered. The review is not overhead; it is the mechanism that produces the return.

A monthly pass merges duplicate notes, confirms no area has gone silent, and archives anything in Resources you have not touched in a year. A quarterly pass prunes Resources properly. That rhythm is enough. Daily organizing is a sign the structure is wrong, not a sign of discipline.

> Practical tip: Keep one note called `Weekly review` with the five questions as a checklist. Reusing the same note each week means the review takes four minutes to start instead of fifteen.

What does a second brain look like for a team?

For a team, PARA works as a top-level skeleton and fails as a personal system imposed on everyone. The difference is ownership: a shared structure with no named owner decays faster than a personal one, because everyone assumes someone else is tidying it.

A workable team version: Projects are engagements, launches, or migrations, each with a single owner and an end date. Areas are functions the team maintains: operations, finance, people, quality. Resources hold templates, brand assets, vendor lists, and research that spans projects. Archive holds closed engagements, retained for reference and audit.

Two habits matter more in teams than in personal use. Meeting notes belong to the project they served, linked from the project home rather than filed by date. And every archived project should carry a short lessons note, because the archive is the only place where past work pays for itself.

Where does Doitify fit?

The retrieval problem and the project problem are the same problem. A decision note that lives in a document nobody opens is lost, even if it was written carefully.

Doitify keeps project documents, meeting notes, risks, tasks, and progress reports in the same workspace as the project they belong to, so finding the note is a byproduct of opening the work. Projects move through stages, checklists and sub-tasks capture the detail, and reports show what changed without a separate filing exercise.

One clarification, since this is our product: Doitify is built for project, team, and goal management, not as a general-purpose note-taking app. For a purely personal archive of reading notes, a dedicated notes tool is lighter. The two can coexist, with PARA as the folder logic in both.

What are the most common mistakes?

• Creating folders before listing projects. The folder structure should be a consequence of the project list, not a guess at it.
• Filing by topic out of habit. If a folder is named after a department, it will never close and never help.
• Keeping a Misc folder. It becomes the largest folder and the reason the system fails.
• Capturing without expressing. Saving is not learning. If nothing is produced from the archive, the archive is a landfill with labels.
• Over-engineering the hierarchy. Five levels of nesting costs more attention than it returns.
• Skipping the review for three weeks. This is how every abandoned system starts.
• Migrating tools instead of sorting. A new app with the same mess is the same mess.

Conclusion

The second brain method is not a note-taking trick. It is a decision about which axis your information is sorted on, and the answer it proposes is actionability: projects for what finishes, areas for what persists, resources for what might help, archive for what is done.

Start smaller than feels satisfying. List your active projects, create four folders, move only what serves those projects, and put the rest in Archive without apology. Then protect the 25-minute weekly review, because that appointment, not the folder names, is what turns a tidy afternoon into a system you still use next year.

If this post on second brain method was helpful, you might also enjoy How to Reduce Meeting Overload and Time Tracking Project Management Tool.