Linking Your Thinking in Obsidian, and its alternatives
Nick Milo's Linking Your Thinking (LYT) framework runs on Obsidian and teaches Maps of Content, MOCs, hub notes that gather links to everything on a topic so a growing vault of linked notes doesn't turn into an unfindable web. It's a well-regarded, Obsidian-native approach. If MOCs aren't clicking for you, or you don't want to build and maintain them by hand, here's what else actually solves the same problem.
LYT emerged from Nick Milo's own Obsidian practice, and the core insight is genuinely useful: as a note vault grows past a few hundred notes, links alone stop being enough to navigate it, so you need a small number of "map" notes that give you an entry point into a topic. Milo was among Obsidian's early adopters and shipped the first version of his LYT approach in the tool's first year. The framework has built a real following in the Obsidian community specifically because it solves a problem that Zettelkasten-style linking alone doesn't: findability at scale.
What LYT actually asks of you
The MOC itself is not automatic. You decide when a topic deserves its own map, you decide which notes belong on it, and you go back and update it as new notes arrive. That's a real ongoing commitment on top of everything else in your note-taking practice, and it's the same maintenance pattern that eventually strains every method in this space, including Building a Second Brain's own distillation habit, covered in full on why second brain systems fail, and the one fix.
The real alternatives, method by method
| If MOCs feel like too much upkeep, try | What it does instead |
|---|---|
| PARA | Organizes by actionability into four fixed buckets, no map-building required |
| Zettelkasten linking alone | Skips the map layer; relies on note-to-note links and search to surface connections |
| Building a Second Brain | Adds a distillation habit on top of PARA instead of a navigation layer |
| An AI-maintained hub | Builds and updates the equivalent of a MOC automatically as notes come in |
Each of these solves the same underlying problem, findability in a growing collection of notes, from a different angle. PARA sidesteps the need for maps entirely by giving every note a fixed home based on actionability rather than topic. Pure Zettelkasten-style linking leans on search and note-to-note connections instead of a dedicated hub note. Building a Second Brain takes PARA and adds a review habit that keeps the most useful notes surfaced. None of them require you to build and maintain MOCs by hand, though none of them do exactly what a good MOC does either, which is give you a single page that shows an entire topic at a glance.
The AI version of a Map of Content
The actual value of a MOC, one page that shows you everything connected to a topic, doesn't require you to build it by hand. An assistant with access to your full note archive can maintain the equivalent structure automatically: every time a new note touches a topic, the topic's overview page updates itself. You get the navigability LYT is built around without owning the upkeep of curating it note by note. That's the same shift covered generally on the PKM methods comparison page, and it applies to LYT's map-based approach as directly as it applies to PARA's folders.
Worth saying plainly. LYT is a genuinely good framework, not a problem to be solved. The alternative here isn't "MOCs are wrong." It's "the upkeep of building them by hand doesn't have to be yours."
Choosing between them
If you like thinking in maps and topics, keep the MOC habit and consider whether an assistant can maintain the map for you rather than replacing the idea. If actionability, what's active versus dormant, matters more to you than topic navigation, PARA or its fuller BASB version will feel more natural. Either way, the tool underneath doesn't have to be a specific app; the comparison of where Obsidian and AI-native workspaces each fit is on Obsidian vs Notion AI, and the app-level roundup of what AI note tools get wrong is on best AI note-taking apps.
Maps of Content that redraw themselves
The book covers building a hub in plain files where every topic's overview page updates itself as new notes arrive, so you keep the navigability without curating a single map by hand.
Get the bookTopic maps nobody has to curate by hand
The same map upkeep, built for a company: every topic's overview page redraws itself as new material arrives from the work people were already doing. Try the demo.
See the demo