Five to seven metrics on the main view. Past that, hierarchy flattens and a metric that should trigger action sits at the same visual weight as one that is only informational.
Dashboards fail in a predictable way. Someone asks for a metric to be added, nobody ever asks for one to be removed, and after two years the main view has thirty tiles that get scanned and forgotten.
The test a metric has to pass
A metric earns a slot when you can name the decision it changes and the person who makes that decision. "Useful context" is not a decision. Neither is "the board asks about it," which argues for a board report rather than a permanent tile on an operating dashboard.
| Metric | Decision it drives | Owner |
|---|---|---|
| Forecast vs. quota | Whether to intervene this period | Sales leader |
| Pipeline created this period | Whether to add generation activity | Sales and marketing |
| Win rate by segment | Where to focus coaching and pricing | Sales leader |
| Deals with close dates that moved | Which deals to inspect now | Manager |
| Average deal size vs. closed-won | Whether pipeline is priced realistically | RevOps |
The metric that creates the most noise
ORM names total pipeline coverage without context as the metric that generates the most noise. It makes executives feel informed while masking the actual risk.
The mechanism is straightforward. A company can show 4x coverage and still miss badly when the pipeline is low quality, concentrated in the wrong stage, dependent on a few large deals, inflated by stale opportunities, or built on close dates that keep moving. A single coverage tile shows none of that, which is why it reads as reassurance.
If coverage stays on the dashboard, it needs a companion that carries composition, such as coverage split by segment or the share of coverage sitting in aged opportunities. The reasoning behind that split is covered in why the 3x pipeline coverage rule is wrong.
Where the rest of the metrics go
Nothing gets deleted. It gets relocated. Metrics that explain a headline number belong one click beneath it, so a viewer who sees win rate drop can open the segment and rep breakdown from the same tile.
That structure keeps the main view short without losing detail, and it enforces a hierarchy: the top level tells you something is wrong, the layer underneath tells you where. A dashboard that puts both layers on one screen has decided nothing, and it hands that work to every viewer, every time.
Frequently Asked Questions
How many metrics should a sales dashboard have?
Five to seven on the main view. That is enough to describe the state of the number without forcing the viewer to rank thirty tiles by importance every time they open it. Additional detail belongs one level down, reachable by clicking a headline metric rather than sitting beside it.
What happens when a dashboard has too many metrics?
Viewers stop reading it and go back to asking analysts for one-off pulls. A crowded dashboard also flattens hierarchy, so a metric that should trigger action sits at the same visual weight as one that is purely informational, and the signal gets averaged out.
How do you decide which metrics make the cut?
Keep a metric only if you can name the decision it changes and the person who makes that decision. If a metric has not changed a decision in a full quarter, it is reporting habit rather than management information, and it belongs in a drill layer.
Should every team see the same dashboard metrics?
No. A rep acts on their own open deals, a manager acts on their team's coverage and risk, and an executive acts on the forecast and segment mix. Each role needs its own five to seven, because a metric one role acts on is background noise for another.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like how many metrics should be on a sales dashboard? into prescriptive action for your team.
Schedule a Demo