How Many KPIs Should Be on a Dashboard?

The right number of KPIs on a dashboard is 5 to 9 — enough to give context, few enough to maintain focus. But the real answer depends on the dashboard's audience, purpose, and layout. Here's how to decide for your specific case.

---

Why This Question Matters

Every KPI you add to a dashboard competes for attention. Add too few and the dashboard feels incomplete — users open another tool to find what's missing. Add too many and the dashboard becomes a wall of numbers where nothing stands out.

The goal isn't to display data. It's to support a decision. The right number of KPIs is the minimum needed for someone to act.

---

The Research: What Works in Practice

Cognitive science gives us a useful anchor. George Miller's research on working memory suggests people can hold 7 ± 2 items in short-term memory at once. Applied to dashboards:

• 3-5 KPIs for executive dashboards (strategic, viewed monthly)
• 5-7 KPIs for management dashboards (tactical, viewed weekly)
• 7-9 KPIs for operational dashboards (detailed, viewed daily)
• 10+ is almost always too many — unless you're designing a monitoring wall, not a decision dashboard

These aren't arbitrary limits. Dashboard usability studies consistently show that comprehension and decision speed drop sharply after 7-9 metrics on a single view.

---

It Depends on Dashboard Type

Executive dashboards: 3-5 KPIs

Executives have the least time and the highest decision stakes. Their dashboard should answer one question: "Are we on track?"

Typical KPI set:

• Revenue (vs. target)
• Profit margin
• Customer count or ARR
• One operational health metric (NPS, churn, utilization)

That's it. Four KPIs, a trend chart, and maybe one drill-down. If an executive dashboard has 12 KPIs, it's a report masquerading as a dashboard.

Management dashboards: 5-7 KPIs

Managers need enough context to identify problems and allocate resources. They typically view dashboards weekly and drill into specific areas.

Example for a Sales Manager:

• Revenue MTD vs target
• Pipeline value
• Win rate
• Average deal size
• New opportunities this week
• Forecast accuracy

Six KPIs — each one linked to a chart below it for context.

Operational dashboards: 7-9 KPIs

Operations teams monitor things in real-time or daily. They need more metrics because they're making frequent, granular decisions.

Example for a Support Operations lead:

• Open tickets
• Average response time
• Resolution rate
• Tickets by priority (P1/P2/P3)
• SLA compliance
• Agent utilization
• Customer satisfaction (CSAT)
• Escalation rate

Eight KPIs — but each one is actionable. If a KPI is "interesting but not actionable," it doesn't belong on an operational dashboard.

---

The KPI Audit: Should This Metric Be Here?

For every KPI on your dashboard, ask these three questions:

1. "What decision does this KPI support?"

If you can't name a specific action someone would take based on this number, remove it. Vanity metrics (total page views, lifetime revenue, headcount) often fail this test unless they're explicitly tied to a goal.

2. "Will anyone notice if I remove it?"

Try this experiment: remove a KPI from the wireframe and show it to your stakeholder. If they don't notice it's missing within 30 seconds, it wasn't important.

3. "Is this a KPI or a detail?"

KPIs belong in the dashboard's hero row — the top section of large, prominent numbers. Details belong in charts, tables, or drill-through pages. If a metric is only relevant when investigating something else, it's a detail, not a KPI.

---

Layout: Where to Put KPIs

The number of KPIs also depends on how much screen space you have. A common layout pattern:

The KPI Row

Most dashboards place KPIs in a horizontal row across the top:

This works well for 3-6 KPIs. Beyond 6, the cards get too narrow on most screens, especially in Power BI's standard canvas size (1280×720).

The KPI Grid

For 7-9 KPIs, use a 2-row grid instead of a single row:

| Row 1: Revenue | Profit | Customers | ARR | | Row 2: Churn | NPS | MRR Growth | CAC |

This keeps each card readable while fitting more metrics above the fold.

The KPI Sidebar

An alternative for operational dashboards: put KPIs in a vertical sidebar on the left, with charts occupying the main area. This works well when KPIs need to be visible while users interact with charts.

---

Antipatterns: When You Have Too Many

The "Kitchen Sink" Dashboard

20+ KPIs on one page. Every stakeholder got their metric included. Nobody can find what they need. Fix: split into multiple pages or tabs, each focused on a specific decision.

The "Traffic Light" Overload

Every KPI has a red/yellow/green indicator, but when 15 metrics all show green, the dashboard communicates nothing. Fix: only use conditional formatting on the 3-4 metrics that genuinely need threshold alerts.

The "One KPI Per Stakeholder" Problem

A dashboard designed by committee where every attendee in the requirements meeting got one KPI added. Fix: force-rank metrics by the decision they support, not by who requested them.

---

The Multi-Page Solution

If your requirements genuinely need 15+ metrics, don't cram them onto one page. Use multiple pages:

• Page 1: Overview — 5 hero KPIs + trend chart (the "are we on track?" page)
• Page 2: Detail — Breakdowns, tables, drill-throughs (the "why?" page)
• Page 3: Operational — Real-time metrics, alerts, queues (the "what do I do next?" page)

This is how real dashboards work in Power BI, Tableau, and Looker Studio. Each page has a clear purpose and an appropriate number of KPIs.

---

How to Decide: A Quick Framework

Use this decision tree:

1. Who is the primary audience?

   • Executive → 3-5 KPIs
   • Manager → 5-7 KPIs
   • Operations → 7-9 KPIs

2. How many pages?

   • Single page → max 7 KPIs
   • Multi-page → up to 9 per page, each page with a clear focus

3. For each KPI, does it pass the 3-question audit?

   • Supports a decision? ✓
   • Would be noticed if removed? ✓
   • KPI-level, not detail-level? ✓

4. Does the wireframe feel scannable in 5 seconds?

   • If yes → you're good
   • If no → cut the lowest-priority KPI and check again

---

Wireframe It First

The easiest way to test whether you have the right number of KPIs is to wireframe the dashboard before building it. Drop KPI cards onto a canvas, add your charts, and see if the layout feels balanced.

With datawirefra.me, you can:

• Drag KPI cards onto the canvas and resize them
• See if 6 cards fit comfortably on one row, or if you need a grid layout
• Share the wireframe with your stakeholder before investing build time

It takes 5 minutes and saves you from the "too many KPIs" conversation during the review cycle.

---

Summary

• 3-5 KPIs for executive dashboards
• 5-7 KPIs for management dashboards
• 7-9 KPIs for operational dashboards
• 10+ means you need multiple pages, not a bigger dashboard

For every KPI, ask: does it support a decision? Would it be noticed if removed? Is it a KPI or a detail?

The sweet spot for most dashboards is 5-7 KPIs — enough context, zero clutter. When in doubt, cut. You can always add a detail page.

Wireframe your KPI layout →