learn-visual-storytelling-with-phoebe / Session 2 of 6
Learn Visual Storytelling with Phoebe · Session 2 of 6

Structure, and why the reveal fails

You have a sentence. Tonight is where it goes. The instinct is to build to it, because that is how every story you have ever enjoyed was told, and it is precisely wrong for a room of people deciding something. We will take one deck through three structures, watch what each one does to the last four minutes of the meeting, and write the skeleton for yours.

🟠 Hands-on Bring session 1's sentence Skeleton written tonight 45 min
0-3 · Welcome 3-18 · Three structures, one deck 18-40 · Build-along: write the skeleton 40-45 · Q&A
Part 0

Where we are

Session 1 produced a sentence. A sentence is not yet a deck, and the most consequential decision left is not which charts to use. It is whether the sentence arrives at the start or at the end.

🎫 Clear all three quiz questions to stamp your passport Live = presented in the 45 minutes Self-study = the full depth, after class

★ What you walk out with tonight. A written skeleton for one real deck: the claim, three supports in descending order of strength, the cost or risk, and the ask. Six lines, no slides.

Part 1 · covers the reveal

Nobody in a meeting wants a detective story

7 min live

Withholding the conclusion is a genuine narrative technique and it works beautifully in a novel, a documentary and a conference talk. It fails in a business meeting for reasons that have nothing to do with taste.

Building to it Background What we did What we found THE POINT The point lands with four minutes left, into a room that has been guessing for thirty-six and has already formed views. Questions get asked about slide two while you are on slide nine. Leading with it THE POINT Strongest support Next support Cost, risk, and the ask The point lands in the first ninety seconds. Everything after it is the room testing a claim it can already see, which is the useful conversation. If the meeting is cut short, the important part already happened. The reveal assumes the audience will wait, will not interrupt, and will still be there at the end. In a meeting, all three assumptions are false, and the third one is false on the calendar before you start.
🔍 Click to zoom - the same forty minutes, and only one of them survives being cut to twenty
LiveFour reasons the reveal fails here specifically4 min▶
  • The audience is not captive. A novel reader has chosen to be there and can stop. A meeting attendee cannot stop, so instead they multitask, and the moment they stop following is the moment before your conclusion.
  • They will interrupt. Senior audiences interrupt because interrupting is how they work. If they do not know where you are going, their questions pull you off course. If they do, their questions test the claim.
  • The meeting will be cut. Thirty minutes becomes eighteen because the previous item ran over. Build-to-it structures lose the conclusion. Answer-first structures lose the third support, which nobody misses.
  • The deck gets forwarded. More people will read your deck alone, out of context, than will sit through you presenting it. They read slide one and maybe slide two.

Note what is not on that list: attention span, seniority, or a preference for brevity. The reveal fails structurally, not because your audience is impatient.

Slide 1: "Subscription retention review - Q3". Slide 2: how we pulled the data. Slide 3: revenue by month. Slide 4: origin mix. Slide 5: churn by cohort. Slide 6: Guji churns at 3x, recommend pausing auto-renew.

Six slides before the claim. By slide 3 somebody has asked why revenue matters here, and answering that honestly means admitting it does not - it is context you included because you had it. The recommendation gets ninety seconds.

Slide 1: "Guji auto-renew churns at 12.4 percent against 4.1 elsewhere. Recommend pausing it until supply recovers." Slide 2: the churn-by-cohort chart. Slide 3: what pausing costs, and the ask.

Three slides. The revenue and origin-mix charts are gone, because with the claim visible you can see that neither supports it. The meeting spends its time on whether to pause, which is the only question that was ever worth the room.

Part 2 · covers the skeletons

Two shapes that work, and one that does not

7 min live

You do not need a library of narrative structures. You need two, chosen by whether your audience already agrees there is a problem.

THE PYRAMID use when the room already agrees there is a problem 1 · The claim, with its number 2 · Three supports, strongest first 3 · What it costs, and the risk 4 · The ask SITUATION AND TURN use when they do not yet know there is a problem 1 · What everyone believes is true 2 · The one fact that breaks it 3 · The claim, with its number 4 · The ask THE ONE THAT DOES NOT WORK · chronological Background, method, what we did first, what we did next, what we found, what it means. It organises the deck around the order you did the work, which is of interest to exactly one person in the room. Both working shapes put the claim in the first two slides. The difference is only whether you spend one slide first establishing that the question is worth asking.
🔍 Click to zoom - the choice between the two is about the audience, not about the finding
LiveOrdering the supports, and how many4 min▶
  • Three supports, not five. Beyond three, each additional one lowers the average strength of your case. The room remembers the weakest, and a weak fourth support is an invitation to argue about the fourth support instead of the claim.
  • Strongest first, not last. The same logic as the claim itself. If the meeting is cut, you want to have said the good one.
  • They should be independent. Three views of the same data is one support shown three times, and a sharp audience will say so. If two of your supports fall together when one assumption changes, they are one support.
  • Name the strongest counter-argument yourself. Slide three, not the Q&A. Raising it yourself costs you a minute and buys you the room's trust for the rest of the meeting. Waiting for them to raise it costs you the meeting.

The cost-and-risk slide is the one people cut when the deck runs long. It is the one senior audiences look for first, because a recommendation with no stated cost reads as a recommendation from somebody who has not thought it through.

Self-studyWhere the chronological deck is genuinely right3 min▶

Chronological order fails as a persuasive structure, which is not the same as failing always. It is correct in three places, and knowing them stops you overcorrecting.

  • An incident review. The sequence is the finding. What happened at 03:12 and what happened at 03:19 is the substance, not the scaffolding.
  • A method appendix. Somebody reproducing your work needs the steps in order. Put it behind the deck, where it does no harm and does real good.
  • A project retrospective where the question is genuinely "how did we get here" rather than "what should we do".

The test is whether time is a variable in your finding or just the order you happened to work in. Almost always it is the second one.

Build-along

Write the skeleton

★ 22 min · everyone writes

Six lines in a text file. Still no slides. If a skeleton does not hold up as six lines of plain text, it will not be rescued by a template.

Pick the shape. Does the room already agree there is a problem? Yes, pyramid. No, situation and turn, and you get exactly one slide to establish the situation.

Claim on line one. Your sentence from session 1, unchanged. If you find yourself editing it here, session 1 is not finished.

Three supports. Write them as sentences, not as chart names. "Churn by cohort" is a chart. "Only one cohort is above 5 percent" is a support.

Cut to three and order them strongest first. Check they are independent: if one assumption change knocks out two of them, you have two supports, not three.

Cost and ask. What does the recommendation cost, what is the strongest argument against it, and what exactly are you asking somebody to do. Name the person if you can.

Write the six lines before opening the deck. Then open the deck and see which existing slides map onto which line. The unmapped ones are your answer about what to cut.

Say each support out loud as a sentence. If it comes out as a chart title, it is not a support yet - it is a piece of evidence looking for a claim.

Test independence. Change one assumption in your analysis and see how many supports survive. Two that fall together are one.

Write the counter-argument you least want raised and put it on the cost slide. This is the single highest-return five minutes in the whole session.

Read the six lines to somebody without showing them anything. If they can restate your claim afterwards, the skeleton holds.

If you take one thing from tonight. Put your strongest support second, not last. The instinct to save it is borrowed from storytelling, and in a meeting the ending is the part most likely not to happen.

Homework

Before session 3

25 min
  1. Re-skeleton one deck you already presented. Compare the new order to what you actually did, and note how many slides do not map to any line.
  2. Take a deck somebody sent you and identify its shape. Most are chronological, and most of their authors would say they are not.
  3. Write the counter-argument slide for a recommendation you are currently making. Do it before anybody asks.
  4. Bring one slide that carries more than one idea to session 3. Everybody has one and it is usually the busiest slide in the deck.
Check yourself

Three questions

Clear all three and session 2 gets stamped in your passport.

1 · What is the strongest reason the build-to-it structure fails in a business meeting?

The failure is structural, not about the audience's character. Three things reliably happen to meetings: they get shortened, they get interrupted, and the deck gets read by people who were not in the room. Build-to-it loses the conclusion in all three. Answer-first loses the third support, which nobody misses.

2 · You have five supports for your claim. Why cut to three?

The memory limit is a real effect but it is not the operative one here. The problem is that adding a weak fourth support hands the room something easy to attack, and a case is judged by its weakest visible link rather than by the count of links. Length is a side effect, not the reason.

3 · When is chronological order genuinely the right structure?

The test is whether the sequence carries the finding or merely records the order you worked in. In an incident review, 03:12 and 03:19 are the substance. Option A is the usual justification and it does not survive contact: unfamiliar audiences need the situation-and-turn shape, which is one slide of context, not six. B is the honest reason people do it, and it is not a reason.

Sources covered

What this session teaches, and where it came from

✓Why the reveal failsNot captive, will interrupt, will be cut, will be forwarded - four structural reasons, none about attention span
✓The pyramidClaim, three supports strongest first, cost and risk, the ask. Minto's answer-first lineage named
✓Situation and turnOne slide of shared belief, the fact that breaks it, then the claim. For rooms that do not yet see a problem
✓Ordering supportsThree not five, strongest first, independent, and naming your own counter-argument on slide three
✓Where chronological is rightIncident review, method appendix, retrospective - when time is a variable rather than a work order
◐Freytag and story arcsNamed as the source of the build-to-it instinct, and why the transfer to a meeting does not hold

Every fact on this page, and its verification tier, is recorded in the course's source map.

Session 2 cheat sheet · pin this

Answer firstThe ending is the part that may not happen.
Pyramid or turnChosen by whether they see a problem yet.
Three supportsStrongest second, right after the claim.
Independent supportsTwo that fall together are one.
Your own counter-argumentSlide three, not the Q&A.
ChronologicalOnly when time is a variable.