KPI Dashboard Examples: The One-Page View Your Board Can Follow

The KPI dashboard examples worth copying share one trait: someone can read them in two minutes and know which two things need attention. Below are working examples for three audiences (the board, the leadership team and each department), the line that connects them back to the strategy, what to leave off, and how often each one should refresh.

Most dashboards fail for the opposite reason to the one people expect. They are not short of data. They carry so much of it that the reader has to do the analysis, and a board member reading a forty-tile dashboard the night before a meeting will not.

What a KPI dashboard is for

A KPI dashboard answers three questions, in this order:

1. Are we on track against what we said we would deliver?
2. Where are we not, and is it getting better or worse?
3. Who owns each number?

Anything that does not help answer one of those belongs somewhere else: an appendix, an analyst's workbook, a team's own tracker. A dashboard is a decision aid, not an archive.

The line from strategy to every number

Before the examples, the structure they all hang from. A dashboard is only as good as the line behind it:

STRATEGY       Grow recurring revenue from existing clients
                 |
ORGANIZATION   Recurring revenue · Client retention · Gross margin · On-time delivery
KPIs             |
DEPARTMENT     Sales: expansion revenue, renewal pipeline
KPIs           Client services: 90-day retention, value reviews held
               Operations: on-time delivery, cost per delivery
               Finance: gross margin, days sales outstanding

Every number on a department dashboard should name the organization KPI it serves, and every organization KPI should name the strategic priority behind it. If you cannot draw that line, the problem is upstream of the dashboard: the KPIs themselves need work. The method for building them is in how to create KPIs, and a strategy map is a good way to draw the line as a picture before you build the table.

The examples below use one fictional company throughout: a 240-person distribution business whose strategy is to grow recurring revenue from existing clients. All figures are illustrative.

KPI dashboard example 1: the board view

The board sees the organization KPIs and nothing below them, on one page, in the same format every quarter.

Below the table, two lines, no more:

Needs the board's attention: retention fell a point this quarter after two contract losses in the northern region. The recovery plan is on page 3.

Decision requested: approve the second regional account manager (budget on page 4).

Why it works: five rows, a baseline and a target for each, one named owner, and a trend column, so the board can see direction as well as position. The status column is a judgment, so keep the rules for it written down ("At risk" means the owner does not expect to hit the year-end target on the current course).

This page is the "numbers" and "against the plan" sections of a board pack. For how it sits alongside the narrative, the decisions and the risks, use the board report template.

KPI dashboard example 2: the leadership team view

The leadership team needs the same organization KPIs plus the early signals that predict them, so it can act before the board numbers move. It refreshes monthly.

The left half is what happened. The right half is what is likely to happen next. When a leading indicator is well short of target, the lagging KPI will follow in a quarter or two, which is exactly the warning the leadership team needs and the board does not. The difference between the two kinds of measure, and how to set targets for each, is covered in leading and lagging indicators.

KPI dashboard example 3: department views

Each department gets three to five KPIs that translate the organization's into its own work, and each row says which organization KPI it serves. These refresh weekly.

Client services

Operations

Sales

Three things to notice. Nobody's department dashboard says "recurring revenue" except the people who can move it directly. Operations carries a margin KPI because cost per delivery is something only Operations controls. And two departments serve the same organization KPI (retention) with different measures, which is the translation working as it should.

The one-page test

Before you ship any of these, put the dashboard in front of someone who did not build it and ask three questions. Which number is most worrying? Who owns it? What is being done about it? If they cannot answer in two minutes, the dashboard is not done.

What to leave off

• Numbers with no target. A figure without a baseline and target forces the reader to guess what good looks like.
• Activity counts presented as results. Emails sent, meetings held, tickets touched. They can be useful leading indicators on a department view; they do not belong on the board's page.
• Department KPIs on the board view. Boards that see department detail start managing departments. Keep that one level down and offer it in an appendix.
• Gauges, dials and colors that mean different things on different rows. A plain table with a status word is faster to read than twelve speedometers.
• Anything nobody owns. If a number has no single owner, either assign one or remove it.
• Last year's KPIs that no longer serve this year's strategy. Retire them openly rather than letting them linger at the bottom of the page.

How often to refresh each view

A dashboard that refreshes more slowly than decisions are made is a history book. One that refreshes much faster than anyone looks at it is noise. Match the rhythm to the meeting that uses it.

Board reporting: where the dashboard fits

The board view is the spine of board reporting, not the whole of it. A good pack wraps it with a short headline, the decisions the board is being asked to make, and the risks to watch. The dashboard keeps the pack comparable from quarter to quarter: same rows, same order, same definitions, so directors can see trajectory without re-learning the layout.

The hardest part is rarely the dashboard itself. It is agreeing the five organization KPIs and the department KPIs beneath them, each with an owner and a baseline. Once those exist, the dashboard is mostly a matter of filling in the table.

Frequently asked questions

What should a KPI dashboard include?

Each KPI with its baseline, target, current value, trend and a single named owner, plus a short note on what needs attention. The board view should show only the organization's KPIs; department views show each department's three to five, each tied to the organization KPI it serves.

How many KPIs should a board dashboard have?

Usually five to seven. Enough to cover the strategic priorities and the basics such as cash, but few enough to fit on one page and be read in a couple of minutes. If the board needs more detail, put it in an appendix.

How often should a KPI dashboard be updated?

Match it to the meeting that uses it: quarterly for the board, monthly for the leadership team, weekly for departments. The underlying data can update more often, but the reviewed version should follow the decision rhythm.

What is the difference between a KPI dashboard and a board report?

A KPI dashboard is the numbers: each KPI against its target, with trend and owner. A board report wraps the dashboard with a headline, the decisions the board is asked to make, the risks and an appendix. The dashboard is one section of the report.

Should the board see department KPIs?

Not on the main page. The board's job is to judge whether the organization is on track and to make a few decisions; department detail pulls it toward managing operations. Keep department dashboards available in an appendix for directors who want them.