Split Your MOCs Before They Become Unusable

Maps of content are one of the better ideas in Obsidian — a way to give structure to a collection of notes without forcing a rigid folder hierarchy. The problem is that they grow. Fast. And once a MOC is overgrown, it stops being useful and starts being something you scroll past.

The culprit is usually Obsidian's own flexibility. That freedom is the point of the tool, but it's also a trap: handed complete flexibility, the instinct is to use it. What actually works is the opposite — complete rigour about what earns a place in any given MOC. Two questions to run every time you're about to add something:

• Does this item absolutely only belong here and cannot be moved anywhere else?
• If it could be grouped with something else, should this become a child MOC or a neighbouring one instead?

Splitting early is always easier than untangling a MOC that's already overgrown. The more you wait, the more links accumulate, the harder the edit. What's your rule for deciding when a MOC has earned its own child?

Keep the schema simple,
Zhenia