Get AI summaries of any video or article — Sign up free
How to Take Smart Notes - Book on a Page thumbnail

How to Take Smart Notes - Book on a Page

5 min read

Based on Zsolt's Visual Personal Knowledge Management's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Treat notes as part of the thinking process: ideas become actionable only when written and structured for later recombination.

Briefing

Smart notes aren’t a productivity accessory—they’re the mechanism that turns thinking into usable knowledge. The core claim behind the Zettelkasten (“slip box”) approach is that writing on paper is part of the thinking process itself: ideas become real only when they’re externalized as notes that can be rearranged, linked, and reused. That matters because contemporary learning and research depend on external scaffolding; without it, the mind can’t reliably hold, develop, or retrieve complex reasoning.

At the center of the method is a simple, repeatable workflow built to make progress feel immediate. Instead of starting with a topic, doing research, and then writing from scratch on an empty page, the system works bottom-up: capture ideas as they arise, file them into a structured note network, and later assemble them into drafts. The transcript contrasts this with the “status quo” academic pipeline—choose a topic, search literature, take notes, outline, write, and hope the deadline lands—where notes often end up compartmentalized and writing becomes a slow, goal-driven grind. In the Zettelkasten approach, the “atomic” steps (read, write a note, link it, sequence it) create short feedback loops, so momentum doesn’t depend on finishing a large project.

The method traces its inspiration to German sociologist Niklas Luhmann, who built an enormous personal knowledge system: roughly 90,000 notes total, including about 1,200 index entries, around 600 manuscript outlines, and approximately 15,000 literature notes. The transcript uses his output to argue that the volume is manageable when notes are captured consistently—about six notes per day on average when counting workdays. Luhmann’s system relied on multiple note types. “Permanent notes” contain one idea per slip, written in full sentences with precise references, while “literature notes” record what was read (paraphrased in the reader’s own words) alongside bibliographic details and page numbers. “Fleeting notes” act as a temporary scratchpad for ideas that get processed later.

A key design choice is standardization: one idea per note, brief and selective entries, consistent formats, and a workflow that reduces decision fatigue. The transcript uses a shipping-container analogy to make the point: end-to-end standardization makes the whole system more efficient, and similarly, standardized note formats make it easier to connect ideas without spending mental energy on how to store them. Creativity then emerges from the ability to link across domains—because the system is interlinked rather than a set of isolated folders.

When it’s time to write, the system avoids brainstorming from memory. Instead, writers select an existing sequence of notes and turn that sequence into linear text, using the note network as a reservoir of arguments, examples, and citations. Topics “emerge” from clusters in the hierarchy, supported by Luhmann’s numbering scheme that encodes depth and branching. The transcript also emphasizes that note-taking must be selective to preserve the ability to forget and remember; capturing everything leads to dilution, while capturing nothing leads to loss of knowledge. The payoff is compounding: small, correctly filed ideas accumulate into deeper understanding, and the workflow—more than raw talent—drives learning through frequent, fast cycles of writing, linking, and revising.

Cornell Notes

The Zettelkasten (“slip box”) approach treats notes as part of thinking, not as a record after the fact. It replaces top-down academic writing (topic → research → write from an empty page) with a bottom-up workflow: capture fleeting ideas, convert them into permanent and literature notes, link them in a structured hierarchy, and later assemble selected sequences into drafts. Standardization—one idea per note, brief/selective entries, and consistent processing—reduces decision fatigue and creates short feedback loops that sustain motivation. The transcript uses Niklas Luhmann’s productivity and note volume to argue that the system is doable and that topics emerge from clusters in the note network. The result is compounding knowledge: byproducts of one project become inputs for the next.

Why does the transcript insist that writing is part of thinking rather than a separate task?

It leans on the idea that intellectual work happens on paper. The anecdote about Richard Feynman contrasts “notes as a record” with “notes as the thinking process,” arguing that without writing he couldn’t do the work. Neil Levy’s observation reinforces the same point: notes don’t make thinking easier by themselves, but they make it possible by providing external scaffolding for a mind that can’t reliably hold everything internally.

