This is the free chapter. It's the one I'd read first if I were deciding whether to buy the rest.
A chart in a video has a different job from a chart in a report. A report's reader can look twice. A video's viewer gets one pass, at speed, often on mute, and cannot read a value off a moving mark.
That constraint drives almost everything in this chapter, and it has an academic backing that's worth knowing about because it's counterintuitive: animation is excellent for presentation and one of the worst formats for analysis. Static traces and small multiples win when someone needs to read exact values. Reels are presentation, so animation is correct — but it means every analytical beat has to settle on a clear static state and the value has to be annotated explicitly. Never make the audience eyeball a quantity from motion.
1 · One chart is not an analysis
The blunt version, delivered after a video whose entire statistical content was "a radius got smaller", shown on a single line chart: "doesn't dig into any of the in-depth metrics, uses one boring chart, this just isn't a well made video."
Three rules came out of it:
- A chart per analytical beat, each answering a different question.
- At least one must show a distribution, not a summary statistic. On that video I computed a 67th percentile and threw the distribution away — when the percentile was literally the thing being explained.
- Before locking a script, ask: "what is the most interesting number in this dataset that I have not put on screen?" For that episode it was the along-track versus cross-track error split — the reason the forecast cone is becoming an ellipse rather than a circle, which was on disk and never used.
And a related trap: don't let already-fetched assets set the ceiling. I had the position data and the wind radii locally, everything needed to animate a storm moving and growing, and rendered one frozen frame of it because the still was already downloaded. Fetching is cheap. A dead chart isn't.
2 · Lie factor near one
The graphical element's size should be proportional to the quantity. That's Tufte's rule and it's the floor, not the ceiling.
The version that actually bites in practice isn't bar-area distortion, it's
axis machinery. A charting library that "nices" an explicit domain will round
[1, 9] outward to 0 → 10 and put ticks at rank 0 and rank 10, neither of
which exists. For an ordinal quantity that isn't cosmetic — it invents
categories. Full write-up in chapter 7 §5.
Check the rendered axis end labels against what you asked for, in a still, every time. An explicit domain is a request, not a guarantee.
Three more that fall in the same bucket:
- Real dimensions must be real. Any pitch, court or field has to use true proportions with equal pixels-per-metre on both axes. A squashed rectangle is a lie factor problem wearing a sports jersey.
- Place event markers to match the real description of each event — near-post finish, thirty-yard strike, cut-in from the left, and credit them honestly ("shot spots match each goal's description"), never as exact coordinates you don't have.
- Normalise to one direction. Teams switch ends at half-time, so a first-half and second-half goal must both be drawn attacking the same goal. Don't split them onto opposite sides of the pitch because that's where they physically happened.
3 · The honest statistics layer
For anything that claims a relationship:
- Plot the real points. All of them, if you have them. Never pad a cloud with generated dots to make it denser.
- Draw the fit, and draw it as its own beat rather than as chrome.
- Show the interval. A shaded 95% band around the fit.
- Print r, n and p on the plot. On-plot, not in a card, so they can't be separated from the picture they describe.
- Units in the axis titles. Always. "Response time" is not an axis label. "Ambulance response time, minutes" is.
- Keep any on-screen sigma and any derived rarity computed from the same numbers, so they can't disagree with each other inside one frame.
And the method has to fit the distribution — count data isn't normal, a sigma on a small sample is descriptive only, and rarity gets quantified as a frequency or with a model that fits. That's chapter 3 §5, and it's the difference between rigour and the appearance of rigour.
4 · Emphasis by de-emphasis
The single most-cited colour rule in data journalism, and the one people underdo: grey the crowd and light one thing.
Reserve exactly one saturated accent for the subject. Everything else is low-contrast. And when you highlight the subject, actively dim everything else — don't just brighten the hero, darken the field. The delta is what the eye reads.
Density encoding for the cloud. Let opacity encode local density so the mean blob glows solid and the tails fade. The shape itself then shows the relationship before any line is drawn, which means your first analytical beat has already landed before the fit appears.
Keep the entry a quick coordinated rain-in, not a long cascade. Heavy staggering gives negligible or negative tracking benefit — that's a measured result, not a taste preference.
A caution on one-accent discipline. It's easy to reach for a second accent when two things need emphasis in the same frame. If two things need emphasis, you have two charts.
5 · Stage the reveal
Never show a finished chart. A great animated chart is a sequence of reveals, each synced to a narration beat, building one analytical layer at a time and ending on a single surprising point.
The universal order:
axes/frame → the cloud rains in → the fit draws on →
a threshold or highlighted band → the ONE hero point
Start simple, add overlays one at a time, and give the eye time to read each before the next.
Distribution first, outlier last. Establish what "normal" looks like before the surprise. The famous version of this move shows years of typical variation and then drops the outlier year on top of it — the outlier only means something against an established baseline.
The design principles behind staging, from the controlled experiments, and they're worth applying verbatim:
- Maintain valid data graphics through the transition. Every in-between frame is still a real chart.
- Object constancy. A dot representing a datum keeps its identity across the whole animation. Never re-spawn it — the eye is tracking the same object.
- Use staging for complex changes. Never move everything at once; sequence the sub-transitions. Staged animation beat simultaneous animation in almost every condition tested.
- Group similar motions. Animate like objects together with shared timing — fewer things to track keeps it inside working memory.
- Minimise occlusion and travel distance. Prefer simple, predictable paths.
- Slow in, slow out, on every move. It signals start and end, and it feels physical.
- Avoid ambiguity. Don't let points cross or swap in ways that break correspondence.
Two further constraints from the animation-comprehension literature: apprehension — the motion has to be perceivable, so segment it and don't over-densify, and congruence — the motion must correspond to a real change in the data. Decorative motion raises cognitive load and buys nothing.
The camera is the narrator's finger. Open wide showing the whole cloud, then a slow S-curve push-in to the region carrying the story, then pull back wide for the payoff. Ease it; never a linear zoom. And clip the plot to its own band so a zoom can't spill over the rest of the layout.
6 · Annotate on a static state
Because viewers can't read values off motion, every analytical beat settles and then labels.
- A drawn ring or arrow tied by a leader line to a two-to-four-word label. Animate the stroke on rather than fading it in.
- A guide line from the point to the axis, so the viewer can literally read the value off the scale.
- Label the value at the element, at the end of the line or beside the point. Never make them find the axis.
- Number readouts count up rather than hard-cutting.
Draw the gap you state out loud. If the narration says one thing is twice another, there should be a visible measured span on screen showing it. An asserted comparison is a claim; a drawn one is evidence. This is the same coupling idea as the caption rule in chapter 4 §6 — the words label the mark, the mark proves the words.
7 · The minimalism target
The aesthetic bar is dark-field macro-finance minimalism, and it comes down to six things:
- Near-black field, ruthless minimalism, one message per chart. Almost no chart junk, few or no gridlines, huge negative space. If an element isn't carrying the point, delete it.
- A bold takeaway title that states the conclusion. Not "Income vs response time" — "Your ZIP decides how fast help comes."
- Muted field, one accent.
- Threshold lines and regime shading. A dashed horizontal line at a meaningful benchmark and a shaded zone for the danger quadrant. For an ambulance-response chart: dash the real eight-minute standard across the plot and shade the quadrant of poor ZIP codes that blow past it. Then the story is "look how many dots live in the red zone" rather than a scatter you have to interpret.
- Smooth draw-ons with values labelled at the element.
- Confident pacing. Let a beat breathe on a static, fully-labelled state before moving.
8 · The banned chart, and what replaces it
Slope charts are banned outright. Two ranked columns joined by diagonals turn into spaghetti the moment more than about three entities cross, and the crossings are the entire reason you drew it. The chart destroys its own subject.
Use a dumbbell instead. One row per contender, both endpoints legible, and the length of the connector is the size of the disagreement. Same finding, measurable instead of tangled.
Pie is banned everywhere except one slot: a set of weights, animated from equal slices to actual ones. Weights genuinely are angular shares of a whole that sums to one, which is the single case a pie encodes honestly, and the equal-to-weighted animation supplies the baseline a static pie never has. A pie anywhere else is a bug.
And never let big text be the visual. A sentence set large is not a chart. If your beat's visual is a headline, the beat has no visual — you have narration with a caption. Every beat needs something that encodes a quantity.
9 · The chart is not the hook
This is where chart craft collides with distribution reality, and the collision is expensive if you don't know about it.
Every static-chart opener on this channel lives in the 40–50% skip band. A rigorous 43-chain scatter with logos doing a physics drop-in measured 44.7% skip and about 4,500 views on the same week that a moving-simulation opener measured 21.4% and 218,000. The chart data was real and rigorous, and that did not save it. It read as "a fact", not as a spectacle.
A settled scatter, beeswarm or bar chart at frame 0 is a chart no matter how many marks it has. It is not motion.
But charts aren't banned — a chart opener that runs works. Within chart-openers alone the correlation between skip and views is −0.78, and one running-chart opener measured 27.1% skip and 132,000 views.
The recipe that reliably drags a chart concept out of the death band: find the physical process behind the number and animate that at frame zero, then resolve to the chart. An income-versus-ambulance-response scatter opened on two clocks ticking side by side — one freezing when its ambulance arrives, the other still climbing, and posted 36.3% skip, the best any chart concept had ever opened on that channel, clearing the whole death band.
So: lead with the process, never with the axes. Then everything else in this chapter applies to the chart the process resolves into.
10 · Anti-patterns
Each of these has shipped here at least once.
- Dumping the whole finished chart at once. The most common one.
- Rainbow or multi-accent colour. Two accents means neither is an accent.
- Decorative motion that reveals nothing. Fails congruence; costs attention.
- Over-staggered dot entry. Measured as no better and sometimes worse.
- Linear or robotic zooms. Every camera move eases.
- A text sentence used as the visual.
- An annotation anchored off the top bar of a sorted bar chart. The top bar is the longest by construction, so the callout lands on the data. Anchor into real white space.
- Labels stacked below a dot in a dense region. Side-place them — left-half events label left, right-half label right, so they never collide.
- A settled scatter at frame zero. §9.
11 · The checklist version
Every chart in a video should be able to answer these before it's built, not after:
- What single question does this chart answer, and is it different from the previous chart's question?
- Is a distribution visible somewhere in this video, or only summary statistics?
- Does the mark size match the quantity, and do the axis end labels match the domain I asked for?
- Is the crowd grey and is exactly one thing lit?
- Does it build in layers, one per narration beat, ending on the hero?
- Does every analytical beat settle on a static state with the value labelled at the element?
- Is every stated comparison also drawn?
- Are units in the axis titles, and are r, n and p on the plot?
- Is anything moving that doesn't correspond to a change in the data?
- If this is frame zero — is it a process, or is it axes?
The printable version is in the pack: the chart-craft checklist.
10 more failures · free · no email
