Design a KPI Dashboard Layout for Executive Business Reporting
Design an executive KPI dashboard with metric selection, visual layout, color coding, and BI tool recommendations.
π The Prompt
Act as a business intelligence consultant specializing in executive dashboard design. Design a comprehensive KPI dashboard for [COMPANY NAME], a [BUSINESS TYPE, e.g., D2C e-commerce brand, B2B SaaS company, logistics provider] with approximately [REVENUE RANGE] in annual revenue.
The dashboard will be used by [PRIMARY AUDIENCE, e.g., C-suite, department heads, board of directors] for [FREQUENCY, e.g., daily, weekly, monthly] review meetings.
Step 1 β KPI Selection: Identify the 12-15 most critical KPIs organized into these categories:
- Financial Health (e.g., revenue, margins, cash runway)
- Customer Metrics (e.g., acquisition, retention, satisfaction)
- Operational Efficiency (e.g., cycle times, utilization, error rates)
- Growth Indicators (e.g., pipeline, expansion, market share)
For each KPI, specify: definition, formula, data source, update frequency, and a meaningful benchmark or target.
Step 2 β Dashboard Layout: Propose a visual layout with:
- A top-level summary row with 4-5 "hero" metrics and trend indicators
- Mid-section with 3-4 interactive charts (specify chart type and why it fits)
- Bottom section with a detailed data table and drill-down capability
- Alert/exception section highlighting metrics outside [THRESHOLD, e.g., Β±10%] of target
Step 3 β Design Principles: Apply these best practices:
- Information hierarchy (what the eye should see first)
- Color coding strategy (green/yellow/red thresholds for each KPI)
- Recommended time comparisons (MoM, QoQ, YoY)
- Mobile responsiveness considerations
Step 4 β Implementation Recommendations:
- Suggest 2-3 BI tools best suited for this use case (e.g., Tableau, Looker, Power BI) with rationale
- Data refresh architecture recommendations
- Access control and sharing strategy
End with a list of 5 common dashboard anti-patterns to avoid and how this design prevents each one.
π‘ Tips for Better Results
Limit hero metrics to 5 or fewerβcognitive overload kills dashboard adoption. Always include trend context (e.g., vs. last period, vs. target) alongside raw numbers so executives can interpret at a glance. Test the dashboard with actual users in a 5-minute walkthrough before finalizing.
π― Use Cases
Operations managers, BI analysts, and executives building or redesigning dashboards to track company performance and drive data-informed decisions.