Turn evidence into a decision-ready story

Data storytelling is the work of helping a particular audience understand what the evidence means for a decision. It is not permission to remove inconvenient records, hide uncertainty or manufacture a dramatic ending. The story should become clearer as you shorten it, while its scope remains intact.

Begin with the reader. A manager needs to know what to do next and why. An analyst needs the definitions, methods and diagnostics needed to reproduce the result. A frontline team needs to know what change is proposed, what will be measured and what remains uncertain. You can change the order and detail for each audience without changing the underlying claim.

Separate observation, interpretation and recommendation

An observation is a checked description: “East's recorded mean duration was 79.63 minutes versus 45.96 at West.” An interpretation relates the result to context: “East also handled longer routes and a different service mix, so the raw gap does not isolate hub performance.” A recommendation proposes an action: “Investigate route and service mix before making a hub-performance decision.” These sentences play different roles.

When these roles blur, a number can acquire a causal story it did not earn. “East's poor management added 33.67 minutes” skips from an observed difference to an unmeasured explanation. An honest story can still be specific: name the missing comparison that would make a decision safer, and say what evidence would change your recommendation.

Build a short evidence chain

Use this sequence when preparing a decision brief:

1. State the decision and the proposed next step.
2. Give one or two checked findings with units, denominators and period.
3. Explain the comparison and the uncertainty that matters to the decision.
4. State the boundary of the conclusion.
5. Identify a concrete next measurement or decision trigger.

This is a writing scaffold, not a requirement that every report use the same five headings. The reason for the sequence is to keep the recommendation traceable to evidence. A reader should be able to ask “Why?” and move backward from action to finding to raw data and definitions.

A worked management brief

“Plan a real controlled pilot before considering a full checklist rollout. In the simulated 40-participant teaching trial, the checklist mean was 3.20 minutes lower than control; the 95% Welch interval was 0.55 to 5.85 minutes lower. The interval includes benefits smaller than the hypothetical 2-minute worthwhile threshold. These synthetic results do not establish real-world effectiveness or capture cost and quality trade-offs. A real pilot should pre-specify the primary outcome, independent assignment unit, sample-size plan and quality guardrails.”

Notice what the brief does not do. It does not put p = 0.0191 in the headline, because the decision depends more directly on the effect range and threshold. The p-value can appear in the methods appendix. It does not promise that collecting more data will confirm the favored outcome. It describes what the next study must resolve.

For the observational side, a companion paragraph might say: “Across the 240 recorded synthetic shipments in weeks 1–8, 51 were late (21.25%). East and West had 25/120 and 26/120 late shipments respectively, while route lengths and service shares differed substantially. Investigate comparable route/service groups and promise definitions before interpreting a raw hub ranking.”

Choose the visual for the sentence

If your key sentence is about the checklist effect and a worthwhile threshold, show the difference interval with a zero line and a −2-minute reference. Two separate mean bars hide the direct contrast and can make overlap confusing. Label the direction: negative means lower checklist duration.

If your sentence concerns the shape of delivery times, use the histogram or a dot/box display rather than the effect-interval chart. If it concerns rating response bias, show response counts or rates for late and on-time shipments, with denominators. Every figure needs a caption that can stand alone outside the slide deck: outcome, units, source file, scope and meaning of uncertainty marks.

Include a text equivalent. For the trial chart: “The point estimate is −3.20 minutes; the interval spans −5.85 to −0.55, excluding zero but crossing the −2-minute worthwhile threshold.” A person who cannot see the graph now receives the same essential comparison. Do not use color alone to distinguish observed results from thresholds.

Be concise without burying limitations

Not all caveats deserve equal prominence. Put the limitation that could change the decision beside the headline. Put technical implementation details in a reproducibility appendix. “Synthetic data; operational effectiveness untested” belongs near a rollout recommendation. The exact random seed belongs in the appendix. Both matter, but they serve different reading needs.

A practical audit asks: could someone copy the chart into another presentation and unintentionally make a stronger claim? If so, add a scope label to the chart itself. Does the title say “proves” when the design only supports association? Are counts missing? Is the selected period unusually favorable? Have you disclosed excluded records and exploratory comparisons? Does a polished number imply precision beyond the data, such as reporting a rough operational estimate to six decimals?

Make the next step falsifiable

“Continue monitoring” is often too vague. A better proposal names what would be measured and what would count as a decision change. For this capstone, propose a real pilot design and a pre-specified practical threshold; do not invent an exact required sample size without a power calculation and justified inputs. Specify a quality outcome that the current fixture lacks and explain why it matters.

Attempt Practice 11A–11C and Checkpoint C. Your goal is a brief that another person can challenge constructively because the question, evidence and uncertainties are visible.