Knowledge Management

This deck introduces the core ideas behind personal knowledge management, the practice of capturing, organizing, and using information so it actually supports your thinking over time. You'll work through questions about capturing habits, the difference between collecting and curating, and why over-collecting can hold you back. It also covers popular frameworks like PARA, the concept of a second brain, and approaches such as progressive summarization, atomic notes, and evergreen note-taking.

The cards are a good fit if you are building or refining your own note-taking system, whether you are a student managing coursework, a professional handling lots of reading and projects, or simply a curious learner who wants to retain more of what you read. Even if you have never used a dedicated PKM tool, the deck will help you understand the vocabulary and principles behind methods you may have heard about.

To get the most out of studying, treat the cards as prompts for reflection rather than isolated trivia. After reviewing a concept like PARA or progressive summarization, try applying it to something you are currently working on so the idea sticks. Spacing your review sessions over several days, rather than cramming, will also help these foundational ideas move into long-term memory, where they can quietly shape how you save and revisit information in the future.

Personal knowledge management (PKM) is the practice of capturing, organizing, and reusing information so it becomes easier to think, create, and make decisions. The core idea is cognitive offloading—shifting the work your biological brain struggles with (remembering details, holding unfinished commitments, locating old ideas) into an external system that can be relied on. This external system is often called a "second brain." When it works, you stop re-remembering things in your head, the unfinished commitments that David Allen calls "open loops" stop preoccupying you, and your attention can respond smoothly to the next event. When it breaks down, the costs of poor cognitive offloading become visible: decision fatigue, missed commitments, lost ideas, and the feeling of being busy without being productive. A weak PKM system also imposes context-switch costs because partially captured work is hard to resume, and it creates a knowledge bottleneck where useful information exists somewhere but cannot be found, trusted, or reused quickly enough.

A few principles cut across nearly every PKM approach. Capture must be fast, low-friction, and consistent across devices, because useful ideas vanish quickly. Capturing and processing should be kept as separate steps—capture stays instant, while a later moment is reserved for thoughtful organization. Once captured, material must be sorted by signal versus noise, because high-value insight compounds over time while low-value clutter makes future retrieval harder and decision-making slower. The trap is over-collecting, which gives the false feeling of progress without real understanding; curating therefore matters more than collecting, and the strongest orientation is retrieval over storage—the goal is not to save everything but to make the right ideas easy to find and use when they matter. A useful question before saving anything is whether it will serve a future project, decision, conversation, or explanation; the strongest systems also prefer fewer inboxes (ideally as few as possible) so that processing becomes a single, predictable habit. Simple systems usually outlast complex ones, because a workflow you can sustain on bad weeks is worth more than a perfect system you abandon.

Modern PKM is increasingly assisted by AI, which can summarize notes, cluster related material, and help query the archive. AI works best, however, when the underlying notes are already clear and structured—the quality of automated assistance cannot exceed the quality of the input context. The practices in the rest of this book should therefore be treated as the foundation that makes AI useful, rather than as a substitute for those practices.

PARA is an organization framework built around four buckets: Projects, Areas, Resources, and Archives. Projects are short-term efforts with a clear outcome and deadline, such as launching a landing page or preparing an interview loop. Areas are ongoing responsibilities you must maintain over time, such as health, finances, management, or learning. Resources hold reference material and topic-based knowledge that may be useful in the future. Archives keep inactive material from projects, areas, or resources so it stays searchable without cluttering active work. Periodically, after a major life or work shift, a PARA migration moves existing notes between these buckets to reflect what is actually current.

Within PARA, three classic note types do most of the work. A reference note stores facts, definitions, or source material that supports future work. A project note tracks thinking, decisions, and resources tied to a specific active outcome. A source note captures key ideas from a book, article, podcast, or video while preserving attribution, so you can locate the original later. None of these are useful without context, because even an accurate idea is unusable on revisiting if the circumstances that made it matter are not recorded. For this reason, capturing and processing are kept separate: capture stays fast while a later moment is reserved for organization. Source material should be attributed clearly to prevent confusion, support credibility, and make it easy to revisit the original; a source map—a note listing the primary sources, authors, and references behind a topic—can be especially useful when several atomic notes draw from overlapping material. A summary note that condenses a single source into its key claims and personal takeaways serves a related purpose but stays distinct from atomic notes.

