Vanity Metrics vs Decision Metrics: A Filter for Your Dashboard
A simple three-question test to decide whether a metric belongs on your dashboard — or in the bin.
By Tillmann Kühn · 12 July 2026
Every metric feels important to the person who reports it. That is exactly why dashboards bloat until they are unreadable. The discipline is not collecting more numbers — it is filtering them. Here is the test I run on every candidate metric.
The three-question filter
A metric earns a spot on the dashboard only if it passes all three:
- Does it change a decision? If the number moved 20% up or down, would anyone do something differently? If not, it is context at best and noise at worst.
- Is it actionable by this audience? A metric a viewer cannot influence belongs on someone else's screen. Board-level dashboards and team-level dashboards fail differently when this is ignored.
- Is it trustworthy? If people quietly doubt how it is calculated, they will ignore it — and worse, ignore the good metrics next to it.
Total impressions usually fails question one. Cumulative signups fails it too (it can only ever go up). Pipeline coverage, CAC payback, activation rate — these change decisions.
Leading vs lagging: put both on the screen
Revenue is a lagging metric: by the time it moves, the causes are months old. Pair every lagging metric with the leading indicator that predicts it:
- Revenue ← qualified pipeline created
- Churn ← product activation in week one
- Organic traffic ← pages ranking in positions 4–10
The lagging number tells you where you are; the leading number tells you where you are going. A dashboard with only lagging metrics is a rear-view mirror.
Beware the ratio that hides the base
A 100% conversion rate on two visitors is not a success. Always show the denominator near the ratio, or a small sparkline of volume beside it. Ratios without base rates are how teams celebrate statistically meaningless swings.
The "so what?" column
For internal dashboards I sometimes add a literal annotation next to each KPI: one line stating what a red value should trigger. "Pipeline coverage below 3x → pull forward outbound." It turns a number into a decision, which is the entire job.
The best dashboards are aggressively edited. Every number you remove makes the ones that remain louder.
Want a dashboard like the ones I write about?
Book a free discovery call and I'll map your KPIs to a tailor-made build.
Book a call