Building a Second Brain in Practice

After Reading Tiago Forte's Book

I read "Building a Second Brain." The core idea is to store all useful information in an external system to reduce the cognitive load on your brain. Organize information using the PARA structure (Projects, Areas, Resources, Archives) and manage it with the CODE process (Capture, Organize, Distill, Express).

Great book. But putting it into practice turned out to be a different story entirely.

Step 1: Capture

Collect everything. Good articles from Twitter, technical discussions on Slack, ideas from meetings. I dumped it all into an inbox folder in Obsidian.

First week: 73 notes piled up in the inbox. The problem was they just accumulated without ever getting organized. Capturing is easy. Building the habit isn't hard either. The next step is where things break down.

My initial mistake was capturing too much. I was saving every tweet, every newsletter sentence, and it led to information overload. Adding a filter of "will this actually be useful later?" finally slowed the inbox flood. From 73 per week down to 21.

Step 2: Organize

Applied the PARA structure. Projects for notes related to active work, Areas for things I maintain continuously (health, finances, career), Resources for interest topics (tech trends, design patterns), Archives for finished projects.

But so many things were ambiguous. Is a "React 19 new features summary" a Project or a Resource? If I'm in the middle of a migration project, it's a Project. If it's just study material, it's a Resource. (Spending time on this classification felt like it defeated the purpose.)

I ended up simplifying PARA to three buckets: Active, Reference, Archive.

Step 3: Distill Is the Hardest Part

This is the stage where you extract key insights from your captured notes. The book calls it "progressive summarization" -- bold, highlight, summarize in stages.

I did this diligently for 23% of my notes. The remaining 77% were captured and never looked at again. If I'm being honest, the pattern was that I got satisfaction from the act of collecting information, and found the organizing part tedious.

Is it pointless if you collect 100 notes and only refine 23? Not necessarily -- sometimes you search for and rediscover old notes later. But it's not efficient.

Step 4: Express

Turn refined notes into outputs. Could be a blog post, an internal tech talk, whatever. In fact, this blog post itself came out of my second brain.

Outputs generated from my second brain over three months: 4 blog posts, 1 internal tech sharing presentation, 1 project proposal. Not a huge number, but the time I used to spend hunting for "where did I save that?" definitely decreased.

Honest Assessment After Three Months

I spent too much time building the system. Folder structure, tag taxonomy, template setup -- the first two weeks went to infrastructure. There was a period where I was so focused on perfecting the system that I wasn't actually taking notes.

Now I keep the system simple and focus on capture and search. Even rough categorization is fine if search is fast. Obsidian's search is fast enough to make this strategy work.

A second brain won't change your life. But it's definitely reduced those "I wrote this down somewhere" moments where I'd waste 30 minutes hunting for something.