In Part 1, I laid out the philosophy and the "why" of Personal Knowledge Management. Why you need a system, why your brain is not a reliable hard drive, and why linking your notes together beats stuffing them into folders.
This part is where things get practical. Understanding the concepts is the easy part. The hard part is resisting the urge to spend six hours setting up a beautiful Obsidian vault with custom CSS, thirty plugins, and a daily journal template, then never writing a single note in it.
I know. I have done this. Multiple times.
The Tool Landscape (Or: Welcome to the Circus)
Let me save you some time. Here is every major PKM tool, what it is actually good for, and why you might (or might not) want to use it.
Obsidian: The Current King
Obsidian stores your notes as plain Markdown files on your local drive. That is its killer feature. Your notes are just files. You can open them with any text editor. You can version control them with git. You can migrate them to another tool by copying a folder. You own your data.
It has bi-directional links, a graph view that shows your notes as interconnected nodes (which looks incredible and is moderately useful), and a plugin ecosystem that is frankly absurd. There are plugins for spaced repetition flashcards, Kanban boards, calendar views, PDF annotation, citation management, and a hundred other things.
The pros: data ownership, offline-first, infinitely customizable, free for personal use.
The cons: infinitely customizable means infinitely distractable. You can spend more time tweaking your vault than using it. The graph view is beautiful but mostly just makes you feel smart. And the plugin rabbit hole is real.
Who it is for: Researchers, writers, developers, anyone who values owning their data and wants a system that will last decades.
Who it is not for: People who just want to take notes and never think about their system again.
Notion: The Swiss Army Chainsaw
Notion is an all-in-one workspace that does everything: notes, wikis, databases, project management, Kanban boards, calendars, and probably tax preparation at this point. It uses a block-based editor where every piece of content is a drag-and-drop block. You can build a personal wiki, a task tracker, a reading list database, and a company handbook all in the same workspace.
The pros: incredibly flexible, beautiful interface, great for team collaboration, databases that actually work.
The cons: it is slow. The web app can lag. The mobile app is worse. It is cloud-hosted: your data lives on Notion's servers in a proprietary format, not as local files you own. (Notion added a limited offline mode in August 2025, but the web app still needs a connection and offline databases are capped.) And the flexibility means you will spend three days designing a perfect page template instead of writing notes.
Who it is for: Teams, project managers, people who want notes and tasks in one place and accept the cloud dependency.
Who it is not for: Privacy-conscious users, offline workers, people who get distracted by design.
Roam Research: The Philosopher's Toolkit
Roam introduced the mass market to bi-directional linking and networked thought. It is an outliner: every note is a nested bullet list. It has daily pages that encourage journaling and linking. It lets you reference individual blocks from any page, which means you can reuse snippets across contexts without duplication.
The pros: fluid linking, effortless daily journaling, block references are genuinely powerful for research.
The cons: subscription pricing at $15/month with no free tier. Cloud-only. Minimalist interface that feels barebones. And the outliner format drives some people crazy.
Who it is for: Academics, writers, deep thinkers who work with interconnected ideas over long time horizons.
Who it is not for: People who prefer rich text, visual formatting, or a one-time payment.
Logseq: The Open Source Roam Alternative
Logseq is what happens when the open source community builds a Roam clone and improves it. It uses the same outliner + daily notes + bi-directional links approach, but stores everything as plain Markdown or Org-mode files on your local drive. It is free, open source, and respects your privacy.
The pros: local-first, open source, free, similar functionality to Roam without the subscription.
The cons: slightly rougher around the edges. The UI is not as polished. Mobile support has historically been weak (improving though).
Who it is for: People who want Roam-style features but refuse to pay $15/month or trust the cloud.
Evernote: The Veteran
Evernote was the original PKM powerhouse. It pioneered the "capture everything" approach with web clippers, audio notes, image search, and cross-device sync. It still works fine.
The pros: mature product, excellent web clipper, powerful search (including text inside images).
The cons: it has stagnated. The interface feels dated. The free tier is increasingly restrictive. And it is cloud-only with proprietary format, so migrating out is painful.
Who it is for: People who have been using it for ten years and it still works for them.
Who it is not for: Anyone starting fresh today.
TiddlyWiki: The Tinkerer's Dream
TiddlyWiki is a personal wiki in a single HTML file. Each note is a "tiddler." You open the file in a browser, edit, save. It is infinitely customizable through plugins and macros.
The pros: one file, completely self-contained, open source, infinitely customizable, runs anywhere there is a browser.
The cons: infinitely customizable means you will spend weeks tweaking it. Syncing across devices requires manual setup. It is not for casual users.
Who it is for: Tinkerers, developers, people who want total control over their system.
Who it is not for: Anyone who just wants to write a note and have it saved.
The Great Debate: Local-First vs Cloud
Here is the question that splits the PKM community: where should your notes live?
Cloud advocates say: Sync just works. I can open my notes on any device. I do not have to think about backups. Collaboration is built in. And I do not have to set up anything.
Local-first advocates say: My notes are plain text files on my machine. I own them. No subscription can take them away. No company shutdown can erase them. I can open them in any tool, now and in 20 years.
I have been on both sides. I used Notion for two years. It worked great until I needed to take notes on a plane and realized I had no internet. Then I switched to Obsidian and felt a deep sense of calm. My notes are just files. They sync via git and iCloud. They will outlive every app on this list.
The local-first position wins for longevity. But it requires some technical comfort. You need to think about sync, backups, and setup. Cloud is easier. Local-first is more durable. Pick your tradeoff.
Why Markdown Is the Universal Format
If you take one thing from this guide, let it be this: write your notes in Markdown.
Markdown is plain text with lightweight formatting. It has no vendor lock-in. You can write it in any text editor. Every PKM tool supports it. It renders beautifully on GitHub, in VS Code, on blogs, and in publishing tools. It is version-control friendly (git diff actually works on it). And it will still be readable in 50 years when Notion, Roam, and Obsidian are footnotes in the history of software.
Every time I moved notes between systems, the Markdown users had an easy time. The proprietary-format users had a bad time. Learn from our pain.
My Actual Setup (Yours Will Be Different, And That Is Fine)
After years of cycling through systems, here is what I have settled on. It is not perfect, but it has stuck longer than anything else.
Capture layer: A note in my phone (Apple Notes or Drafts) for quick capture. Zero friction. If it takes more than two seconds to record a thought, the system fails.
Permanent storage: Obsidian vault on local disk, synced via git and iCloud. Plain Markdown files. One folder for conceptual notes (Zettelkasten style), one for project notes (PARA style), one for daily journal entries.
Review rhythm: I spend 15 minutes every Friday reviewing new notes, making connections, and archiving what is stale. I do not always do it. But I try.
Search: I rely on Obsidian's full-text search and backlinks more than folder navigation. The graph view is a nice party trick but I rarely use it for actual work.
That is it. Six tools from that long list reduced to three. The rest were experiments that taught me what I did not need.
How to Start Without Overwhelming Yourself
If you are new to PKM, do not do what I did. Do not spend a weekend setting up a perfect system. Do this instead:
-
Pick one app. Obsidian or Logseq if you want local-first and free. Notion if you want cloud and convenience. Use it for one month. Do not even look at other apps.
-
Write one note per day minimum. It does not matter what. A thought, a summary of something you read, a meeting recap. Build the habit.
-
Link two notes together once a week. Just one link. This is how the system starts generating value.
-
Review once a month. Open a note from three months ago. Update it. Connect it to something new. Watch the network grow.
-
Resist the urge to reorganize. Your system will naturally evolve toward the structure you need. Premature organization is the enemy of a working PKM system.
The Real Lesson
I started out thinking the perfect tool would fix my forgetting problem. It took trying almost everything to realize that no tool saves you from the work of actually thinking.
PKM is a practice, not a product. The best system is the one you actually use. The best tool is the one that stays out of your way. And the best notes are the ones you revisit, connect, and turn into something real.
So pick a tool, any tool, and start writing. The system will figure itself out.