Plot mind map for a novel

Fix the ending you are writing toward

Put the ending at the root of the map. Not the theme and not the premise: the ending, in one sentence that names the final scene and what it costs. Everything you branch from that root has to be consistent with it.

Under the root, add three children: the final scene, the thing the protagonist has to give up to reach it, and the question the reader is left holding. A novel usually resolves the second of those and deliberately leaves the third open, and writing both down early keeps you from resolving it by accident in the last chapter.

If you genuinely do not know how it ends, write three endings as sibling nodes instead of one. They will share some turns and contradict others, and the shared turns are the part of your story that is already decided. Cross-link each ending to the turns it depends on and the spine appears on its own.

• The root is the ending in one sentence, not the premise
• Children: final scene, what it costs, the question left open
• Three possible endings reveal the turns they share
• Every branch upstream has to be consistent with the root

Note: An ending you would not want to read is still an ending. Committing to one on the map is cheaper than discovering your dislike in the last week of a draft.

Map the protagonist's want and need

Make a branch for your protagonist and split it in two. Want is the external goal the plot is about: the job, the escape, the recovered relationship. Need is the internal change the story forces: the truth they have to admit, the habit they have to drop.

Under each, add what the protagonist believes at the start. That belief is normally wrong, and it is the thing the plot has to break. It is also the cheapest way to check your turning points: a turning point that does not dent the belief is scenery, however well written.

Name the antagonist's want in the same shape as the protagonist's. When both sides want the same thing from different angles, the map reads like a story, and when the antagonist has no want at all, the villain work turns into obstacle work and the plot gets tired.

• Want is the external goal, need is the internal change
• The opening belief is usually wrong and must be broken
• The antagonist gets a want in the same shape
• Every turning point puts pressure on the belief

Note: Protagonists who get what they want without learning anything usually feel like a series of events. If the map has no belief under the character, that is often why.

Branch each turning point by consequence

This is the part that changes the map from a synopsis into a plot. A turning point is a choice the protagonist makes, and the branch beneath it is what that choice costs. The cost is a consequence that lands on somebody, and it is what forces the next choice along.

Give each turning point three children: the choice made, the immediate cost, and the situation the character is now in. Build the sequence with Shift+Enter to add sibling turning points in order, so the chain reads left to right. The map then shows a causal spine rather than a list of things that happen.

Test the chain by reading only the cost children. If the costs do not push the next choice, the story has episodes rather than a plot. Add a consequence for each turn until every turn makes the next one nearly unavoidable, and you have found the shape of the book.

• A turning point is a choice, and its child is the cost
• Children: choice made, immediate cost, new situation
• Shift+Enter adds sibling turns in story order
• Reading only the cost children reveals the causal chain

Note: Consequences that hurt nobody do not drive a story. If the cost of a decision is only inconvenience for the person who chose it, the turn can usually be cut.

Keep the threads you must pay off

Every subplot, secret and recurring object is a thread, and each one needs a branch with three children: where it is planted, the promise it makes to the reader, and where it is paid off. A thread branch without a payoff child is a debt the book has taken on, and readers remember debts better than they remember payoffs.

Cross-link the plant to the payoff so you can see the pair at a glance. A plant with no payoff attached is either a promise you have not made yet or a setup you have forgotten, and both are worth knowing before the readers point them out.

Use the layer stack to hold the threads apart. Put the timeline on one layer and each character or thread group on another, up to 8 layers in total. The 3D stack guide explains the explode slider and trace mode, which show the threads hovering over each other.

• Each thread has a plant, a promise and a payoff
• Plants are cross-linked to their payoff
• One layer for the timeline, one per thread group
• Trace mode shows links that cross between layers

Note: Deleting a layer keeps the nodes on it, so you can rearrange threads between layers freely. A map with no payoff node anywhere is the most common reason a reader says the ending felt unearned.

Find where the middle sags

The middle is where the map earns its keep. Collapse every branch except the middle third and read what is left. A sagging stretch is a run of beats where nothing is lost and no one is forced to decide anything. You can see it on the map, because the cost children do not escalate.