How does the Zettelkasten workflow differ from the usual academic pipeline?

The “status quo” path is top-down: pick a topic, research and read, take notes, outline, write, and then start over with an empty page. The Zettelkasten path is bottom-up: read and process ideas into a growing network of notes, then later select and sequence existing notes to draft and publish. Instead of brainstorming from memory, writing begins by assembling a set of notes already stored in the system.

What are the three major note types, and what job does each one perform?

Fleeting notes capture raw ideas immediately (even on a napkin) and are reviewed daily while context is still fresh. Literature notes store paraphrased takeaways from sources along with bibliographic details and page numbers—without copy-pasting. Permanent notes (“zettels”) hold one idea per note in full sentences, written in the context of other permanent notes, with precise references; they’re filed into the hierarchical structure and linked to related ideas.

What does “standardization” buy, and why is it compared to shipping containers?

Standardization makes the system efficient end-to-end. The shipping-container analogy argues that individual actors may prefer older methods, but global efficiency arrives only when every step (factories, trucking, cranes, ships, warehouses) uses a shared standard. In notes, consistent formats (one idea per note, selective brevity, repeatable processing) reduce decision-making and make linking and retrieval smoother—freeing attention for writing and connecting ideas rather than managing the system.

How do topics “emerge” in a Zettelkasten system?

Topics emerge from clusters within the hierarchical note structure. The transcript highlights that Luhmann’s numbering scheme encodes depth and branching, so the structure itself signals how many related thoughts exist and where they sit in the “tree.” It also mentions special permanent notes like overview notes (covering a topic with entry points) and summary notes (covering a cluster with a map of what’s inside).

Why does the transcript warn against making everything a permanent note or everything a fleeting note?

If everything becomes permanent, the system loses the ability to forget and select; the value of the slip box dilutes. If everything stays fleeting, notes pile up and create a recurring “clear the house” cycle, causing important ideas to be discarded and knowledge to be lost. The workflow’s selectivity is presented as essential for long-term compounding.

Review Questions

  1. How does the Zettelkasten approach change the moment when writing begins, and what replaces brainstorming from memory?
  2. What distinguishes literature notes from permanent notes in both content and purpose?
  3. Which mental-resource constraints (attention, short-term memory, motivation) does the workflow target, and how does the “atomic” step design help?

Key Points

  1. 1

    Treat notes as part of the thinking process: ideas become actionable only when written and structured for later recombination.

  2. 2

    Use a bottom-up workflow: capture and process ideas into a linked note network, then assemble sequences into linear drafts when publishing.

  3. 3

    Standardize note formats and processing steps (one idea per note, selective brevity, consistent workflow) to reduce decision fatigue and sustain momentum.

  4. 4

    Separate note types by function: fleeting notes capture context quickly, literature notes paraphrase sources with bibliographic details, and permanent notes store one idea in the context of other notes.

  5. 5

    Build a hierarchical structure (not just a web of links) so “going deeper” and “cross-linking” serve different navigation purposes.

  6. 6

    Avoid extremes: selective forgetting is necessary—capturing everything dilutes value, while keeping everything fleeting creates recurring loss cycles.

  7. 7

    Focus on distillation and elaboration (connecting and reframing ideas) rather than rereading and repetition-only memorization.

Highlights

The transcript’s central reframing: writing isn’t a chore; it’s the mechanism by which thinking happens and becomes retrievable.
Niklas Luhmann’s scale—about 90,000 notes and roughly six notes per workday—serves as evidence that the system is practical, not mystical.
A shipping-container analogy argues that end-to-end standardization is what unlocks efficiency—and the same logic applies to standardized note formats and workflows.
Instead of brainstorming topics, the method selects from already-accumulated note clusters; topics “emerge” from the structure of the slip box.
The workflow is designed for short feedback cycles: small atomic tasks keep attention and motivation from collapsing over long writing timelines.

Topics

Mentioned