How to Build a Second Brain — and Why Most Attempts Fail

Tiago Forte's Building a Second Brain (2022) sold hundreds of thousands of copies and spawned a cottage industry of courses, templates, and YouTube walkthroughs. The promise was appealing: your life contains too much information for one biological brain to retain, but a structured digital system — a "second brain" — can capture, organise, distill and express everything you care about. Twelve months later, most readers have given up on the system they built. The second brain sits half-populated, unvisited, and vaguely guilt-inducing. The underlying book wasn't wrong, but the way it's typically implemented produces this exact failure mode, and it's worth understanding why.

What the Book Actually Argues

Strip Forte's framework to the bones and it's four moves, captured under the acronym CODE: Capture, Organise, Distill, Express. Capture the ideas, texts, and stimuli worth keeping. Organise them in a way that supports future retrieval. Distill over time — extracting the core insight from each captured item. Express — put the accumulated insights to work in actual output.

Stated at this level, the framework is hard to argue with. The individual practices are all sensible. The organising schema Forte proposes (PARA — Projects, Areas, Resources, Archive) is a reasonable default. The book's real contribution is less the specific system and more the insight that most knowledge workers need deliberate infrastructure to offload cognitive load that would otherwise overwhelm them.

The failure, when it happens, is not in the framework. It's in the implementation.

Why Most Second Brains Fail

Three failure modes, in decreasing order of commonness.

1. Capture-heavy, express-light

The single biggest failure. People spend their energy on the capture step — bookmarking articles, saving highlights, forwarding emails to their note system, clipping web pages — and almost no energy on the express step. After six months they have thousands of captured items and have produced nothing from them.

The ratio matters enormously. If your time is 90% capture and 10% express, you've built a read-it-later pile, not a second brain. The system will decay and you'll eventually abandon it. If your time is 40% capture and 60% express — pulling material out, synthesising it, using it in output — the system compounds and earns its keep.

Forte's book does talk about this ratio, but in practice the capture step is easy and the express step is hard. People optimise toward the easy step, because it feels productive. It isn't, at least not in the sense they think.

2. Over-elaborate organisation

The second failure. People build an elaborate PARA structure with sub-folders, tags, colour codes, multi-level hierarchies. The organising work consumes a disproportionate share of their attention. Then, when they want to retrieve something, the organisation gets in their way — they can't remember which area it's in, or whether something is a resource or a reference.

The truth of organisation: for a personal note system, search beats structure. You're the only user; you know what you wrote; search inside Obsidian or Notion will find almost anything in under ten seconds. Elaborate folder structures are overhead that rarely earns back what they cost to maintain.

The working version: one folder for current projects, one for archive, and aggressive tagging only where a tag would genuinely help retrieval. That's enough. Most of the elaboration is theatre.

3. Captured material you'll never use

The third failure. You're capturing everything interesting — articles, podcast highlights, screenshots, tweets. Most of it, honestly, is not worth capturing. It was interesting in the moment. It's not going to feed into any work you'll do.

The filter, which Forte undersells: capture only what connects to something you're actually working on or thinking about. If you can't, within a day of capture, articulate why this specific piece might matter to a specific project or line of inquiry, it doesn't belong in your system. Let it go.

The discipline is uncomfortable. Our instinct is to save things that might be useful, because the cost of saving feels trivial. It isn't trivial — the compound cost is an overfull system where signal drowns in noise. Aggressive pre-filtering at capture time is the single biggest lever for making the second brain actually work over years.

The Version That Actually Compounds

A working second brain, at the end of year five, should have a specific set of properties. Not a lot of items — fewer than you'd think. A high proportion of items that have been revisited, distilled, and used in output. A clear connection between the system and what you're actually producing in your work.

The build-up, practically:

Year 1: Minimal Viable System

• Pick a tool (Obsidian is fine). Create one folder for current projects, one for reference, one for archive.
• Capture only what clearly relates to a current project or an active thinking thread. Aim for modest volume — 5-15 items a week, not 50.
• Each captured item gets a one-sentence note explaining why it matters to you. If you can't write the sentence, don't capture.
• Weekly review: 20 minutes. Look at what you captured. Distill anything worth keeping into a shorter, cleaner note. Archive or delete the rest.

Year 2-3: Output Habit

• Start producing output from the system. Not big output — small output. A weekly email to your team summarising something. A monthly essay for your own blog. A quarterly internal memo.
• The output is the forcing function. When you sit down to write, you pull from the system. If you can't pull anything useful, the system isn't working — diagnose what's missing.
• The distillation habit takes over from the capture habit. You're synthesising, not just collecting.

Year 5+: The Compound

• The system contains maybe 2,000-4,000 items, most of which are your own distilled notes rather than clipped content.
• Retrieval feels fast. You can pull relevant material for any active project in minutes, because you've distilled enough of it that the key ideas are already in shape.
• The system starts to show patterns. Connections you didn't notice, returning ideas, themes that recur across projects. This is where the second brain genuinely produces thinking you couldn't produce without it.

The Honest Limit

The second brain concept is easy to oversell. It won't make you smarter. It won't produce insights by itself. It doesn't replace the hard work of actually reading, thinking, and writing. What it does, reliably, is reduce the cognitive load of carrying around half-formed ideas in working memory, and make it easier to revisit work you've done before instead of starting from scratch each time.

For knowledge workers whose output is primarily text — writing, analysis, strategy, research — this leverage is real and compounds meaningfully over a decade. For workers whose output is primarily action — operations, sales, management of real-time situations — the leverage is smaller. You can still benefit from a capture system, but the investment in a full second brain often isn't worth the return.

The specific tell that your version isn't working: ask yourself, honestly, whether you'd miss it if it disappeared tomorrow. If the answer is "no, I'd be fine," you've been building theatre. A working second brain is something you'd rebuild inside a week because losing it would cost you real output. If yours doesn't feel that way, you're doing the capture step without the express step, and you should either fix that or stop spending time on the system.

What Forte Doesn't Emphasise Enough

The part of Forte's framework that gets undersold, even in the book itself: Express is the whole point. Capture, Organise, and Distill exist to serve Express. If you're not expressing — not producing output that pulls from the system — the system has no function. It's a hoard.

The test of a working system is not what's in it. The test is what comes out. Essays you've written, decisions you've made, presentations you've built, conversations you've had better for having the accumulated reference material. If these artefacts exist and the system is visibly contributing to them, the second brain is earning its keep. If the artefacts don't exist, no amount of reorganising the system is going to save it.

The move for anyone who's been building a second brain for more than six months without producing output: set a small public commitment. A weekly 500-word essay on something you care about. A monthly summary to a specific audience. A quarterly review you share with a peer. Whatever form works. The commitment forces the express step, which is the step that turns the rest of the system from overhead into infrastructure.