A board meeting mind map that ends in a decision

Decide what the meeting must conclude

A meeting that concludes nothing has consumed an hour of eight people's attention. Before you build the map, write the one sentence that must be true when everyone leaves: the 2027 budget is approved, and the hiring plan stays paused until the March numbers land.

Put that sentence in the root label and give it two children. One branch lists the decisions the meeting has to reach, and the other lists the items that are for information only. Everything that follows hangs off those two lists, so it is obvious at a glance which items still need a call.

If you cannot write the sentence, the meeting is a briefing rather than a board meeting, and it probably belongs in an email. That is a useful conclusion, and it is far cheaper to reach it before the pre-read goes out than after five people have read it. The complete Canvasola guide shows how a map is started and saved.

• The root label states the outcome the meeting has to produce
• One branch for decisions needed, one branch for information only
• Information items are named so they can be skipped without argument
• No meeting goes in the diary without its required outcomes written down

Note: A root label that reads like a title gives the map nowhere to go. The sentence after it is what turns a calendar entry into a decision the board can be asked for.

Give every agenda item a branch

One branch per agenda item, in the order the chair will take them. Under each branch, add four children: the decision required, the options considered, the recommendation, and the owner. The Meeting Notes template, one of the 13 starters, gives you that skeleton, and you delete the parts this meeting does not need.

Keep the items that need no decision on their own branch. A branch labeled Finance update with no decision under it tells the room it can relax, and it takes two minutes instead of twenty. It also makes the real agenda visible: the branches that do require a call.

Add a branch for anything that arrives late, and do it honestly. Pre-reads change, and a map that shows a new branch added on the morning of the meeting is more useful than one that pretends the item was planned. Everyone can see what moved.

• One branch per item, in the order the chair will take them
• Children: decision required, options, recommendation, owner
• Information items live on a separate branch
• Late additions get their own branch rather than being buried

Note: If an item needs more than four children, it is really two agenda items wearing one name. Splitting it takes a minute and saves the meeting a digression.

State the decision on each branch

Write the decision as a sentence with a verb in it: approve the 2027 budget at 4.2 million, or pause hiring in the support team until March. A label like Budget tells the reader nothing, and the minute-taker ends up inventing the wording that will bind the company.

Test each label with a simple question: could someone who was not in the room record this decision without interpretation? If the label contains the word and, it is probably two decisions on one branch, and two decisions take twice as long to reach.

Keep the options to three or fewer on the branch, with the recommendation named. More than three options on a slide or a branch reads as a lack of preparation, and the extra options usually belong in the note with the reasoning that disqualifies them.

• Every decision label starts with a verb
• No label contains the word and
• Three options maximum on the branch
• The recommendation is named, not implied

Note: Write the decision label as you would like it to appear in the minutes. If the phrasing is awkward, the decision is not ready to be taken yet.

Attach the evidence in the notes

The branch carries the decision and the note carries everything behind it. Open the rich note on the agenda item and use its bulleted list: one bullet per figure, one per source document, one per risk. The notes guide covers how the note editor works, including the numbered list and links.

Record numbers with their origin. Write the cell reference for a figure that came from a sheet, and the date you pulled it, because a number without a date is an opinion. If two branches rely on the same figure, cross-link them so nobody revises one and forgets the other.

Keep the deck separate from the map. The map is where the reasoning lives and the place the board reads before it arrives. When the meeting happens, the branch is what you project or read from, and the note is what you answer a question from.

• One bullet per figure, source document and risk
• Every number carries its origin and the date it was pulled
• Shared figures are cross-linked between branches
• The reasoning lives in the note, the decision lives in the label

Note: A rich note holds up to 80,000 characters, so there is no pressure to trim the evidence out of the map and lose it between drafts.

Name the owner and the deadline

Two more children on each decision branch: the owner, with the actual name and role, and the date by which the decision has to be made. A team cannot own a decision, so write a person. If that person is not in the room, the branch is a report-back item and should be written as one.

