Communication

A track of P14 · Data Visualization & Communication.

Turning a result into a message an audience trusts: lead with the finding, build dashboards that earn their tiles, present uncertainty honestly, and write about numbers without overclaiming.

You spent three weeks on the analysis, the method is sound, the deck has fourteen slides, and the reply was "thanks, interesting". Nothing was wrong with the work. It simply arrived in an order that made the reader do the interpretation themselves — method first, finding somewhere on slide nine — and nobody had the budget of attention to get there.

A finding that no one acts on may as well not exist. This track is about the gap between having the right answer and getting it to change a decision — the part of data work that lives in slides, memos and dashboards rather than notebooks.

It opens with the one-slide answer: lead with the finding, not the method; pass the "so what" test; frame the same result one way for an executive (decision first) and another for a peer (method first). Then dashboards that earn their tiles — what actually deserves a tile, how alert fatigue sets in, how a dashboard decays when no one prunes it. Then presenting uncertainty honestly: intervals, fan charts, and treating "we don't know yet" as a real finding rather than a failure to hide (cross-linking the P7 forecast work). It closes on writing about numbers — making only the claims your data supports, and keeping causal language disciplined when all you have is a correlation (cross-linking P8).

Leadfinding first, then methodFrameexec vs practitionerShowdashboards, uncertaintyWriteclaims the data supports
Carrying a result to a decision: lead with the finding, frame it for the audience, and never let the prose overclaim.
Communication — TransformerLab