Second Brain vs. Zettelkasten: How to Combine Them

A second brain and a Zettelkasten solve overlapping problems: a second brain helps you keep and use knowledge, while a Zettelkasten develops ideas through connected notes. You can combine them by organizing active work around projects and keeping reusable ideas in a linked note collection.

The distinction matters when a useful observation becomes a real assignment. Your notes might explain why a design works, but they do not necessarily say which design was approved or what remains unfinished. Tools like fenbs keep that active work and its decisions outside the note collection, available to connected assistants.

What is the practical difference?

These are useful emphases, not opposing rules. A project collection can contain thoughtful linked notes, and an idea archive can support deadlines. The question is where you want to spend your attention: finding material for something you are doing, or developing thoughts whose eventual use may be unknown.

For the broader definition, read what a second brain is. Here, the decision is about how your notes should behave once you have started saving them.

Which approach should you start with?

Start with a project-oriented second brain when you repeatedly lose information needed for current work. Say you are preparing a community event: you need the venue instructions, approved poster, contact notes, and draft schedule together. A collection organized around that event gives those materials a clear immediate use.

Start with linked permanent notes when your main challenge is developing ideas across many pieces of reading. A permanent note is a thought written so you can understand and use it later without reconstructing the original conversation. Its value comes from the idea and its relationships, rather than the folder containing it.

Tiago Forte describes the knowledge workflow behind Building a Second Brain in his introductory guide↗ (opens in a new tab). The Zettelkasten method overview↗ (opens in a new tab) emphasizes writing about a focused topic and connecting notes. Read the original explanations, then test the habits against work you actually do.

You do not need to turn every receipt, meeting agenda, or rough sketch into a permanent note. Some information is useful only because a project is active. Conversely, a durable insight should not disappear simply because you completed the project that first made it interesting.

How can you combine them without keeping two copies?

Give each piece of information one main home. Keep the source as evidence, write your reusable idea as a note, and refer to that note from the project using it. A link lets you reuse the reasoning without creating a second version that can drift.

1. Capture the source with its title, author, location, and the reason you saved it. A bare link rarely explains why future you should open it.
2. Write a focused note when you have a thought worth developing. State the claim in your own words and distinguish your interpretation from the source.
3. Connect that note to another idea and explain the connection. A link labeled with a reason is more useful than a collection of unexplained references.
4. Point the active project to the note when it informs the work. Record the project decision separately, including what the person approved and what happens next.

For example, an event poster project might use a note about making dates easy to scan. That note can also help with a future class schedule. The decision to use a particular layout belongs to the poster project; the broader observation can continue developing after the poster is printed.

When those source links lead to live work, fenbs keeps Links and listings alongside project context, so the next assistant can see what the reference was used for.

What would this look like in Obsidian?

Obsidian supports links between notes, including links to a heading in another note, as its internal links documentation↗ (opens in a new tab) explains. That gives you a straightforward way to connect a project page, a source note, and a reusable idea. You can use that capability without needing a complicated folder system.

Say you are drafting an onboarding guide. Create a project note with the intended reader and the material you need. Create a source note for an interview and a separate idea note explaining a recurring point of confusion. Link the project to the idea with a sentence about how it could improve the guide.

Project: New member guide
Goal: Help a new member complete their first request.
Relevant idea: [[Examples should show the first complete action]]
Reason: Readers know the policy but cannot picture the first step.

Idea: Examples should show the first complete action
Claim: A useful example shows the input, the action, and the result.
Evidence: Interview notes from the guide project.
Connection: [[Instructions need a visible stopping point]]
Question: When does a worked example become too specific?

The example is a proposed layout, not a requirement of either method. Keep the note readable enough that someone can understand its claim without opening every link. If you need a full app setup, the Obsidian second brain guide covers that neighboring question.

An approved instruction for the guide should still have a clear project record. An idea can be plausible and useful without being the instruction the team has chosen to follow.

What changes when an AI assistant reads the notes?

An assistant needs a smaller, clearer starting point than your entire archive. Give it the current question, the relevant notes, and the status of their claims. Ask it to distinguish a source statement, your interpretation, a proposal, and an approved decision.

In the onboarding example, an assistant could compare two note ideas and propose a clearer example. It should not infer that an interview comment is an approved policy. Require it to name the source supporting each important factual change and ask when the project record leaves an approval unresolved.

The AI second brain guide explains the wider role of reusable knowledge for assistants. For this combined setup, the important boundary is simple: reading useful notes does not make every note an instruction.

Keep private reflections out of a shared work packet unless they are needed and appropriate to share. A personal archive can serve many purposes, while a project assistant only needs the information relevant to its assignment. Review the actual material you provide before asking it to continue.

How to do this with fenbs

1. Create a free account, then add the project your notes are helping you complete.
2. Add the current tasks and the useful references in Links and listings. Keep the original notes where you maintain them; include enough explanation to show why each reference matters.
3. Record what people have chosen in Decisions and rules. Leave interpretations in context notes and unresolved choices as open questions.
4. Connect a supported assistant using Integrations. Ask it to read the project context before working and consult the relevant source material through the access you provide.
5. Before stopping, save what changed, what was checked, and the next step in Where we left off. Add a lesson when applying a note taught you something new.

fenbs does not replace Obsidian as a linked writing environment, and it does not automatically read your note collection or import its contents. It fits when the missing piece is the live work record. If your only need is private reading and idea development, a note collection may be enough.

How do you know the combination is helping?

Test a small cycle instead of reorganizing everything. Choose one project, save a useful source, develop one connected idea, apply it, and record the outcome. Then close the notes and try to resume the work later from what you saved.

You should be able to explain what the idea means, why it applies, what the project chose, and what remains. If one of those answers is missing, repair that part of the system. Adding more tags or links will not answer an approval question that nobody recorded.

After the project ends, retain the ideas that still have something to say and the work record that explains the outcome. Our second brain articles explore other setups; the broader AI brain introduction explains why work context needs a dependable home.