Where we start
Sessions 1 to 3 gave you rules: one keyword per line, four to seven branches, one home per idea. Rules are easy to nod at and hard to know you have followed. A bench is a rule you cannot nod at, because it reports a number and the number is either what you hoped or it is not.
★ What you walk out with tonight. Your own notes, in a shape that reports zero collisions, zero labels off the page, three to seven branches and one home per idea, plus the honest knowledge of which rung they started on.
Every number below is read off the drawn map. Branches, depth and words are counted in the outline you can see and edit. Collisions and off-page labels are read back from the rendered picture with getBBox() after it is painted. If the layout fails, the numbers say so. The only thing that is not a measurement is the one-line verdict, and it wears a badge saying so.
What gets measured, and which rule each number belongs to
6 min liveNine numbers, and each one is a rule from an earlier session turned into something countable. Two of them cannot be counted in the outline at all: they only exist once the map is drawn, which is why the bench draws it.
LiveWhy two of the numbers need the picture3 min▶
Branches, depth and words can be counted from the text. Whether two labels land on each other cannot, because it depends on where the layout puts them, how long the words are, and how much room a branch's slice of the circle leaves. So the bench does what you would do: draws the map, then looks.
- Collisions are pairs of label boxes that intersect in the drawn picture. Nine means nine pairs, not nine labels.
- Off the page counts labels whose box crosses the canvas edge. A sentence hung at the second ring is wider than the room it has, and the count says so.
- Smallest label is the rendered pixel size of the type, which changes with your screen and not with the outline. A map that reads at a desk may not on a phone, and this is the number that tells you.
The layout rule is deliberately plain: each main branch gets a slice of the circle in proportion to the leaves it carries, and children share their parent's slice evenly. A cleverer engine could hide collisions by nudging labels apart, and then the bench would be teaching you that the problem does not exist.
Self-studyWhat the bench refuses to model3 min▶
There is no recall score. No "this map will be remembered 23 percent better". Session 1 covered why: the literature finds a real effect from active organising, weak designs, one motivation drop, and a crossover study whose table disagrees with its abstract. A number built on that would be a guess wearing a decimal point.
The verdict line is the one non-measurement, and it is badged "heuristic" on the widget so nobody mistakes it. Its rules, in order: nothing to map; one branch or a flat list over seven; more than seven main branches; more than two labels colliding or off the page; under sixty percent short labels; one idea in two homes; otherwise good. The two thresholds it leans on, four and seven, are the two capacity estimates from session 2, and neither is a law about mind maps.
Fourteen notes, five shapes, one trap
★ 26 min · everyone drivesBelow are Daybreak's fourteen launch notes exactly as captured. Take the presets in order, watch the numbers, then try the red one. After that, paste your own notes into the outline box and the bench works on those instead.
The map bench
Five shapes of one meeting. Every number except the verdict is read off the drawn map below. Edit the outline and everything follows.
The ladder below was read off this bench in a browser before this page was written. Take the presets in the same order and you will get the same numbers, because they come from the same measurement.
LiveRead the ladder: it gets worse before it gets better4 min▶
Three rows carry the lesson, and none of them is the obvious one.
- Grouping alone is worse on the page. Five branches with sentences still on them drops collisions from nine to seven, and pushes seven labels off the edge, because a sentence hung at the second ring is longer than the room it has. The verdict changes from "a list in a circle" to "does not fit". That is the honest order of operations, and if you stop here your map is uglier than your list was.
- Keywords alone are not the fix either. The red preset is 96 percent short labels and it is the worst state in the bench: twenty-six branches and thirteen collisions. The keyword rule and the branch budget only work together, which is why sessions 1 and 2 were one argument in two parts.
- The last rung is invisible on the page. "One keyword per branch" and "one home per idea" draw almost identically. One number separates them, and it is the one from session 3 that tells you which diagram you are drawing.
LiveNow yours: paste and read10 min▶
Replace the outline with your own notes. Two spaces per level, first line is the centre. If your notes are a flat list, paste them flat and read the honest starting point before you touch anything.
Paste as captured and write down the collision count. That is your baseline and it is usually between five and fifteen.
Group first. Indent every line under one of three to seven headings. Expect the verdict to get worse and off-page to rise. Do not stop here.
Cut to keywords. Work down the outline shortening each line to the word that brings it back, moving numbers and names to a third level. Watch words-per-node fall and collisions clear.
Read the shared count. If it is above zero, you have an idea in two branches. Pick one home and leave a pointer, or accept that you are drawing a concept map and say so.
Read the smallest label and then narrow your browser window. Watch it fall. The number at which you stop being able to read the map is the number your phone will show.
If you take one thing from tonight. Any single rule applied alone makes the map worse on at least one count, and the bench will tell you which. The rules are a set, and the set is: group to seven or fewer, cut to keywords, give every idea one home. In that order.
What the numbers can and cannot tell you
4 min liveA bench that reports its own limits is worth more than one that reports a score. Five things this one cannot see, and what to do about each.
| The number | What it misses | So |
|---|---|---|
| Labels colliding | Box width is estimated at 6.6px a character; real glyphs vary a little | Treat 1 as "look", not as "fail" |
| Ideas in two branches | Matches the label exactly; "Legal sign-off" and "legal review" are two ideas to it | It is a signal you check, not a detector you trust |
| Words per node | Cannot tell a good keyword from a bad one; "thing" is one word | The read-back test from session 1 still applies |
| Fattest to thinnest | Some branches deserve to be fat; a launch has more comms than pricing | Above 4x, ask whether the fat branch is two branches |
| The verdict | It is a rule of thumb with seven thresholds and no evidence base | Read the eight numbers above it, not the line |
Self-studyWhy the layout is deliberately not clever3 min▶
Most mind-mapping software has a layout engine that nudges labels apart until nothing overlaps. That is a good feature in a tool and the wrong feature in a bench, because it hides the thing the bench exists to show. A map whose labels only fit because the software moved them is a map that will not fit when you draw it by hand, or print it, or put it on a phone.
So the bench uses the ordinary radial rule and nothing else: slices in proportion to leaves, children sharing their parent's slice, rings at fixed distances. When it reports a collision, the collision is a property of your outline, not of the engine, and fixing the outline fixes it everywhere.
The Daybreak product manager ran her supplier maps through this bench and found that every one of them reported one shared idea: "payment terms" appeared under both Contract and Finance on all nine maps. She had been drawing nine concept maps without knowing it. The fix was one pointer per map, and the nine maps became readable at a glance for the first time, with nothing else changed.
Before session 5
25 min- Run three real sets of notes through the bench, as captured first. Write down the baseline collision count for each. Bring the three numbers.
- Take the worst one to zero collisions and zero off-page using only the outline box. Count how many lines you had to move versus shorten. The ratio tells you whether your habit is sentences or sprawl.
- Find one shared idea in any of the three and decide, in writing, whether it wanted a pointer or a concept map. One sentence of reasoning.
- Keep the outlines. Session 5 is about why the text version is the one worth keeping, and you will want yours.
Three questions
Clear all three and session 4 gets stamped in your passport.
1 · You group fourteen captured sentences under five headings. Collisions drop from 9 to 7 and off-page labels rise from 0 to 7. What happened?
The ladder shows this exact step. Grouping is the right first move and it makes the page worse on its own, because the labels are still sentences and the second ring has less room per label than the first. The cure is the next rung, not a different grouping. Stopping here is how people conclude that mind maps do not work.
2 · The red preset is 96 percent one-to-two-word labels, exactly what session 2 asked for, and it reports 26 branches and 13 collisions. Why?
Grouping felt like losing detail, so every keyword went straight onto the centre. Each rule fixes one failure and leaves the other alone. The bench makes this visible by giving a preset that passes one rule perfectly and fails the map anyway.
3 · Why does the bench have no "recall improvement" number?
Session 1 laid out the literature: a real effect from active organising, weak trial designs, one motivation drop, one study whose table disagrees with its abstract. A bench that turned that into "23 percent better recall" would be inventing precision the sources do not have. Eight measurements and one labelled heuristic is the honest shape.
What this session teaches, and where it came from
Every constant and the full ladder with all nine columns: the course's source map.
Session 4 cheat sheet · pin this
You just edited a map as text and the picture followed. Session 5 is about why that is the version worth keeping: an outline diffs, versions and outlives the tool that drew it, and when to render it versus when to pick up a pen anyway.