← archive
002

the second brain that didn’t think

For a long time, I built a note-taking system that was supposed to make me smarter. In the end, I kept only what helps a specific project move forward.

article9 min read

For a long time, I wanted to build myself a second brain.

It sounds convenient: put everything you learn into Obsidian, link your notes together, then retrieve ready-made thoughts when you need them. You become smarter and more productive, and finally stop losing good ideas.

I believed it. I began building the system: folders, rules, names, links. At some point, the system became a pursuit of its own. I spent less time working on projects and more time thinking about how to organise material for future work.

Now I think I had mistaken one thing for another. I was building a warehouse when what I needed was a desk.

the promise of a second brain

The idea itself isn’t foolish. We read more than we can hold in our heads. We collect thoughts, links, quotes and observations. Writing things down really can ease the burden on memory and help us return to material.

The problem starts when note-taking is presented as the first step towards any intelligent result. A promise grows around it: set up the system properly, and knowledge will begin turning itself into articles, decisions and new ideas.

But a note doesn’t transform anything automatically. It leaves a trace. After that, you still have to recall, check, compare, write or act.

I can’t pinpoint when this began. I only remember the general desire: to stop losing thoughts and turn reading into a useful reserve for future projects.

different systems, different promises

Notes come in several popular forms, each promising to solve its own problem.

A summary helps preserve the thread of a lecture or book. Cornell notes divide a page into notes, questions and a summary. GTD gets tasks and next actions out of your head. PARA sorts material into projects, areas, resources and archives. Progressive summarisation suggests gradually highlighting the most important parts of saved material. Zettelkasten builds a network of small notes connected by meaning.

These aren’t competing religions. They answer different questions: what am I trying to remember, what do I need to do, where will I need this and how will I find it later? The mistake begins when someone combines every system without a task for those systems to support.

I tried to treat these approaches as parts of one large system. That was the mistake: different tools answer different questions, but I wanted one universal machine.

how I built the system

I imagined one vast map of knowledge. Every thought would have its place, every link its connection, and every project a supply of material from earlier thinking.

I spent a long time setting up that map: inventing folders, templates and rules for new entries. Each decision seemed small, but together they became a job of their own.

There’s a peculiar pleasure in it. You see tidy names, a graph of connections, a count of notes. Every new setting feels like progress. But the progress happens inside the system. It doesn’t necessarily bring the project any closer to a result.

A system has a cost. You have to decide where to put material, what to call it, what to link it to, whether to rewrite it in your own words and whether to review it later. Sometimes that takes more attention than the thought itself.

When a note needs that much maintenance, it starts protecting its own existence rather than your work.

luhmann’s slip-box, without the magic

Discussions of second brains often turn to Niklas Luhmann, the German sociologist. His slip-box, or Zettelkasten, has become the main exhibit for the claim that a large note system helps us think.

Luhmann really did have a large slip-box. The Niklas Luhmann Archive describes it as a tool for thinking and a “second memory” that helps with connections and distinctions. The archive also shows that his notes changed over time: early cards more often recorded his work with reading, while later ones became more compact and focused on propositions.

The scale of the collection often turns into a legend. But the archive describes 27 units, each holding roughly 2,500–3,500 cards. That is a description of a collection, not an instruction for everyone to produce the same number of notes.

Sönke Ahrens made Zettelkasten accessible to contemporary readers. He suggests writing notes in your own words, connecting them and using them as material for writing. That’s a useful interpretation. But an explanation that helps teach a method doesn’t prove that it works for everything.

Luhmann had a specific research programme, years of practice and the task of building sociological theory. His slip-box was part of that process. Copying its outward form alone produces a collection of cards without the work they supported.

So I don’t want to say that Ahrens “got it all wrong”. More precisely, I took a modern explanation of the method as a universal recipe, then found that Luhmann’s actual practice was more complex than the internet version.

a note is not the same as learning

Recording information is useful. But the act of recording it doesn’t mean you understand or remember it.

Memory research offers a simple example. In experiments with educational texts, retrieval practice — closing the material and trying to recall it in your own words — often produced better results on a delayed test than rereading or creating a concept map. Another study found benefits from self-testing for long-term retention.

That doesn’t mean we should throw away all maps and summaries. It means the important moment is when you retrieve a thought from memory and find out whether you can use it.

