I've built dashboards that get opened every morning and dashboards that get opened twice and then forgotten. After enough of both, the difference is pretty clear — and it's almost never about the charts or the visual design.

The Most Common Dashboard Failure Mode: Too Many Metrics

The first dashboard I built for a sales team had 23 metrics. Revenue by region, pipeline by stage, conversion rates at each stage, rep activity numbers, average deal size, win rate by product, time-to-close, competitive win rate, call volume... everything the CRM could produce, I put in.

Nobody used it after the first week. When I asked why, the VP of Sales said: "I can't tell what I'm supposed to do differently when I look at it."

That's the failure. A dashboard full of metrics is not the same as a dashboard that supports decisions. More information does not equal better decisions — it often means no decision gets made because nobody knows which number to focus on.

The Question That Reframes Everything

Before building a dashboard, ask: "What decision will someone make differently because of this dashboard?" If you can't answer that question specifically, you're building a reporting artifact, not a decision tool.

For the sales team example, the decision was: "Which deals should our sales manager focus coaching attention on this week?" That's one question. Build the dashboard around one question.

Design Principles That Actually Matter

Fewer metrics, bigger story. The best dashboards I've built have three to five metrics. Not 23. Three. They force you to choose what matters, and forcing that choice is actually the most valuable part of the process.

Always show context. A number without context is almost meaningless. Revenue of $450,000 — is that good? What was last month? What's the target? What was this period last year? Every metric on a well-designed dashboard has a comparison point that gives it meaning.

Put the "so what" in the title. Instead of a chart titled "Monthly Revenue by Region" consider "Southeast Revenue Is 23% Below Target." The title does the analytical work of telling the viewer what the chart means, not just what it shows.

Design for the reader's workflow. If a sales manager looks at their dashboard at 9am while drinking coffee on their phone, the dashboard needs to work in that context. Five taps to get to the number they need is five taps too many.

The Maintenance Problem

Dashboards that stop being used often stop being used because the underlying data broke, a metric changed definition, or the business context changed but the dashboard didn't. Building a dashboard without a maintenance plan is like deploying code without monitoring — it'll silently rot and nobody will know.

Assign ownership. Set up data quality alerts. Schedule quarterly reviews. A dashboard is a product, and products need maintenance.