160 cards
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...
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, finan...
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 pipel...
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 numbe...
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, f...
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 bidirectio...
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...