How to Set Up a Digital Zettelkasten You Will Use

To set up a digital Zettelkasten, choose one place to write notes, capture ideas in your own words, and connect each lasting note to relevant ideas with an explanation. Start with a question you need to answer, then add only the organization that helps you find and use the notes.

The aim is a collection you can think with, not a perfect filing system. When an idea changes ongoing work, fenbs can retain the project decision and next step for connected assistants. Your note collection can stay where you prefer to read and write.

What should you do in the first session?

1. Write one active question at the top of a starting note. Make it specific enough that new material can help answer it.
2. Create a capture area for rough observations, source references, and questions you do not want to interrupt your work to develop.
3. Turn one worthwhile capture into a note that explains a single useful idea in your own words.
4. Write a second note that supports, challenges, or applies the first. Link them and explain the relationship.
5. Create a small index that points to these notes and records the next question you want to investigate.

For example, a designer might start with “How can our project estimates explain uncertainty?” One note could distinguish a planning assumption from a promise. Another could describe when a range helps a client understand risk. The connection matters because it helps the designer write a clearer estimate.

Stop there and use the notes before importing a whole archive. The broader second-brain library covers related ways to keep knowledge. This setup succeeds when it helps with an actual question, even while the collection is small.

What does the software need to support?

Look for a comfortable writing surface, a dependable way to find a note, and links you can follow later. Test your intended workflow with two notes before adding extensions or elaborate rules. Check how you will keep a copy of your work and what happens to references when you rename something.

Use the linking syntax your chosen app actually supports. For example, Obsidian documents both double-bracket links and Markdown links in its internal-link guide↗ (opens in a new tab). Those are specific software features, not requirements that every note app follows in the same way.

An ordinary document can also hold a small collection, provided you can reach individual ideas. Google Docs documents links and bookmarks↗ (opens in a new tab) for that purpose. You still need to explain why two passages belong together; navigation does not create the reasoning.

Avoid choosing the entire system around a feature you have not needed yet. Your first practical test is whether you can return tomorrow, find the note, understand its point, and continue thinking. If that works, you have enough structure to begin.

How do you separate captures, sources, and your own ideas?

Captures are temporary reminders. Source notes describe material you encountered and where to find it. Lasting idea notes explain your own reasoning in a form you can reuse. These are working distinctions you can put in headings or note labels; they do not require a separate app for each kind.

Keep enough source detail to verify your interpretation. Zotero distinguishes notes attached to a particular source item from standalone notes in its notes documentation↗ (opens in a new tab). Whether you use that app or another method, preserve the difference between what the source says and what you infer.

What makes a note useful beyond today?

Give it a title that makes a claim or asks a precise question. Explain the idea without assuming you remember the conversation that produced it. Include an example and any important limit, especially when the idea came from one incident rather than broader evidence.

For the estimate example, “Assumptions” is a topic label. “An estimate becomes easier to revise when its assumptions are explicit” states an idea you can examine. Add why you think this is true, what experience or source supports it, and when more explanation might overwhelm the reader.

Keep a note together when its parts depend on one another. Split it when separate arguments need their own connections or evidence. You do not need every note to have the same length, and a short paragraph is not automatically a complete thought.

How should you connect notes and review them?

Write the reason for each important connection in a sentence. “This challenges the earlier note because a client may read a range as indecision” is useful. A list of related titles without explanation leaves your future self to reconstruct the argument.

Use the index to suggest a few reading paths around real questions. It should point to entry notes, disagreements, and gaps rather than reproduce the contents of the entire collection. Add another index when a new question deserves its own route, not because a folder feels untidy.

During review, develop worthwhile captures, correct unclear notes, and follow a few links. Ask whether the collection changed your explanation or revealed a question you had missed. If nothing is being used, narrow the question before spending more time on organization.

When should an idea become a task or decision?

A lasting note describes something worth considering again. A task says what somebody needs to do. A decision records what a person chose for a particular situation. Keep those meanings distinct so an assistant does not turn a tentative idea into an instruction.

The designer might retain the general note about assumptions, then decide to test a short assumptions paragraph on the next proposal. The task is to draft and review that paragraph. If the experiment is unfinished, a clear AI handoff needs its current status and next check, not the whole history of the note collection.

How to do this with fenbs

1. Create a free account. One person can start free with no credit card.
2. Add your active project and a context note explaining the reviewed insight, its source reference, and what remains uncertain.
3. Record the approved choice in Decisions and rules, then create a task describing the next action and how you will check it.
4. Connect your assistant from Integrations. Ask it to read project context before working and save progress before stopping.

If you only want a personal place to read, link, and develop ideas, your note app may be sufficient. fenbs fits when those ideas guide ongoing work that people and connected assistants need to pick up again.