A Map of Content, or MOC, is a note whose entire job is to link to other notes. It holds almost no ideas of its own. Instead it points: here is the note on spaced repetition, here is the one on the forgetting curve, here is the half-formed one you started last week. Think of it as a hand-made table of contents for a topic, one that grows as your thinking grows. The term comes from Nick Milo's Linking Your Thinking work, where MOCs are the answer to a simple problem: a note collection that gets big enough stops being navigable, and you need somewhere to stand.
Where a MOC sits: between folders and search
Two older tools try to solve the same problem, and both fall short in opposite directions.
Folders are rigid. A note on "attention" can go in Psychology or Productivity or Study Habits, but a folder forces you to pick one. Once filed, it hides everywhere else. Search is the opposite: it finds anything, but it has no memory and no shape. It returns a flat list, ranks nothing by importance, and shows you no path through a topic.
A MOC lives in the gap between them. Unlike a folder, it does not own the notes it lists, so the same note can appear in five different maps without being copied or moved. Unlike search, it is curated: you decide which notes matter, in what order, under which headings. It gives a topic a front door and a rough hierarchy without locking anything in place.
Why not just use backlinks?
If your notes already link to each other, you might ask what a MOC adds. This is a fair question, and the honest answer is that MOCs and backlinks do different jobs. Backlinks are automatic and undirected: they show you every note that happens to mention this one, in no particular order, with no sense of which connections carry weight. That is powerful, but it is raw. A MOC is the opposite: slow, deliberate, and shaped by judgment. You choose the ten notes worth surfacing out of the hundred that mention a topic, and you arrange them so a reader (usually future you) can move from overview to detail.
This is also what separates a MOC from the pure emergent structure of the Zettelkasten method, where meaning is meant to arise from links alone. MOCs add a curated layer on top. They pair best with atomic notes, because a map of single-idea notes is far more useful than a map pointing at sprawling documents.
The honest downside: it is manual, and it can go wrong
A MOC is work. Every link on it, every heading, every reorder is something you did by hand, and nobody does it for you. That opens two failure modes worth naming.
The first is neglect. A map you build once and never tend becomes a stale index that quietly lies about what your notes contain. The second is the opposite: premature structure. It is easy to spend an afternoon building an elegant map for a topic you have five notes on, mistaking the tidy feeling of organizing for the harder work of thinking. Milo's own advice is to make a MOC only when you feel a real "mental squeeze," when scattered notes actually start to overwhelm you, not before.
How to start one
- Wait for the squeeze. Start a MOC when a topic genuinely feels tangled, not on day one.
- Make a plain note titled for the topic, like "Memory MOC."
- List the handful of existing notes that matter most, with a word or two on why each belongs.
- Add light headings only once the list is long enough to need them.
- Revisit it when you add notes to that area, and delete links that no longer earn their place.
MOCs are one structure among several inside personal knowledge management, and they overlap with the index-note habits in the second brain approach.
Where automatic connection fits
We build ClairMind, so treat this as a biased but even-handed note. A hand-built MOC and an app that surfaces connections for you are two different bets, not the same tool. ClairMind leans on AI to link related notes automatically, which removes the upkeep but also removes the deliberate curation that gives a good MOC its judgment. If the act of choosing and arranging links is where your thinking happens, build maps by hand in a tool made for it. If you would rather capture fast and let connections surface on their own, automatic is the lighter path. Both are legitimate. They just value different kinds of effort.