How Many KPIs on a Dashboard? The 3-Question Audit
3–5 for executive, 5–7 for management, 7–9 for operational. The harder question is which ones. Here's the 3-question audit that cuts the rest.
Gabriel ThieryThe right number of KPIs depends on who the dashboard is for: 3–5 for executive dashboards, 5–7 for management dashboards, 7–9 for operational dashboards. More than 9 on a single view almost always means a second page, not a bigger canvas.
The count is the easy half. Which ones is the hard half, and my test for that is blunt: a KPI card without a comparison is just a number. If it doesn't show period-over-period or year-over-year, it tells the reader where they are without telling them whether that's good, and they have to go somewhere else to find out. That's the moment the dashboard failed.
The card on the left tells you where you are. Only the one on the right tells you whether that's good.
Why This Question Matters
Every KPI you add competes for attention with the ones already on the page. Add too few and your reader opens a second tool to find what you left out. Add too many and they scan a wall of numbers without landing on any of them.
A dashboard exists to support a decision. The right number of KPIs is the smallest set that lets someone act on it, and that set is smaller than the list you were handed in the requirements meeting.
The Research: What Works in Practice
The number most often quoted here is George Miller's 7 ± 2, from his 1956 paper "The Magical Number Seven, Plus or Minus Two" (opens in a new tab). Most articles that cite it skip the caveat. Miller measured how many items people hold in working memory, not how many they can scan on a screen. You scan a dashboard rather than memorise it, so 7 ± 2 anchors the range without setting it.
Attention competition does more of the work. Nielsen Norman Group's eye-tracking research (opens in a new tab) shows readers move across a screen in predictable patterns and skip most of what sits on it. Each card you add takes attention from the cards beside it, and that trade is what sets the ranges:
- 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+ belongs on a monitoring wall rather than a decision dashboard
I apply the same ranges in executive dashboard design and across the layout patterns that structure them.
It Depends on Dashboard Type
The same question has three answers. Which one applies depends on who is reading.
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)
Four KPIs, a trend chart, and at most one drill-down. Put 12 KPIs on that page and you have built a report and hung it on a dashboard.
That is also why the executive end of the range is tight: a filter on that view asks the reader to do work the page was built to do for them.
Management dashboards: 5-7 KPIs
Managers need enough context to spot a problem and move resources at it. They open the dashboard weekly and drill into one area at a time.
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 sitting above the chart that explains it.
Operational dashboards: 7-9 KPIs
Operations teams watch the same board through the day. They carry more metrics because they make more decisions, each one smaller than the one an executive makes once a month.
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, and someone can act on each one. A card that is interesting to look at but never changes what the team does belongs in a chart further down the page.
The KPI Audit: Should This Metric Be Here?
Three questions, asked of every card on the page.
1. "What decision does this KPI support?"
Name the action someone takes when this number moves. If you can't, cut the card. Total page views, lifetime revenue and headcount usually fail here, because they move without anyone changing what they do next.
2. "Will anyone notice if I remove it?"
Take the card out of the wireframe and show the page to the person who asked for it. If they read the whole thing without asking where it went, the card was decoration.
3. "Is this a KPI or a detail?"
KPIs go in the hero row at the top of the page, at a size you can read from across a meeting room. Details go in charts, tables and drill-through pages. A metric you only reach for while investigating something else is a detail.
Layout: Where to Put KPIs
Screen width caps the count as hard as the audience does. Three arrangements cover most dashboards.
The KPI Row
Most dashboards place KPIs in a horizontal row across the top:
| Revenue MTD | Deals Closed | Win Rate | Avg Deal Size | Pipeline |
|---|---|---|---|---|
| $1.2M | 47 | 32% | $25K | $4.8M |
A row holds three to six cards. Past six they narrow until the labels start wrapping, and Power BI's default 1280×720 canvas hits that wall before a wider one does.
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 |
Each card keeps its width, and nine of them still land above the fold.
The KPI Sidebar
Operational dashboards can run the cards down a left sidebar and give the main area to the charts. The numbers stay on screen while someone filters and drills through the charts beside them.
Antipatterns: When You Have Too Many
The "Kitchen Sink" Dashboard
Twenty or more KPIs on one page, because everyone in the requirements meeting got their metric in. Afterwards nobody can find theirs. Split the page into tabs and give each tab one decision.
The "Traffic Light" Overload
Red, amber and green on every card. Fifteen greens read as wallpaper, and the one amber you needed to catch disappears into them. Keep conditional formatting on the three or four metrics that have a threshold somebody acts on.
The "One KPI Per Stakeholder" Problem
The requirements meeting ran as a round of turns, and each attendee left one metric behind. Rank the list by the decision each metric supports, then cut from the bottom.
The Multi-Page Solution
When the requirements need 15 or more metrics, spread them across pages instead of shrinking the cards:
- Page 1, overview. Five hero KPIs and a trend chart, answering "are we on track?"
- Page 2, detail. Breakdowns, tables and drill-throughs, for the "why?"
- Page 3, operational. Live metrics, alerts and queues: what do I do next.
Power BI, Tableau and Looker Studio all page this way. Each page then gets its own KPI count rather than a share of one.
How to Decide: A Quick Framework
Use this decision tree:
-
Who is the primary audience?
- Executive → 3-5 KPIs
- Manager → 5-7 KPIs
- Operations → 7-9 KPIs
-
How many pages?
- Single page → max 7 KPIs
- Multi-page → up to 9 per page, each page with a clear focus
-
For each KPI, does it pass the 3-question audit?
- Supports a decision? ✓
- Would be noticed if removed? ✓
- KPI-level, not detail-level? ✓
-
Does the wireframe scan in 5 seconds?
- If yes → you're good
- If no → cut the lowest-priority KPI and check again
Where the Count Goes Wrong in Practice
Six KPIs look reasonable in a requirements doc and cramped on a 1280-wide canvas. The number that works is the number that still works at the width you are building for, and you cannot settle that in a spreadsheet.
Lay the cards out at real size and you find out in a minute whether six fit across one row or push you into a grid, and whether the sixth card was ever worth the width it takes from the first.
Lay out your KPI row → (opens in a new tab)
What to Cut First
- 3-5 KPIs for executive dashboards
- 5-7 KPIs for management dashboards
- 7-9 KPIs for operational dashboards
- 10+ means another page rather than a bigger dashboard
When you are over the range, cut the cards with no comparison before you cut anything else. A bare number is the card doing the least work on the page, and it is usually there because someone asked to see a metric rather than act on it.
Frequently asked questions
How many KPIs should be on a dashboard?
It depends on the audience: 3–5 KPIs for executive dashboards, 5–7 for management dashboards, and 7–9 for operational dashboards. More than 9 on a single view almost always means you need a second page rather than a bigger canvas.
How many KPIs should an executive dashboard have?
3 to 5. Executives have the least time and the highest decision stakes, so their dashboard should answer one question — 'are we on track?' — at a glance. If an executive dashboard has 12 KPIs, it's a report masquerading as a dashboard.
What happens if a dashboard has too many KPIs?
Comprehension and decision speed drop sharply once a view exceeds 7–9 metrics. Every KPI competes for attention, so adding more dilutes the ones that matter. The fix is to split into multiple focused pages or tabs, each tied to a specific decision, rather than cramming everything onto one screen.
Gabriel Thiery
Builder of datawirefra.me. I help BI teams plan dashboards people actually use — before they write a single DAX formula.
Connect on LinkedIn