How to branch a mind map with a rule

One idea per branch

A branch is a claim, not a container. If a label needs the word "and", it holds two ideas, and the map has lost the property you need most: you should be able to read a branch label and know what sits on it. Split it into two siblings.

This rule is what makes a map reusable. A map of single-idea branches can be exported to Markdown, printed, or re-read six months later by someone who was not there. A map of compound labels can really only be read by you, in the order you happened to think in.

Canvasola allows 8,000 characters per node label, so there is no technical excuse for an overloaded label. That limit protects the canvas rather than encouraging long text. If you are writing toward it, the branch is doing too much work.

• A label that needs the word "and" is two branches
• One branch answers one question about the topic
• If you cannot restate a branch in five words, split it
• Long detail belongs in a node note, not the label

Note: The rule applies to branches, not to the root. A root label may be a phrase, because it names the subject rather than one part of it.

Make sibling labels parallel

Siblings are read as a list, so they should share a grammatical form. All nouns, such as Budget, Timeline and Owners. All verbs, such as Estimate, Schedule and Assign. Or all questions. Mixed forms force the reader to translate each label into a common shape before comparing them.

Parallel labels are what make a map skimmable, and skimmability is the reason for drawing it. You should be able to look at a branch, read only the first words of each child, and already have the shape of the answer. When you must read whole sentences, you wrote a list and drew a frame around it.

Fix parallelism where the cost is lowest. Renaming one label is a two-second edit; renaming six to match it is one short pass. A map with five parallel branches and one outlier is still a map, but a map where every branch takes a different form is a list wearing a disguise.

• Pick one form for the level: nouns, verbs or questions
• Start every label the same way when order matters
• Keep sibling labels roughly the same length
• One label written differently? Rewrite the level

Keep the depth to three levels

Three levels below the root is usually the most a reader can hold at once. Level one is the subject, level two a category, level three an item. Anything below that is detail, and detail belongs in a node note, where it can be searched and read on demand.

Deep maps are also slow maps. Every extra level means holding the parent chain in mind to read a leaf, and taking more horizontal room in tree mode. If a branch runs four levels deep, the fourth level is usually a note in disguise.

If your topic has more depth, split it across layers instead of digging deeper. Canvasola lets you scope a map to one layer at a time, so a four-level subject can become two three-level layers. You keep the reading depth and lose the sprawl.

• Level one is the subject, level two a category, level three an item
• A fourth level is usually a note
• If the topic is deeper, use layers rather than nesting
• A deep branch usually means the root is too broad

Note: Canvasola allows up to 2,000 nodes in a single map, so nothing stops you building a deep tree. That limit protects performance, not your reading.

Add a child without breaking the rule

Canvasola's mind map shortcuts let you extend a branch without leaving the keyboard. Tab adds a child to the selected node, Shift+Enter adds a sibling next to it, and Shift+Tab moves the selection back to the parent. Rename any node with Enter or F2, and a whole branch can be built this way.

The order you use them in keeps the map clean. Add the parent first, Tab to its first child, Shift+Enter across the siblings, and only then go one level deeper. Building a level at a time lets you check the labels against each other before they are buried under children.

If a new branch breaks the rule you set, fix it while it is a keystroke away. Splitting a compound label into two siblings costs two Shift+Enter presses. Finding the same problem three levels down costs a pass over the whole branch. The shortcut cheat sheet has the full list of map keys.

1. Add the child. Select the parent node and press Tab to create a child underneath it.
2. Add the sibling. Press Shift+Enter to add a peer next to the current node, then type the next label.
3. Step back up. Press Shift+Tab to return to the parent and check that the sibling labels still read in parallel.
4. Rename in place. Press Enter or F2 to edit a label, and keep it short enough to scan in one glance.

Move a branch when the logic moves

Thinking changes, and a branch that sat under one node often belongs under another. When you move a branch, the node travels with its children, so the subtree stays intact rather than leaving orphans behind. Shift+Tab walks you up toward the root one level at a time, which is how you find the parent you had in mind and see what already sits beside it.

Moving is not the same as merging. If two branches are really one idea under two names, merge them rather than nesting one under the other. A map with two branches both called Budget still gives the reader two things to plan, and the work gets done twice.

After a batch of moves, run auto-arrange to clear the manual positions and let the layout settle again. Moved nodes leave gaps and crossings behind, and rebuilding is faster than nudging each one back. The radial versus tree guide explains what that rebuild does.

• Shift+Tab walks up the tree to find the parent you meant
• Merge duplicates instead of nesting them
• Press A afterwards to clear stale positions
• Undo with Ctrl/Cmd+Z if a move was wrong

Name the root precisely

The root label is the one line that has to work without context, because it is what a reader sees first and what appears alone on the first slide in presentation mode. Name it as the question or the claim the map answers. "Q3 rollout risks" is a map. "Q3" is a folder.

A precise root makes the branches easier to name, because you already know what counts as a branch. If you cannot write a good root label in one line, the map often covers two subjects and wants to be two maps.

The root is also where you put the note that explains the map to a stranger. One short note saying what the map is for and when it was written saves the next person an email. If you have never drawn a map before, what a mind map is for covers the basic shape first.

• Name the root as a question, a claim or a decision
• Keep it to about eight words
• Use the root note to say what the map is for and when it changed
• If two root labels keep fighting, split the map in two

Note: Presentation mode opens on the root label alone, so a vague root means a vague first slide. Fix the root before you present, not in the room.

A checklist you can reuse

• Every branch label carries a single idea, with no "and" hiding a second one
• All siblings at a level are written in the same grammatical form
• Nothing sits more than three levels below the root
• Detail that outgrew a label sits in a node note instead
• The root names a question, a claim or a decision in about eight words
• Duplicate branches were merged rather than nested
• Auto-arrange was run after the last round of moves

Common mistakes to avoid

• Compound labels. A branch labeled "Design and test" holds two branches in one string, and neither can be followed up on its own. Split it into two siblings while it is still short.
• Mixed sibling forms. One noun, one verb and one question at the same level makes the reader convert each label before comparing them. Pick a form and rewrite the level.
• The fourth level. Detail that keeps growing downward ends up as a deep branch nobody reads to the end. Move it into a node note, or split the subject across layers.
• A vague root. A root like "Project" or "Research" tells the reader nothing, and it is the only line visible on the first presentation slide. Name the decision instead.
• Nesting duplicates. Moving a branch under a near-identical branch creates two versions of one idea that will both get worked on. Merge them into one branch with two children.

Frequently asked questions

How many branches should a mind map have?

There is no fixed number, but a branch count you can hold in your head is the useful limit. If you have to scroll to remember what is on the far side, the map is too wide to read as one thing. Splitting into layers beats adding more branches at the top.

Does the 8,000 character limit per node label mean long labels are fine?

No. The limit only protects the canvas, and a label that long is really a note. Canvasola stores notes separately with formatting, links and dictation, so keep the label short and put the detail where it can be searched later.

Should branch labels be complete sentences?

No. Labels should be parallel, short phrases that can be scanned in one glance. Sentences belong in the node note, where they can be formatted, searched and read properly instead of crowding the structure of the branch. A label that reads as a sentence is a note you have not moved yet.

This guide is part of the mind mapping guides collection. For the wider product tour, read the complete Canvasola guide, and keep the keyboard shortcut cheat sheet open while you work.