A Real Zettelkasten Workflow in Obsidian

A Zettelkasten workflow built around Obsidian hinges on one practical idea: write single-idea notes, then make meaning by linking them in a non-hierarchical network—so new insights emerge from the connections rather than from a top-down taxonomy. Participants frame Zettelkasten (often “ryome” or “ryomatically”) as a system for thinking that becomes especially powerful for writing, because the network of linked notes turns research fragments into drafts, structure notes, and eventually publishable output.

The conversation starts by defining Zettelkasten as a “network of single idea notes” connected without strict hierarchy. Instead of organizing knowledge by categories, the system treats each note as an addressable unit that can inform other notes. Linking—whether via digital links or paper-style references—creates a web where unexpected relationships can surface. That web, in turn, supports writing: one participant uses the system explicitly as a “system for writing,” while another uses it more as a way to understand the world, with creation and feedback as downstream effects.

A key workflow emphasis lands on the later stages of the process: connecting ideas and producing writing. Participants outline a common four-part arc—consume material, create fleeting notes, convert them into permanent “main notes,” then connect and write—but they push hardest on the mechanics of linking and on how to turn connections into structure notes. Structure notes are described as a thinking space: they pull together related single-idea notes, add transitional language, and expose gaps or questions. A live example shows a structure note on “Pratihara,” where linked notes from multiple traditions (Hindu and Christian perspectives) are gathered under headings like “What is Pratihara” and “Pratihar and effort,” then rewritten into a more coherent internal argument.

The discussion then gets technical about identifiers and plugins. Some participants debate Folgezettel-style alphanumeric IDs (inspired by Nicholas Luhmann) versus relying on digital linking and native hierarchy. In digital systems, IDs aren’t strictly necessary, but they can still help: long identifiers can act as “forcing functions” that require each note to connect to something else, and they provide quick visual cues in a sidebar about what cluster a note belongs to. Others argue that digital tools can replace much of the need for IDs by using structure notes and named links.

Obsidian-specific tooling becomes a centerpiece. One participant demonstrates a “breadcrumbs” approach that auto-infers parent/child relationships from links, enabling bottom-up navigation of the Zettelkasten tree without manually encoding sibling relationships. The demo also highlights a practical principle: automation should not replace the human work of deciding what a link means. Links can be inferred, but the interpretation—why two ideas belong together—still requires natural-language context inside the notes.

Finally, the group offers startup guidance: begin with one note and create a second only when it relates; always link rather than letting notes float unconnected. Some recommend reading “A System for Writing” as a foundation, then building literature notes in Obsidian (optionally using Readwise import). The overall takeaway is that Zettelkasten succeeds less through perfect organization and more through sustained, deliberate linking that gradually reveals what a writer actually cares about and what they should explore next.