The six sessions 🎯 · one claim, all the way through
The running situation is Daybreak's Guji churn problem - a real finding, correctly analysed, badly told. The coffee-subscription company from the SQL, system-design, product-design, communication, course-design and dataviz courses. Same claim every session, so the only thing that changes is what you did with it.
The one sentence
Subject, finding, size, consequence. The four tests it has to pass, why topic decks survive so well, and the four honest reasons the sentence will not come.
🏛️ Session 2 · easyStructure
Why the detective story fails in a business meeting. Two skeletons that work, the chronological one that does not, and where to put your own counter-argument.
1️⃣ Session 3 · mediumOne idea per visual
The takeaway title, the titles-only test, the four homes for the second idea, and the fear of looking thin taken seriously rather than dismissed.
🔦 Session 4 · mediumEmphasis
Emphasis is relative, so the only way to add it is to remove it. Five channels ranked by pull, the three-second test, and greying out your own work.
📏 Session 5 · bench nightSequence and pacing
The sequence bench. Where the point lands, words before it, distinct claims and labelled visuals - all read off the rendered deck, plus what one context slide costs.
🗣️ Session 6 · hands-onFour tellings
Spoken in two minutes, a one-page memo, a deck nobody narrates, three lines in a chat. What each drops, and why readership runs opposite to effort.
Your passport 🎫
Clear all three quiz questions in a session and it gets stamped. Six stamps means nothing you send goes out without a sentence and a measured order. Stamps live in this browser only.
What this course is not, so you land in the right place 🧭
| If your question is | Go here instead |
|---|---|
| Which encoding does this question need, and is the chart honest? | learn-dataviz-with-phoebe |
| How do I make the ask, listen first, or deliver bad news? | learn-communication-with-phoebe |
| How do I read a metric and question it? | learn-data-literacy-with-phoebe |
| How do I design a session people learn from? | learn-course-design-with-phoebe |
| The charts are right. How do I turn them into something that changes a decision? | you are in the right place |
Session 6 is about the story changing shape, not the chart. How a chart survives a slide, a doc, a phone and a printer is learn-dataviz-with-phoebe session 6, and two courses owning one subject disagree with each other eventually.
What is honest here 🧾
The bench in session 5 reads its numbers back out of the rendered slides. One figure is a model, and it says so on the widget itself.
| Claim | Status |
|---|---|
| Where the point lands | Really measured. The index of the slide carrying the conclusion, found in the rendered deck after it is drawn |
| Words before the point | Really measured from the rendered text of every slide up to and including the point. Titles, claims and body text all counted |
| Distinct claims and labelled visuals | Really counted in the DOM. If a lever silently failed to change the deck, these report the truth rather than the intention |
| Time to the point | A model, labelled as one on the widget: words at 160 wpm plus 15 seconds a slide. Both constants are stated and neither is a finding |
| Daybreak's numbers | A teaching situation. The measurement code is real |
The knowledge map 🧠
The whole course at a glance - hover a session to spotlight its concepts, click any node to jump in.