The Problem: Notes Without a Map
You've been using a note-taking app for a year. You have 500 notes. Some of them are brilliant — insights you're proud of, research that took hours to compile, frameworks that changed how you think. Most of them are unreachable. You know they exist somewhere. You can search for them. But you can't browse them; you can't see how they connect; you can't navigate from one topic cluster to another.
This is the "note graveyard" problem: a large note collection organized (or unorganized) in a way that makes individual notes hard to find and relationships between notes invisible.
Folder-based organization creates hierarchy but destroys flexibility — a note on "decision-making in teams" might belong under "Leadership," "Psychology," "Management," or "Meetings." You pick one, and it becomes invisible under the others.
Maps of Content (MOCs) in your notes solve this differently: instead of forcing notes into a hierarchy, you create a special "map" note that links to a cluster of related notes on a topic — a navigational hub rather than a folder. Notes can appear on multiple maps. The map doesn't own the notes; it points to them.
Where Maps of Content Come From
The Maps of Content concept was developed and named by Nick Milo, creator of the "Linking Your Thinking" (LYT) framework and course. Milo published and refined the MOC concept through blog posts and the LYT Kit for Obsidian starting around 2020, and it became widely adopted in the Obsidian and PKM (Personal Knowledge Management) community.
The concept builds on several intellectual foundations:
Hypertext theory (Ted Nelson, 1960s-70s): The idea of non-hierarchical, linked documents as an alternative to sequential or hierarchical information structures. MOCs apply hypertext thinking to personal note organization.
Zettelkasten's structure notes (Niklas Luhmann, 1950s-90s): Luhmann's "structure notes" (or register notes) served a similar function — overview notes that organized clusters of connected cards. MOCs are a digital evolution of this concept.
The emergence problem: As note collections grow to hundreds or thousands of notes, emergent clusters of notes form around topics without any explicit organizational structure. MOCs make those emergent clusters explicit and navigable.
Nick Milo's key insight: maps are different from folders. A folder owns its contents — a note can only be in one folder. A map merely points to notes — a note can appear on many maps. This preserves flexibility while adding navigability.
The MOC Method, Step by Step
Understanding What a MOC Is
A Map of Content is a note that links to other notes on a related topic, with brief context about each link.
It is NOT:
- A folder (doesn't contain or own notes)
- An index (comprehensive list of all notes on a topic)
- A summary (doesn't replace the notes it links to)
- A hierarchical category (doesn't impose parent-child relationships)
A good MOC is curated, contextual, and navigational: it shows you the landscape of a topic and helps you move through your notes purposefully.
Step 1: Let MOCs Emerge Naturally
The most common MOC mistake is creating them upfront before you have enough notes. MOCs should emerge from existing note clusters — they formalize connections that already exist in your notes.
When to create a MOC:
- You have 5-10+ notes on a topic and find yourself searching for them repeatedly
- You're starting a project and need a hub to navigate relevant existing notes
- You want to make connections across a cluster of notes visible
Start with notes first. Let the clusters emerge. Create the MOC when you feel the pull of the topic — when you want a map.
Step 2: Create the MOC Note
Create a note with a clear, topic-focused title. Common naming conventions:
- "MOC — Decision Making"
- "PKM Home" (for a top-level "home" MOC)
- "Decision Making MOC"
- "⭐ Writing (MOC)" (with an emoji to signal MOC type)
The note's content is primarily a list of links to related notes, organized in a way that makes sense to you — grouped by subtopic, ordered by progression, or arranged by relevance.
Step 3: Write Contextual Links, Not Just Links
A basic MOC might just list links:
- [[Note on cognitive biases]]
- [[Kahneman System 1 and System 2]]
- [[Decision fatigue]]
A better MOC adds brief context:
## Foundations
- [[Kahneman System 1 and System 2]] — the core dual-process theory; start here
- [[Heuristics and their limits]] — how mental shortcuts work and fail
## Practical Application
- [[Decision fatigue]] — why decision quality degrades through the day
- [[Analysis paralysis]] — when too many options prevent deciding
- [[Two-pizza rule for team decisions]] — Amazon's framework for small-group decisions
## Contrarian Takes
- [[When intuition beats analysis]] — cases where gut instinct outperforms deliberation
The context makes the MOC a genuine guide, not just a list.
Step 4: Link MOCs to Each Other (Create a Home MOC)
For large note collections, create a "Home MOC" — a top-level map that links to your other MOCs. This gives you a single entry point to your entire note network.
# Home
## Areas of Focus
- [[Decision Making MOC]]
- [[Writing MOC]]
- [[PKM and Knowledge Systems MOC]]
- [[Product Strategy MOC]]
## Active Projects
- [[Q4 Strategy Project MOC]]
- [[Book Notes — Thinking Fast and Slow MOC]]
The Home MOC is your dashboard — the first note you open when you want to navigate your knowledge system.
Step 5: Evolve and Prune MOCs Over Time
MOCs are living documents. As you add notes, add links to relevant MOCs. As topics evolve and cluster differently, split a MOC into two (when it gets large) or merge two (when they're always accessed together).
Splitting: When a MOC grows to 20+ links in one section, split it. "Decision Making MOC" might split into "Cognitive Biases MOC" and "Decision Frameworks MOC."
Merging: When you realize two MOCs always lead you to the same notes, merge them.
A Worked Example
A product manager, Yuki, builds a MOC-based note system in Obsidian:
Current notes on product strategy:
- [[Product-Market Fit definition]]
- [[OKRs vs KPIs — what's the difference]]
- [[Jobs to be Done framework]]
- [[Product discovery vs delivery]]
- [[How to run user interviews]]
- [[Priya's insight on retention vs acquisition]]
- [[Product strategy vs product roadmap]]
- [[North Star Metric examples]]
Yuki creates "Product Strategy MOC":
# Product Strategy MOC
## Core Concepts
- [[Product-Market Fit definition]] — the fundamental goal; what PMF actually means
- [[Product strategy vs product roadmap]] — strategy sets direction; roadmap is the plan
- [[North Star Metric examples]] — how leading companies define their single organizing metric
## Frameworks
- [[Jobs to be Done framework]] — understanding what customers "hire" a product to do
- [[OKRs vs KPIs — what's the difference]] — goal-setting mechanics
## Research & Discovery
- [[Product discovery vs delivery]] — dual-track agile; why discovery never stops
- [[How to run user interviews]] — practical interview guide
## Insights & Observations
- [[Priya's insight on retention vs acquisition]] — from Q3 review; valuable counterpoint to growth obsession
When Yuki prepares for a product strategy presentation:
She opens the Product Strategy MOC first. She sees the landscape of her notes at a glance. She navigates to the notes she needs. She doesn't search; she browses the map.
Three months later, the MOC grows to 30 links. Yuki splits it into "Product Strategy MOC" (keeping the strategy notes) and a new "User Research MOC" (the interview and discovery notes).
Where MOCs Shine
For large note collections (200+ notes): MOCs become essential when a collection is large enough that you can't hold a mental map of it. The navigational overhead of un-mapped collections grows exponentially; MOC overhead grows slowly.
For non-hierarchical knowledge: Topics that span multiple domains (decision-making touches psychology, management, finance, and personal life) resist folder organization. A MOC can surface notes from anywhere in your system under one topic without moving the notes.
For active knowledge workers: The contextual notes in a well-maintained MOC make it a genuine intellectual artifact — a curated guide to a topic that reflects your own understanding, not just a list of stored notes.
Where MOCs Break Down
For small note collections: With fewer than 100 notes, MOCs add structure that isn't needed. Search is fast, topics are findable by memory, and the overhead of maintaining maps exceeds their navigation benefit.
For action-oriented systems: MOCs are navigational tools for knowledge networks, not task management. If you need to track what to do and when, MOCs don't help — GTD or PARA are better fits.
Maintenance requirement: An unmaintained MOC is worse than no MOC — it gives false confidence that you've found all the relevant notes when you've only found the ones that were added before the MOC was last edited. Add links to relevant MOCs every time you add a new note.
Tool dependency: MOCs work best in tools with strong wikilink support (Obsidian, Roam Research, Logseq). In tools without bidirectional linking, the MOC-to-note connections are one-way and harder to maintain.
Tools That Support MOCs in Your Notes
| Tool | MOC support | Notes |
|---|
| Obsidian | Excellent — bidirectional links, graph view, backlinks pane | The native home of MOCs; best overall |
| Roam Research | Strong — daily notes integrate with MOC pages | Good; subscription cost |
| Logseq | Good — block-based linking, graph view | Free; Obsidian alternative |
| Notion | Workable — internal page links | Less fluid than dedicated PKM apps |
| Bear | Limited — internal links exist but no graph view | Better for individual notes than MOC systems |
| WebSnips | Captures web content to feed the note network | Handles web capture; separate tool for MOCs |
WebSnips and MOCs: Web clippings are often the raw material that gets processed into permanent notes, which then appear on MOCs. When researching a topic that has a MOC in Obsidian, clipping relevant web passages in WebSnips — organized by the same topic — keeps your web research aligned with your note system. The clipping feeds the note, which feeds the MOC.
Common MOC Mistakes
Mistake 1: Creating MOCs before you have enough notes.
An MOC with three links is just a list — it doesn't provide the navigational benefit of mapping a real cluster. Wait until you feel the pull of the topic (you're repeatedly searching for related notes) before creating the map.
Mistake 2: Making MOCs too comprehensive.
An exhaustive MOC that links to every note on a topic loses the curated quality that makes it useful. A MOC should link to the most important, most connected, most frequently useful notes in a cluster — not every note that touches the topic. You're building a navigational aid, not an index.
Mistake 3: Treating MOCs like folders.
If you're adding notes "to" your MOC, you're thinking of it as a folder. MOCs don't contain notes; they point to them. A note isn't "in" the MOC — it's linked from it. This distinction matters: a note can be linked from many MOCs simultaneously (a fact about cognitive biases could appear on both the "Decision Making MOC" and the "Psychology MOC").
Mistake 4: Not linking back from notes to MOCs.
Bidirectional linking (adding a link from the note back to its MOC) makes your system self-healing — when you're in a note and want to find related notes, the MOC link brings you back to the navigational hub. If links are only one-directional (MOC to note), notes feel isolated.
Frequently Asked Questions
How many MOCs should I have?
This depends on your note collection size and your interests. Most active PKM practitioners with 300-1000 notes have 10-30 MOCs. Start with 3-5 and let them grow naturally. The number of MOCs roughly scales with the number of distinct topic clusters in your notes.
Should my MOC be a hub (links in) or a map (links out)?
MOCs in Nick Milo's LYT framework are maps — they link OUT to notes in the topic cluster. But notes link BACK to the MOC (via Obsidian's backlinks, or manually), making the MOC also a hub. Both directions matter. In practice: build the MOC with outgoing links first; let backlinks handle the incoming direction automatically.
Can I use MOCs without Obsidian?
Yes. MOCs are a conceptual approach, not a tool-specific feature. In Notion, a "MOC" is a top-level page with links to other pages. In Roam, it's a page with block references. In a paper system, it's an index card with references to other cards (similar to Luhmann's structure notes). The tool shapes the implementation; the concept works anywhere.
Key Takeaways
- Maps of Content (MOCs) are notes that link to clusters of related notes — navigational hubs that make large note collections browsable without imposing hierarchical folder structures.
- Developed by Nick Milo (Linking Your Thinking framework, ~2020) and widely adopted in the Obsidian PKM community.
- Maps, not folders: a note can appear on many MOCs simultaneously — MOCs point to notes; they don't own them.
- Let MOCs emerge: create them when you feel the pull of a topic (5-10+ notes exist, you keep searching for the same cluster) — not upfront.
- Contextual links beat bare links: brief context for each link makes the MOC a curated guide, not just a list.
- Home MOC as entry point: a top-level Home MOC linking to all your topic MOCs gives you a single dashboard for navigating your entire knowledge system.
Conclusion
Maps of Content solve one of the most persistent problems in personal knowledge management: the large note collection that becomes unsearchable and unnavigable as it grows. By providing a non-hierarchical navigational layer — curated maps that link across note clusters without forcing notes into folders — MOCs allow knowledge networks to grow organically while remaining accessible. For anyone building a second brain in Obsidian, Roam, or similar tools, MOCs are the navigational infrastructure that makes a large collection of notes feel like a coherent, explorable knowledge base rather than a pile of digital files.
Try WebSnips free — capture the web research and articles that feed your note network into organized collections, creating a consistent pipeline from web content to processed notes to MOC entries.