Zettelkasten System: Principles, Structure, and Examples

A Zettelkasten system is a collection of short, addressable notes connected by meaningful references. You use those connections to develop an argument or discover a question, rather than only retrieve something you saved. It is useful when your reading needs to become writing, research, or an explanation you can defend.

Your linked notes hold the thinking; tools like fenbs can keep the reviewed findings, project rules, and next steps an AI assistant needs to use that thinking. The two records serve different purposes. A promising connection in your notes is still a possibility until you decide what to do with it.

Where does the method come from?

Zettelkasten is German for a slip box. Sociologist Niklas Luhmann described his working collection in Communicating with Slip Boxes↗ (opens in a new tab). Stable positions and references let him connect notes without putting every idea into a rigid subject hierarchy. His account describes a personal working method, not a universal software specification.

The University of Bielefeld archive inventory↗ (opens in a new tab) documents numbered notes, cross-references, bibliographic material, and indexes in his collections. Those are useful historical anchors. They do not mean you must reproduce his handwriting, exact numbering, or furniture to build a useful modern practice.

For a first collection, judge the method by a practical question: does revisiting these notes help you think beyond what you remembered from the source? A folder of copied passages may be valuable reference material. It becomes a different kind of resource when your own explanations and connections let you work through a question.

Which principles make the notes useful?

Use the following as starter rules for your own practice. Their purpose is to make notes understandable and reusable, not to pass a test of historical purity. You can change the format when you find a clearer way to do the work.

• Give each note a clear subject. A title such as “A missing receipt blocks reimbursement” is easier to use than “Finance thoughts.”
• Explain the idea in your own words. Separate a direct quotation from your interpretation, and keep the source location beside both.
• Make the note understandable later. Define an unfamiliar term instead of assuming you will remember the surrounding chapter.
• Link for a reason. Say whether another note supports, challenges, qualifies, or applies the idea.
• Preserve a dependable address. Other notes should still reach the idea after your collection grows.

A short note can still need several paragraphs. Split it when two ideas need different explanations or different connections. Splitting every sentence into a new file can make an argument harder to follow. The useful unit is an idea you can explain and reuse, with enough context to avoid misreading it.

What structure should a beginner use?

Start with three kinds of material: sources, idea notes, and entry points. Sources tell you where information came from. Idea notes develop your interpretation. Entry points gather links around a question you want to explore. Keep a temporary inbox only if it helps you capture things before processing them.

Do not make the entry point a complete catalog of every note. For an essay about workplace forms, it might link to three competing explanations for incomplete submissions. That gives you a route into the material. You can add another route later when a different question becomes important.

The broader second-brain collection covers other ways to organize knowledge. If you want a particular app implementation, use the separate Roam Research guide.

How do identifiers and links work?

Choose an address you can keep: a unique filename, an app-generated note ID, or a number written on a paper slip. A simple digital example is N014-receipt-requirements. Do not renumber the collection whenever your understanding changes. You can revise the title or explanation while keeping references dependable.

In Obsidian, internal links↗ (opens in a new tab) can point to another note, a heading, or a block. The app supports both its double-bracket links and Markdown links. Choose the format your other tools can read; a link that works in one app may need different handling after export.

Write a sentence beside a useful connection: “N022 offers a competing explanation: people may understand the requirement but lack the document.” That sentence saves future you from guessing why you linked the notes. A shared tag such as forms identifies a subject, but it does not explain the relationship.

What does a worked example look like?

Say you are studying how to improve a fictional college reimbursement form. During a practice exercise, you notice that a participant leaves the receipt field empty. Your first record should describe that limited observation. It should not announce that all students find the form confusing.

1. Keep the observation and its source: practice session A, task three, receipt field left empty. Mark the example as a fictional exercise.
2. Write an idea note: “A form can ask for a document without explaining which documents qualify.” Add the limits of the observation.
3. Create a competing note: “A missing attachment can mean the document is unavailable.” Explain what evidence would distinguish the explanations.
4. Connect both to an entry point: “Why do people stop at the receipt step?” Add a next research question rather than a premature answer.

The collection now gives you something to investigate. If you later revise a form, keep that project decision separate from the research possibility. In fenbs project context, you can record the chosen wording and the outstanding check without presenting your entire note collection as approved instructions.

When is the extra work worth doing?

Try the method when you return to the same questions across several sources. It can suit an extended paper, a research practice, or recurring professional writing. For a grocery list or a document you only need to locate, a searchable folder may do the whole job with less maintenance.

Watch for three traps: copying without interpreting, linking without explaining, and organizing instead of producing work. A useful review ends with a better question, a clearer argument, or a draft paragraph. It does not need to end with a more elaborate graph. Test your collection by using it for an actual piece of writing.

AI can suggest connections, but you should check the cited passages and decide whether the relationship holds. Give it a narrow request using the ideas in our system prompt examples. If you are evaluating storage for an AI application itself, choosing an agent memory system addresses that separate decision.

How to do this with fenbs

1. Create a free account and add the writing or research project that your notes support.
2. Add a concise AI context note containing the reviewed findings, their source references, and the questions that remain open.
3. Record the choices you make in Decisions and rules. Keep a hypothesis in a note until a person actually chooses a course of action.
4. Connect a supported assistant from Integrations. Ask it to read the project context before drafting, then save progress with the remaining checks before it stops.

fenbs is free for one person, no credit card. It is not the right fit if your only need is a paper slip box or an editor for linked notes. Keep that collection in the medium you prefer; use fenbs when the work it informs needs decisions, tasks, and continuity across assistant sessions.