Building a Second Brain: Tiago Forte's PARA Method Explained

Building a Second Brain (BASB) is Tiago Forte's personal knowledge management system, built on the CODE framework (Capture, Organise, Distil, Express) and the PARA organisational method (Projects, Areas, Resources, Archives). The core premise — shared with David Allen's GTD — is that the brain is for generating ideas, not storing them. A well-designed external system handles storage and retrieval; the brain handles thinking.

You probably have great ideas fairly regularly. The problem is locating them when they would be useful. They live in four different apps, two notebooks, a voice memo from six months ago, a bookmarked article you haven't read, and an email folder called "important" that contains three hundred items. When you need the idea that was relevant to this project, you have a vague memory it exists somewhere and no reliable way to find it. So you start from scratch, again.

Tiago Forte spent several years building a course and then a 2022 book around the solution to this specific problem. Building a Second Brain (BASB) — a Wall Street Journal bestseller, translated into more than 25 languages and read by over 500,000 people — is a personal knowledge management system adopted inside organisations including Genentech, Toyota, and the Inter-American Development Bank. Its premise is the same one David Allen identified for task management: the brain is poorly designed as a storage system, and trying to use it as one incurs costs that a well-designed external system can eliminate. Allen's GTD externalises task commitments. Forte's system externalises knowledge and information. They address different parts of the same underlying problem.

What is Building a Second Brain?

Building a Second Brain is a personal knowledge management (PKM) methodology for saving and systematically reminding yourself of the ideas, insights, and connections you've accumulated through experience and learning. The core premise: your biological brain is designed for generating ideas, not for storing and retrieving them on demand. Working memory holds roughly four chunks of information at once — a finding from George Miller's foundational cognitive psychology research — and long-term memory retrieval is associative and unreliable rather than systematic.

A second brain is an external, centralised, digital repository — typically a note-taking app — that captures, organises, distils, and expresses your knowledge so your biological brain doesn't have to hold it. The result is that you spend less time looking for things and more time doing the best, most creative work you're capable of.

The system has two interlocking frameworks: the CODE method, which describes the information lifecycle, and the PARA method, which provides the organisational structure. Understanding both is the prerequisite for implementing either effectively.

The CODE framework: the information lifecycle

Capture means collecting the ideas, insights, quotes, references, and information that resonate as potentially useful — not trying to read and remember everything. The selection criterion Forte suggests is resonance: does this idea strike you as interesting, useful, or relevant to something you're working on or thinking about? If yes, capture it. The capture habit is the foundation of the system; without it, nothing else functions.

Organise means placing captured material into a structure that makes it findable when relevant. This is where the PARA method lives. Organise by actionability — what is this useful for right now? — not by topic or source.

Distil means processing captured notes to their most useful and concentrated form, so that when you return to a note in six months you encounter the substance rather than needing to re-read the entire source. Forte's progressive summarisation technique is the specific practice for this step. Forte also draws on physicist Richard Feynman's practice of maintaining a list of 12 open questions — the most important problems he was working on — and testing everything he learned against them. The second brain is where the material that feeds those questions accumulates.

Express means using the material in the system to produce finished work: articles, presentations, analyses, decisions, plans. The system has no value if it only accumulates information. Its value is in what the information enables. A second brain that only captures and never expresses is a library nobody visits.

The PARA method: organisational structure

PARA divides all information into four categories based on actionability rather than topic. This is the design choice that distinguishes it from conventional filing systems organised by subject or source. The question is not "what is this about?" but "how actionable is this right now?"

Projects are active, time-bound outcomes with a clear definition of done. A project has a goal that will eventually be achieved and will then be complete. Writing a report, launching a feature, preparing a presentation: each has a defined endpoint. Material relevant to active projects goes into the Projects folder because it has the highest near-term actionability.

Areas are ongoing responsibilities with no defined endpoint. Health, finances, professional development, a particular client relationship, a management responsibility: these continue indefinitely and require ongoing attention without ever being "done." Material relevant to ongoing areas of responsibility goes into the Areas folder.

Resources are topics of interest that may be useful in future but are not tied to any current project or ongoing responsibility. An interest in behavioural economics, a collection of design references, notes from books on a topic you find interesting: these belong in Resources. They are not actionable today but may become relevant when a future project makes them so.

Archives contain inactive items from any of the other three categories. Completed projects move to Archives. Areas that are no longer active move to Archives. Resources that are no longer relevant move to Archives. The archive is not deletion — it is accessible by search and can be revived when relevant.

What makes PARA different from conventional filing

Conventional filing systems organise by topic: all marketing material in one folder, all research in another, all client material in a third. The problem is that the same piece of information is often relevant to multiple topics and its relevance shifts over time as projects and priorities change. Organising by topic forces a single permanent categorisation on material whose relevance is dynamic.

