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.