Why Zettelkasten Fails in Obsidian
Zettelkasten can turn an Obsidian vault into a maintenance project. Keep the useful principles while dropping addresses, forced links, and atomic note rules.
What the original Zettelkasten solved
A physical slip box has no search field. You cannot type a phrase and see every matching card, so you need an address system that explains where a card sits and how to reach related cards.
Niklas Luhmann used numbered addresses and links between slips to solve that physical retrieval problem. A new card could branch from an existing one; its address preserved the relationship while giving it a stable place in the box.
The useful principle was not the numbering format. It was that a note should remain findable and connect to work you may do later.
Obsidian changes the medium. You can search every note, follow backlinks, add aliases, and link phrases directly. Reproducing a paper address system adds work without restoring a missing capability.
Why the Obsidian version becomes exhausting
A typical digital Zettelkasten introduces several decisions for every idea:
- Is the idea atomic?
- What is its title?
- Does it need an identifier?
- Should it be rewritten in permanent language?
- Which notes should link to it?
- Does an index note need updating?
Each choice looks small, but together they make capture expensive—especially while a thought is still developing.
A useful research note may contain a quotation, objection, question, and connection to a current project. Splitting it immediately can destroy the context that made the material interesting. You then have to interrupt your thinking to maintain the vault or save a rough note that appears to violate the method. After enough repetitions, many people stop capturing.
The same problem appears when Obsidian and Notion become too complicated for simple notes: the system consumes attention that should have gone into reading, thinking, or writing.
Atomic notes are optional
An atomic note contains one idea that can stand alone. That can help when assembling a book chapter or comparing arguments from several sources, but it is not a rule you must obey during capture.
Let the first note match the thought:
- A paragraph is fine.
- A page is fine.
- A rough collection of quotations and reactions is fine.
Split it later if a real project needs smaller pieces. At that point, you know which distinctions matter and are editing for a purpose instead of predicting every future use.
This also preserves context. Highlights and isolated quotations often become difficult to interpret after the reading session, a problem explored further in why Readwise highlights lose context.
Replace addresses with searchable context
You can make a note retrievable without a code such as 4b2c. Include:
- A plain title containing words you would search for.
- The original source or link.
- The date, when timing matters.
- One sentence explaining why you saved it.
- A related-note link when the relationship is already clear.
Do not add links just to make the graph look connected. A link is useful when following it helps continue a line of thought. Decorative links make the graph denser without improving retrieval.
Treat tags with the same restraint. Use one when it supports a repeated search or workflow; do not build a complete taxonomy before you know which categories matter.
A simpler Obsidian setup
Start with one capture folder and one folder for active projects. Everything else is optional.
When capturing, give the note a recognizable title and enough context to remain useful. Leave it in capture unless an active project needs it elsewhere.
When you begin writing or planning, search using the language of the task. Open relevant notes and create links while combining them into an outline or draft. Organization then happens when it produces value, rather than in case it might become useful.
If you think spatially, folders and lists may still feel restrictive. These Heptabase alternatives for visual thinkers show ways to use visible clusters instead of a large text graph.
Do not rebuild an existing vault
If the vault already contains permanent IDs and hundreds of linked notes, keep it intact. A complete migration creates another long project with little immediate return.
Use the simpler approach for new material. Search old notes when needed, and rename or split an old note only when it enters active work. The vault improves through use while preserving links that already help, without requiring continued obedience to the entire method.
When Zettelkasten still makes sense
The full method may suit you when maintaining the system is part of your thinking. It can also work for a long writing project with a stable subject and a growing set of arguments.
It is a poor fit when you change topics frequently, mostly collect reference material, or resent processing notes after capture.
Use a simple test: search for an idea recorded several months ago and use it in something you are making. If you can do that reliably, the system works. The cleanliness of the graph, number of links, and purity of each note do not matter.