1. Capturing and organising at the same time
The most common and the most damaging. You are adding ideas while simultaneously deciding where they belong, which means every new thought triggers a small restructuring decision. Generation slows to nothing and the structure ends up shaped by whatever you happened to think of first.
Do them as separate passes. Dump everything unstructured, then group in a second sitting. The clusters that emerge from what you actually wrote are almost never the categories you would have picked in advance.
2. Categories chosen before the content exists
Related, and worth separating. Starting with Health / Work / Money / Relationships feels responsible and produces a filing cabinet — a structure inherited from convention rather than from your situation.
Those headings admit everything, so they rank nothing. Derive categories from the items you captured. If three of them come out weird and specific, that is a good sign, not a problem to tidy up.
3. Even depth
Developing every branch to the same level looks organised and wastes most of the effort. Real subjects are lumpy — one area is understood and needs no subdivision, another holds all the uncertainty.
Deepen only where more detail would change a decision. Symmetry is an aesthetic preference that costs you readability.
4. Never deleting
Maps accumulate. Nothing forces removal, so a two-year-old map contains things that are done, abandoned, or were never really yours, and each one costs a little attention every time you open it.
A branch you have skipped past in three consecutive reviews is data: it is finished, or it was never real. Delete it or park it deliberately. Minty Path's Paused and Archived states exist for exactly this — the difference between a decision and slow rot.
5. Everything is a priority
If most of the map is marked current, you have not prioritised, you have relabelled. Minty Path encourages keeping Focus to one to three branches and keeps it independent of status and dates: marking a branch Focus claims only that this is where attention goes, and the guideline makes the choice visible.
The discomfort of picking three is the mechanism working, not a limitation to route around.
6. Dates as motivation
Adding an Aim date to a branch to make yourself feel accountable teaches you, reliably, to ignore your own dates. Miss four self-imposed targets and the fifth carries no weight — including the one that was genuinely fixed.
Keep the two kinds apart. An Aim date is a soft target you chose; a Deadline comes from outside you. Minty Path treats a passed Aim date calmly rather than rendering it overdue, precisely so that red still means something when it appears.
7. Confusing hierarchy with dependency
Putting a branch under another because it must happen first. Those are different claims — belongs under versus depends on — and merging them corrupts the structure to express an ordering.
Dependencies frequently run between distant parts of a map. They need their own kind of line, which is why relationship cross-links are drawn dashed and kept visually distinct from the solid hierarchy.
8. The map that is only a diagram
The big one, and the one that is invisible while it happens.
You build a genuinely good structure. It is accurate. You show someone. And then you never open it again, because everything you would actually do about it lives elsewhere — a task app, a calendar, your head. The map and the work drift apart within about three weeks, and the map is the one that stops being updated.
This is not a discipline failure. It is what happens when the format cannot hold work. If a branch can only carry a label, the map is a thinking artifact with a short half-life. If a branch can carry a next action, a note, a date, and evidence, the map stays alive because it is where the work is.
When a traditional mind map is not enough
Signs you have outgrown the diagram:
- You maintain a separate to-do list that duplicates parts of the map, and they disagree.
- You cannot tell which branches are finished without remembering.
- The map has not changed in a month, but the work has.
- You keep wanting to attach a file, a link, or a date and there is nowhere to put it.
- Someone asks what is actually done and you have to reconstruct it.
At that point the answer is not a better diagram. It is a map where the branch is a place work lives — which is what Minty Path builds: Plan View for structure, Work View for the branch you are on, with todos, notes, reminders, dates, and proof attached to the branch itself. A branch cannot even be marked Proven without evidence attached, so the map cannot drift out of sync with reality by accident.
Try it without an account if you recognise the drift.
9. Building the whole thing in one sitting
Structure invented before contact with reality is fiction, and expensive fiction, because you will defend it rather than revise it.
Make the first level, stop, and come back tomorrow. What is obviously wrong on second look is the map earning its keep.