A mind map stops being readable at a fairly predictable point: somewhere past a hundred topics, or four levels deep, or the moment you start scrolling to find a branch you added yesterday. The usual response is to zoom out, which makes the text too small, or to restyle it, which changes nothing.
The fixes that work are structural, and there are five of them: collapse, split, re-level, re-layout, and delete. In that order, because they get progressively more expensive.
First, work out which problem you have
Three different failures look identical from a distance.
Too wide. One parent with fifteen children. The eye can't group them, so you read the list rather than seeing the structure. This is the most common and the easiest to fix.
Too deep. Five or six levels. Deep maps read like a directory tree. You lose the path back to the root, and the leaves are so far from the centre that their context is gone.
Too tangled. Reasonable width and depth, but branches keep referring to each other and the lines cross. That's a map fighting its own hierarchy, and it's a different problem; see mind map vs concept map.
Diagnose before fixing. Splitting a map that was merely too wide throws away a structure that only needed one intermediate level.
Fix 1: Collapse everything, then expand one branch
Before restructuring anything, collapse the whole map to the first level.
Two things happen. You can suddenly see whether the top level is right, and it usually isn't, because top-level branches accumulate by accident. And you get a working rhythm: expand one branch, work inside it, collapse it again. A map you navigate this way stays readable at sizes where the whole-map view is useless.
Autofocus, if your tool has it, is the same idea with less clicking: show one branch and dim everything else.
This costs nothing and solves the presentation half of the problem outright. Do it before anything below.
Fix 2: Add a level instead of removing items
For a branch that's too wide, the instinct is to delete children. Usually the right move is to insert a grouping level.
Fifteen tasks under "Launch" is unreadable. The same fifteen under "Before", "Launch day" and "After" is three groups of five, and five is a number the eye takes in at once. You haven't removed anything; you've made the width a depth.
How to find the groups: read the children and look for the word that repeats, or the question they answer. If no grouping suggests itself after a minute, the branch genuinely is a flat list, and a flat list of fifteen things wants a list layout or a table, not a radial map.
The working numbers: aim for three to seven children per node, and no more than four levels deep. These aren't laws, but a map that violates both at once is always hard to read.
Fix 3: Take a level out
The mirror image, and the one people never do. Ask of each intermediate topic: does this node say anything, or is it just a container?
Topics called "Other", "Misc", "General", "Notes" and "Stuff" are containers with no meaning, and every one of them adds a level between the reader and the content. Delete the node, promote its children, and the map gets a level shallower for free.
The same applies to a node with exactly one child. That's not a hierarchy, it's a rename.
Fix 4: Change the layout to match the content
Layout isn't decoration; it's a claim about the shape of the data, and the wrong claim makes a fine map unreadable.
- Radial — balanced exploration, roughly equal branches. Fails badly when one branch is ten times the others.
- Horizontal (right-side tree) — deep, text-heavy trees. The best default for outlines and long labels, because nothing has to be read sideways.
- Top-down org chart — real hierarchies with short labels. Wastes horizontal space fast.
- Timeline — anything with an order. If your branches are stages, this removes the need to explain the order in the labels.
- Matrix or list — flat, repetitive content. Stop drawing a tree for data that has none.
If one branch dwarfs the others under a radial layout, that's the layout telling you the truth: switch to horizontal, or promote that branch to its own map.
Eight layouts to switch between without redrawing, collapse and autofocus for reading one branch at a time, and several maps side by side on one canvas when a branch outgrows its parent.
What it doesFix 5: Split the map
When a single branch has become the size of the map it lives in, it wants to be its own map, with the parent topic as its new centre.
Split when any of these is true:
- One branch holds more than about a third of the topics.
- A branch has its own audience: someone would open it without needing the rest.
- The branch has a different lifecycle: the rest of the map is finished and that part is still moving.
Keep the parent topic in the original map as a stub, so the trail back exists. Tools that let you put several maps side by side on one canvas make this cheaper than it sounds, because you can split without losing the overview.
Fix 6: Delete, honestly
The last fix is the one nobody wants: some of it is not worth keeping.
Two tests. Would you write this topic again today? And has anything below it changed in three months? A branch that fails both is archive material, and in a map you don't archive, you export. Export the map, put the file somewhere, delete the branch. The map is a working document; the export is the record.
Prevention
Three habits keep this from recurring:
- Name the map's job in the centre. Not the topic; the job. Anything that doesn't serve it doesn't go in, and you'll know at capture time rather than three months later.
- Prune at the end of each session, while you still remember what was speculative.
- Start a second map early. The reflex to keep everything in one map is what produces maps nobody opens. Two maps with a link between them are almost always more useful than one map twice the size.