What Makes a Great Executive Dashboard?

The One-Glance Test

A great executive dashboard passes the one-glance test: a person with relevant domain knowledge can look at it for five seconds and answer the question "are we on track?" without clicking, scrolling, or filtering.

• This test eliminates dashboards that require context to interpret (e.g., raw numbers with no targets)
• It eliminates dashboards with too many metrics (the eye cannot prioritise more than 5–7 items at a glance)
• It requires that the most important metric is visually dominant — not buried in a table row
• Every element that does not help pass the one-glance test is a candidate for removal or demotion to a drill-down view

How to Select the Right Metrics

Metric selection is the highest-leverage design decision. These principles guide the selection:

• Show metrics that drive decisions, not metrics that are easy to measure. "Emails sent this week" is easy to measure. "Revenue per email sent" drives a decision.
• Limit primary metrics to 5–7 maximum. Research on human working memory (Miller's Law) establishes 7±2 as the limit for simultaneously held items.
• Every metric needs a target or comparison: showing $120K revenue is meaningless; showing $120K vs $100K target (120% of goal) is actionable.
• Distinguish leading indicators (metrics that predict future outcomes) from lagging indicators (metrics that confirm past outcomes). Both belong, but they require different positions on the dashboard.
• Vanity metrics (total registered users, total page views) belong off the executive dashboard — they look good but rarely drive decisions.

Visual Hierarchy and Layout Principles

Dashboard layout determines where attention goes. These principles produce dashboards that communicate clearly:

• Top-left priority: The eye reads top-left to bottom-right. Place the most critical metrics in the top-left. Operational details belong at the bottom.
• Consistent colour semantics: Green = good/on track, red = problem/off track, grey = neutral/informational. Do not use colour for decoration.
• Big numbers for primary KPIs: Large typography (48–72px) for the 2–3 most important numbers. Small numbers for supporting context.
• Trend indication: Every KPI needs a trend indicator — not just the current value but whether it is improving or worsening vs the previous period.
• White space is not wasted space: Dense dashboards are harder to read. Generous spacing between components improves comprehension speed.

The Three-Layer Structure

Effective executive dashboards follow a three-layer information architecture:

1. 1Status layer (5-second view): 4–6 primary KPIs with target vs actual and trend. This is what an executive sees on their first glance. Is everything green? If yes, no action required.
2. 2Context layer (30-second view): Supporting charts that explain the KPIs — breakdown by segment, time series, top performers/laggards. Answers "why is the KPI at this value?"
3. 3Drill-down layer (2-minute view): Accessible on click — detailed breakdowns, individual records, raw data exports. Available for investigation but not in the primary view.

Common Mistakes That Kill Dashboard Effectiveness

These are the design decisions that make otherwise well-built dashboards ineffective:

• Too many metrics: Adding a metric "just in case it's useful" dilutes attention from the metrics that actually matter
• No targets: A number without a benchmark is not information — it is trivia
• Inconsistent time periods: Mixing daily, weekly, and monthly metrics on the same view creates comparison confusion
• Real-time data that does not need to be real-time: Constantly-updating numbers distract; daily or weekly refresh is sufficient for most executive metrics
• Metrics defined differently by different stakeholders: "Active users" means something different to product, marketing, and finance — define every metric precisely before building

Implementation Checklist

• Dashboard passes the one-glance test: is on-track/off-track visible in 5 seconds?
• Maximum 7 primary metrics in the status layer
• Every metric has a target or period-over-period comparison
• Leading indicators and lagging indicators are clearly differentiated
• Colour semantics are consistent: green = good, red = problem
• Three-layer structure: status → context → drill-down
• Metric definitions agreed and documented before development starts

Common Mistakes to Avoid

• ✗Building what stakeholders request rather than what the decision-making process requires — these are often not the same
• ✗Designing for data completeness rather than decision support — executive dashboards are not data catalogues
• ✗No iteration with real users after launch — the first version is always wrong; plan for 2–3 rounds of revision based on actual usage
• ✗Building desktop-only when executives review metrics on mobile — responsive layouts matter
• ✗Automating data refresh but not monitoring data quality — a dashboard showing stale or incorrect data is worse than no dashboard

Frequently Asked Questions