Executive Dashboard Layout: 4 Rows, 5 KPIs, 30 Seconds

An executive doesn't want a data exploration tool. They want "are we on track" answered immediately, and then they want the dashboard to get out of the way.

That leaves you about thirty seconds and roughly four rows. Every filter added to an executive view is a small admission that you didn't know which number they came for.

---

What Makes an Executive Dashboard Different

Four constraints separate this audience from every other one you build for:

The failure mode is an executive page built to look like an analyst's workspace. Stephen Few drew that line in Information Dashboard Design: Displaying Data for At-a-Glance Monitoring (opens in a new tab): a dashboard is a display for monitoring at a glance, not a tool for open-ended analysis. The moment your page asks the executive to go looking, you have handed the work back to the person with the least time to do it.

---

KPI Selection: The 3-5 Rule

An executive dashboard should have 3 to 5 KPIs, and I would hold that line hard. (That's the executive tier of the KPI count framework: 3–5 executive, 5–7 management, 7–9 operational.) Each one should map to a strategic question:

Pick three to five from that list, weighted by what the executive is being asked about in the meeting this dashboard feeds. Where a leadership team can't agree on which five matter most, the disagreement is about strategy, and no layout settles it for them.

The "Add One More" Problem

The request to add one more metric arrives on every project. Three answers, in the order I'd try them.

1. Ask which of the current KPIs comes off to make room. That turns an addition into a trade, and the trade is the conversation you wanted anyway.
2. Offer it as a drill-through: the metric appears as detail when they click the KPI it sits under.
3. Put it on a second page, a deep-dive tab they open when the headline number looks wrong.

Adding the sixth card quietly is the expensive option. The sixth sets the precedent, and a page that grows once keeps growing until someone rebuilds it.

---

Layout: The Inverted Pyramid

The headline sits above the fold. Everything below it exists to answer the next question.

Four rows, each one answering the question the row above it raises.

Row 1: KPI Cards (Hero Row)

• 3-5 large KPI cards spanning the full width
• Each card carries the metric name, the current value, a comparison (vs. target or vs. last period), and a trend indicator
• This row answers: "Where do things stand right now?"

Row 2: Primary Trend Chart

• One chart showing the most important metric over time (12 months, 4 quarters, or 52 weeks)
• A line or area chart. Bars make the reader compare values one at a time when the question is about direction
• Include a target line or forecast line for context
• This row answers: "Are we heading in the right direction?"

Row 3: Breakdown or Comparison

• One chart showing where the number came from: revenue by segment, performance by region, pipeline by stage
• A horizontal or vertical bar chart, or a treemap
• This row answers: "Where should we focus?"

Row 4 (optional): Key Actions or Alerts

• A small section highlighting 2-3 items that need executive attention
• "EMEA revenue is 20% below forecast" or "3 enterprise deals closing this week"
• This row answers: "What needs my attention right now?"

Four rows, and all four have to fit above the fold on the screen your audience is running. That last part is a decision rather than a default. Power BI's 1280×720 canvas is a guess about someone else's monitor, and almost nobody checks what resolution their executives have before wondering why people scroll.

---

Chart Types That Work for Executives

Use these:

• KPI cards with a big number and a trend indicator, which is where every executive dashboard starts
• Line charts for movement over time, since executives think in trajectories
• Horizontal bar charts for rankings and comparisons, where the category labels stay readable at any length
• Bullet charts for actual against target, which pack the comparison into less space than a gauge
• Sparklines inside the KPI cards, adding direction without adding a chart

Avoid these:

• Pie charts. The human eye compares lengths far more accurately than angles or areas, which is why data visualization experts consistently recommend bar charts over pie charts (opens in a new tab) for comparison. Use a horizontal bar chart instead.
• Stacked bar charts. Only the bottom segment sits on a shared baseline, so every segment above it gets compared by eye and gets compared badly. Break them into separate bars.
• Scatter plots. They ask for interpretation time that a thirty-second visit doesn't have.
• Heat maps. If you have to explain the chart type, it isn't earning its place on an executive page.
• Gauges. A lot of space for one data point. A KPI card with a target says the same thing and leaves room for the next card.

---

Colors and Formatting

Keep it minimal

• One primary color for data, and blue is the safest default
• Gray for baselines, secondary series, and context
• Red and green kept for conditional alerts: behind target, ahead of target
• No more than three colors on a single page

Color is the last thing I'd spend time on. A good layout answers the headline question before anyone has decided to read properly, and no palette moves that number. When an executive dashboard reads slowly, the cards are in the wrong order or there are too many of them.

Typography

• KPI values should be the largest text on the page
• Metric names sit above them, small and descriptive
• One set of font sizes, so 14pt and 18pt don't end up on two elements doing the same job
• Chart labels in regular weight, without bold or italic

Whitespace

• Executive dashboards need more of it than operational dashboards do
• Each KPI card gets padding and clear separation from its neighbour
• Empty space is doing work on this page. Filling it with decorative elements takes that work away

---

Filters: Less is More

Left: the answer is already on screen. Right: six ways to go looking for it.

Executive dashboards should have zero to two filters, and the shortlist is short:

1. Time period (This quarter, Last quarter, YTD, Last 12 months)
2. Business unit, where the executive oversees more than one

Region filters, product filters and date-range pickers belong on the management and operational views you reach through drill-through. An executive who has to configure a filter before the page tells them anything has been handed a small research project.

Where they do need to switch context, give them named views instead: bookmarks or tabs called "Company Overview", "EMEA View", "Enterprise Segment", with the filters already set. Picking a named view is a choice. Configuring a filter is work.

---

Comparisons: Always Show Context

An executive reading a bare number has to ask someone whether it is good, and the asking is the thing the dashboard was built to prevent. Put the comparison on the card or leave the card off.

Pick one comparison type and hold it across every card. Where one card compares to target and the next compares to last month, the reader has to check the label before they can read the number, and checking labels is the opposite of glancing.

---

Refresh Cadence and Data Currency

Executive dashboards should show when the data was last updated in the header, where it gets read, rather than tucked into a corner.

• Weekly dashboards: "Data through Friday, March 20, 2026"
• Monthly dashboards: "Data through February 2026"
• Real-time dashboards: "Last updated: 5 minutes ago"

An executive who can't tell whether a number is from yesterday or last week will discount it, and a number nobody trusts stops getting opened. A visible timestamp costs one text box.

Refresh schedule:

• Refresh before the regular meeting, so Monday morning for a Monday review
• Set up email or Teams alerts when the refresh completes
• Never show partial-period data without a clear label ("MTD: through March 15")

---

Common Executive Dashboard Mistakes

1. Too many metrics

Scrolling and squinting are two symptoms of the same problem. Cut back to three to five KPIs and put the rest a click away.

2. No comparison context

A number on its own gives the reader nothing to weigh it against. Is $8.2M good? The card can't say, so the executive asks someone, which is the request the dashboard was supposed to replace.

3. Operational detail on an executive view

Order IDs, individual customer names, and hourly data belong on the operational dashboard. Putting them here reads as a page that hasn't chosen its audience.

4. The "everything dashboard"

One page serving the CFO, the CMO and the COO serves none of them, because their KPIs barely overlap. Build separate views, or separate tabs.

5. Visual complexity

Dual-axis charts, secondary Y-axes and logarithmic scales all need a preamble before anyone can use them. Anything that needs a preamble belongs on a page with more time on it.

---

The Executive Dashboard Checklist

Six things to settle before anything gets built:

1. KPI selection confirmed. The stakeholder has approved the three to five metrics.
2. Comparison type agreed. Target, last period, or forecast.
3. Layout matches the inverted pyramid. KPIs, then trend, then breakdown, then alerts.
4. No scrolling required. Everything fits above the fold at the resolution your audience runs.
5. Filter count is 0-2. Time period and business unit, and nothing else.
6. Refresh cadence documented. When and how often the data updates.

Not one of those six is about chart formatting. Get an executive to agree to the list and the build is mostly assembly.

The one I'd fight hardest for is number 5. Every filter you add moves the work of deciding what matters from you, who has thought about it, to the person with the least time to do it.

Sketch the four rows and send the link → (opens in a new tab)