#3 Collaboration, or what? (Plus 2 BREATHTAKING LIVE Demos!) • Zettelkasten Live

Collaboration in the Zettelkasten world works best when it’s designed around shared method—not shared authorship. Two writers describe how a German book on the “Selle custom” (Zettelkasten) method started as a joint manuscript idea, but the practical outcome became mostly one person’s notes with the other adding selective “spicing.” The key lesson: collaboration only stays smooth when the collaborators think in compatible ways and can interpret each other’s notes without constant translation.

Their process began with archives already built from using the method for about one or two years. Each person had dozens of notes (one archive reportedly had 144 notes; the combined project ended up around 100 note files after filtering and discarding confusing or unhelpful material). Instead of trying to merge everything immediately, they created a list of note titles, organized chapters from those titles, and brainstormed outlines. The original plan—each person producing their own outline and then merging—fell apart, largely because integrating drafts was painful and time-consuming. In practice, the manuscript writing became a single voice, with the other collaborator contributing expansions and additions when the timing and structure allowed.

Beyond logistics, the discussion puts heavy weight on note craftsmanship, especially titles. Notes are treated like blog posts: readers (including future readers) have little patience for cleverness or word games. Titles should be plain, direct, and specific enough that the note can be found and understood years later. The writers argue that “meticulous” naming is not aesthetic fussiness; it’s a survival strategy because memory fades and even the author won’t reliably recall what a note meant.

When the conversation turns to what collaboration means, two distinct questions emerge. First: does the Zettelkasten method itself play a role in collaboration? The answer is yes, but only in certain collaboration styles—like sharing finished text or using outlines as a shared structure. If collaboration is split into independent sections (common in academic papers), the method doesn’t automatically unify the work; it mainly helps with organization and later retrieval.

Second: how can people collaborate with “set of customers” (read: other contributors or collaborators) using the method? Their approach relied on sharing a Dropbox folder containing each person’s notes and then writing separately while still being able to understand what the other was doing. They emphasize that this works when backgrounds are similar enough that notes remain interpretable. Cross-disciplinary collaboration—like a physician collaborating with a physicist and then adding a biologist—can create friction if notes are mixed in one repository without a shared interpretive frame.

The episode also broadens into open-science and tool strategy. Plain text is presented as the backbone of software-agnostic note-taking: it makes multi-author editing feasible and reduces lock-in. The discussion contrasts plain-text workflows (where diffs can be merged line-by-line) with Word-style collaboration that often forces file splitting and comment-based review. Finally, the live demo explains how notes “communicate” through links: start with a concept note, branch into structured “processing” notes, and later refine by replacing broader links with more specific ones during maintenance. The overall message is pragmatic: collaboration is less about merging everything at once and more about building interoperable archives, disciplined titles, and a shared method that survives time, tools, and authorship changes.