A summary that feels good to reread can create an illusion of knowledge. You recognise familiar phrases and mistake that recognition for the ability to explain the idea. Close the note and ask: “What is the main point, and how does it change the task?” If there’s no answer, you still have a store of material.

four different kinds of note

I began distinguishing notes by the work they do.

Information from others — a quote, fact, link or summary of someone else’s argument. It helps to record the source and the question that made you save it. Without those, a link quickly becomes a souvenir.

An idea of your own — your wording, hunch, objection or observation. Keep it separate from a quote. Otherwise, a month later, you won’t know what you came up with yourself and what you merely paraphrased well.

A working note — a decision, a list of questions, a draft, meeting notes or a next step. It doesn’t need to last forever. It matters while the task is moving.

An archive — something kept for reference, history or an obligation. An archive doesn’t need to pretend to be active thought. If material is rarely used, that’s fine. It serves a different purpose.

You can keep these categories in one app. But don’t pretend that every note has the same future. A quote from a book, a project decision and a personal hypothesis need different treatment.

a project folder instead of a universe

From archive to action A note becomes useful when it passes through a project and turns into action. raw materiallinkquoteobservation projectquestiondecisionnext step workwritinglayoutconversation archivelater
the second brain as a working deskRaw material should not remain an archive: a project connects it to a decision and a next step.

These days, I’m more likely to start with “What task am I working on?” than “Where should I put this thought?”

Each project has its own folder and a short goal. I keep context, questions, useful sources, decisions and next actions there. When a project ends, its material can go into the archive. While it’s active, the folder remains a working desk.

This changes how I read. When I know what I’m focusing on, I notice outside information differently. I don’t try to pay attention to everything. I notice what could help a specific task.

There’s no mysticism or automatic brain involved. Attention has a direction. If I’m building a website and thinking about composition, I notice examples in interfaces, books and videos. Without the project, those same examples might pass me by.

For example, when I’m working on a website and keeping its composition in focus, I start noticing similar solutions in interfaces, books and videos. The project doesn’t create information; it gives my attention a filter.

A minimal project folder might look like this:

  • goal: what should change when the project is complete;

  • context: who it’s for and what constraints apply;

  • questions: what I don’t yet know;

  • material: links and information from others, with a reason for keeping them;

  • decisions: what I chose and why;

  • next step: an action I can actually take, rather than a vague intention to “work on the project”.

Without a goal and a next step, the folder quickly becomes another archive.

when a note is useful

Testing whether a note is useful Four questions separate a working note from a note kept just in case. NOTE CHECK what does it let you do? recallreturn to a fact decideexplain a choice createwrite or build somedayno task yet
a simple test instead of a note counterA useful note helps you recall, decide or create. If all that remains is “someday”, set it aside.

I keep a note if it helps in at least one of four situations:

1. It helps me recall something specific when I need it. 2. It helps me make a decision and record the reason. 3. It becomes material for a piece of writing, a layout or a conversation. 4. It preserves a result I’ll need to return to.

There’s another test: what does this note let me do? Not “What does it contain?”, but “What can I do after reading it?”

A quote might let me check an argument. A list of questions might let me conduct an interview. A rough sentence might help me write a paragraph. If the only answer is “It might come in handy someday”, the note hasn’t yet shown why it needs to exist.

when the system becomes procrastination

A system starts getting in the way when maintaining it is more satisfying than the work it was created to support.

You rename folders instead of finishing the text. You move old notes into a new structure. You add plugins to capture notes faster, then never reopen them. You read another guide to Zettelkasten so you can finally start doing Zettelkasten properly.

I recognise myself in this. Sometimes it was easier to adjust the structure than open the project and take the next awkward step. Settings gave me a sense of control; the work required a decision.

For that situation, I keep one short rule: don’t create a new structure until the current project runs into a specific problem. If I can’t name that problem, I probably need a next step rather than another setting.

what I kept

I haven’t stopped taking notes. I’ve stopped expecting notes to make me smarter on their own.

A note is now a way to get a thought out of my head, examine it and bring it back into the work. Sometimes it lasts a day. Sometimes it helps me write something months later. Sometimes it’s more honest to discard it immediately.

I don’t need a second brain that collects everything. I need an external desk where I can see what I’m working on and what to do next.

The size of an archive doesn’t make you smarter. Engaging with a thought does: trying to recall it, putting it in your own words, testing it against a task and changing a decision when it doesn’t hold up.

If a note supported that action, it was useful. If it only increased the note counter by one, it was a record. There’s a difference.