Organize Your Knowledge with Zettelkasten
Based on trms's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Capture ideas immediately in an inbox, then rewrite source-based ideas in your own words to ensure processing.
Briefing
Zettelkasten turns scattered notes into a connected knowledge system by forcing ideas into small, linkable “atomic” entries with stable identifiers. The payoff is not just organization—it’s the ability to trace how concepts evolve through chains of related notes, which can accelerate writing, research, and new questions.
The method draws inspiration from Niklas Luhmann, a German sociologist who—despite not formally studying sociology—built a prolific academic output using thousands of small paper slips. Each slip held one idea in the center, with a number in the top-left corner so notes could reference one another. Luhmann stored the slips in boxes and used cross-references to build intellectual networks. The transcript credits this approach with helping him become a professor at the University of Bielefeld and publish roughly two books per year until his death.
To replicate the core mechanics digitally, the workflow starts with an “inbox” for fleeting notes. Whenever an idea appears—whether from reading, conversation, or observation—it gets written down immediately in the nearest place, physical or digital. The key is processing: if the idea comes from a source, it should be rewritten in one’s own words rather than copied verbatim. Notes also need bibliographical metadata (title, author, and other source details) so the origin can be revisited later.
Next comes the “slip” stage: moving inbox notes into permanent entries inside a dedicated folder (the example uses a folder named zk-demo). Each note should receive a unique ID, with the transcript recommending a date plus time for filenames. The practical reason is stability: filenames can change if titles change, but an ID functions like a permanent link. In the note body, writers should link to other notes as often as possible, since the system’s purpose is to explore connections rather than merely store information.
The transcript emphasizes atomization: keep notes as small as possible. If an idea won’t fit, split it into multiple slips. Smaller units create more links and therefore more pathways for discovery. For grouping, the method uses tags (via a hash sign like #tag), leveraging software that supports tags such as iA Writer and Obsidian. Tags can be derived from a simple internal sentence—“This note is about X, Y, and Z”—allowing multiple tags per note.
After building the collection, the next step is to mine it: look for what’s present, what’s missing, and what questions arise. Instead of brainstorming in isolation, the transcript advises following the chains already forming in the slip-box—clusters tend to emerge as interest grows, reading increases, and new notes generate further questions. Finally, the system is presented as adaptable: rules can be bent to fit different fields, whether humanities, software engineering, or history. The overall message is that a well-linked slip-box becomes a “second brain” for developing ideas over time, not a static archive.
Cornell Notes
Zettelkasten organizes knowledge by turning each idea into a small, permanent note that can link to other notes. The workflow starts by capturing fleeting ideas in an inbox, rewriting source-based ideas in one’s own words, and recording bibliographical details. Notes then move into a dedicated slip-box folder with stable unique IDs (recommended as date + time in filenames) so references don’t break when titles change. Each note should be atomized as much as possible, linked to related notes, and optionally grouped with tags (e.g., #X #Y #Z) for faster retrieval. Over time, the slip-box helps generate new questions by revealing what’s missing and where clusters of ideas have formed.
Why does the system insist on stable IDs instead of relying on note titles or filenames alone?
What does “atomize your ideas” mean in practice, and why does it matter?
How should notes be captured and processed when an idea comes from a source?
What role do links and tags play, and how do they differ?
How does the slip-box move from storage to idea generation?
Review Questions
- What steps turn an “inbox” note into a permanent slip, and what information must be preserved during that transition?
- How do stable IDs, linking, and atomization work together to prevent broken references and encourage discovery?
- Why does the transcript recommend looking for “what’s missing” inside the slip-box rather than brainstorming from scratch?
Key Points
- 1
Capture ideas immediately in an inbox, then rewrite source-based ideas in your own words to ensure processing.
- 2
Store permanent notes in a dedicated slip-box folder and assign each note a stable unique ID (e.g., date + time in the filename).
- 3
Use links between notes as the primary mechanism for building connections and exploring how ideas develop.
- 4
Keep notes small—split larger ideas into multiple notes to increase link density and support deeper idea chains.
- 5
Add tags (e.g., #X #Y #Z) to group related notes for faster retrieval, leveraging tag support in tools like iA Writer or Obsidian.
- 6
Include bibliographical information inside notes when ideas come from external sources so references remain traceable.
- 7
Treat the system as adaptable: bend rules to fit the demands of different fields instead of following them blindly.