Built from years of watching good data get ignored
This page explains the reasoning behind the course: where the method comes from, what it borrows from journalism and design, and how each module gets tested before it's taught.
Where the method comes from
A method assembled from three fields, not invented from scratch
The course draws on newsroom editing practices for structuring information around a reader's question, on information design for choosing visuals that reduce cognitive load, and on internal communications work for understanding how different departments actually consume updates. None of these fields on their own solves the "dashboard nobody acts on" problem. Combined, they cover it reasonably well.
Every module is written around an internal reporting scenario first, then the underlying technique is extracted afterward. That ordering matters. It keeps the lessons anchored to situations people recognize instead of abstract design theory.
How a module gets built
Every lesson starts as an internal reporting failure, then gets rebuilt
Before writing a lesson, we collect an example of a report or dashboard that technically worked but didn't move a decision forward. We map out why: was the headline buried, was the chart type mismatched to the message, was the audience wrong for the depth of detail included?
Once the failure point is clear, we rebuild the same data into a version that addresses it, and the difference between the two versions becomes the core teaching material. Participants see both, side by side, rather than being told abstractly what "good" looks like.
This approach means updates to the course happen slowly and deliberately. A module only changes once a clearer example has been found and tested with a small group first.
What guides the teaching
Four principles behind every module
Structure before decoration
A well-sequenced argument in plain bar charts communicates more than a beautifully designed report with no clear order.
Design for the skim
Assume the reader has ninety seconds. Everything essential should survive being read only that far.
One dataset, many shapes
The underlying numbers rarely need to change across audiences. The framing, depth, and vocabulary do.
End on a decision
A report without a clear next step tends to get filed and forgotten, regardless of how sound the analysis was.
Who the course is for
Built for the person between the data and the decision
Participants tend to be analysts asked to present their own findings, operations managers who inherit weekly dashboards, and product or finance staff who prepare updates for leadership. Some arrive comfortable with spreadsheets but unsure how to write around them. Others arrive confident in presenting but unsure which chart actually supports their point.
The course does not assume a background in statistics or design. It does assume familiarity with whatever reporting tool your organization already uses, since the exercises are meant to be applied directly to your own dashboards rather than a generic sample dataset.
