Building a Second Brain is a 2022 book by Tiago Forte about keeping what you learn in a digital system outside your head. Its method is CODE: capture what resonates, organize it with PARA by where you will use it, distill it with progressive summarization, and express it by shipping work built from saved pieces.
Free: the Second Brain Starter Kit
Seven plain markdown files to set one up this week, in Obsidian or any editor, with Claude or any AI.
What is Building a Second Brain about?
Building a Second Brain, published in 2022, argues that your memory is a poor place to store ideas. Tiago Forte proposes a digital notes system, the second brain, that holds what you learn so you can find and reuse it. The book is about habits, not apps: what to save, where to put it and how to use it.
The book grew out of a course Forte had taught since 2017, and it reads like one: a short case for the idea, then the method step by step, then the habits that keep it running. If you only want the definition and the method in brief, start with what a second brain is.
The book's central claim is practical. Most knowledge workers already consume more than they can remember. The question is not how to read more but how to keep the useful part where you will find it when a project needs it.
What is the CODE method in Building a Second Brain?
CODE is the book's four-step workflow. Capture saves only what resonates with you. Organize files it by actionability using PARA. Distill compresses notes to their essence with progressive summarization. Express turns saved material into finished work, which the book treats as the point of the whole system.
| Step | What the book says | Go deeper |
|---|---|---|
| Capture | Keep what resonates: inspiring, useful, personal or surprising | Second brain template |
| Organize | File by where you will use it next, with PARA | The PARA method |
| Distill | Compress notes in layers each time you revisit them | Progressive summarization |
| Express | Ship work built from saved pieces, early and often | This page, below |
The order matters less than the loop. The book's test for any note is whether it ever reaches the express step. Notes that never do are cheap to keep but should not take up your attention.
What are the key ideas beyond CODE and PARA?
Three ideas carry most of the practical value. Intermediate packets: build work from small reusable pieces like outlines and drafts. Twelve favorite problems: a short list of open questions that decides what you capture. And the Hemingway bridge: stop each session knowing the next step, so restarting costs little.
- Intermediate packets. Instead of starting big projects from a blank page, you assemble them from pieces you already made: a slide, a research summary, a list of questions from an old meeting. This is the idea most readers skip and the one with the biggest payoff.
- Twelve favorite problems. Borrowed from the physicist Richard Feynman: keep a short list of open questions you care about, and capture what speaks to them. It is the filter that stops capture from becoming hoarding.
- The archipelago of ideas. Before writing, gather the relevant notes into an outline of islands, then connect them. Writing becomes arranging rather than inventing.
- The Hemingway bridge. End each work session with a note on what comes next, so tomorrow starts with momentum instead of a search.