How to Build a Personal Knowledge Management System That Actually Sticks
I've built and abandoned more note-taking systems than I can count. Evernote, then Notion, then Obsidian, then a brief and embarrassing detour into a folder of
I’ve moved my notes between these three apps more times than I’d like to admit. Notion was my home for two years. Obsidian has been my daily driver for about three now. Logseq I’ve tried to love twice and bounced off both times, though I understand exactly why some people swear by it.
Every “which note app” post tends to end with “it depends.” That’s true but useless. So here’s the version I wish someone had handed me: what each tool actually is underneath, where it breaks, and who should pick which one.
Notion is a database with a text editor bolted on. Obsidian is a folder of plain text files with an interface bolted on. Logseq is an outliner with a graph database bolted on.
That sounds like trivia. It isn’t. It determines almost everything else — how fast the app feels, what happens when it syncs badly, whether you can leave, and what kind of thinking the tool encourages.
If you remember only one thing from this post, make it that.
Notion’s real strength isn’t note-taking. It’s structured information: project trackers, content calendars, CRM-ish tables, wikis for teams, dashboards that pull from five databases. If your “notes” are really records with properties and statuses, nothing else here comes close.
What I liked when I used it daily:
What wore me down:
Pick Notion if your work involves other people, or your information is tabular, or you want one tool for docs and tasks and light project management. It’s a collaboration product that happens to do notes.
Don’t pick it if you write long-form, work offline often, or care about owning your files in a format that will outlive the company.
Obsidian’s pitch is local Markdown files. That’s it. Everything else — plugins, graph view, canvas — is decoration on top of a directory on your disk.
For me that’s the whole ballgame. My vault is roughly a few thousand notes now, all plain .md files. I can grep them, back them up with rsync, open them in any editor, and if Obsidian disappears tomorrow I lose nothing but the interface.
The things that actually matter day to day:
[[wikilinks]] and backlinks changed how I take notes. I write smaller notes and connect them instead of building one giant document.The honest downsides:
Pick Obsidian if you write a lot, want to own your data, and are willing to spend a weekend setting up a system and then mostly leave it alone.
Don’t pick it if you want zero configuration, need real-time collaboration, or you know you’ll spend three weeks tweaking plugins instead of writing.
Logseq is the one I keep wanting to click with. It’s built around blocks and daily notes. You open the app and you’re in today’s journal. You write bullets. You link and tag as you go. Structure emerges from the bottom up.
When it works, it’s the closest thing to how my brain actually operates. I dump a thought, tag it, and it shows up wherever that tag lives. No deciding which folder a note belongs in.
Why I bounced off it twice:
Pick Logseq if you think in outlines, live in daily notes, and want bidirectional links without Obsidian’s configuration overhead.
Don’t pick it if you write long prose, need a polished mobile app, or want maximum file-format safety.
| Notion | Obsidian | Logseq | |
|---|---|---|---|
| Data format | Proprietary + export | Plain Markdown files | Markdown + block DB |
| Offline | Limited | Full | Full |
| Speed | Network-dependent | Instant | Fast |
| Databases | Excellent | Via plugins | Limited |
| Long-form writing | Good | Excellent | Awkward |
| Collaboration | Excellent | Weak | Weak |
| Setup effort | Low | Medium-high | Low-medium |
| Cost | Free tier, paid plans | Free, sync paid | Free, sync paid |
Stop looking for the one app that does everything. It doesn’t exist, and chasing it is how you end up with four half-migrated note collections and no actual notes.
The tool matters less than the habit. A mediocre app you write in daily beats a perfect system you set up once and abandon. I’ve watched people spend months optimizing their Obsidian vault and produce nothing. I’ve also watched people do genuinely great work in Notion databases that would make a purist wince.
My current setup: Obsidian for everything I write and think, plain Markdown, eight plugins, Git for backup. Notion for the one shared project board I can’t avoid. Logseq installed, opened maybe twice a month, mostly out of guilt.
If I had to give one recommendation: if you write for yourself and care about owning your words, use Obsidian. If you work with other people, use Notion. If you think in bullets and journal daily, try Logseq — but give it a real two weeks before you decide.
Can I use more than one? Yes, and many people do. The trap is duplicating content across apps. Pick one as your source of truth and use the other for a specific, non-overlapping job.
Is Notion too slow for serious writing? For short docs, no. For long writing sessions on unreliable internet, yes. That’s the main reason I left.
Do I need Obsidian Sync? No. Git, iCloud, Dropbox, or Syncthing all work. They each have failure modes. Test your setup before you trust it with years of notes.
Is Logseq dying? I don’t know, and I won’t pretend to. Check the project’s repository and community before betting on it long-term. The same advice applies to any tool you’re committing to.
What about Apple Notes, Bear, or plain text files? All reasonable. Apple Notes is faster than all three here and syncs effortlessly. It just doesn’t link or scale the way these do. If you don’t need links or databases, you may already have the right app.
The best note-taking app is the one you’ll still be using in a year. Everything else is a feature comparison.
I've built and abandoned more note-taking systems than I can count. Evernote, then Notion, then Obsidian, then a brief and embarrassing detour into a folder of
I've been running a bilingual blog for about six years now — English on one side, Chinese on the other. Not translated copies of each other, which is a trap a l
Every few months, a story lands about an AI that "hacked" something. It broke out of a sandbox. It found a bug in a test harness. It exfiltrated its own weights