Every company has a dashboard somewhere. Most of them are unloved. Built by someone who's no longer with the company, populated with metrics that mattered six pivots ago, full of numbers nobody quite trusts, opened maybe once a quarter when somebody has to fill in a board update. The dashboard exists, technically. But the team operates on Slack threads, gut feelings, and the founder's last all-hands.
The dashboards that get used share three properties. First, they're short — usually under ten metrics, sometimes under five — because anything longer means the dashboard is a list of things instead of a model of the business. Second, the metrics are the ones the team actually cares about, not the ones the dashboard tool's marketing page suggested. Third, every metric has a written interpretation: what's a good week, what's a bad week, what threshold should make somebody do something about it. Without those interpretations, a number is decoration.
The practical move that works: start with the smallest possible dashboard. One screen. Five numbers. Each number gets a sentence. The sentence is what makes it operationally useful — "we want this to grow 5% week over week; under 0% growth, we should call a meeting." Now the dashboard isn't a report, it's a thermostat. The team checks it because the answer to "are we okay?" actually lives there, and the dashboard answers that question without anyone having to do interpretation work.
Once the small dashboard is being opened — actually being opened — you can layer in more detail, more breakouts, more cohorts. But until that core "are we okay?" thermostat exists and gets used, every additional chart is decoration. The question we ask new operations teams: if your dashboard tool went down tomorrow, who would notice? If the answer is "nobody," the dashboard isn't operational; it's wallpaper.