Compare the density of consequences at the start, the middle and the end. If the middle has half the consequences of the other two, it will read as a pause, and readers commonly stop in the middle of a book rather than at the end. The fix is one larger irreversible decision, not three more scenes.

Look for the other cause of a sag: a branch that has been open for a long time. An unresolved thread introduced in the first quarter and not touched again will pull the reader out of the middle when they realize they are still waiting for it. Cross-links make those long threads visible.

• Collapse to the middle third and read only the costs
• A sag is a run of beats with no escalating consequence
• The middle needs roughly as many turns as the beginning
• Long-open threads pull the reader out of the middle

Note: A sagging middle is usually a missing decision rather than a missing scene. Adding another event to a plot with no pressure in it just makes the slow part longer.

Test the shape before you draft

Read the map end to end before you write prose. Export it as Markdown and read the outline as a document, because a tree you scroll through hides pace in a way that a flat list does not. Anything that reads badly as an outline reads worse at 90,000 words.

Sketch the shape on the root node. The node thumbnail can hold a freehand drawing, with color and a brush you choose, so you can draw the emotional curve of the book next to the structure and compare them. If your curve is flat while your structure climbs, one of them is lying, and it is easier to find out now.

Walk the top level in presentation mode. Press P for the root slide and then one slide per first-level branch, which is a fast way to check that each arc has its own shape. The chapter mapping guide takes the map into per-chapter detail, the book summary guide covers how to record what an existing novel is doing, and the complete Canvasola guide covers the tool itself.

• Markdown export gives you a flat outline to read for pace
• Sketch the curve on the root node's freehand thumbnail
• Presentation mode walks one slide per top-level arc
• The shape is settled before the prose starts

Note: You are allowed to change the map later. That is the point of testing before drafting: the map is where changes cost an afternoon, and the draft is where they cost a month.

A checklist you can reuse

• The root label states the ending in one sentence
• Protagonist want and need are on separate branches
• The opening belief and the antagonist's want are written down
• Every turning point has a choice, a cost and a new situation
• Reading only the cost children produces a causal chain
• Every thread branch has a plant, a promise and a payoff
• Plants are cross-linked to their payoffs
• The middle third has been collapsed and read for sagging

Common mistakes to avoid

• Mapping scenes in order. A branch per scene records what happens but not why. Branch by consequence instead, so the map shows the chain of cause and effect rather than a calendar.
• Threads without payoff. A subplot with no payoff node is a debt the book has taken on. Readers forgive a twist; they rarely forgive a promise that was never kept.
• Fixing the ending after the middle. Changing the ending once you have written the middle invalidates the turns that pointed at the old one. Fix the root first and let the branches answer to it.
• Adding scenes to cure a sag. More events in a plot with no pressure in it produce a longer slow stretch. A sagging middle needs one larger irreversible decision, not more material.
• No antagonist want. When the opposition has no want of its own, they become obstacles instead of characters. Give them the same want-and-need shape as your protagonist.

Frequently asked questions

How detailed should a plot map be before I start drafting?

Detailed enough that every turning point has a choice and a cost, and every thread has a payoff. That is usually a few dozen nodes for a novel. A single Canvasola map holds up to 2,000 nodes, so a plot of this size fits with room to spare.

Do I have to know the ending before I write?

No, but you should know it on the map. Writers who improvise keep the ending somewhere else, and it leaks into the middle as a limp or a surprise that contradicts page forty. Three candidate endings on sibling nodes is a workable compromise.

Can I keep characters on separate layers?

Yes. Put each character or thread group on its own layer, with the timeline on another, and the stack holds up to 8 layers. The layer tabs let you read one thread at a time, and the 3D view shows how the threads overlap in time.

What if my plot map looks like a list of events?

It probably is one. Read only the cost children of each turn, and if the costs do not force the next choice, add consequences until they do. A plot is a chain of pressure, and events without pressure are a chronology.

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