Where we start
Open the map you brought. Somebody is waiting for it: a colleague who needs the plan, a reader who needs the brief, a room that needs the decision, or you next month needing to remember. Ask one question of it before anything else tonight: what was it for? Daybreak's autumn launch map has been through every shape in the course, and it still has not answered that. Tonight it does, and so does yours.
★ What you walk out with tonight. One real map, the one you owe somebody, turned into the outline it ships as, in the order its reader needs, and graded honestly on the final scorecard against everything the earlier five sessions claimed.
Two neighbours, so you land in the right place. Weighing options against criteria with scores and weights is learn-decision-intelligence-with-phoebe. Turning a finding into a deck that changes a decision is learn-visual-storytelling-with-phoebe. Here the subject is the last mile of a map: naming its job, and getting it off your desk in a shape a reader can use.
Plan, brief, decide, revise
5 min liveA map does one of four jobs. It plans work, it briefs a reader, it lays out a decision, or it tests what you remember. Each job pulls the map into a recognisably different shape, and that shape is the tell: look at the branches and you can say which job the map is doing, and whether it is the job the owner thinks it is doing.
LiveEach job has a tell4 min▶
You do not need to ask the owner what a map is for. The branches say. Read the four tells on Daybreak's launch and then on the map you brought, and expect at least one surprise: a map drawn as a plan that is actually a brief is the commonest thing in the room.
- Plan: branches are workstreams, dates on the twigs. Supply, Packaging, Pricing, Comms, Ownership, and hanging off them "4000 bags · 1 Oct", "page copy 20th", "email ten days before". The map is organised around who does what, and the twigs are when. If your map has no dates anywhere, it is not planning anything yet.
- Brief: branches are the reader's questions, not your topics. The finance lead does not care about Packaging. She will ask whether existing subscribers keep their price, whether the seasonal price applies only to new ones, and how many bags the first batch is. A brief for her has those three questions as its branches, and your topics become twigs under whichever question they answer.
- Decide: two or three option branches carrying the same twig names. "Old sleeve" and "New sleeve", each with cost, legal, and whether it names Guji underneath. Every twig name repeats under every option. That is the cross-link test from session 3 firing on every twig at once, and it means the honest shape is a table, not a map. Part 1's self-study card takes this further.
- Revise: the map redrawn from memory with the gaps marked. Same centre, same branches, and two twigs that did not come back, ringed. This map is not for anyone else. It is a measurement of what your labels are doing, and part 3 is about reading it.
Check the tell before you do anything else to the map tonight. Fixing the collisions on a map that should have been a table is polishing the wrong object.
Self-studyThe decision map is secretly a table4 min▶
Options against criteria is a grid: options down one side, criteria along the other, one cell per pair. When you draw that grid as a map, each option becomes a branch and each criterion becomes a twig, so the same twig names repeat under every option branch. That repetition is the map telling you it is the wrong shape.
The cost is not aesthetic. A map can only show what is on it, so an option you forgot to assess against one criterion simply has one twig fewer, and nothing on the page says so. A table has a cell there, and the cell is empty, and an empty cell is a question you can see. On Daybreak's sleeve decision, nobody had asked what the new sleeve would cost; on the map, "New sleeve" just had two twigs where "Old sleeve" had three, and it looked tidy. In the table it was a blank.
- Two or more branches with identical twig names is the trigger. One shared twig is a pointer, as session 3 taught; a whole set shared is a grid.
- Draw the grid. Options as rows, criteria as columns. Fill what the map had. Look at what is empty.
- Stop there. Weighing the criteria, scoring the options and defending the weights is a discipline of its own, and it is learn-decision-intelligence-with-phoebe. Tonight only gets you to the honest shape; what you do in the cells is that course.
Daybreak's launch map went to the finance lead as a brief the week before the pricing meeting. The product manager did not send the five-branch map. She re-cut it: the centre became "Autumn launch, for finance", the branches became the finance lead's three questions, and the facts under Pricing and Supply moved to whichever question they answered. Two of the original five branches, Packaging and Comms, had nothing the finance lead would ask about, so they vanished into a one-line appendix at the bottom. The reader opened it and found her first question answered on the first line, which is the entire test of a brief.
Map thinks, outline ships
5 min liveA map has no reading order. That is its whole strength while you think, because you can enter it anywhere and every branch is one glance from the centre. It is also the reason a map should not leave your desk: a reader will start somewhere, and where they start is the branch that happened to be at the top, which is the branch you happened to draw first. Readers need an order. Give them one, and the shape that carries an order is an outline.
LiveA map has no reading order3 min▶
Hand a five-branch map to a colleague and watch where their eyes go. Top first, usually, then clockwise, because that is how people read a page with no other instruction. Your map's top branch is whichever one you drew first, which was whichever one you were thinking about when you started. Nothing about that order is for them.
- Readers need an order, and a document with an order is an outline: numbered, indented, read from the top. That is what leaves your desk.
- Pick the order by the reader's first question. Not the most important branch, not the biggest: the one that answers what they will ask first. For the finance lead that is Pricing. For the roastery it is Supply. Same map, two outlines.
- The map stays yours. It is the thinking tool and it keeps working as one. Nothing is lost by not sending it, because everything on it is in the outline.
- Nothing is retyped. The outline is the session 5 text file. You are numbering the branches and moving one block to the top. Two minutes, and the diff shows exactly which block moved.
The one thing you add is the order. Everything else was already there, which is why the hand-off is the cheapest step in the course and the one most often skipped.
Self-studyWhat survives the hand-off4 min▶
Every element of the map has an exact counterpart in the outline. Knowing the mapping means the hand-off is mechanical, and knowing what changes at each step means you do not lose the two things a map quietly drops: the sentence behind each keyword, and the pointer behind each "see".
| Map element | Outline element | What changes |
|---|---|---|
| The centre | The title | Gains the reader: "Autumn launch, for finance", not just "Autumn launch" |
| A main branch keyword | A numbered heading | Gains its number, which is the order; loses its colour, which the reader never needed |
| A twig | A bullet under the heading | Stays a short line; a twig that was two words can stay two words |
| A number or date on a twig | Its sentence, restored | "4000 bags · 1 Oct" becomes "First batch: 4000 bags from the roastery by 1 October"; the reader did not hear the meeting |
| A "see Comms" pointer | A cross-reference line | Becomes "see 4.2", because the outline has numbers and the map only had names |
| Position and distance | Indentation and order | Membership becomes indent depth; the reading order is chosen, not inherited |
The fourth row is the one that costs time and earns it. On your own map the keyword brings the sentence back because you were there. The reader was not, so every number gets its sentence back in the outline, and that is the only real writing in the hand-off.
If the question came out longer than about twelve words, it is probably two questions, and the second one is the second heading. If you could not write it at all, you do not yet know who the reader is, and that is the finding: a map with no reader is still a plan for yourself, and it can stay a map.
Redraw it from memory
4 min liveThe fourth job is the one a map does for you alone. Close the notes, take a blank page the next morning, and redraw the map without looking. Then put the two side by side. Whatever did not come back is telling you something specific about a label, and it is the most honest test a keyword ever gets.
LiveThe blank-page test3 min▶
The morning after you draw a map, redraw it on a blank page without looking. Centre, branches, twigs, as many as come back. Then compare, and read every gap as a statement about one label.
- A twig that did not come back was one of two things. Either it was not important, or it was labelled with a word that does not bring its sentence back. Session 2's rule was that the keyword is the word that brings the sentence back; the blank page is where that rule gets tested for real.
- Fix the word first. On Daybreak's redraw, "Sidamo" vanished from under Supply. The sentence was "the blend leans on Sidamo because Guji is short", and "Sidamo" alone did not carry it; "backup: Sidamo" would have. Relabel, then redraw again tomorrow.
- Then decide whether the twig earns its place. "Win-back" also vanished, and no relabelling helped, because nobody in the meeting owned it and nothing depended on it. It came off the map and onto a separate list. A gap that survives a better label is a twig that was never load-bearing.
- A whole branch missing is a different finding: the branch was badly named, or it was two branches and neither name fitted. Session 1's homework caught this once already; the test is the same, run on purpose.
Do this to the map you owe somebody before you ship the outline. The twigs that did not come back to you will not come back to the reader either, and the reader only gets one reading.
Self-studyWhy this is the honest use of the memory claim3 min▶
Session 1 read the research both halves at once and came out with a narrow claim: making a map is an active, organising thing to do with material, and active organising beats passive re-reading. Whether the radial shape adds anything on top of the organising is not established, and the best-designed comparison put maps only slightly ahead of an outline of the same text.
The blank-page test sits exactly inside that claim. Redrawing from memory is active organising a second time: you are rebuilding the tree, not re-reading it. It works with any shape, a map, an outline, a table, because the work is in the rebuilding. And it does not depend on the radial layout being special, so it does not borrow anything from the half of the literature that did not hold up.
That is also why the test is a measurement rather than a memory trick. You are not trying to remember more; you are finding out which labels fail, and a label that fails for you on Wednesday morning is a label that fails for a reader on first sight. The session 1 evidence supports using a map to organise and re-organise. It supports no number for how much you will remember, and none is offered here.
Ship the map you owe somebody
★ 22 min · everyone shipsOne real map, the one somebody is waiting for. In twenty minutes it gets a named job, a checked tell, one pass through the bench, an outline in the reader's order, and an honest grade. Then it leaves your desk tonight.
Name the job. Write one of four words at the top of the text file: plan, brief, decide, revise. If you want to write two, you have two maps and two readers, and tonight you ship one of them. Write the reader's name next to the word.
Check the tell. Plan: are there dates on the twigs? Brief: are the branches the reader's questions? Decide: do two or more branches repeat the same twig names? If they do, the honest shape is a table; draw it as options by criteria, look at the empty cells, and carry the table's text forward instead of the map's. Revise: has it been redrawn from memory yet?
Bench it once. Paste the text file into session 4's bench and read three numbers before you touch anything: labels colliding, labels off the page, ideas living in two branches. All three should be zero. If any is not, fix it in the text, not in the picture, and paste again.
Write the outline. Same text file. Write the reader's first question at the top, move the branch that answers it to line one, number the branches in the order the rest of their questions will come. Give every number and date its sentence back. Turn every "see" pointer into a numbered cross-reference.
Grade it. Six rows on the scorecard below, one per session, 0 to 2 each. Grade the map you have, not the map you meant to draw. A row scored 0 tonight is the first thing to fix tomorrow, and it is written down.
Open the text file, not the picture. Everything tonight happens in the outline from session 5. If the map you owe only exists on paper or as a PNG, type it first; five minutes, and it is the last time you will ever do that for this map.
Write the job and the reader on line one as a comment above the centre. "brief, for the finance lead". Everything below it now has a test: does this line answer something she will ask?
Run the decide check on every pair of branches. Read the twig names under branch one, then under branch two. If they are the same list, you are looking at a grid. Draw it before going further.
Paste into the bench and write the three numbers down. Collisions, off-page, shared. If your session 5 homework was done, they are already zero and this step takes thirty seconds. If not, this is where the map gets finished.
Reorder and number. Cut the branch that answers the first question and paste it at the top. Number the rest. Save. The diff against this morning's file is one block moved and some numbers added, which is exactly what the hand-off is.
Restore the sentences. Every twig with a number or a date on it gets the sentence it stood for. This is the only writing tonight, and it is for the reader who was not in the room.
If you take one thing from the whole course. The map is the thinking and the outline is the telling. Keep the map for yourself, because it has no reading order and you do not need one. Send the outline, because the reader does. Nothing is lost between them except the order, and the order is the one thing you add.
After the course
25 min- Ship the outline to the person who is owed it, tonight or tomorrow, and note what they asked first. If it was not line one, you guessed their first question wrong, and the next outline for that reader starts differently.
- Keep the text file and diff it after the meeting. Whatever moved, was cut or was added in the room is the difference between what you thought the plan was and what it turned out to be, and the diff is the only record of that.
- Run the blank-page test on any map a week later. Not the next morning this time. The twigs that fail at a week are the labels that will fail a reader who opens the file cold.
- Pick one list you have been drawing as a map and let it be a list. A shopping list, a reading list, a to-do list with one branch. It was never a map, and putting it in a circle cost you a page every time.
Three questions
Clear all three and session 6 gets stamped in your passport.
1 · A map has branches "Old sleeve" and "New sleeve", and under each one the twigs read cost, legal, names Guji. What is the map telling you?
Identical twig names under every option branch is the cross-link test firing on every twig at once. The honest shape for options against criteria is a table, because a table has a cell for every pair and an empty cell is visible, while a map simply has one twig fewer and looks tidy. Draw the grid; weighing what goes in the cells is the decision-intelligence course.
2 · Daybreak's launch map has Supply at the top, because it was drawn first. The outline for the finance lead starts with Pricing. What decided that?
A map has no reading order, and the order it appears to have is the order you happened to draw it in, which is about you. An outline has an order, and the only honest way to choose it is by the reader: the branch that answers their first question is line one. Same map, different reader, different outline, and nothing is retyped because it is the session 5 text file with one block moved.
3 · You redraw a map from memory the next morning and "Sidamo" under Supply did not come back. What does that tell you, and what do you do first?
A missing twig is a statement about one label. "Sidamo" alone did not carry "the blend leans on Sidamo because Guji is short"; "backup: Sidamo" would have. Relabel first, because a twig cut for being forgotten might only have been badly named. If it still does not come back with a better word, it was not load-bearing, and it leaves the map. Putting the sentence back is the list creeping in, which session 1 spent an evening on.
What this session teaches, and where it came from
Every fact on this page, and its verification tier, is recorded in the course's source map.
Session 6 cheat sheet · pin this
You can now shape what you know into a map, tell when a map is the wrong shape, measure one, keep it as text, and hand it off as the outline it was for. Three doors open from here. Drawing icons and containers while somebody is still talking is learn-sketchnoting-with-phoebe, the next course in this section. The full syntax for rendering your text file, shapes, icons and classes, is learn-mermaid-with-phoebe session 5. And when the outline you shipped has to become a deck that changes a decision in a room, that is learn-visual-storytelling-with-phoebe.