PKM Wiki

Maps of Content

4 min read

A Map of Content (MOC) is a note that curates links to other notes around a theme, topic, or question, with added commentary and context. It functions as an index, a table of contents, and a thinking tool rolled into one. Nick Milo introduced the term and popularized the pattern, though the underlying practice of creating index notes predates any specific framework.

What a MOC Is

At its simplest, a MOC is a list of wikilinks organized around a topic. But a good MOC goes further: it adds narrative structure, explains relationships between the linked notes, and provides commentary that makes the collection more than the sum of its parts. A MOC about "motivation" might group links into intrinsic vs. extrinsic motivation, link to relevant research notes, and include a few sentences explaining why certain notes challenge or support each other.

The analogy from the vault: if links and backlinks are roads, tags are road signs, and folders are houses, then MOCs are maps. Each serves a different purpose, and they are complementary rather than competing.

How MOCs Differ from Other Organizational Tools

MOCs vs. folders. A note can only live in one folder, but it can appear in many MOCs. A note on "dopamine" might be linked from MOCs on neuroscience, motivation, habit formation, and addiction. Folders enforce single-category classification; MOCs allow the same note to participate in multiple contexts.

MOCs vs. tags. Tags connect notes by shared label, but they provide no context about the relationship. A MOC adds structure and narrative. Where a tag query returns a flat list, a MOC presents a curated, hierarchical, annotated view.

MOCs vs. database queries. Dataview or similar query-based approaches generate lists dynamically from metadata. These are powerful but impersonal. A MOC is handcrafted prose with intentional organization. The act of building a MOC is itself a thinking exercise that deepens understanding.

When to Create a MOC

The signal is cognitive friction. When you have accumulated enough notes on a topic that you can no longer hold the landscape in your head, it is time for a MOC. Nick Milo suggests a threshold of roughly 5-10 notes in a topic cluster. Below that, links between notes are sufficient. Above that, you need a map.

MOCs are also valuable when you need to think through a topic. Creating a MOC forces you to organize and relate ideas, which often reveals gaps, contradictions, or unexpected connections.

MOC Maintenance

A MOC is a living document. As new notes are created and existing notes evolve, MOCs need periodic review. The maintenance is lightweight: scan for new notes that should be linked, remove links to notes that have been merged or deprecated, and update the commentary as your understanding deepens.

Nesting and the Home Note Pattern

MOCs can link to other MOCs, creating layers of navigation. A "Psychology MOC" might link to sub-MOCs on "Cognitive Biases," "Motivation," and "Learning." At the top level, a Home Note (sometimes called a "Dashboard" or "MOC of MOCs") serves as the entry point to all major MOCs in the vault.

This nesting provides hierarchical navigation without the rigidity of folders. You get the benefits of structure while maintaining the flexibility of a linked knowledge graph.

MOCs Beyond LYT

While Nick Milo's Linking Your Thinking (LYT) framework popularized MOCs, the pattern is independent of any specific methodology. People using Zettelkasten, PARA, Building a Second Brain, or no formal method at all create MOCs. The concept is universal: whenever you have enough notes on a topic to need a map, you make one.

Key Points

  • A MOC is a curated index note with links, structure, and commentary around a theme
  • MOCs complement folders (single location) and tags (no context) by offering multi-membership with narrative
  • Create a MOC when a topic cluster exceeds what you can navigate by links alone
  • MOCs nest naturally; a Home Note provides a top-level entry point
  • The pattern is method-independent, not tied to any single PKM framework

Open Questions

  • Should MOC creation be partially automated (AI suggesting clusters that need a MOC) or remain a manual thinking exercise?
  • At what vault size do MOCs themselves need a meta-organizational layer beyond simple nesting?

References