Idea Emergence Q&A Part 1: How to Create MOCs, How to use Tags & Folders

Content maps (MOCs) are presented as the fastest way to turn scattered notes into usable thinking—especially once a person hits a “mental squeeze point,” when the note library starts to feel overwhelming. Instead of forcing rigid folder hierarchies, the approach favors link-based systems like Obsidian and Rome, where ideas can emerge bottom-up and then collide into new connections. The practical payoff: most work time should shift into the map itself, where notes are added and recombined until progress happens in a kind of “ideation acceleration,” likened to particle collisions that produce new results while discarding what no longer fits.

The workflow starts with when to create a map, not just how. Two entry points are offered: bottom-up creation when someone wants to avoid forgetting what they’re working on (start a new MOC and throw notes into it), or top-down creation when the topic is already clear (start from the idea and compile notes under it). The “mental squeeze point” is the trigger—when the person can’t keep everything in working memory, a MOC becomes the offload mechanism that reduces cognitive burden through chunking. Chunking is treated as tightly linked to MOCs: the map provides headings and structure so retrieval becomes easier later.

A key design choice is minimizing folders in favor of links. Folders are described as top-down and potentially rigid, while links enable bottom-up formation and organic connection. Still, folders aren’t rejected entirely; the guidance is to keep their number low (roughly “lop off a zero,” such as 100 down to 10) so they don’t recreate the old rigidity. The “five levels” of emergence are discussed as a framework built from notes and links rather than folders, with a warning that over-structuring too early is a common trap. Structure should be “earned” as enough content bubbles up to justify it.

For naming and organization, numbers are treated as an aesthetic and sorting tool rather than a requirement. The home maps use three-digit numbering to keep them sorted at the top in file explorers, with the caveat that over-numbering can lead to unnecessary rigidity. Dewey Decimal inspiration appears in the concept of using broad categories at the high level, but the system avoids deep decimal granularity to preserve fluidity.

Tags are handled with similar nuance. They’re powerful for discovery, but over-tagging dilutes usefulness because searches return muddy results when tags become too common. Tags are framed as “weaker relationships” compared with links: links imply a stronger connection, while tags often indicate shared interest or descriptors. The advice is to define how tags will be used—especially descriptor tags—and to rely on the home note as a guide for what’s validated.

Finally, future-proofing is emphasized. MOCs should include purpose statements so later revisits preserve context, and new maps should be connected back to a “home map” via links (breadcrumbs) so the library remains navigable even after long gaps. Chronological tracking is suggested for meetings or logs using timestamps or IDs, but auto-updating filenames in link-based systems can reduce the need for immutable timestamp IDs. The overall message: build maps when overwhelmed or when a topic is ready, keep structure light until it’s earned, and let links do the heavy lifting for emergence and retrieval.