PARA organises by actionability, which reflects how material is actually used: primarily in the context of current projects, secondarily in the context of ongoing responsibilities, with resources available as background and archives accessible when historical context is needed. The same note can be moved between categories as its actionability changes, without the hierarchical permanence that topic-based filing imposes.

Progressive summarisation

Forte's technique for the distil step involves layered highlighting that builds progressively each time a note is reviewed. The four layers:

• Layer 1 (soil): On first capture, save the full source or the most relevant passage

• Layer 2 (oil): On first review, bold the most interesting sentences and passages

• Layer 3 (gold): On second review, highlight the most important bolded passages

• Layer 4 (gems): On subsequent engagement, write a short summary in your own words at the top of the note

Each layer represents increasing confidence in what is most valuable, developed across multiple encounters rather than in a single reading. This solves a specific problem: the note taken quickly in the flow of reading is often a faithful capture of the source but an unreliable guide to its most useful elements. Distillation across multiple passes produces a note that is genuinely useful as a resource rather than just a faithful record.

Important caveat: progressive summarisation should only be applied to notes you return to more than once. Over-distilling everything as you capture it adds process overhead without value. The technique is most useful on your most important and frequently referenced material.

Intermediate Packets

One of the more practical concepts from BASB is Intermediate Packets (IPs) — small, self-contained, reusable units of work that serve as building blocks for larger projects. An IP might be a summary of a research paper, a set of slide templates, a list of past client objections, or a well-crafted paragraph that can be adapted for future use.

The concept addresses a specific failure mode in knowledge work: starting each project from scratch when previous work could be reused. By thinking in IPs, you build a library of finished units of work that can be assembled and adapted rather than rebuilt. A 200-word explanation of a concept you've written before is an IP. So is a set of interview questions, a financial model structure, or a curated reading list on a topic. The second brain is the home for all of these.

Best apps for building a second brain

The system is tool-agnostic — Forte himself uses multiple apps. The most commonly used options:

• Notion — the most popular choice for BASB; highly flexible with databases, templates, and PARA folders built in. Notion's official PARA template is available on Forte's website.

• Obsidian — preferred by users who want local file storage, bidirectional linking, and a graph view of note connections. Strong for building a Zettelkasten-style knowledge graph alongside PARA.

• Evernote — the original tool Forte built the system in; cross-platform with strong capture tools and web clipper.

• Apple Notes — sufficient for a simple PARA implementation at no cost; limited on features like bidirectional links.

• Readwise Reader — the best capture layer for highlights from articles, books, and PDFs; integrates with Notion and Obsidian to automatically populate your second brain with reading highlights.

The most important factor is not which app you choose but whether you use it consistently. A simple PARA structure in Apple Notes that you maintain beats an elaborate Notion setup that you abandon after three weeks.

Building a Second Brain vs GTD

Forte trained under David Allen and the two systems are designed to be complementary, not competing. GTD handles open commitments: tasks, projects as action sequences, and the trusted system that ensures nothing is forgotten. BASB handles knowledge: the information captured and organised to support the thinking and output that GTD's project actions require. GTD answers the question of what to do next. BASB answers the question of what you know that is relevant to it.

The integration point is the project level: a project in GTD, which is any outcome requiring more than one action, corresponds directly to a project in PARA, which is any active time-bound outcome. The project's next actions live in the GTD system. The project's knowledge, research, references, and notes live in the PARA system. When working on a project, both systems are consulted together: what is the next action, and what do I know that is relevant to it?

Building a Second Brain vs Zettelkasten

The Zettelkasten (slip-box) method, developed by sociologist Niklas Luhmann, organises notes as an interconnected network of atomic ideas linked by relationships rather than by folder hierarchy. Where PARA organises by actionability, Zettelkasten organises by connection — the goal is a network of linked ideas that surfaces unexpected relationships.

BASB is more immediately practical for knowledge workers with active projects and ongoing responsibilities. Zettelkasten is better suited for researchers and writers whose primary output is long-form original thinking developed over years. Many practitioners implement PARA as the file structure and use Zettelkasten-style linking within it, particularly in Obsidian where bidirectional links make this straightforward.

How to start building your second brain: a minimum viable implementation

The most common failure mode is over-engineering the system before using it — spending more time designing folders and tags than capturing and using material. Start with the minimum viable version:

1. Choose one note-taking app. Notion, Obsidian, or Evernote are the most common. Don't switch apps for the first three months.

2. Create four folders: Projects, Areas, Resources, Archive. That is your entire initial structure. Do not create subfolders yet.

3. Do a capture sweep. Spend thirty minutes moving existing notes, bookmarks, and documents into the relevant PARA folder. Don't organise deeply — just get things into the right top-level category.

4. Build the capture habit. For the next two weeks, capture anything that resonates to your inbox. Every article, idea, meeting note, and insight goes into a single inbox first, then gets processed into PARA during a weekly review.

5. Start progressive summarisation only on notes you return to. Don't bold and highlight everything as you capture. Only apply distillation to notes you've already returned to once.

