A Spreadsheet Is Not a Story: A Four-Scene Brief for Decision-Ready Explainers

Most spreadsheet updates fail for a simple reason: they show the evidence before they name the decision.

The numbers may be correct. The workbook may be carefully maintained. But the person opening it still has to answer four questions for themselves:

1. What changed?
2. Compared with what?
3. Why does the change matter now?
4. What should happen next?

That is why a narrated explanation should not become a screen recording of a worksheet. The useful unit is not the cell. It is the decision behind a small, reviewable set of cells.

Start with one viewer question

Before choosing a chart or a scene, write a sentence that a decision-maker could ask aloud.

For example:

Did fulfilment performance improve after the routing change, and should the team extend it to the remaining regions?

That question gives the source material a boundary. It tells you which period, comparison, assumption, and next action belong in the explanation. It also makes it easier to remove everything that is merely adjacent.

A four-scene brief

Here is a compact pattern that works for KPI exports, operating dashboards, financial workbooks, and survey comparisons.

Scene 1: Establish the decision and the time window

Show the decision in plain language, then anchor the analysis to a period. A single line such as “Week 26 after the routing change” is more useful than opening on a dense dashboard.

The reader should know whose decision this is and what timeframe is in scope before seeing a percentage.

Scene 2: Show the comparison, not every value

Choose the baseline that makes the decision meaningful: before/after, plan/actual, cohort A/cohort B, or current/proposed.

Use a small number of values with their units and definitions. If the comparison is not valid because the population, filter, or calculation changed, say that instead of animating a misleading trend.

Scene 3: Explain the mechanism or constraint

This is the scene dashboards usually omit. A metric moved, but what operational condition changed with it?

For the routing example, the explanation might show a simpler handoff path, the affected regions, and the constraint that still prevents rollout everywhere. The viewer does not need every implementation detail. They need the relationship between the change and the outcome.

Scene 4: End with the decision, owner, and review condition

An explanation should give the viewer a next move. That might be “extend the pilot after the data owner validates the final two regions,” not “the project succeeded.”

The final frame can keep three things visible:

• the recommended action;
• the owner of the validation; and
• the condition that would change the decision.

That makes the content useful in a meeting and still reviewable afterwards.

Keep the workbook as evidence

An explainer should make evidence easier to understand. It should never replace validation.

Before sharing, the data owner should still check the source period, filters, units, calculation, comparison baseline, labels, and conclusion. Link or attach the workbook where the audience needs to inspect it. If a number changes, update the source and the explanation together.

This division of labour is important: the spreadsheet remains the auditable evidence; the visual sequence helps a human follow the comparison and decision.

A prompt is not enough; provide a brief

When you create a source-led explainer, include the following with the selected workbook or chart:

Viewer: regional operations lead
Question: should the routing pilot expand?
Period: weeks 22–26
Comparison: pilot regions vs. their own pre-pilot baseline
Evidence: order volume, fulfilment time, exception rate
Constraint: two regions use a different handoff process
Decision: extend only after exception-rate review

This is short enough to review, but it prevents the common failure mode of turning every visible metric into narration.

Where this workflow fits

KPainter is the source-to-explainer workspace I founded. Its Excel-to-video workflow starts from a workbook, chart, or selected data range and asks for the metric, comparison, audience, and decision that the viewer needs to understand.

The important part is not the tool. It is the reviewable brief: one question, one valid comparison, a visible mechanism, and a named next step. With that structure, a spreadsheet update can become something a team can understand before the meeting rather than a file they open during it.

Xinwei is Founder of KPainter.