Second Brain: What It Is and How to Build One
November 11, 2026 · 10 min read
Second Brain: What It Is and How to Build One
A second brain is a personal system of digital notes that remembers what you read, learn and plan, so your head is free to think. Tiago Forte's method builds one in four steps (Capture, Organize, Distill, Express) and sorts notes into four PARA folders. You can start one today in plain Markdown files.
What Is a Second Brain?
Forte describes it as "an external, centralized, digital repository for the things you learn" in his introductory guide to the method. In practice, it's where book notes, meeting notes, saved articles and half-formed ideas live, sorted so you can find them when a project needs them.
The problem it solves is simple. Your memory is good at having ideas and bad at holding them. A second brain does the holding, so a quote you saved last spring is still there when you sit down to write the report it belongs in.
Tiago Forte is the name most tied to the idea. He teaches it in a course and a 2022 book, both called Building a Second Brain. His free articles lay out the core: a four-step loop called CODE plus a folder scheme called PARA. Neither depends on a particular app, which is why this guide shows the method in plain files.
The CODE Method: Capture, Organize, Distill, Express
CODE is the four-step process at the heart of Tiago Forte's Second Brain method. Each step has one job, and Forte suggests recycling finished work back into your notes, which turns the steps into a loop.
The arrow from Express back to Capture matters. Every post, talk or report you finish produces feedback and fresh material, and that goes back into the system.
- Capture. Keep only what resonates: a passage that surprised you, a how-to you'll need again, a decision from a meeting. Forte's heading for this step is "Capture only the most important information", so resist saving whole articles.
- Organize. File each note by where you'll use it next, not by subject. PARA, covered in the next section, handles this.
- Distill. Each time you revisit a note, shrink it a little so the key point stands out. Progressive Summarization, further down, is the technique.
- Express. Turn notes into finished work. Forte calls the reusable pieces Intermediate Packets: meeting notes, research findings, a slide deck of analysis, action items from a call. Finish one per work session and save it, so your next project starts with material in hand.
How Do You Organize a Second Brain With PARA?
PARA sorts everything into four top-level categories, defined in Forte's article on the PARA method:
- Projects: short-term efforts with a goal, such as relaunching a website or giving a talk.
- Areas: parts of your life or work that need ongoing attention, like health, finances or a team you manage.
- Resources: topics you're interested in and learning about, such as Git or cooking.
- Archives: anything from the other three that's no longer active but worth keeping.
The rule that makes it work is organizing by actionability. Ask which project or area a note will help next, and file it there. A note on commit messages sits in Resources until a project needs it, and then it moves into that project's folder.
Here's a small system on disk:
second-brain/
├── 0-Inbox/
├── 1-Projects/
│ ├── website-relaunch/
│ └── conference-talk/
├── 2-Areas/
│ ├── health/
│ └── finances/
├── 3-Resources/
│ ├── git/
│ └── note-taking/
└── 4-Archives/
└── 2025-kitchen-renovation/
Number prefixes keep the folders in PARA order instead of alphabetical order. The Inbox isn't one of the four categories. It's a holding spot for quick captures that you empty once a week. When a project ends, drag its whole folder into 4-Archives.
Forte says PARA works in your computer's file system, a cloud drive or a notes app, so this tree carries over to whatever tool you pick later. To sketch your own layout before creating folders, paste an indented list into the directory tree generator.
How Progressive Summarization Distills a Note
Progressive Summarization is Forte's technique for the Distill step, described in his 2017 article on Progressive Summarization. You compress a note in layers, and only as far as that note deserves:
- Layer 0 is the original source.
- Layer 1 is the excerpt you bring into your notes.
- Layer 2 bolds the best parts of those excerpts.
- Layer 3 highlights the best of the bold.
- Layer 4 is a short summary in your own words.
Here's a captured note after two passes:
# Writing commit messages (git-commit docs)
Source: https://git-scm.com/docs/git-commit
PARA: 3-Resources/git
> **Summary:** One short subject line, a blank line, then the detail.
> Write the subject so it still makes sense on its own in a log.
## Excerpts
- Begin with **a single short line, no more than 50 characters**, that sums up the change.
- Follow it with a blank line and a more thorough description.
- Git treats the text up to the first blank line as the commit title.
The bullet excerpts are Layer 1, the bold phrase is Layer 2, and the blockquote at the top is Layer 4. When you come back in six months, you read the summary first and the bold second. Most notes never need more than bold, and that's fine.
Layer 3 is the awkward one in Markdown. Obsidian marks highlights with ==text== (see the Obsidian formatting syntax), but that isn't part of CommonMark or GitHub Flavored Markdown. Our editor's preview doesn't render it, so the demo below sticks to bold, a blockquote and a task list. Edit the note, then export it as a PDF to see a distilled note as a finished page.
Express: Turning Notes Into Finished Work
Output is the whole point. When a project starts, open its folder, pull in the relevant Resources notes and read their summaries first. Copy the best bold lines into a draft, and you're writing from material instead of a blank page.
Markdown keeps the last step short. Paste the draft into the Markdown editor, check the preview on the right, and use the Download/Export menu. Downloading the .md file is unlimited, while PDF, HTML and DOCX exports count toward a free pool of 3 a day. Free toolbar exports also top out at 5,000 characters, and Pro removes both limits.
How Do You Build a Second Brain in One Afternoon?
You don't need a course or a new app to get started. A folder, a text editor and a couple of hours are enough to get the skeleton working:
- Create the four PARA folders plus an Inbox, numbered as in the tree above.
- List your active projects and give each one a folder inside 1-Projects. If something has no end goal, it's an area, not a project.
- Add a folder for each ongoing responsibility in 2-Areas.
- Leave old notes where they are. Move one into PARA only when a project needs it, because reorganizing years of files first is the fastest way to quit.
- Pick one capture habit, such as typing three lines after every meeting, and send everything to the Inbox.
- Block 20 minutes a week to empty the Inbox, file each note and bold the lines that still matter.
We prefer starting this way, in plain Markdown files and a folder tree, before committing to any app. Markdown files open in every text editor, outlive the apps that created them, and many note apps can open or import them. For a consistent shape for reading or meeting notes, start from one of these Markdown templates.
What Kind of App Suits a Second Brain?
Ranked lists of apps are easy to find, but the method doesn't depend on any one tool. Forte's own guide names several notes apps as options. Look for these traits instead of a brand:
- Notes stay in an open format, ideally Markdown files you can move.
- Folders, or something equivalent, give PARA a home.
- Capture takes seconds, including from your phone.
- Search works across every note.
- Sync is there if you work across devices.
If you're weighing specific second brain apps, our comparison of Markdown note-taking apps covers eight of them. Obsidian users can read our review of editing in Obsidian before setting up a vault. Our Obsidian second brain tutorial then builds the vault's folders, templates and weekly review.
One limitation to be clear about: our editor isn't a second-brain app. Signing in lets you save files to My Files, but that's a flat list with no folders, tags, search or links between notes. It fits the Express step instead, where you draft the finished piece and export it.
Why Do Second Brains Fail?
Most systems stall for one of four reasons, and each maps back to a CODE step:
- Hoarding. You clip whole articles and everything you read. Capture fixes it: save only the parts that resonate.
- Endless reorganizing. Weekends disappear into tags and folder names. Organize by actionability, then stop, since PARA has only four folders on purpose.
- Notes nobody reads. Long excerpts with no bold and no summary are as hard to use as the original. Distill a note when you touch it, not all at once.
- Never shipping. The collection grows, but no post, report or talk comes out. Express is the cure: finish one Intermediate Packet each session.
App hopping deserves a mention too. Switching tools every few months resets the habit, and plain files make the move cheaper when it does happen. AI-assisted setups, where a language model reads your notes, are a separate topic with their own trade-offs.
A second brain doesn't have to start with an app decision. Make four folders, file one project's notes, bold the lines that matter and add a summary when you revisit a note. Once that loop runs for a few weeks, you'll know which features you actually need. Until then, write and export your drafts in the editor, which is free and needs no account.