A few conventions make retrieval far more reliable. Notes should be written in your own words, because rewriting improves understanding and makes notes more useful on re-reading. Evergreen notes are atomic—capturing one idea per note—so they can be linked, refined, and reused without confusion. Effective note titles are specific and descriptive enough that you can predict the note's value before opening it. Tags often matter less than people expect: too many become messy quickly, so strong titles, links, and search usually outperform elaborate tag schemes. Linking notes helps ideas reinforce each other and exposes patterns, and templates reduce friction for recurring note types like meeting notes, reading notes, and project briefs.

The CODE method—Capture, Organize, Distill, Express—is Tiago Forte's four-step model for turning information into output. Capture and Organize behave much like other PKM workflows: save inputs reliably and place them in a structure such as PARA. The novelty of CODE is the explicit emphasis on the back half of the pipeline, where most personal knowledge work actually breaks down.

Distill means progressively compressing notes to their most essential ideas, which is the same as note compression in other traditions. In practice, it is done in layers: layer 1 marks standout passages, layer 2 bolds the most important, layer 3 paraphrases them, layer 4 reorganizes the result, and layer 5 rewrites the takeaway in your own voice. This layered compression is progressive summarization. The risk of skipping layers is keeping more noise than signal, so retrieval stays slow and the saved notes are no cheaper to re-read than the originals. A useful target size is the minimum viable note—the smallest self-contained note that still conveys a useful idea and can later be expanded without becoming unfocused.

Express is what CODE exists to enable: producing a creative output—writing, teaching, designing, or building—that draws on the notes captured and refined. CODE differs from classic GTD precisely here, because GTD centers on managing tasks and commitments while CODE centers on finished creative work. A protected, low-interruption creative hour is one mechanism for protecting this step, and weekly reviews can ensure that active notes are actually being driven toward output. Good notes shorten the distance between raw inputs and coherent writing because ideas are already partially shaped; a strong PKM principle is to store information in ways that make future action easier, not in ways that simply feel organized today.

A Zettelkasten—German for "slip-box"—is a personal knowledge system of atomic, uniquely addressed notes that are densely linked so ideas combine into new insights over time. The metaphor comes from a physical wooden card index used by German scholars, where each card carries a single idea and references others by number. The most famous practitioner was the sociologist Niklas Luhmann, who used a Zettelkasten of roughly 90,000 notes to publish more than 70 books and 400 academic articles. The lesson is not the size of the archive but the way linked atomic notes act as a conversation partner: you write into the slip-box and read out of it when drafting, letting the network suggest arguments you did not start with.

The Zettelkasten distinguishes three kinds of notes by lifespan. A fleeting note is a quick capture of an idea in the moment. A permanent note is rewritten in your own words, given a stable address, and integrated with the rest of the slip-box. A literature note is a short, source-anchored summary of a passage you want to remember, written so you can engage with the idea rather than the source. Fleeting notes have a typical lifespan of a few days at most: if they are not rewritten as permanent or literature notes in that window, they almost never will be, and they slowly turn into digital clutter, so processing them daily or every few days is essential.

Two structural choices make Zettelkasten notes accumulate. First, atomic notes—one idea per note—make linking, refining, and reuse possible without confusion. Second, IDs are often alphanumeric (such as 202405180930) rather than purely sequential integers, because this lets you add new notes between existing ones later. Some practitioners go further with a folgezettel, where the note ID explicitly encodes successor relationships—e.g. 21/3d7a—so the order and branching of an argument become part of the address itself. The point is structure-oriented note-taking: letting the structure of the slip-box emerge from the ideas themselves rather than forcing ideas into a pre-existing folder hierarchy. A traditional alternative is the commonplace book—a long-running personal notebook organized by topic—but this tends to be topically curated rather than address-based, and it lacks the dense linking that lets a slip-box generate unexpected connections. A productive way to mature in any note-taking system is the Japanese progression of shu-ha-ri: first learn the rules of atomic, linkable notes, then break them thoughtfully for your own work, then transcend them entirely.

Getting Things Done (GTD), created by David Allen, is a productivity method built around capturing every task and idea in an external system so your mind is free to focus. The workflow has five stages: Capture, Clarify, Organize, Reflect, and Engage. Capture funnels every open loop into a trusted inbox. Clarify asks, for each item, whether it is actionable and, if so, what the next physical, visible step is. Organize places items in lists (next actions, projects, waiting for, someday/maybe, reference). Reflect is the weekly review that keeps the lists trustworthy. Engage is simply doing the work—the state Allen calls "mind like water." Inbox consolidation—routing all captures to a small number of trusted inboxes, often one—turns processing into a predictable habit, and a regular drive toward inbox zero keeps unprocessed material from accumulating.

