The definition
A mind map is a diagram with one subject at the centre and related ideas branching outward, where the position of something carries meaning. Distance from the centre indicates how specific it is; branches that share a parent are related; the shape of the whole thing shows you how the subject is organised.
That last part is what separates a mind map from a drawing with lines on it. In a mind map, the structure is the content. Move a branch and you have made a claim about how the subject works.
Why the format does anything useful
The honest answer is not the one usually given. You will read that mind maps mirror how the brain stores information — the "radiant thinking" claim from Tony Buzan, who popularised the format in the 1970s. The neuroscience behind that specific claim is weak, and it is worth being straight about it.
What is defensible is narrower and more practical:
A list forces a sequence you may not have. Writing five items top to bottom implies an order. Often no order exists yet, and inventing one quietly commits you to a plan you have not thought about.
Hierarchy is visible instead of remembered. In an indented outline, "is this a sub-point of that one?" requires counting indentation. On a map it is a line you can see.
Non-linear editing is cheap. Adding a branch between two others costs nothing. In a document, inserting a section means renumbering and re-reading.
Peripheral vision does real work. With twenty branches on screen you notice that two say the same thing in different words. In a scrolling list you never see them together.
That is a genuine set of advantages. It is not "your brain works this way."
When it is the right tool
- You do not yet know the categories. Mapping lets structure emerge instead of demanding it upfront.
- The subject has parts that relate to each other, not just a sequence of steps.
- You are trying to see the whole thing at once — the size of a problem, the areas of a job, the scope of a decision.
- Several people need to agree on what the thing contains before arguing about order.
- You are returning to something after a gap and need to reload the shape quickly.
When it is the wrong tool
Worth saying, because mind maps get recommended for everything:
- You already know the order. That is a checklist. A map adds ceremony.
- The content is fundamentally prose. An argument with nuance loses the nuance when reduced to branch labels.
- You need one number. Spreadsheet.
- The thing is genuinely a sequence — a recipe, a deployment, an onboarding. Steps are steps.
- Someone else needs to act on it without you present. Maps are excellent thinking tools and mediocre handover documents.
The part most maps get wrong
A mind map's usual failure is not being ugly or disorganised. It is being finished and inert: a good structure that you never open again, because everything you would actually do about it lives somewhere else — a task app, a calendar, your head.
This is why "mind map" and "planning tool" have drifted apart. Traditional mapping tools optimise for the diagram. The diagram is a thinking artifact, and thinking artifacts have a short half-life unless the work attaches to them.
The fix is structural: a branch has to be able to hold more than a label. If a branch can carry a next action, a note, a date, and evidence that something happened, the map stays alive because it is where the work is. If it can only carry a label, you have made a picture — and pictures are for the moment of thinking, not the months afterwards.
Minty Path is built around that specific gap. A Growth Path is a map you can work inside: Plan View for the structure, Work View for the branch you are on, with todos, notes, reminders, dates, and proof attached to the branch they belong to. You can try it without an account — the real canvas, saved in your browser.
The vocabulary
- Central topic / root — the subject. One per map. If you have two, you have two maps.
- Branch — a major area. Usually three to seven at the first level.
- Sub-branch / child — a subdivision. Depth costs readability; go deep only where it changes a decision.
- Leaf / end branch — a branch with nothing under it. Where actual work usually attaches.
- Cross-link / relationship — a connection between branches that are not parent and child. This is where dependencies live, and it should look visually different from the hierarchy or the map lies about its own structure.
Getting started without overbuilding
The first map should take about ten minutes:
- Write the centre as a question, not a category. "How do I move into data work?" beats "Career."
- Add three to six branches — things that could each fail for their own reasons.
- Stop. Do not go three levels deep on day one. Detail invented before you have looked at the shape is mostly guesswork.
- Leave it. Come back tomorrow and notice what is obviously wrong. That reaction is the map doing its job.