6. Express something using your notes within the first week. A short summary, a reply to an email that draws on captured research, a presentation slide. The system only proves its value when you use it to produce something.

Progressive summarisation, Intermediate Packets, and the full CODE workflow can all be added incrementally as the basic system is running and its value is clear.

Where Aftertone fits in

The integration point between a second brain and a task and calendar system is the Projects layer. When a project in PARA has associated next actions, those actions need to be scheduled and executed. Aftertone's task scheduling places PARA project work into the calendar with specific times, converting knowledge-management projects into implementation intentions — specific scheduled commitments rather than vague intentions to "work on the project when there's time." The knowledge lives in the second brain. The execution lives in the calendar. The second brain is not a filing system. It is the infrastructure that turns scattered thinking into finished work — and finished work requires both a place for the ideas and a schedule for the actions.

Frequently asked questions

What is Building a Second Brain?

Building a Second Brain is a personal knowledge management (PKM) system developed by Tiago Forte, published as a book in 2022. It is built on the premise that the brain is better suited to generating ideas than to storing and retrieving them reliably. The system provides a structure — CODE (Capture, Organise, Distil, Express) and PARA (Projects, Areas, Resources, Archives) — for capturing, organising, distilling, and expressing information so that knowledge accumulated over time is findable and usable rather than scattered across multiple tools and forgotten.

What are the 4 PARA categories?

Projects: active, time-bound outcomes with a clear definition of done, such as a report being written or a feature being launched. Areas: ongoing responsibilities with no defined endpoint, such as health, finances, or a particular client relationship. Resources: topics of interest that may be useful in future but are not tied to any current project. Archives: inactive items from any other category, preserved and searchable but removed from active view.

What is the CODE framework in Building a Second Brain?

CODE stands for Capture (collecting information worth keeping), Organise (placing it into the PARA structure by actionability), Distil (processing notes to their most useful form through progressive summarisation), and Express (using the knowledge to produce finished work). The four steps describe both how to build the second brain and how to work with it on an ongoing basis.

What is the difference between Building a Second Brain and GTD?

GTD (Getting Things Done) is a task and commitment management system — it ensures every open commitment is held in a trusted external system and processed into concrete next actions. Building a Second Brain is a knowledge management system — it ensures captured information is organised by actionability and findable when relevant to a project. GTD tells you what to do next. BASB tells you what you know that is relevant to it. Forte trained under David Allen and the two systems are designed to be used together, with GTD at the task layer and PARA at the knowledge layer.

What is progressive summarisation?

Progressive summarisation is Tiago Forte's technique for distilling notes across multiple encounters. On first capture, you save the relevant passage. On first review, you bold the most interesting sentences. On second review, you highlight the most important bolded text. On subsequent engagement, you write a short summary at the top in your own words. Each pass increases confidence in what is most valuable and produces a note that future-you can scan quickly rather than re-read in full. Apply it only to notes you've already returned to, not to everything as you capture it.

What is the best app for building a second brain?

Notion is the most popular choice — highly flexible with a well-established PARA template community. Obsidian is preferred by users who want local file storage and bidirectional links between notes. Evernote is the original tool Forte built the system in, with strong cross-platform capture. The most important factor is not which app you choose but whether you use it consistently. A simple PARA structure you maintain beats an elaborate system you abandon.

Is Building a Second Brain worth it?

Yes, for knowledge workers whose primary bottleneck is information retrieval and reuse — researchers, writers, consultants, and anyone who produces creative output from accumulated knowledge. The system pays for itself when you find yourself reusing material across projects rather than starting from scratch each time, or when you stop losing ideas between the moment they occur and the moment they would be useful. The realistic failure mode is over-engineering: spending more time building the system than using it. The minimum viable version — one app, four PARA folders, capture anything useful, process during weekly review — works better than an elaborate system that requires constant maintenance. Start minimum; add complexity only when you hit specific friction.

What is the difference between PARA and Zettelkasten?

PARA organises by actionability: material is placed based on what it's useful for right now (Projects, Areas, Resources, Archives). Zettelkasten organises by connection: notes are atomic, linked to other notes by concept, and the value is in the emergent network of ideas rather than hierarchical folders. PARA is better for project-oriented knowledge workers who need to find material relevant to active work. Zettelkasten is better for researchers and writers who want ideas to compound and connect over years. They're not mutually exclusive — many practitioners use PARA for folder structure and Zettelkasten-style linking within their notes. Forte's system accommodates both approaches.

What are Intermediate Packets in Building a Second Brain?

Intermediate Packets (IPs) are small, self-contained, reusable units of work — a research summary, a set of slide templates, a curated list, a well-crafted explanation of a concept. The idea is that previous work is rarely reused in knowledge work because it is not stored in a retrievable form. By thinking in IPs and storing them in the second brain, future projects can be assembled from existing units rather than built from scratch each time.