GTD draws several useful distinctions. A project is any desired outcome that requires more than one action; a single task is one observable action you can complete in one sitting. A "next action" is the very first physical, visible step toward a project, with no ambiguity about what to do, and a Horizon 1 review confirms that every project has a defined next action right now. The two-minute rule says that if an action takes under two minutes, do it immediately at capture time instead of deferring it. Non-actionable items are routed to trash, reference, or someday/maybe; items delegated to others go to a "waiting for" list so nothing slips through while you are not the driver; the inbox triage stack works through each item with a small set of standard questions (actionable? project? two minutes? delegate?). A trusted system is one you can rely on to hold your commitments and surface them at the right moment; when it is not trusted, you start re-remembering things in your head, capture less, and eventually abandon the tool.

GTD also describes a six-level hierarchy of goals: runway, projects, areas, goals, vision, and purpose. Reviewing at each horizon is part of a multi-layered cadence: daily for the inbox, weekly for projects and a trigger list—calendar, email, notes, projects, waiting for, someday/maybe—and quarterly or annually for vision and purpose. Horizon 3 thinking asks you to evaluate some captures against long-term, multi-year direction rather than only today's tasks. A "learning project" in GTD is a project whose outcome is acquiring a skill or understanding, broken into next actions like reading chapters, summarizing, and teaching. A pre-mortem note imagines that a project has already failed and lists the most likely reasons before starting, surfacing hidden risks; a decision log or decision journal records important decisions, alternatives, reasoning, and a later follow-up comparing actual versus expected outcome. A trigger note—a checklist that activates when a specific kind of project starts—lets you turn recurring steps into a reusable file rather than a recurring task.

Modern PKM tools such as Obsidian, Roam, and Logseq treat each note as a card-index entry: a unique address, one idea, an explicit title, and outbound links—an approach in the spirit of the wiki, with pages of internal links intended to be revised over time as understanding grows. The defining feature is the bidirectional link—recognized by both source and target—allowing navigation from either side. A graph view visualizes notes as nodes and links as edges, making it easy to spot clusters, orphans, and bridges between ideas. Daily notes are timestamped, one-per-day entries that act as both a lightweight journal and a capture inbox. Together, these patterns form what is loosely called a personal knowledge graph—the map of what concepts exist in your thinking and how they connect. Orphan notes, which have no inbound or outbound links, are usually hard to find in context and rarely reactivated; the cleanest remedies are either to edit them into the active graph or to archive them honestly.

As that graph grows, you need a way to navigate it without browsing the entire web. That is the role of a Map of Content (MOC), sometimes called a hub note: a note (not a folder) that curates and orders related atomic notes around a topic, often with commentary and cross-references. A MOC is created when a topic has accumulated several atomic notes that benefit from being introduced, ordered, and linked for future readers, including your future self. The difference between a MOC and a folder is that a folder groups files by location, while a MOC is itself a note that describes relationships. MOCs also benefit from review: a monthly MOC review adds new links, fixes broken ones, and merges topics that have grown together; tag gardening does the same for tags, pruning, merging, and renaming so the tag set stays small and meaningful rather than sprawling. The atomic principle shows up as the "one idea per note" rule in practice—if you removed any one paragraph and the rest still held a single coherent point, the note passes; otherwise it should be split.

Three more conventions increase the network's value. First, distinguish a structure note (whose job is to organize other notes around a theme) from a claim note (which takes a position or makes an argument). Descriptive notes can be wrong without misleading you, but argumentative notes carry commitments you can later test, refine, or refute. Second, prefer questions over topics when starting notes: a topic is a noun, while a question demands a position, and question-driven notes age better; the describe-and-name heuristic says that if you cannot describe an idea in one sentence and give it a clean title, you do not yet understand it well enough to save it as a permanent note. Third, prefer context tags ("@meeting," "@errand") or value-based tags ("#principle," "#example," "#counterexample," "#question") over sprawling topic tags, because role-based tags carry information that titles often cannot. Search usually beats folders, since it matches on content rather than on a single filing decision; beware the "first in, last out" trap where the newest notes get the most attention while older, possibly more valuable ideas go unread for years. A trusted index file—a small set of notes listing your main MOCs, areas, and projects—gives you a place to start the day.

