Start From the Decision, Not the Data

A familiar scene. Someone has done real work. They present twenty slides of careful analysis. The room nods. Questions are asked and answered. Everyone agrees it was interesting.

And nothing happens.

That outcome is usually blamed on the audience: they did not engage, they are not data literate, they had already decided. Occasionally true. Far more often the presentation was constructed so that acting on it was impossible, and the construction error is specific.

The analyst organised the presentation around their own journey. Here is the question I was given, here is the data I gathered, here is how I cleaned it, here is the method, here are the results, and in the final minutes, here is what I think it means.

That sequence is how the work was done, and it is close to the worst possible order for a decision-maker. It puts the thing they need first at the end, and it spends their attention on material that helps them evaluate your method rather than your conclusion.

By the time you reach the recommendation, the meeting is running late and half the room is reading email.

The fix is not better charts. It is inverting the structure, and that inversion follows from a single question asked before any of it: what decision is this for. The rest of this lesson is about answering that question properly, because most presentations that fail cannot answer it at all.

The question what decision is this for sounds obvious and is answered badly most of the time. Some tests that sharpen it.

Who can act? Name the person. If nobody in the room can change anything based on what you say, you are informing rather than deciding, and that is a different presentation with different rules.

What are the options? A decision requires at least two. If there is only one course of action, you are seeking approval, not supporting a choice, and the presentation should argue rather than explore.

What would change the answer? This is the most useful question of the three. If the audience would do the same thing regardless of what your analysis showed, the analysis is decoration. That happens more often than analysts like to admit, and finding it out early saves everyone the work.

When is it decided? A decision this week and a decision next quarter need different things from you. The first needs a recommendation; the second can afford to build understanding.

And what is the cost of being wrong in each direction? This determines how much certainty is required. A reversible, cheap decision needs a good-enough answer today. An expensive, irreversible one justifies waiting for better evidence, and saying so is a legitimate output.

Working through these before you build anything changes what you build. Most importantly, it sometimes tells you not to build it, because the decision is already made or the analysis cannot move it.

That conversation with whoever commissioned the work is the highest-return ten minutes available in this whole discipline.

The same analysis, arranged the way it was done and the way it should be delivered.

The analysis order runs from background, through data and method, to results, and finally to implications. Each step depends on the one before, which is why the work happened that way. Delivered in that order, the audience spends most of its attention before reaching anything actionable, and the recommendation lands when attention is lowest.

The delivery order inverts it. The recommendation comes first: here is what I think we should do. Then the reason, in one or two points. Then the evidence supporting each. Then the caveats and what would change the conclusion. And the method, data and detail sit in an appendix for anyone who wants them.

Why this works better. A decision-maker can stop at any point and still have what they need, which respects that they may only give you three minutes. Questions arrive against a stated conclusion, which is a more productive conversation than questions against an open exploration. And the people who want the method still get it.

The common objection is that leading with the conclusion feels presumptuous, as though you are telling them what to think. In practice the opposite reads worse: withholding your view while walking through your working reads as either evasive or as not having formed one.

You did the work. Say what you think it means.

A discipline that improves presentations more reliably than any other, and it is mechanical enough to apply without judgement.

Every chart, table or slide carries exactly one message, and that message is written as the title.

Not Revenue by region, which is a description of the axes. But Growth is concentrated in two regions, which is a claim. The first tells the audience what they are looking at. The second tells them what to conclude, which is the thing you were hired to determine.

What this discipline forces, and why it works.

If you cannot state the message in a sentence, you do not yet know what the exhibit is for, and the audience certainly will not work it out.

If two messages fit one chart, it is two charts. Combined exhibits where the audience must find both points usually deliver neither.

If an exhibit has no message, it should not be there. This deletes a surprising proportion of most decks, and the deleted material is generally the analyst showing what they did rather than what they found.

And the sentence titles, read in sequence, become the argument. If you strip a deck to its titles and it reads as a coherent case, the structure is sound. If it reads as a list of topics, the deck has no argument and the audience will not construct one for you.

That last test takes two minutes and it catches most structural problems. A deck whose titles are Revenue, Costs, Headcount, Outlook is a set of topics. A deck whose titles are Revenue growth has stalled outside two regions, Costs rose faster than volume, We are carrying capacity for a plan we abandoned, and Two options follow, is an argument.

A single number carries almost no information, and audiences routinely receive presentations built entirely from single numbers.

Customer satisfaction is seventy-two. Is that good? Nobody in the room knows, including frequently the presenter. The number becomes meaningful only against something.

