{{ summaryTitle }}
{{ summaryValue }}

{{ summaryLine }}

Main branches{{ resultsReady ? computation.values.root_branch_count : '—' }} Levels{{ resultsReady ? computation.values.max_depth : '—' }} Layout{{ resultsReady ? layoutLabel : '—' }}
Up to 80 characters. This becomes the map's center.
One idea per line; indent child ideas by two spaces. Up to 30 ideas and 5 levels.
Balanced is best for overview; directional layouts suit linear reading.
Colors distinguish main branches; hierarchy remains readable without color.
The neutral default keeps the outline order unchanged.
{{ sort_siblings ? 'Alphabetical within each branch' : 'Keep entered order' }}
{{ line }}{{ line }}

{{ mapExportStatus }}

The chart renderer is unavailable. Branch sizes remain available in the idea outline.

{{ chartExportStatus }}

IdeaParentLevelMain branchCopy
{{ row.label }}{{ row.parent }}{{ row.depth }}{{ row.branch }}

{{ tableExportStatus }}

Meeting Agenda Generator Build a timeboxed meeting agenda from outcomes and owned topic rows, with exact overrun minutes and practical facilitation checks.
RACI Matrix Generator Build a RACI matrix from activity rows and find missing owners or overloaded roles before the project handoff reaches the wider team.
Revision Schedule Planner Build a revision timetable around exam dates and weekly availability, with subject coverage plus spaced priorities and capacity warnings.
Visual Schedule Cards Generator Create printable visual schedule cards from routine rows with picture cues and first-then options plus timing estimates and page planning.

A mind map organizes one subject into branches and nested ideas. The central topic sets the scope, main branches divide that scope into themes, and child ideas add detail beneath the branch they belong to. This hierarchy is useful for planning, studying, outlining, and breaking a broad subject into manageable parts.

The quality of a map depends more on relationships than decoration. A short label makes a node easier to scan, while a clear parent makes its meaning understandable. If an idea belongs to several branches or needs cross-links, a network-style concept map may be a better fit than a strict tree.

LayoutReading patternUseful for
BalancedMain branches spread to both sidesOverview and comparison
Left to rightIdeas follow one horizontal directionLinear explanation and presentation
Top to bottomLevels descend verticallyProcess-like or outline-style reading

Changing layout or color does not change the hierarchy. Alphabetical sorting does change the order of ideas within each parent, so entered order should be kept when sequence, priority, or chronology carries meaning.

How to Use This Tool:

Draft the hierarchy as a short outline before choosing how it should look.

  1. Enter a concise Central topic that covers every branch.
  2. Write one idea per line in Idea outline. Use two leading spaces for each child level and never skip a parent level.
  3. Choose a Map layout for the intended reading direction and a branch palette for visual separation.
  4. Enable Sort sibling ideas only when alphabetical order is more useful than the order you entered.
  5. Review the map and branch counts. Correct the outline when a node appears under the wrong parent or one branch carries too many unrelated ideas.

Interpreting Results:

The displayed branch and level counts describe structure, not idea quality. A large branch may need splitting, but it may also be appropriately detailed. A small branch may need more thought or may simply represent a narrow topic.

Use the outline view to confirm each parent, level, and main branch. The visual map can make a misplaced node look plausible, while the hierarchy table exposes the exact relationship.

Technical Details:

An indented outline describes a rooted tree. Each non-empty line becomes one node; its indentation depth determines its level, and the nearest preceding node one level above becomes its parent. The same valid outline always produces the same hierarchy.

Transformation Core

Outline textDepthParent rule
No leading spacesLevel 1Direct child of the central topic
Two leading spacesLevel 2Child of the nearest previous level-1 idea
Four leading spacesLevel 3Child of the nearest previous level-2 idea
Blank lineNoneIgnored

Rule Core

  • Indentation must use pairs of spaces. Tabs and odd numbers of leading spaces are rejected.
  • A line cannot jump to a deeper level when the required parent level does not exist.
  • Optional list markers such as a dash, asterisk, or bullet are removed from the start of a label.
  • The map accepts up to 30 ideas, five levels, 80 characters per topic or idea, and 3,000 characters in the outline.
  • Sibling sorting is case-insensitive and applies separately within each parent. It does not move an idea to another branch.

Layout and palette are presentation choices applied after the tree is built. Branch size counts every idea in that main branch, including all descendants.

Worked Example:

A project with one nested task

For the central topic Project, enter Goals, then Scope on the next line with two leading spaces, followed by People with no indentation. The result has two main branches, Goals and People, while Scope appears as a child of Goals.