The personal knowledge pipeline—capture, process, connect, create—turns raw inputs into finished outputs. Most pipelines break at the connection and creation stages, where captured notes must become projects, drafts, decisions, or teachings. The minimum viable workflow is the smallest end-to-end loop you can sustain on bad weeks, prioritized over a perfect system you abandon. A lightweight daily habit that scales well is the 1-1-1 note: one sentence on what you captured, one on what you processed, and one on what you created. A shelf is a deliberate, time-limited area of focus—a few weeks—where most reading and note-taking is directed to build a coherent body of material that can feed multiple projects, distinct from a single project which has one outcome.

Review ties the system together at multiple rhythms. The weekly review clears inboxes, organizes active material, and reconnects notes to current priorities. Daily processing is for inbox triage; weekly is for projects and the trigger list—calendar, email, notes, projects, waiting for, someday/maybe; monthly is for MOCs and tags; quarterly is for areas, archives, and source maps, and longer horizons keep mature notes honest. Just-in-time review—revisiting notes only when they become relevant to a project, meeting, or decision—is the most cost-effective cadence for older material. A kill criterion (for example, "unread for 12 months and no project link") lets the system prune itself rather than accumulate stale projects, because a project that has had no next action or no activity in a defined window should be re-energized, deferred, or closed during review. A review queue—a small, prioritized list of notes due for re-reading—turns review into a queue rather than an open-ended slog, and a synthesis deadline—an explicit date by which notes on a topic must be turned into a written draft or talk—prevents notes from aging without payoff. A periodic knowledge inventory, often expressed as the list of areas in PARA, audits what topics, skills, contacts, and resources you actually have documented; a knowledge gap—something you can name as important but cannot speak to without preparation—is converted into a learning project by writing the gap as a question, setting a deadline, listing the 3–5 source notes that will result, and scheduling a first review of the resulting note. Exposure, the deliberate act of returning to old notes through review, search, or serendipity, gives stored knowledge a chance to influence current work.

The system also has to fight two slow forms of decay. Note decay happens when saved material loses context or usefulness because it was never processed into something reusable. Note rot is the gradual loss of value as terminology, projects, or context shifts and the note is no longer interpretable; both can be reduced by adding context at capture time, linking notes to projects, using clear titles, and revisiting notes during reviews. The urgency is sharpened by the idea of the knowledge half-life: in many technical fields, half of what you know becomes outdated within only a few years, so a system that only archives stops being a system. A quarterly review reduces knowledge debt—accumulated gaps and outdated beliefs that eventually cost time and credibility—by deliberately re-reading older notes, checking them against current understanding, and updating or removing what no longer holds. The evergreen garden metaphor captures this lifecycle: fleeting notes are seedlings, literature notes are growing, permanent notes are evergreen, and unneeded notes should be composted—deliberately released from active consideration rather than merely archived. Each new note becomes more valuable as the network grows because it can be linked from and to more ideas, which is why an empty slip-box feels useless at first; a minimum viable network of around 30–50 well-linked atomic notes on a focused topic is enough to start producing insights from connections rather than from any single note.

Several output-focused practices convert stored notes back into living competence. Spaced retrieval re-encounters notes at expanding intervals—1, 7, 30, 90 days—so ideas move from short-term into long-term memory, addressing the plain "use it or lose it" problem. Deliberate practice applies focused, feedback-rich repetition at the edge of your ability rather than passive consumption. The difference between consuming and creating is that creating forces you to organize inputs into artifacts—notes, drafts, code, conversations—and teaching is one of the strongest PKM practices, because it surfaces the gaps in your understanding; if you cannot explain a note in plain words, the note itself is probably incomplete. The Feynman technique makes this concrete: explain the idea as if teaching a beginner, identify where you stumble, return to the source, and rewrite the note until it is clear. Tacit knowledge—the feel of a design, a manager's intuition about a person—is hard to capture directly, but writing down the cases you handled, the cues you noticed, and the outcomes turns pattern recognition into a documented set of examples. A useful ladder runs from case note to lesson note to principle to framework, each rung more abstract and more reusable; principles notes collect tested rules of thumb phrased as imperatives, and framework notes capture reusable mental models such as first principles or 80/20 with their uses and limits. Finally, conditions for serendipity—dense linking, diverse reading, time away from notes before revisiting, and tools that surface random or related notes—turn incidental discoveries into a feature, while a skill tree visualizes prerequisites so you can plan learning paths and avoid dead-end investments.