How to mind map a book without a summary

Central claim as the root

The root of a book map is the sentence the book wants you to accept. Write it in your own words, in one line, and if you cannot manage it yet, that is the first thing the book owes you. A root reading "Book Summary" tells you nothing; a root reading "Remote work pays off when office time is wasted" tells you what every branch must support.

A claim root makes disagreement visible. When a branch seems to argue against the root, you have found the counter-argument, the qualification or a section the author treats as secondary, and each deserves a place. A book you dislike is easier to write about this way.

For fiction the root is the central question rather than a claim: "what does it cost to return home?". Either way the root should be something you could use as an essay title. The introduction to mind maps explains how the root shapes everything below it.

• One sentence in your own words, never the book title
• The root is arguable: a reader could disagree with it
• If you cannot write the root, keep reading before you map
• The root later becomes the title of your essay

Branches for the argument, not the chapters

Chapter branches reproduce the book's structure, and argument branches reproduce its reasoning. A chapter order is often a delivery choice, while the argument might run claim, mechanism, evidence, objection, answer. If your branches match the contents page one for one, you have built a contents page with extra steps.

Give each branch one job. "How the mechanism works", "The evidence offered" and "The strongest objection" are jobs; "Chapter 3" and "Chapter 4" are none of them. When two branches do the same job, lift one with Shift+Tab and give the merged branch a label covering both.

Add branches with Tab and Shift+Enter, and use Shift+Tab to raise a node to its parent when it belongs elsewhere. Parallel sibling labels matter more for an argument map than for almost any other kind.

1. Write the root claim. One sentence, your own words, in the root node. If you cannot, read further before mapping anything else.
2. List the jobs of the argument. Name what the book must do to convince you: mechanism, evidence, objection, answer. Ignore chapter order.
3. Give each job one branch. Add a branch per job with a short label, and merge any two branches doing the same job.

Evidence and quotes go in notes

A branch that says "two firm studies show a 12% drop" proves nothing on its own. The evidence belongs in the note: the study, the sample, the figure, the page, the date. Node notes hold rich text with bold, italic, lists and links, so a quotation can sit under its branch with its citation attached.

Add a link inside the note when you work from an online text or a source you want to return to. Each note holds up to 80,000 characters, enough for a quotation, a summary and your reaction. You can also attach an image to a node: PNG, JPEG, WebP or GIF up to 1.5 MB.

Search reads notes as well as labels, so a well-noted map is searchable later. Press Ctrl/Cmd+F with the map active to find a half-remembered quotation, and choose a result to jump to the node. The notes guide covers the panel, links and Dictate.

• Study, sample, figure, page and date go in the note
• Link the source inside the note
• Attach a cover or diagram image, up to 1.5 MB
• Use Dictate when talking beats typing

Character or theme branches that carry the map

Some books are carried by people rather than claims. When a novel's map keeps growing under one character, that character is a branch and claim-shaped branches are the wrong frame. A useful fiction map holds the central question in the root, one branch per major character or theme, and a second level for wants, obstacles and change.

Cross-links do the work here in a way they do not in an argument map. Draw a link between two nodes to show that two characters meet, that a theme echoes later, or that one object carries the plot. Cross-links are tubes with no label editor, so describe the relationship in a node note.

The 3D layer stack can hold one book at two depths, with characters on one layer and themes on another, and trace mode shows the links that cross between them.

• Root holds the central question, branches hold characters
• Second level: wants, obstacles, what changes
• Links show meetings, echoes and recurring objects
• Describe the link in a node note, tubes have no label

One map per book, not per edition

Keep one map per book. Editions have different pagination and occasionally different endings, and a second map for the paperback means you no longer know which one your notes belong to. Put edition-specific detail in the notes with a marker such as "2nd edition, p. 143", and keep the argument in the branches. For a set text, the study mind map template applies the same shape to a single chapter.

Longer books exceed what one pass can hold, and a map of 2,000 nodes is not useful. Split a long book by part: the 2D layer tabs scope the map to one layer, a maximum of 8 layers is allowed, and keeping the root claim in the first layer keeps it in view. Layers keep a big book readable.

Export the map when the book is finished so the thinking outlives the session. A mind map exports to Markdown or OPML 2.0 as text and to SVG or PNG as images, and a multi-layer map round-trips with its layer tags intact.

• One map per book, whatever edition you read
• Edition and page details live in the notes
• Split a long book into layers, up to 8
• Export to Markdown or OPML 2.0 when it is done

Turn the map into an essay plan

The map is not the essay, but it is the essay's plan. Your first-level branches are candidate paragraphs in the order the argument runs, and each branch's children are the sentences and evidence that support it. Write the paragraph order from the map, then draft each paragraph against its own branch and note.

The review method for a book map is an argument trace. Close the book, say the root claim, then name each branch and the evidence under it, in order. A branch you cannot state is one you do not yet understand, and evidence you cannot place is decoration rather than support. The guide for students turns a traced argument into revision questions.

The Book Summary starter is one of 13 templates in four categories and gives you a shape to rename rather than an empty map. The template gallery lists them all, and from there the same branches become the outline you draft against.

• Branches become paragraphs, in the order the argument runs
• Children become the sentences and evidence for that paragraph
• Trace the argument aloud with the book closed
• Four to eight first-level branches is a typical working size

A checklist you can reuse

• The root states a claim or a central question in your own words
• Branches describe the argument's jobs, not the chapter order
• Sibling branch labels are parallel and do one job each
• Evidence, quotes and page references are in node notes
• Every branch has at least one piece of evidence under it
• The map holds one book, with edition details in the notes
• The argument was traced aloud with the book closed
• The map was exported to Markdown or OPML 2.0

Common mistakes to avoid

• Branches that match the contents page. A chapter-by-chapter map is a contents page with extra steps. Branch by the job the argument does, not by page order.
• A root that is the book title. The title says nothing about what the book argues. Write the claim in one sentence, and revise it if the book argues otherwise.
• Evidence on the branch. A branch holding a statistic gives you a claim with no support. Move the study, the number and the page into the note.
• One map per edition. Two maps mean two half-trusted versions of the same thinking. Keep one map and mark edition-specific pages in the notes.
• Treating the map as the essay. A map is a plan, not a draft. Write each paragraph against a branch and its note, then check the argument traces.

Frequently asked questions

How do I mind map a novel rather than an argument?

Put the central question in the root instead of a claim, then give each major character or theme a branch with wants, obstacles and change underneath. Use cross-links for the relationships the tree cannot show, such as a meeting between two characters, and describe each link in a node note.

Can I use images from the book in the map?

Yes, a node can hold an image in PNG, JPEG, WebP or GIF format, with an upload limit of 1.5 MB. You can also draw freehand on a small node canvas and save that into the same thumbnail slot, which suits a diagram you would otherwise have to describe in a note.

What can I do with the map once the book is finished?

Export it as Markdown or OPML 2.0 to keep the structure as plain text you can search and reuse, or as SVG or PNG to keep the shape. The branches then double as an essay outline, a review skeleton or a set of revision questions you can reuse for the next book.

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.