A dashboard answers a question that gets asked again and again, on a schedule, by people who already know the business. That definition does most of the work. It rules out what usually gets built instead, a page holding everything the data team can compute, which is a wall.
Worked example: a 14-tile dashboard cut to six
Measure it. Sahyadri Diagnostics' first monthly page carried 14 tiles. A reader trying to understand what changed has to compare tiles against each other, and 14 tiles admit 91 pairwise comparisons. Cut to the six that carry a decision and the comparisons fall to 15, a reduction of 83.52%. At a realistic four seconds of attention per tile, the scan cost goes from 56 seconds to 24. Calling the six-tile version a simplification of the fourteen-tile one undersells it. Somebody decided what the page is for, and that makes it a different artefact.
Design the reading order on purpose. In a left-to-right layout the eye enters top-left, moves right, drops and comes back, so the top-left tile holds the strongest position on the page. That tile carries the claim. For Sahyadri's month, the claim is that turnaround-time breaches rose to 5.71% of tests from 4.12%. On top of that, 48.07% of network volume is in the two Pune centres, which breach at 9.1% and 7.8% against 3.15% for the other six, a ratio of 2.69 times. The top-left tile says that, in a sentence, with the two numbers. Everything else on the page is there to let a reader check it or act on it.
Advertisement
What does a dashboard tile need, and what should the title say?
Each tile needs three things and nothing more: a metric, a comparison and a status. The metric is the number now. The comparison makes it interpretable, and it's the prior period, the target, or the same metric elsewhere. The status is the judgement. It belongs on the tile, because a tile without a judgement leaves every reader to form their own, and they won't all form the same one. A tile that says 5.71% is data. A tile that says 5.71%, against 4.12% last month and a 4.00% standard, breaching, is a fact with a verdict attached.
The dashboard's own title follows the same rule as an exhibit's. "Operations dashboard, September" is a filing label, and a page read every month is the one context where a stable address is defensible. What works is a label as the standing title and a claim as a dated subtitle that changes each month. The subtitle carries the month's message.
Common dashboard mistakes and how to avoid them
Three failures turn up often enough to name. The first is the tile with no owner: a metric nobody is accountable for, which produces discussion and no action. The second is stale data presented as live. Fix it by putting the refresh time on the page and saying what the latency is, instead of implying there's none. The third is the dashboard that grows. Every month someone asks for one more tile, nobody ever asks for one fewer, and after a year it's a wall again. The countermeasure is a fixed tile budget with a swap rule. A new tile displaces an old one, and somebody makes that call out loud.