Executive Dashboard Planning Guide

What leaders actually need

Executive dashboards fail when they're designed by data teams for data teams. The CEO doesn't need to see how many tickets were closed or how many rows were processed. They need to see whether the business is healthy, growing, and on track.

The purpose of an executive dashboard is to answer three questions:

1. Are we on track? (against targets and plan)
2. Where do I need to pay attention? (problems and opportunities)
3. What's changed? (trends and anomalies)

The three layers of an executive dashboard

Layer 1: Headline status (what the CEO sees first). Three to five top-level metrics, each with a clear red/amber/green status. Revenue, pipeline, customer health, cash position, growth rate. This fits in the top third of the screen.

Layer 2: Supporting context (what explains the headlines). Trends, comparisons, and breakdowns that add context. Revenue by segment, pipeline by stage, customer satisfaction trend. This fills the middle section.

Layer 3: Drill-down (what answers "why?"). Click on any metric to see the detail behind it. Not visible on the main screen but accessible with one click. This is where operational data lives.

Choosing executive metrics

The right metrics depend on your business model, but most executive dashboards need some version of:

• Revenue metric: Revenue, MRR, bookings — whatever measures income for your business model
• Growth metric: Month-over-month or year-over-year growth rate
• Pipeline/forecast metric: What's coming? Are targets achievable?
• Customer health metric: Churn, NPS, renewal rate — are customers staying?
• Financial health metric: Cash position, runway, profitability

That's five metrics. Resist the urge to add more. If the leadership team needs specific operational metrics, those belong on department dashboards, not the executive one.

Design principles

• Targets on every metric: A number without a target is meaningless. "$1.2M revenue" means nothing. "$1.2M / $1.5M target" tells a story.
• Trend lines, not just numbers: Is this number going up or down? How does it compare to last quarter?
• Colour for status only: Green = on track. Amber = attention needed. Red = problem. Don't use colour decoratively.
• Mobile-friendly: Executives check dashboards from their phones. Design for small screens too.
• Commentary space: Some dashboards include a brief text note explaining the current state. "Revenue below target due to delayed Project X — expected to close by month end."

Data and refresh considerations

• Refresh frequency: Daily is sufficient for most executive dashboards. Real-time adds complexity without adding value at this level.
• Data quality: Executives lose trust fast when numbers don't match other reports. Ensure the dashboard uses the same data sources as financial reporting.
• Historical comparison: Show current period vs same period last year. Seasonality matters.
• Consistent definitions: "Revenue" means the same thing on the dashboard as in the board report. Define and document metric calculations.

Common mistakes