A dashboard that doesn't change a decision is decoration

Here is the line I keep coming back to after years of building reporting for revenue teams: a dashboard that does not change a decision is decoration. It can be beautiful, real-time, and technically flawless, and still be worthless, because the job of a report is not to display data. It is to change what someone does next.

Most reporting fails this test quietly. It shows the number, colors it green or red, and stops. The viewer nods, feels informed, and does exactly what they were going to do anyway. That is not reporting. That is a very expensive way to feel busy.

The two-question test

I judge every chart, tile, and dashboard by two questions the viewer should be able to answer in one breath: why does this matter, and what do I do about it?

If a sales leader looks at a tile and cannot say why it matters, the tile is noise. If they can say why it matters but not what to do differently, the tile is trivia. Only when both answers are obvious does the report earn its place, because only then does it have a path to changing behavior.

Try it on your own dashboard. Walk across the top row of tiles and, for each one, force the two answers out loud. Most people get three or four tiles in before they hit one they cannot justify. That tile has been sitting there for a year, refreshing faithfully, changing nothing.

Annotate for the decision, not the data

The cheapest fix is also the one almost nobody does: annotate every executive-facing tile with one line of why-this-matters and one line of do-this.

A number on its own outsources interpretation to the viewer, and different viewers interpret it differently, which is how a leadership meeting turns into an argument about what a chart means instead of a decision about what to do. A single annotation collapses that. "Win rate down 6 points this quarter, concentrated in deals without an identified economic buyer. Action: inspect commit-stage deals for buyer coverage before the forecast call." Now the chart is not showing data. It is proposing a move.

This is a habit, not a platform. You can do it in whatever tool you already have. The discipline is refusing to ship a tile without stating the decision it serves.

Adoption is the real metric of reporting

The uncomfortable truth about most reporting suites is that a large share of the reports are never opened. Built once for someone who asked, shipped, and then quietly abandoned while they keep running in the background.

Adoption, not volume, is the honest measure of a reporting function. The most-built, least-opened report in your company is not a feature. It is evidence that the reporting is optimizing for looking comprehensive instead of driving action. Killing a report nobody opens is not a loss. It is a cleanup, and it makes the reports that matter easier to find.

So the second thing I look at, after the two-question test, is usage. What actually gets opened, by whom, before which meeting? The reports that survive that filter are the spine of the system. The rest is inventory.

What good looks like

Reporting that drives action has a specific shape. Every view maps to a decision and a role. Every executive tile carries its why and its do. Thresholds and alerts surface the moments that need a response, instead of asking a human to notice a slow drift on a chart nobody is watching. And the suite is small, because the unused reports have been retired rather than left to rot.

The payoff is not prettier dashboards. It is meetings that end in decisions instead of interpretation, signals caught while they still matter, and a reporting function people actually rely on because it has earned the trust. The measure of a report was never how much data it shows. It is whether anyone does anything differently because it exists.

Start with the two questions. They are almost embarrassingly simple, and they will tell you, tile by tile, which of your reporting is working and which of it is decoration.

I write about making revenue operations legible, and I run a productized Revenue Engine Audit that scores reporting alongside four other dimensions of a revenue engine. Reporting that changes behavior is one of the five.