Second Brain vs. Just Do the Thing

Key Points

Most second brain systems become procrastination tools—you spend more time organizing than creating
The best productivity system is invisible: it doesn’t require constant maintenance or meta-work
Capture ruthlessly, organize minimally; the 80/20 on personal knowledge management is real

I’ve watched hundreds of people fall into the productivity trap. They buy an expensive notebook, set up a Notion workspace with seventeen linked databases, install a PKM app, and suddenly they’re spending three hours a week maintaining their system instead of, you know, doing the actual work.

I get the appeal. Tiago Forte’s Building a Second Brain is genuinely insightful on how to capture and process information effectively. The second brain movement isn’t wrong—it’s just been weaponized by the productivity content industrial complex. Now everyone thinks they need an elaborate external brain or they’re somehow failing at modern life. That’s nonsense.

The real problem is this: a second brain system becomes productive theater when you care more about how you organize your work than whether you actually finish it. I’ve known founders with meticulously tagged Obsidian vaults who ship less than scrappy operators with a simple Google Docs folder. I’ve seen writers with color-coded research systems who publish fewer articles than writers with a “notes” folder and a strong bias toward action.

The Meta-Work Trap

Here’s what happens with most elaborate productivity systems: you’re not being productive. You’re feeling productive. There’s a difference.

You’re tweaking your tagging system. You’re creating templates for templates. You’re reorganizing your folders because the original taxonomy doesn’t quite capture the nuance of that one note about market positioning. You’re learning Dataview syntax so you can build a custom dashboard. You’re watching YouTube tutorials on advanced Roam Research techniques.

This is all meta-work. It’s work about work. It’s the professional equivalent of organizing your desk instead of writing the memo, and we all know that’s bullshit.

David Allen’s Getting Things Done has it right: the purpose of a system isn’t to be impressive—it’s to free your brain so you can focus on execution. The moment your system requires constant maintenance, it’s failed its fundamental job. You’ve traded actual output for the illusion of control.

I respect the people building these tools and systems. Tiago Forte, Andy Matuschak, Maggie Appleton—they’re doing genuinely creative work. But somewhere along the way, the practitioners started confusing having a system with being effective. Those aren’t the same thing.

When a Second Brain Actually Helps

Let me be clear: I’m not anti-system. I’m anti-elaborate-system-that-doesn’t-pay-for-itself-in-output.

A second brain makes real sense if you’re doing research-heavy work. If you’re writing a book, pulling insights from fifty sources, and need to trace ideas back to where you found them—yes, invest in a system. If you’re running multiple businesses and need to retain institutional knowledge that your team will use—yes, build something substantial. If you’re writing a lot and patterns matter more than any single capture—absolutely, formalize the capture process.

But if you’re a founder spinning up ideas, or a solo maker iterating on a product, or a consultant delivering client work—you probably don’t need a second brain. You need a quick capture mechanism and the discipline to actually execute on the work.

My approach is embarrassingly simple. I use Apple Notes for quick thoughts. I use Google Docs for projects in progress. I use a simple spreadsheet for business metrics. That’s it. No plugins. No syncing across seventeen apps. No custom workflows. I spend maybe five minutes a week maintaining it, which is exactly how much a system should require.

For longer-term stuff—like when I was building Openmark—I kept a simple project folder with a status doc, sketches, and links. Nothing fancy. Nothing that required learning a new app or mastering a new syntax. Just enough structure that I could pick it up after three weeks away and remember where I left off.

The Optionality Question

Nassim Taleb talks about building optionality into decisions—keeping your options open without overcommitting. That’s how I think about information capture. I want to keep good ideas available without being locked into a system that requires constant feeding.

The trap with elaborate second brain systems is that they create negative optionality. You’re locked in. You’ve invested so much time in the Roam setup or the Obsidian vault or the Notion architecture that switching feels impossible. You’re trapped in your own system, maintaining it instead of benefiting from it.

A simple system keeps you optionality-positive. You can switch from Apple Notes to Tana to whatever comes next without losing three months of productivity to migration. You’re not hostage to any particular platform or workflow.

The Real Insight: Invisible Systems

The best productivity system is the one you don’t think about. It’s not the one with the most features or the prettiest dashboard or the most sophisticated tagging scheme. It’s the one so frictionless that you never notice it’s there.

Think about it: when you’re in flow, when you’re actually producing—you’re not thinking about your system. You’re not checking your PKM app. You’re not admiring your task management setup. You’re deep in the work, and the system is just quietly capturing what needs to be captured, reminding you of what needs attention, and then getting out of the way.

That’s the whole point. A system that makes you think about systems is a bad system.

I’ve watched this play out in startups too. The teams that move fastest aren’t the ones with the best-documented processes. They’re the ones where processes are so embedded that everyone just knows what to do. No meetings about meetings. No processes about processes. Just work.

The 80/20 on Personal Knowledge

If you’re going to have a system—and you probably should have some structure—here’s what matters:

Capture ruthlessly. If it might be useful, save it. Don’t filter at the input stage. That takes energy and you’ll miss things. Just dump it in.

Organize minimally. Don’t build elaborate taxonomies. Use one level of folders. Maybe two. That’s it. Tag things if you want, but don’t get precious about it. A 95% accurate tag is better than a perfect system you abandon.

Review religiously. This is the one place that matters. Spend time reviewing what you’ve captured. Old notes, past projects, earlier thinking. This is where the real value emerges—in the connection between then and now. Not in how well you organized it.

Ruthlessly delete. Every six months, look at what you’ve captured and delete 80% of it. You don’t need it. The important stuff will resurface. Keeping everything is just hoarding with better branding.

I clean out my Google Drive quarterly. I delete most of my old notes. I don’t keep a history of every meeting. Life’s too short to maintain a museum of your former thinking. You want a system that helps you move forward, not one that requires you to preserve everything that ever happened.

The Real Test

Here’s how you know if your system is working: Are you shipping more? Are you making better decisions? Are you thinking more clearly? Are you executing faster?

If the answer is yes, great. Keep the system. If the answer is no, or if you’re spending more time thinking about the system than benefiting from it, kill it. Just do the work with whatever minimal structure actually serves you.

That’s not anti-productivity. That’s pro-productivity. It’s just honesty about what actually drives output.

The productivity content industrial complex wants you to believe the answer to “why aren’t I shipping?” is “I need a better system.” Sometimes it is. But more often, the answer is just: do the thing. Skip the elaborate capture. Skip the perfect taxonomy. Skip the customized dashboard. Just pick up the work and move it forward.

Your second brain should serve your output. If it’s the other way around, you’re not building a system—you’re building a cage.

Further reading: