Lesson 0007
The most expensive design mistake is making a beautiful slide that doesn’t name its takeaway.
This lesson fixes the gap that showed up in your
Superset vs Holistics critique.
Primary source:
Cole Nussbaumer Knaflic, Storytelling with Data.
Three versions of the same comparison slide. Same diagram, three different headlines. Watch how the reading changes.
Same diagram, three completely different slides. The diagram is just supporting evidence. The headline is the slide.
BLUF
US military communications standard, also adopted by McKinsey (where it’s called the “Minto pyramid”) and every good consultancy. The rule: state the conclusion first, defend it second.
Applied to slides: the headline is your conclusion. The diagram is your defence. Most beginners do it backwards. They draw the diagram, then label it with a topic name. The viewer is left to derive the conclusion themselves, which they will not, in ten seconds.
The fix is procedural, not creative: write the headline before you open Figma. If you can’t state the conclusion as a sentence, you don’t know what to draw yet.
(Hover to un-blur.) Even blurred, the headline still reads. That is a slide doing its job.
The squint test: blur the screen, or stand 10 feet away. If you can still read the headline and grasp the takeaway, the slide works. If you have to lean in to figure out what it’s about, the headline is failing.
This is mechanical, not subjective. Apply it on every slide before sharing. Half-blind viewers (sleepy execs, distracted prospects, the back row of a conference) are your real audience.
When you don’t know how to start, reach for one of these. They cover roughly 90% of technical explainer slides.
Best when comparing two things side by side (your Superset vs Holistics case). Names the one variable that matters and ignores the rest.
Best when introducing a single feature or concept. Names the why before the what. Always make Y a benefit, not a feature.
Best when you need to break an assumption your audience walked in with. Use sparingly. Overused, every slide sounds like a sales pitch.
Your exercise headline was DEVELOPMENT WORKFLOW. That’s a label title, anti-pattern #1.
Let’s try each pattern on it.
All three work. Pick based on the audience:
Your choice · Exercise 0002
Reasoning logged: Outcome pattern fits because the content emphasises a capability gap in Superset, not a side-by-side feature diff. The Contrast formula (“Same workflow. One difference: Y.”) was rejected as feeling AI-generated.
Verdict from critique: works. Technically a hybrid: Line 1 is pure
Outcome (X gives you Y); Line 2 adds a Contrast tail. The two-beat structure is
more persuasive than either pure pattern alone for an absence-on-the-other-side framing. The
uncontracted “does not” lands harder than “doesn’t” because the
full not is the punch.
On the AI-feel objection: half-right. The Contrast formula is recognisable because it works; the fix is to vary the vocabulary, not avoid the structure. The chosen headline does this naturally.
Procedural rule. Apply on every slide.
Exercise 1 of 5
What does BLUF stand for, and what is the rule it states? Don’t peek.
Bottom Line Up Front. State the conclusion first, defend it second.
Originally a US military comms standard so officers could read the most important info even if shelled mid-page. Translates directly to busy executives who skim.
Exercise 2 of 5
Pick the headline pattern that fits each scenario.
(a) You’re explaining row-level security to a CISO who’s never heard of it.
(b) You’re showing why Holistics’ AML beats writing dbt models from scratch.
(c) You’re convincing a prospect that BI should be code-first, not GUI-first.
(a) Outcome. “Row-level security gives every user their own view of the same dashboard.” Introduces the concept by stating its outcome.
(b) Contrast. “Same model logic. One difference: it’s also a queryable dataset.” Side-by-side, name the diff.
(c) Surprise. “Most BI is built in a UI. The best ones are built in code.” Frames code-first as the surprising default.
No pattern is universally right. Pick by the listener’s state of mind.
Exercise 3 of 5
A teammate writes a slide titled METRIC GOVERNANCE with a diagram of metric
definitions flowing into dashboards. Rewrite the headline using each of the three patterns.
Contrast: “Same metric definition. Used by every dashboard, every analyst, every embed.”
Outcome: “One source of truth for every metric. No more arguing about ‘why does this dashboard show a different MRR?’”
Surprise: “Most BI tools let each analyst define metrics their own way. That’s how you end up with three MRRs.”
All three are persuasive. The original (METRIC GOVERNANCE) just labels the slide’s topic and asks the viewer to figure out the value themselves.
Exercise 4 of 5
Apply the squint test mentally. Which of these would still read at 10 feet away?
(a) “Self-Service Analytics”
(b) “Self-service: every business user, their own dashboard.”
(c) “Empowering users to unlock data-driven decisions through democratized analytics.”
(b).
(a) is a label, not a message. (c) has actual words but is too long to read in a single glance and uses too many vague benefit words (“empowering”, “unlock”, “democratized”).
A good headline is short, concrete, and falsifiable. (b) makes a claim you could push back on (“is it really every user?”) which means it’s saying something. Vague claims that can’t be wrong are saying nothing.
Exercise 5 of 5
Re-read your Superset vs Holistics critique. Now look at the “Worked Example” section above. Pick the headline pattern you’ll use when you redo the slide. Why that one?
The critique called out that the slide reads “fair comparison” when the goal is persuasion (sell Holistics). That argues for the Outcome pattern: “Holistics gives you a semantic layer. Superset doesn’t.”
If the audience is a technical evaluator who already cares about the comparison, Contrast works: “Same workflow. One difference: the semantic layer.”
Whichever you pick, the pattern itself unblocks you. You no longer stare at the blank headline space wondering what to type.
Try it on v2 of your Superset slide. Apply the workflow: write the headline
first (state the conclusion as a sentence), squint-test it, then rebuild the diagram. Drop the
result in exercises/0002-superset-vs-holistics-v2.png and I’ll critique
against this lesson’s rules.