Add a third child for what happens if no decision is taken. That default, whether it is defer to the next meeting or proceed at the current level, turns a stalled discussion into a known outcome rather than an argument about process. It is the branch that saves the last ten minutes.

Tie the deadline to something that already exists: the date the accounts are due, the quarter the hiring starts, the month the contract renews. A deadline invented for the meeting will slip, because nothing in the business is waiting on it.

• The owner is one named person with a role
• The deadline is tied to a date the business already has
• Each decision branch says what happens if it is not taken
• Items owned by people outside the room are marked as report-backs

Note: If the owner is missing, the branch is not ready. A decision without an owner is a discussion, and a discussion can be recorded as a decision by accident.

Circulate the map as the pre-read

Export the map as Markdown and send the file as the pre-read, at least two days before the meeting. The export is a plain outline, so it opens in any text editor and anyone can read it without installing anything. There is no shared editing session in Canvasola, so the file is the artifact the board receives.

Use layer tabs when part of the map is sensitive. Scoping the map to one layer lets you read exactly what a restricted section contains before anything leaves your screen, and moving a branch to another layer is safe because deleting a layer keeps the nodes on it.

In the room, press P. The first slide shows the root label and its required outcomes, then each first-level branch takes one slide showing the branch label with its immediate children, which is exactly the shape a decision branch has. The business plan guide shows the same branch discipline for numbers that need approval, and the version history keeps 20 versions if the pre-read changes late.

• Markdown export, sent two days ahead of the meeting
• Layer tabs scope the map when one section is restricted
• Presentation mode runs the meeting, one slide per branch
• Version history holds 20 snapshots if the pre-read changes

Note: A pre-read is a promise about attention. Send it early enough that a director can read it properly, because a document that arrives the night before is read on the way to the room.

A checklist you can reuse

• The root label holds the outcome the meeting has to produce
• Every agenda item has its own branch, in the chair's order
• Each decision label starts with a verb and contains no and
• Information-only items are separated from decision items
• Each decision branch has options, a recommendation and an owner
• Every decision branch names its fallback if no call is made
• Evidence is in rich notes, with numbers, origins and dates
• The Markdown pre-read was sent at least two days in advance

Common mistakes to avoid

• Agenda copied from the last meeting. Reusing last quarter's agenda items keeps decisions that were already taken and misses the ones that have become urgent. Rebuild the agenda from the outcomes the company needs.
• Topic labels instead of decisions. A branch labeled Budget leaves the actual decision to the room. Write the sentence you want recorded in the minutes.
• Evidence buried in a deck. If the numbers only exist in a slide deck, the pre-read becomes the deck. Put the reasoning in the rich notes where people can read it in advance.
• Owners written as teams. A department cannot be chased for a decision. Name the person, and if they are not attending, mark the branch as a report-back.
• Pre-read sent on the morning of the meeting. Directors who open the document during the opening remarks have not read it. Two days is the minimum that makes the meeting shorter rather than longer.

Frequently asked questions

How long should a board meeting map be?

Six to ten branches for a full board, fewer for a committee. Each branch holds one decision with its evidence in the note. If the map has twenty branches, the meeting has twenty items, and the problem is the agenda rather than the map.

Can the board edit the map themselves?

No shared editing is available, so the board receives a file rather than a live document. Send the Markdown export, collect replies in whatever way your board already does, and update the map once with everything that came back. One clear version of the decisions is worth more than three drafts.

How do I keep confidential items separate?

Put the restricted branches on their own layer and use the layer tabs to read that layer on its own before anything is sent. Moving branches between layers is safe, and deleting a layer keeps the nodes, so tidying the stack never loses work.

What if a decision needs more than one meeting?

Split it into two branches with two deadlines, and put the reason for the split in the note of the first one. A branch that waits for a follow-up without saying so tends to disappear between meetings, and the decision it was holding goes with it.

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.