Building a Second Brain: A Review on Knowledge Management

I’ve been drowning in information for years. I’m constantly consuming content—technical documentation, team meeting notes, one-on-one conversations, architecture decisions, industry articles, conference talks, and the list goes on. The problem isn’t the volume; it’s that I’ve never had a good system for capturing, organizing, and actually using all of this knowledge when I need it.

That’s why Tiago Forte’s “Building a Second Brain” caught my attention. The premise is simple but powerful: create a system outside your head to store and retrieve information, so your actual brain can focus on thinking and creating rather than remembering.

The Core Problem It Solves

In my role, I’m constantly context-switching between strategic planning, technical deep-dives, people management, and fire-fighting. By the time I need to recall that brilliant insight from last month’s architecture review or reference a decision we made six months ago, it’s either lost in a sea of notes or I can’t find it quickly enough to be useful.

Forte’s approach is built around what he calls CODE: Capture, Organize, Distill, and Express. It’s not about creating a perfect filing system—it’s about creating a system that works for how you actually think and work.

What Resonated With Me

The concept of “progressive summarization” hit home. Instead of trying to capture everything perfectly the first time, you capture broadly, then progressively distill the most important information. This matches how I actually process information—I don’t always know what’s going to be important until later, when I’m working on a specific problem or decision.

The idea of organizing by project rather than by topic also makes sense for my workflow. I’m not just collecting information for the sake of it; I’m collecting it to use in specific contexts—planning the next quarter’s technical roadmap, preparing for a board presentation, or helping a team member work through a complex problem.

How I’m Applying It

I’ve started implementing a version of this system using a combination of tools I already use. I’m capturing meeting notes, key decisions, and insights in a way that makes them searchable and retrievable. More importantly, I’m being intentional about distilling the most important points so I can quickly reference them later.

For example, when I’m in a one-on-one with a team member discussing career growth, I’m not just taking notes—I’m capturing the key themes and action items in a way that I can reference months later when we’re having follow-up conversations. When I’m reviewing technical proposals, I’m distilling the key trade-offs and decisions so I can reference them when similar questions come up.

The “express” part of CODE is particularly relevant for my role. I’m constantly synthesizing information to communicate with different audiences—explaining technical decisions to non-technical stakeholders, translating business requirements into technical strategy, or helping engineers understand the “why” behind organizational decisions. Having a well-organized knowledge base makes this synthesis much easier.

What I’m Skeptical About

I’ll be honest—some of Forte’s recommendations feel a bit too structured for my taste. The detailed tagging systems and folder hierarchies he suggests might work for some people, but I’ve found that too much structure can become a barrier to actually using the system. I’m experimenting with a lighter-weight approach that still captures the core principles.

Also, while the book is great on the “how” of capturing and organizing, I wish it had more on the “when” and “why” of revisiting and using that information. I’m not just collecting knowledge—I need to actively use it to make decisions and guide strategy. The book touches on this, but I’d love more practical guidance on building habits around actually leveraging your second brain.

The Bottom Line

“Building a Second Brain” has given me a framework for thinking about knowledge management that actually fits how I work. It’s not about creating a perfect system—it’s about creating a system that helps me be more effective in my role.

The real test will be whether I’m still using this system in six months, and whether it’s actually making me more effective. But the early signs are promising. I’m already finding myself able to reference past decisions and conversations more quickly, and I’m spending less mental energy trying to remember things I know I’ve captured somewhere.

If you’re in a leadership role where you’re constantly juggling information from multiple sources and contexts, this book is worth a read. Just don’t feel like you need to implement every single recommendation—take what works for you and adapt it to your workflow.

The goal isn’t to have a perfect second brain. The goal is to have a second brain that actually helps you think better and make better decisions. And that’s something I can get behind.