'A System for Writing' - Practical Note-Taking and Writing Tips with Zettelkasten Expert Bob Doto
Based on CombiningMinds's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
English terminology in Zettelkasten discussions can create misunderstandings when note types are treated like rigid “objects” rather than descriptive categories.
Briefing
A practical writing system beats “perfect” note-taking—especially when it’s built to answer real confusion about how ideas move from reading to notes to drafts. Bob Doto, a Zettelkasten practitioner and author, pushes back on the common failure mode where people adopt terminology and structure from Nicholas Luhmann’s tradition without resolving the misunderstandings that come with it. The result is a system that’s less about rigid taxonomy and more about friction, curation, and deciding what deserves to interact with other ideas.
The conversation starts with why Zettelkasten newcomers get stuck after reading “How to Take Smart Notes.” Doto points to inconsistent English terminology—especially the way “literature note” and “fleeting note” read like distinct “objects” rather than descriptive categories. That mismatch, he says, can make readers treat note types as fixed things instead of as roles in a workflow. Worse, he argues that inconsistent usage of terms like “permanent note” (sometimes meaning all stored notes, sometimes meaning something narrower) fuels micro-culture confusion that then self-perpetuates through articles and summaries. Doto’s own book, by contrast, is framed as a long-running effort to answer the same questions repeatedly—“what is a literature note?”—until the language becomes usable rather than mystical.
From there, the discussion turns to the mechanics of writing long-form work. Doto distinguishes between keeping notes in a Zettelkasten “container” and reorganizing them later for actual writing. In his view, full “gazettal” isn’t an outline; it’s a relationship map. Notes in the main compartment should remain intentionally disjunctive so they can inform each other without forcing premature hierarchy. When it’s time to draft, ideas get pulled out and reorganized into a structure that matches the writing task—then the system can stay clean.
The guest’s experience with Logseq highlights a modern twist: drag-and-drop and outline-like navigation can feel liberating, but it also risks collapsing the separation between storage and drafting. Doto acknowledges the tension and reframes it: Zettelkasten practice relies on context and “hard addresses” (in Luhmann’s paper-based world) so a note can be revisited in the context that created it, even if it later gets used differently. The key is not preserving everything forever, but preserving what has a future function.
That principle shows up in the debate over version control and feedback. Doto argues that beta-reader comments and draft iterations often don’t belong inside the Zettelkasten once their job is done; the question is what function they serve. If comments improve writing style for a specific draft, they can live in a folder or archive rather than clutter the idea network. Similarly, saving every revision is usually psychological overreach: writers have limited time, and working writers can’t afford to treat drafts like permanent artifacts.
Finally, the conversation lands on a broader creative ethic: let imperfection and forgetting exist. Writing output, not system purity, is what sustains the workflow. Doto encourages writers to focus on what they want ideas to do—interact, cite, or inspire—then add friction where it helps thinking slow down, not where it turns note-taking into a substitute for drafting.
Cornell Notes
Bob Doto argues that Zettelkasten-style note-taking works best when it’s designed to resolve confusion and support writing, not when it chases perfect structure. He criticizes inconsistent terminology in “How to Take Smart Notes,” especially how English treats “literature note” and “fleeting note” as if they were fixed objects, and how inconsistent use of “permanent note” spreads misunderstandings. In his workflow, notes stay in a simple container to preserve relationships, while outlining and reorganization happen later when drafting begins—“gazettal” is not an outline. He also warns against hoarding: beta-reader comments and draft versions often don’t need to be imported into the idea system if their function is already complete. The payoff is a cleaner system that makes room for writing, revision, and forgetting.
Why does confusion about Zettelkasten terms persist after reading “How to Take Smart Notes”?
What does “gazettal” mean if it isn’t an outline?
How should a writer decide whether to import feedback or comments into the Zettelkasten?
What’s the role of context when notes originate from conversations, interviews, or external sources?
Why does Doto discourage saving every draft version and every iteration?
How does Doto connect system design to actual writing output?
Review Questions
- What specific terminology inconsistencies does Doto identify as drivers of confusion, and how do they change reader behavior?
- How does Doto’s “gazettal is not an outline” principle affect when and how outlining should happen during drafting?
- What functional criteria should determine whether feedback, comments, or draft versions get stored in the Zettelkasten?
Key Points
- 1
English terminology in Zettelkasten discussions can create misunderstandings when note types are treated like rigid “objects” rather than descriptive categories.
- 2
Inconsistent definitions—especially around “permanent note”—can propagate confusion through communities and secondary articles.
- 3
Keep Zettelkasten storage simple and relationship-focused; reorganize into an outline only when drafting requires structure.
- 4
Import material into the idea system only when it has a future function (e.g., it should interact with other ideas), not merely because it was produced during a draft.
- 5
Beta-reader comments and draft iterations often belong in an archive rather than inside the Zettelkasten once their purpose is complete.
- 6
Saving every version is usually unsustainable for working writers; extract reusable ideas and let the rest go.
- 7
A sustainable workflow leaves room for imperfection and forgetting—writing output, not system purity, drives progress.