Getting Started

How NetworkNotes Is Different

Fewer rules than Zettelkasten, and why that's the whole point.

There are plenty of notetaking methods: plain folders, PARA, Building a Second Brain, Zettelkasten. Strip away the branding and almost all of them answer one of two questions.

Two questions, two families

  • “Where does this note go?” is the filing question: plain folders, PARA, Building a Second Brain, tag systems. They organise notes by location or category, and they’re good at it. When you know what you’re after, you can put your hands on it.
  • “What does this note connect to?” is the linking question: Zettelkasten, evergreen notes, and NetworkNotes. They organise by relationship, so ideas you’d never have filed in the same place can still find each other.

The important part: these two families aren’t enemies. Filing tells you where a note lives; linking tells you what it relates to. You can keep your folders, or PARA, or whatever grouping you already use, and add links on top. That’s the first principle: connect, don’t just file. NetworkNotes never asks you to dismantle your filing system; it asks you to stop treating filing as the only structure you get.

So NetworkNotes doesn’t really compete with the filing methods; it sits happily alongside them. The method it genuinely stands against, the one you’d reach for instead, is the other linking method: Zettelkasten. That’s the comparison worth making in depth.

The problem with perfecting a system

Spend time in Zettelkasten communities and a pattern shows up: people end up perfecting the system instead of writing. Fixed note types, unique IDs, branching sequences, a multi-stage pipeline. Each is one more thing to get right, and one more invitation to tinker instead of think.

NetworkNotes is a reaction to that. It keeps the one idea that matters (a note’s value is in what it connects to) and drops nearly everything else. The aim is a system you don’t have to maintain: write a note, link it, move on.

What NetworkNotes drops

Zettelkasten asks you to…NetworkNotes
Sort notes into fixed types (fleeting, literature, permanent)Any types you like, or none
Keep every note atomic (one idea)Any size: an idea, or everything about a talk
Give notes unique IDs / Folgezettel addressesJust Links
Follow a pipeline (fleeting → literature → permanent)Write a note, link it. That’s the loop
Build toward published writingWhatever you need notes for

The differences that matter

No fixed note types. Zettelkasten sorts every note into fleeting, literature, or permanent. NetworkNotes prescribes nothing of the sort: type or group your notes however helps you (by event, by person, by project) or not at all. The only thing every note shares is that it’s something you want to be able to retrieve later, and every note is “permanent” in that sense, until you no longer need it or rewrite it. Notes are working objects, not archival records.

Notes don’t have to be atomic. A note can be a single idea, and sometimes that’s exactly right. But it can just as well hold everything about an event you attended, a course you took, or a talk you gave. You decide the unit; the method doesn’t.

No addresses, no ceremony. There are no unique IDs and no Folgezettel sequences to maintain. The only structure is the Links you draw.

No prescribed workflow. There’s no pipeline to move a note through. You write it and you link it; that is the entire loop.

A broader goal. Zettelkasten is usually sold as an engine for producing writing, the slip-box as a co-author. NetworkNotes is purely about notetaking: good notes you can retrieve and think with. You can use it to write, but you can just as easily use it for study, project memory, research, or simply remembering what you read.

This is not a knock on Zettelkasten

Its rules exist for a reason, and for someone drafting a book they earn their keep. But if you just want notes that stay useful without becoming a second job, the rules are overhead. NetworkNotes is the method for that: three core concepts, three principles, and nothing to maintain.

Connections

See this page in the whole NetworkMap.