Mind map

What the shape is actually good for​

The case for a map over a list is usually made in terms of creativity, which undersells it. The concrete advantages are narrower and more durable:

• Branches coexist. Three readings of the same problem sit next to each other permanently. In any linear medium — a document, a chat transcript — asking about the second angle pushes the first one out of view, and comparing them means scrolling back and holding both in your head.
• Position is memory you do not have to carry. Five levels into an exploration, “which threads have I already followed” is answered by looking rather than by remembering. This is why stable layout matters more than pretty layout: a map that rearranges itself destroys the spatial memory that made it useful.
• Incompleteness is visible. A short branch next to a dense one is a question you have not worked on yet. A list gives you no such signal — every bullet looks equally finished.

Where a map is the wrong tool is equally specific. It is bad for anything with a required order (a procedure, a chronology, an argument that must be read in sequence), bad as a deliverable someone else has to read, and bad for detail — most mapping tools cap a node at a few words, which is fine for a label and useless for a claim.

Where mind maps stop working​

The failure is not the drawing. Software solved the drawing decades ago, and if the value were in arranging boxes, the average mind map would be worth the twenty minutes it took.

The failure is that a map can only ever contain what you already thought of. You sit down in front of a blank centre and fill the branches with your own habitual moves — the three or four angles you always reach for. The map then presents those angles in a satisfying radial layout, which makes a narrow exploration look like a thorough one. That is worse than a list, because a list at least looks unfinished.

The second failure follows from the first: it dead-ends. A finished map is a picture. Turning it into something you can act on — a memo, a plan, a draft — means retyping the whole thing in another tool, which is exactly the moment most maps get abandoned.

So the useful question about any mind-mapping tool is not how good the layout engine is. It is: who fills in the branches, and where does the map go afterwards?

How MindMax handles it​

By filling the branches in. You put a question, a passage, or a document from your folder at the centre, then pick a thinking model rather than typing a branch — SCAMPER, six thinking hats, first principles, a red team pass — and each branch comes back with that method carried out on your material. What you contribute is the judgement: most of what comes back is unremarkable, and deleting it is the work. See the canvas for how that runs, and mental model for what is in the branches.

One question, six thinking hats: each card is a different angle, each holding points you can expand, keep or delete.

Two consequences follow from the design. Each node is a card holding a short list rather than a single word, so a branch can hold an argument instead of a label — denser than a classic keyword map, and deliberately so. And a branch is not a dead end: it can be handed to the writing pipeline as a ready-made outline, or saved into your folder as an ordinary Markdown note. The file itself is open JSON Canvas in your own folder, not a proprietary document.

Where the map goes next: a branch becomes a note, an article, or a Markdown or PNG export.