Draft status: Outlined. Strong contrarian hook in place. Expand the middle sections with specific tool limitations and the “tools vs. systems” argument.
The question being asked
Every week, someone posts to r/ObsidianMD or r/PKMS asking: “Should I use Notion or Obsidian for my second brain?”
The thread fills with opinions. Obsidian advocates praise local storage, plugin ecosystem, and graph view. Notion advocates praise databases, collaboration, and web access. Someone inevitably mentions Roam Research. Someone else mentions LogSeq. The OP gets overwhelmed and tries one of them.
Six months later, they’ve abandoned it.
Here’s what none of the thread respondents say: the problem isn’t which app you choose.
Tools vs. systems
A second brain is a system, not a tool. The distinction matters:
A tool is something you use. It can be excellent or mediocre. You operate it.
A system is something that operates. It runs on inputs, produces outputs, has maintenance requirements, and degrades if neglected.
Notion and Obsidian are tools. They’re very good tools. But neither of them is a system. You have to be the system , providing the judgment, the tagging, the organization, the synthesis. The tool just stores what you put in.
This is why the comparison misses the point. You’re not choosing between systems. You’re choosing between interfaces for the same underlying problem: knowledge gets stored but not processed.
[EXPAND: A concrete example. A consultant who has a beautifully-organized Notion database and still can’t answer “what do I know about X?” quickly, because searching returns 47 unrelated pages that each contain one relevant paragraph.]
What Notion actually is
Notion is an excellent project management and documentation tool with a flexible database structure that makes it attractive for knowledge management. It’s genuinely useful for:
- Structured data (CRMs, project trackers, content calendars)
- Team wikis with templates
- Simple personal databases
Where Notion struggles as a second brain:
- No synthesis. Saving an article to Notion stores the article. It doesn’t integrate the article’s ideas into your existing knowledge.
- Maintenance overhead. Notion’s power comes from structure. Structure requires effort to maintain.
- Retrieved objects, not answers. When you search Notion, you get documents. Not answers.
[EXPAND: Be fair but honest. This isn’t an anti-Notion piece. It’s about the right tool for the right job.]
What Obsidian actually is
Obsidian is an excellent writing and linking tool for people who want local-first, Markdown-based notes with a visual graph view. It’s genuinely useful for:
- Writers and researchers building conceptual connections manually
- People who want full data ownership and local storage
- PKM enthusiasts who enjoy the process of linking notes
Where Obsidian struggles as a second brain:
- The maintenance problem is worse. The graph view is beautiful when maintained. When you stop linking notes consistently, it becomes a disconnected mass.
- Plugins don’t solve synthesis. There are excellent Obsidian plugins that add AI features. They make it easier to add notes. They don’t compile knowledge from those notes.
- High learning curve for low-context users. Obsidian rewards people who invest deeply in the system. Most people don’t have that bandwidth.
[EXPAND: The honest version of “Obsidian is great if you’re the type of person who enjoys building systems.” Most people aren’t that person, and that’s fine.]
The real comparison isn’t tool vs. tool
The right comparison is tool vs. system:
| Notes App (Notion/Obsidian) | LLM Knowledge Base | |
|---|---|---|
| Organization | You do it | AI does it |
| Synthesis | You do it | AI does it |
| Maintenance | Ongoing effort | Monthly compilation run |
| Retrieval | Search returns documents | Query returns answers |
| Scales with use | Gets harder to navigate | Gets more valuable |
| Link maintenance | Manual | Automatic |
The notes app is the right tool if you enjoy the process of building and maintaining your own knowledge system. Many people do. It’s a genuine craft.
The LLM knowledge base is the right system if you want knowledge that is useful, not knowledge that is organized.
The question to ask yourself
Don’t ask: “Is Notion or Obsidian better for a second brain?”
Ask: “Do I want to maintain a knowledge system, or do I want a knowledge system that maintains itself?”
If you want to maintain it yourself , if you enjoy the process of linking, tagging, and organizing , use Obsidian. It’s excellent for that.
If you want the outputs (findable knowledge, synthesized research, instant recall) without the process of building the system , that’s what AI compilation solves.
Tried Notion and Obsidian and given up on both? We build second brains that maintain themselves.