DataStory

Key Ideas

1. Data needs a decision path

A useful data story moves from context to tension to recommendation. The audience should not have to infer what the communicator wants them to decide.

In practice, this means replacing a neutral dashboard tour with a guided argument. The communicator should tell the audience what question the data answers, why that answer changes the situation, and which choice is now on the table. A decision path prevents the audience from drowning in supporting cuts before they know the main claim.

Why it matters: decision makers rarely experience data in the same order the analyst discovered it. Apply this by writing the requested decision at the top of your outline, then arranging evidence by what the audience must believe before they can responsibly say yes.

A DataStory reader can apply this by building a one-page decision brief before making slides: decision needed, audience fear, current belief, surprising evidence, recommendation, and next owner. If a chart does not support one of those fields, it belongs in backup. This forces the presenter to make the meeting about choice architecture rather than analysis volume.

For example, if activation drops after a product redesign, the data story should not begin with every dashboard panel. It should begin with the decision: whether to roll back, adjust onboarding, or run a targeted experiment. Then each chart earns its place by helping leaders choose among those options.

The reader should also prepare one backup slide for the evidence most likely to be challenged, so the main story stays clean while still respecting skepticism.

2. Empathy changes the explanation

Executives, customers, and analysts do not need the same path through the evidence. Start with the audience's job, risk, and vocabulary before choosing the sequence.

Duarte's communication lens asks the presenter to translate from analyst logic into audience logic. An analyst may care about methods and caveats first; an executive may need risk, timing, and strategic consequence first. The same evidence can be sequenced differently depending on whether the audience is skeptical, unaware, already convinced, or worried about implementation.

Why it matters: empathy prevents the presenter from overexplaining methods while underexplaining consequences. Apply it by writing one audience sentence before each slide: 'They are worried about...' or 'They need proof that...' That sentence should shape the chart, title, and spoken setup.

For an executive audience, empathy often means leading with consequence before method. A churn model, for example, should begin with which customer group is at risk and what decision is time-sensitive, then reveal the supporting cuts. For an analyst peer review, the sequence can reverse. The communicator's skill is choosing the path that earns trust from this audience.

In a board update, empathy may mean translating model confidence into business exposure: how much revenue is at risk, which assumption is fragile, and what decision can wait. The presenter still respects the data, but they package it around the audience's responsibility rather than the analyst's workflow.

This is why a data story for finance may lead with exposure, while a product story may lead with user friction or adoption behavior.

3. Contrast creates meaning

A metric matters when readers see what changed, what was expected, or what alternative is now weaker. Contrast turns a number into a message.

A metric becomes meaningful when the presenter supplies a before-and-after, expected-versus-actual, segment-versus-segment, or risk-versus-opportunity contrast. Without contrast, numbers feel like trivia. With contrast, the data creates tension, and tension gives the story its reason to exist.

Why it matters: contrast tells the room where to look. Apply it by adding a baseline, target, prior period, or alternative option whenever a number might otherwise sit alone. The contrast should answer why the data changes the recommended decision now.

A useful exercise is to write the same metric three ways: compared with last quarter, compared with target, and compared with the best segment. Each contrast tells a different story. DataStory helps the presenter choose the contrast that matches the decision, so a retention discussion does not accidentally become a vanity-growth update.

A contrast can also prevent false urgency. If a metric is down versus last week but normal versus the seasonal baseline, the story changes. DataStory readers should choose comparison points that make action smarter, not just more dramatic.

If no contrast changes the decision, the metric may belong in monitoring rather than in the persuasive story for that meeting.

4. Recommendation beats reporting

Reporting says what happened. Recommendation says what should happen next and why the evidence supports it. That shift is where communication value appears.

The book pushes analysts to own the implication of their work. A recommendation does not mean pretending uncertainty is gone. It means stating the best action the evidence supports, naming the assumptions, and giving decision makers a concrete way to accept, reject, or test the recommendation.

Why it matters: recommendations create accountability. Apply this by pairing the data claim with a proposed owner, timeline, and reversible test when uncertainty remains. That keeps the data story from becoming either a lecture or an unsupported demand.

Recommendation discipline means saying what the data is strong enough to support and what it is not. A good presenter might say, 'This evidence supports a two-week pricing test, not a full rollout.' That level of precision builds credibility because the recommendation has boundaries, assumptions, and a next learning step.

A good recommendation slide can include a small 'what would change our mind' note. That keeps the presentation honest and makes the recommendation easier to discuss. Decision makers can then debate assumptions instead of guessing whether the presenter is overselling the finding.

A recommendation becomes easier to trust when the presenter names the smallest next action that would create more evidence.

5. Visuals and words must share one point

A chart should not compete with the sentence around it. The visual, headline, and spoken explanation should all carry the same claim.

Why it matters: audiences remember the point when the words and visual reinforce each other. Apply it by changing neutral chart titles into insight titles, then checking whether the chart actually proves that sentence. If not, revise the chart or soften the claim.

A common weak slide has a chart saying one thing, a title naming only the metric, and a speaker adding a third interpretation. DataStory encourages alignment: the title states the insight, the chart proves it, and the spoken explanation helps the audience understand consequence and next action.

Before presenting a chart, rewrite its title as a sentence with a verb: 'Enterprise renewals fell after onboarding delays increased.' Then check whether the visual actually shows that relationship. If the chart only shows renewals, the speaker needs another visual or a softer claim. Alignment prevents the audience from hearing one story while seeing another.

This is especially important when a deck uses multiple chart types. A bar chart, line chart, and customer quote can all support one insight, but only if the headline tells the audience how to connect them. Otherwise the speaker becomes the only bridge between disconnected evidence.

This check is simple: cover the chart and read the title, then uncover the chart and ask whether the picture proves the sentence.