You read interesting articles, take notes in meetings, save useful links, and six months later can’t find any of it when you actually need it.

Welcome to the knowledge management problem. Information accumulates. Retrieval fails. You end up re-learning things you already know or searching for information you know you saved somewhere.

A proper personal knowledge management (PKM) system fixes this. Here’s how to build one that actually works.

The Core Problem

Your brain isn’t designed to store everything. It’s designed to make connections and synthesise ideas. Trying to remember every useful thing you learn is doomed to fail.

The solution is an external system—a “second brain”—that stores information and makes it retrievable when you need it.

Most people’s attempts at this fail because they:

• Use too many tools (notes in Apple Notes, bookmarks in Chrome, documents in Google Drive, highlights in Kindle)
• Lack a consistent capture process
• Don’t structure information for retrieval
• Never review or connect ideas

The Three Core Functions

A good PKM system does three things:

Capture: Quick, frictionless way to save information before you forget it.

Organise: Structure that makes information findable later.

Connect: Links between related ideas that create new insights.

You need all three. Just capturing creates clutter. Just organising creates unused archives. Just connecting without capture and organisation means you’re working from memory, which defeats the purpose.

The Tool Question

Tools matter less than you think. The best PKM system is the one you’ll actually use.

Popular options:

• Notion: Flexible, powerful, good for structured information
• Obsidian: Plain text, excellent for linking ideas
• Evernote: Classic option, still works fine
• Roam Research: Built for networked thinking
• Apple Notes or Google Keep: Simple, free, low friction

I use Obsidian because it’s fast, works offline, and stores everything as plain text files I can access forever. But Notion or Evernote would work fine too.

The tool doesn’t matter as much as the system and habits.

The Capture Process

When you encounter something worth saving, you need a frictionless way to capture it immediately.

For articles and web content: Use a read-it-later service like Pocket or Instapaper. Save now, process later.

For thoughts and ideas: Quick capture note in your phone. I have a “Fleeting Notes” section in Obsidian that syncs across devices. Random thoughts go there immediately.

For meeting notes: Template that includes date, attendees, key points, and action items. Fill it in during or immediately after meetings.

The key is capturing everything in the moment. Trying to remember to record it later doesn’t work.

The Organisation Structure

Most people over-organise. Elaborate folder hierarchies sound good but become obstacles.

Better approach: light categorisation plus search and links.

I use broad categories:

• Projects: Active work with defined outcomes
• Areas: Ongoing responsibilities (work, health, finance)
• Resources: Reference material organised by topic
• Archive: Completed or inactive items

Within each, I keep structure minimal. Tags and links do most of the organisational work.

Tags and Metadata

Tags help you find information across categories.

I tag notes with:

• Topics (#productivity, #marketing, #technology)
• Type (#meeting-note, #article-summary, #idea)
• Status (#active, #archived, #to-review)

This lets me find, for example, all active meeting notes about marketing projects with one search.

Don’t go crazy with tags. 3-5 tags per note is plenty. Too many tags is as bad as too few.

The Linking Approach

This is where PKM becomes powerful. Linking related notes creates a network of ideas.

When I write about productivity, I link to related notes about time management, focus, and specific techniques. These connections surface ideas I’d forgotten and create new insights.

Obsidian’s graph view visualises these connections, showing clusters of related topics. It’s not just aesthetically pleasing—it reveals patterns in your thinking.

The Regular Review Process

Information rots if you don’t revisit it. Schedule regular reviews:

Weekly: Review quick captures and fleeting notes. Process them into proper notes or delete if no longer relevant.

Monthly: Review project notes. Update status, archive completed items, identify next actions.

Quarterly: Scan your entire system for orphaned notes, outdated information, and connection opportunities.

This maintenance keeps the system useful instead of becoming a dumping ground.

The Writing-to-Learn Technique

The best way to solidify knowledge is writing about it in your own words.

When I read a useful article, I don’t just save the link. I write a summary note explaining the key ideas as I understand them. This forces actual comprehension and creates reference material in my own language.

These summary notes become far more useful than the original articles because they’re tailored to how I think.

Common Mistakes to Avoid

Over-optimising the system: You can spend forever tweaking your setup. Good enough is fine. Actually using the system matters more than perfect organisation.

Collecting without processing: Saving everything without ever reviewing it creates a pile of unread content, not a knowledge system.

Making it too complicated: If your system requires extensive documentation to understand, it’s too complicated. Simplify.

Not connecting ideas: Notes that sit in isolation aren’t knowledge management; they’re just archives.

The Progressive Summarisation Approach

Tiago Forte’s progressive summarisation technique works well:

Layer 1: Save the full content.

Layer 2: Bold the most important passages.

Layer 3: Highlight the most important bolded sections.

Layer 4: Write a summary in your own words.

You don’t do all layers immediately. You progressively summarise as you revisit notes, gradually distilling to the essence.

Integration with Work

Your PKM system should support your actual work, not be separate from it.

I keep project documentation in my PKM. Meeting notes, research, decision logs—all connected to the broader knowledge base.

When starting a new project, I can search my PKM for related past work, relevant techniques, and people who might help. This makes institutional knowledge portable even if you change jobs.

The Mobile Consideration

Your PKM needs to work on mobile. Useful insights often happen when you’re away from your desk.

Most tools have decent mobile apps now. The experience isn’t perfect, but quick capture and basic review work fine on phones.

I don’t try to do heavy organisation or writing on mobile. Just capture and light review. The deep work happens at my desk.

Privacy and Backup

Your PKM contains your thinking, research, and potentially sensitive information. Back it up properly.

If you use a cloud service (Notion, Evernote), you’re automatically backed up but should still export periodically.

If you use local files (Obsidian), set up automated backups. I use a combination of cloud sync and local Time Machine backups.

When to Reference, When to Remember

Not everything belongs in your PKM. Some things are worth remembering directly. Core concepts in your field, fundamental skills, frequently used information—internalise these.

PKM is for:

• Details you need occasionally but not constantly
• Connections between ideas
• Reference material you might need
• Learning from past experiences

Don’t outsource everything to your PKM. Use it to augment memory, not replace thinking.

The Long-Term Value

A good PKM system compounds over time. Each note you add creates more potential connections. Each review session strengthens understanding.

After a year of consistent use, you have a valuable resource. After five years, you have a comprehensive external brain that contains your professional and personal knowledge, all linked and searchable.

This isn’t just organisational productivity—it’s cognitive leverage. You can think better and produce better work when you have easy access to everything you’ve learned.

The effort of building and maintaining a PKM system pays dividends for years. Start simple, stay consistent, and let it grow organically. The system should serve your thinking, not become an end in itself.