Knowledge Concepts
What is a Map of Content (MOC)? A clear explanation of Nick Milo's PKM concept, how MOCs organize linked notes without folders, and how to build one in Obsidian or any tool.
A Map of Content (MOC) is a note that serves as a curated index of related notes on a topic — not a rigid folder, but a flexible, evolving hub that links to relevant notes and helps you navigate a growing knowledge base without requiring a hierarchical folder structure.
MOCs were popularized by Nick Milo, an Obsidian-focused PKM educator, as a solution to a specific problem: what do you do when your Zettelkasten or linked note system grows so large that you can't navigate it effectively?
When you start a linked note system (Zettelkasten, evergreen notes, or any flat linked system), navigation is easy: you have 50 notes, you know where everything is, and clicking through links is fast.
At 500 notes, navigation gets harder. At 2,000+ notes, the graph view is a hairball and the search returns too many results. You need structure — but the whole point of a linked note system is to avoid rigid hierarchical folder structures that break when topics overlap.
MOCs solve this by providing structure without rigidity:
An MOC is a note with a curated list of links, often organized by subtopic, with brief annotations. It's not comprehensive — you don't try to include everything. You include the notes that are most central, most useful, and most likely to lead you to other relevant notes.
Example MOC: "Pricing Psychology"
# Pricing Psychology MOC
## Core Principles
- [[Loss aversion explains why free trials need to invoke endowment effect]]
- [[Anchoring effects make first prices disproportionately influential]]
- [[Decoy pricing works by making middle option seem like best value]]
## SaaS-Specific Applications
- [[Annual plan anchoring requires prominent monthly equivalent display]]
- [[Freemium works when free users create direct or network value for paid users]]
- [[Trial-to-paid conversion is primarily a friction reduction problem]]
## Further Reading (sources)
- [[Notes from Kahneman - Thinking Fast and Slow]]
- [[ProfitWell pricing research highlights]]
This MOC doesn't replace any of the linked notes — it just provides a curated entry point for the topic. You create it when the topic grows large enough to need organization.
| Feature | Folder | Tag | MOC |
|---|---|---|---|
| Note can belong to multiple | No | Yes | Yes |
| Can be annotated | No | No | Yes |
| Evolves with your understanding | No | Partly | Yes |
| Navigable as a note | No | Limited | Yes |
| Created when needed | No (structure upfront) | Yes | Yes |
Folders are exclusive and rigid. Tags are flat and unannotated. MOCs are curated, annotated, flexible, and created on-demand.
A consultant building a knowledge base on organizational behavior:
After 3 months: Has 300 notes spanning motivation theory, team dynamics, leadership, feedback systems, and organizational culture. The graph view shows clusters but no clear navigation.
Creates MOCs:
Six months later: Preparing a workshop on feedback culture. Opens "Feedback Systems MOC." Sees a curated list of her best notes on the topic. Opens three. Adds two notes she's written since creating the MOC. Done — the MOC is still evolving.
Without MOCs: she would keyword-search "feedback," get 60+ results, spend 30 minutes triaging.
When a topic has 10+ linked notes. Before that, search and graph navigation usually suffice.
When you're about to do deep work on a topic. Before writing a report, a presentation, or a decision memo on a topic, create or visit an MOC. It surfaces what you know and shows gaps.
When a topic keeps appearing across unrelated notes. If "pricing psychology" appears in notes about product management, sales, and behavioral economics, it's probably worth its own MOC.
When navigating feels frustrating. If you find yourself constantly searching for the same cluster of notes, create an MOC for that cluster.
Don't create MOCs preemptively — create them when the need is felt.
Step 1: Search your notes for a topic. Use full-text search or graph view to find notes that cluster around a theme. "Pricing," "persuasion," "feedback" — whatever topic needs navigation.
Step 2: Create a new note titled "[Topic] MOC" or "[[Topic]]." Some people name MOCs with the suffix "MOC"; others just use the topic name. Either works — the content defines it, not the name.
Step 3: Curate, don't catalog. Don't link to every note that mentions the topic. Link to the most central notes — the ones that lead to other relevant notes or that contain the most important ideas. Aim for 10–30 links per MOC.
Step 4: Organize by subtopic with brief annotations. Group links by theme within the MOC. Add a sentence after key links explaining why they matter or how they relate to each other. The annotation is what makes an MOC more useful than a tag.
Step 5: Update when you write new relevant notes. When you write a new note that belongs in this MOC, add the link. The MOC grows with your knowledge.
WebSnips's Connections graph shares something philosophically with MOCs: both surface relationships between pieces of content to aid navigation and discovery.
For researchers who build knowledge from web content:
WebSnips doesn't create MOCs — that's work for your note-taking tool (Obsidian, Roam, etc.). But its connection-surfacing capability mirrors the navigation function that MOCs serve within a note system.
Do MOCs work in Notion? Yes — in Notion, create a page that links to related pages on a topic. It functions as an MOC even without bidirectional links. The limitation is that Notion pages can only appear in one parent; MOCs work around this by using inline links rather than folder membership. A "Pricing Psychology" Notion page with a list of linked pages is a functional MOC.
How many MOCs should I have? There's no target number — create them when navigation becomes painful. Nick Milo's system has thousands of notes and dozens of MOCs. At 500 notes, you might have 5–10 MOCs. At 2,000 notes, maybe 30–50. Let need drive creation.
Are MOCs the same as indexes or tables of contents? Similar concept, different use. An index is static and comprehensive. A table of contents is hierarchical and ordered. An MOC is curated and evolving — you include what's most useful, organized by theme, and update it as your understanding develops. The distinction is intent: an MOC is a thinking tool, not an archival record.
What's the difference between an MOC and a Zettelkasten hub note? Very similar — Luhmann used hub notes within his Zettelkasten that linked to related clusters of cards. MOCs are essentially the digital, named version of the same concept. The terminology differs (hub note vs. MOC); the function is the same.
A Map of Content (MOC) is a curated navigational note that links to related notes on a topic — flexible, evolving, and created when needed rather than pre-imposed as rigid folder structure.
MOCs solve the navigation problem that emerges when a linked note system grows beyond what memory can navigate. They provide structure without the exclusivity and rigidity of folders, and they curate rather than catalog — which makes them useful as thinking tools, not just organizational tools.
Create your first MOC when you notice yourself searching the same cluster of notes repeatedly. That frustration is the signal.
More WebSnips articles that pair well with this topic.
What is citation management? A clear explanation for researchers and academics — how citation managers work, the best tools, and how to avoid the most common mistakes.
What is tacit knowledge? A clear explanation for team leads and ops people — what tacit knowledge is, why it's the hardest knowledge to transfer, and practical methods to make it explicit.
What is a commonplace book? A clear explanation of the centuries-old knowledge collection practice, famous examples, and how to build a modern digital version for writers and researchers.