Personal Knowledge Management (PKM)

Definition

Knowledge Management applied at the level of a single person — practices, processes, and tools for capturing, organizing, and applying knowledge in service of one’s own thinking, creativity, and work output. PKM became a distinct discipline around 2005 (Harold Jarche, Dave Pollard) and surged with tools-of-thought in 2020+ (Obsidian, Roam, Logseq, Notion).

How PKM differs from org KM

PKMOrganizational KM
UnitOne personTeam / department / company
GoalAugment individual thinkingAugment collective capability
ToolsObsidian, Roam, Logseq, personal NotionConfluence, SharePoint, Guru, team Notion
MethodsZettelkasten Method, BASB (Forte), PARASECI Model, CoPs, AARs
Failure modeHoarding without applyingBureaucracy without trust

Canonical methods

MethodAuthorOne-line summary
ZettelkastenNiklas Luhmann (1960s–90s)Atomic notes + dense linking; emergent structure beats imposed hierarchy
Building a Second Brain (BASB)Tiago Forte (2022)CODE: Capture, Organize, Distill, Express. Project-oriented.
PARATiago ForteFolder structure: Projects, Areas, Resources, Archives
Smart NotesSönke Ahrens (2017)Operationalized Zettelkasten for academic writing
PKM (Jarche)Harold JarcheSeek → Sense → Share loop for working in networks

Why it matters

The vault began as Ahmed’s PKM. Most failed startups have founders with weak PKM hygiene — knowledge stays in head, doesn’t survive context switches, can’t onboard a team.

The PKM → organizational KM transition is one of the hardest moves a founder makes. It’s what this week’s Team Onboarding Pack is engineering: the same atomic-note discipline that worked for one person now has to support five.

Modern stack (2026)

  • Editor: Obsidian (markdown + plugins) or Logseq or Notion
  • Sync: git, iCloud, Dropbox, or paid Obsidian Sync
  • Capture: quick-capture inboxes, voice notes, web clippers
  • AI augmentation: Claude/ChatGPT as RAG over the vault — see Augmented Intelligence and RAG
  • Distribution: Quartz, Astro, or similar for selective publishing

Common mistakes

  • “Tool tourism” — switching tools every 3 months, never settling
  • Hoarding without re-reading (capture without retrieval is just stress)
  • Over-organizing (perfect taxonomy that nobody maintains) vs under-organizing (everything in one folder, search-only)
  • Treating PKM as a hobby rather than work — leads to beautiful systems that produce nothing
  • Confusing note-taking volume with thinking quality
  • Skipping the Express phase (Forte) — output is what closes the loop

See also