Interactive graph
PKM
Table of Contents
PKM saves, organizes, and reuses what you learn - not a hobby of collecting apps.
Key Concept
- Save, organize, reuse - three moves, not app-hopping for the perfect stack.
- Output beats tuning the system alone.
- This garden is where reuse happens after capture.
Level 1 - Recognize
PKM is personal knowledge management - save what you learn, organize it where you can find it, reuse it when needed.
Level 2 - Explain
Like catch, label, and cook instead of hoarding groceries until they spoil - three moves beat app-hopping.
Level 3 - Use
Pick one inbox, one organize pass, one express habit - swap tools only when a step fails, not when a blog posts a new app.
Level 4 - Connect
Output beats tuning the system alone - perfectionism about stack is procrastination dressed as research.
Level 5 - Create
Build one complete PKM loop: capture with CODE, organize with PARA Method, then turn one saved idea into work someone can use.
Examples
- The team manager keeps a card file sorted by what she actually uses on game day - she deleted half of it last spring after a loss reminded her what she never opened.
- I screenshotted forty recipes last year and cooked four - the Notes app only keeps what survived a second cook.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| alternative | GTD vs PARA | Note garden vs task inbox when architecture beats action lists |
| contradicts | The Collector's Fallacy | when building the system feels like progress without output |
| extends | Getting Started | PKM is the plain name for the save-organize-use system getting started introduces |
| extends | Personal Knowledge Management | Umbrella term this garden sits under |