The comparisons available, roughly in order of usefulness.

Against time. Seventy-two, up from sixty-five last year. Now it means something, and the direction is usually what matters more than the level.

Against a target. Seventy-two against a target of eighty. This tells the audience whether to be concerned.

Against a comparable group. Seventy-two, where similar teams average sixty-four. This separates a general condition from your specific situation.

Against a segment breakdown. Seventy-two overall, but fifty-one among new customers. This is frequently where the actual finding lives, because the aggregate hides the thing you should act on.

And against what it was before an intervention, which is the weakest of these and the most commonly used, for reasons the catalogue's cursus on knowing what actually works covers in detail.

The practical rule. Never present a number without the comparison that makes it interpretable. If you cannot find one, that is itself a finding: you do not yet know whether this is good.

And choose the comparison honestly. The temptation to select the baseline that makes your number look best is strong, particularly when the number is about your own work, and an audience that later discovers the choice was convenient will discount everything else you showed them.

Analysts routinely strip uncertainty out of presentations, believing that decision-makers want confidence. This is a mistake, and an expensive one.

Why it happens. Hedged findings feel weak. A range looks like you did not finish the work. And there is a real experience of senior people responding badly to it.

Why it is wrong. The decision depends on the uncertainty far more often than on the point estimate. A projection of twelve percent growth leads to one decision if the plausible range is ten to fourteen and a completely different one if it is minus five to thirty. Presenting twelve without the range hides the input the decision actually needs.

And the reputational arithmetic runs the other way from how it feels. An analyst who presents point estimates confidently will be wrong publicly and repeatedly, because the world is uncertain. An analyst who presents honest ranges is right about the range, and builds a reputation for being reliable rather than for being confident.

How to present it without sounding evasive.

Give the range, not a hedge. Between eight and fifteen percent is specific. Roughly around twelve, but hard to say is not.

Say what drives the uncertainty. We do not know how many will renew is actionable, because someone can go and find out.

Say what would narrow it, and what it would cost. This converts uncertainty from a problem into a decision about whether to buy more information.

And distinguish what you know from what you assumed. Most disagreements about analysis are disagreements about assumptions, and surfacing them turns an argument about your competence into a productive conversation about inputs.

These tools touch data communication in several places, and they are useful in inverse proportion to how impressive the use sounds.

Genuinely useful. Turning a finding you have established into clear prose, which is the same line-editing value described in the writers cursus. Producing several framings of the same message so you can pick the one that fits the audience. Drafting the executive summary. Suggesting what a sceptical reader would ask, which is a real rehearsal aid. And critiquing your structure: what is the argument here, which slide does no work, where does this get slow.

Genuinely useful and less obvious. Interrogating your own data, so that a manager without SQL can ask why did this drop in March without waiting three days for an analyst.

Where it flatters and should be distrusted. Asking a model what the data means. It will produce a confident interpretation, and it has no knowledge of your business, your segments, what changed operationally in March, or which of your metrics is known to be unreliable. What it generates is the most typical explanation for that pattern, which is exactly the explanation you would have guessed and which is often wrong for reasons only you could know.

And the hard rule from throughout this catalogue applies with full force here. Numbers come from the tool that computes them. A model asked to calculate a growth rate, a share or a projection produces a plausible figure with nothing behind it, and in a decision presentation that is the worst possible error, because it is invisible and it is load-bearing.

The pattern, once more. Use it on the language around the analysis, not on the analysis.

Collecting the lesson into something usable an hour before a meeting.

Can I name the decision and the person who makes it? If not, I am informing, and I should say so rather than implying a choice is available.

Would the audience do something different depending on what I show? If not, the presentation is decoration and the honest move is to say the analysis does not settle it.

Does my first slide contain the recommendation? If the conclusion is at the end, the structure is the analysis order and needs inverting.

Does every exhibit have a sentence title stating its message? And do those sentences, read alone, form an argument rather than a list of topics?

Does every number have a comparison? And did I choose that comparison because it is the right one rather than the flattering one?

Have I given the range as well as the estimate, said what drives the uncertainty, and separated what I know from what I assumed?

Have I said what would change my conclusion? An analyst who names the evidence that would overturn their view is markedly more persuasive than one who does not, because it demonstrates the conclusion was reached rather than chosen.

And is the method in an appendix rather than in the first ten minutes?

Eight questions. Most decks fail three or four of them, and fixing those is worth more than any improvement to the charts, which is the subject of the next lesson.