How to mind map a chapter step by step

Why a chapter map beats a summary

A summary tells you what the chapter said. A map tells you how the chapter was put together, which is the part you have to rebuild to remember it. Building branches as you read means making the moves the author made: deciding what is a main point, what supports it and what is an aside.

The difference shows up at review time. A list of twelve points is a list you have to check yourself against. A map of four themes with three children each is a shape you can look at and ask "what is missing from this branch?" That question is the reason to map a chapter rather than summarize it.

Build the map in the same pass as the reading; a map drawn afterwards records what you already remember. The introduction to mind maps explains how mapping differs from outlining.

• A summary records sentences; a map records structure
• Mapping during reading forces the decisions the author made
• A map gives you a shape to test yourself against
• The map is built in one pass, not reconstructed later

Set up the branch skeleton

Before you read far, decide how many themes the chapter has. Most textbook chapters hold three to five, and that is a good target for the first level. Write the theme names as branches first if the contents page reveals the shape; if not, start with one and add the rest as you meet them.

Add a branch with Tab and a new theme at the same level with Shift+Enter. If you mis-file a node, Shift+Tab returns it to its parent, and Enter or F2 renames it in place. Re-parenting is cheap, so do not fuss over the skeleton while you read.

The Study Notes starter gives you a skeleton to adapt instead of an empty map. It is one of 13 templates in four categories, alongside Essay Planning, Book Summary and Reading List, and the template gallery shows all of them.

1. Name the map. Set the root label to the chapter title and its number, so the map identifies itself later.
2. List the themes you can already name. Add each as a first-level branch, aiming for three to five in total. Leave space for the rest.
3. Add themes as you meet them. Press Shift+Enter for a new theme at the first level rather than inventing filler branches to fill space.

Keep labels short and parallel

A label is a signpost, not a sentence. Two or three words that name the idea is enough, and the detail belongs in the note. Parallel labels matter more than short ones: if one branch says "Cost of capital" and the next says "How firms decide what to invest in", the map reads as two kinds of thing.

Test each label by reading it on its own. If it needs a pronoun it needs to be shorter or more specific. If it needs a qualifier, move the qualifier into the note. Start sibling labels with the same part of speech, so scanning the branch list gives you a list rather than a mixture of kinds.

Node labels hold up to 8,000 characters, so length is never forced on you. The reason to keep them short is that you will read the whole map at a glance during revision, and a branch of thirty-word labels cannot be scanned. The branching rules cover the parallel-label test in more detail.

• Two or three words per label, same grammatical form across siblings
• Move the sentence version into the node note
• Read each label alone: no pronouns and no dangling qualifiers
• Keep sibling branches the same kind of thing

Note: Long labels are not a hard limit. They are a reading problem, and the fix is a note rather than a shorter description of the note.

Put the detail in node notes

Every node can carry a rich note: formatted text with bold, italic, underline, bulleted and numbered lists, and a link you can add. That is where the definition, the worked example, the page reference and the sentence you want to quote belong.

Open the note panel from the node, type the detail, and add a link to the source when you work from an online text. A note can hold up to 80,000 characters, so there is no reason to compress an explanation into a label. If you would rather talk than type, the Dictate button turns speech into note text.

Search reads notes as well as labels, which is what makes them worth writing. Press Ctrl/Cmd+F with the map active and look for a term you half remember: results are ranked, you move through them with the keyboard, and choosing one jumps to the node.

• Definition, example and page reference live in the note
• Add a link to the source inside the note
• Dictate a note when talking is faster than typing
• Ctrl/Cmd+F searches labels and notes, with ranked results

Color the map by theme

The palette holds 8 colors in a Coggle-style set, plus a row of recent colors. Use it at the first level only: one color per theme, so a glance tells you which part of the chapter you are looking at. Press C to cycle the color of the selected node, and the first child of a node inherits the parent color while siblings cycle the palette.

That inheritance rule does the work for you. When you add a child to a themed branch it arrives in the branch color, so a new sub-point looks like part of its theme without you doing anything. If one node needs a different treatment, press C on that node alone.

Do not reach for color as decoration. If a color does not mean a theme it competes with the colors that do, and a map that needs all eight colors is telling you that the branches are not parallel.

• One color per first-level theme, drawn from the 8-color palette
• C cycles the color of the selected node
• Children inherit the parent color while siblings cycle the palette
• Keep the color legend in the root note

Test recall against the map

The review method for a chapter map is a recall test. Cover the map, or pull up a single branch with Ctrl/Cmd+F and hide it, then retell that branch from memory: what was the idea, and what were the three things under it.

Then compare. A branch where you remembered the idea but not the children needs its children rewritten so they say more. A branch you could not recall at all was either written badly or was never really in the chapter, and both are worth knowing now rather than in the exam. The comparison is the review; rereading is not.

Keep the test short: three minutes over four branches tells you where the gap is. Then rewrite what failed and repeat the test a day later on the rewritten branches only. The student guide covers the wider routine.

• Cover each branch and retell it before you unfold it
• Write the retelling down, then compare it with the note
• Rewrite every branch that failed the test
• Repeat the test a day later on the rewritten branches

Note: A map you have only read is a map you have only read. The recall test is what turns the map into usable revision material.

A checklist you can reuse

• The map has three to five first-level branches, one per theme
• The root label carries the chapter title and number
• Every label is short, parallel with its siblings and readable alone
• Definitions, examples and page references live in node notes
• Each theme has one color from the 8-color palette
• The root note holds the source and a short color legend
• A recall test was run with the branches covered

Common mistakes to avoid

• Mapping the chapter after finishing it. A map built from memory records what you already remember. Build it in the same pass as the reading, while the decisions are still being made.
• Full sentences in labels. Long labels turn the branch list into a paragraph you have to read rather than scan. Keep two or three words and move the sentence into the note.
• One branch per page. A chapter has themes, not pages. Branches that follow the page order become a transcript instead of a structure you can revise from.
• Coloring by emphasis. A color that does not mean a theme is decoration, and decoration competes with meaning. Give every color one job and keep the legend in the root note.
• Skipping the recall test. Reading your own map feels fluent, so fluency is not evidence. Cover the branches and test yourself before the chapter is examined.

Frequently asked questions

How long should a chapter mind map take to build?

Roughly as long as the chapter itself, because you build it while reading. For two hours of reading, expect about twenty minutes of typing into the map alongside it, and ten minutes of recall test afterwards. The typing is not extra work, it is where the structure forms.

Should I use a template or start from an empty map?

The Study Notes starter, one of 13 templates in four categories, saves you the blank page and gives you a skeleton to rename. Delete the branches that do not apply to your chapter and add the ones it is missing. An empty map works well if you already know the shape the chapter takes.

What if the chapter has more than five themes?

Group them. Put the larger themes on the first level and let the smaller ones become children, and stop at three levels of depth. If the map still does not fit on one screen, check whether two of your themes are really one theme with two names.

Can I search a chapter map later?

Yes. Press Ctrl/Cmd+F while the map is active and search labels and notes together, with ranked results and keyboard navigation. Search only works when a map is the active surface, so switch to the map tab first if the canvas has focus.

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.