What is a KPI dashboard?
A KPI is a metric someone has agreed to be accountable for. A KPI dashboard is the page where those metrics live: a small set of headline figures, each shown against a target or a previous period, with one or two charts explaining why the figures moved.
That makes it different from an operational dashboard, which shows everything happening right now, and from an exploratory dashboard, where analysts dig. A KPI dashboard answers one question — "are we on track?" — for one audience, and it should take under a minute to read.
A worked example: a regional sales manager’s KPI dashboard shows bookings this month against quota (68% with 9 working days left), win rate this quarter (31% vs 28% last quarter), average deal size, pipeline coverage for next quarter (2.4×), and a bar chart of bookings by rep. Five numbers, one chart, one decision: which reps need help before month end.
Why 5 to 7 KPIs, and how to choose them
A page with 20 tiles is a report, not a KPI dashboard. Nobody can hold 20 numbers in their head, so the eye skips to the one that looks alarming and ignores the rest. Five to seven headline figures is the range that survives contact with a real weekly meeting.
To get from a long list to a short one, run each candidate through three tests:
- Would we change a decision if this number moved 10%? If not, it is context, not a KPI. Keep it on a second page.
- Can we influence it within the review period? A quarterly KPI on a daily dashboard just sits there.
- Is it defined the same way by everyone who will read it? "Revenue" including or excluding refunds and VAT is two different numbers. Write the definition down once and apply it everywhere. Our list of KPIs by department is a good starting point.
A useful pattern is 3 outcome KPIs (revenue, margin, customers) plus 2–4 driver KPIs (conversion, average order value, on-time delivery) that explain them.
Which KPIs belong on which dashboard?
The same business needs different KPI pages for different roles. Building one page for everyone produces a page for no one.
- Owner or CEO: revenue vs plan, gross margin, cash in bank, net customers gained, one number for the biggest current risk (overdue receivables, stock cover, backlog). The executive overview template is built around this set.
- Head of sales: bookings vs quota, pipeline coverage, win rate, sales cycle length, bookings by rep.
- Head of marketing: qualified leads, cost per lead by channel, lead-to-opportunity conversion, marketing-sourced revenue.
- Operations manager: on-time delivery, throughput, quality (defects or returns), cost per unit, utilisation.
- Store or branch manager: sales vs plan for their own site, basket size, conversion, staff hours vs sales, stock-outs.
- Head of support: first response time, resolution time, backlog, satisfaction, tickets per customer.
Build the owner’s page first. It forces the metric definitions everyone else will inherit.
How should a KPI dashboard be laid out?
Readers scan from the top left. Put the single most important figure there, larger than the others, with its comparison directly underneath ("$412k this month · 92% of plan · +8% vs last year"). Then:
- Top row: the 5–7 headline tiles, each with a target or prior-period comparison and a colour only when the number is off target. A tile that is always green is decoration.
- Middle: one trend chart for the most important KPI over the last 12–13 periods, so a bad week is seen in context.
- Bottom: one breakdown — by rep, by store, by product line — sorted with the worst performer visible, because that is where the conversation goes.
- Off the page: everything else, reachable by clicking a tile to see the rows behind it.
Two rules of thumb: if the page needs scrolling on a laptop, it has too much on it; and if a tile has no comparison, readers cannot tell whether to worry. Our dashboard design principles go deeper on layout.
How often should a KPI dashboard refresh?
Match the refresh to the decision, not to what the technology allows. A number that refreshes every minute but is reviewed every month invites people to react to noise.
- Live or hourly: daily trading, orders, support queue, plant output — anything where someone acts today.
- Daily overnight: most sales and marketing KPIs. Yesterday’s figures, ready before the 9am stand-up.
- Weekly or monthly: margin, cash, churn, headcount — figures that only settle after a period closes.
Whatever the cadence, show it. "Updated 06:40 today" on the page prevents the question "is this current?" from being asked in every meeting. Connecting live to the source system makes this automatic; importing on a schedule works just as well when the source is a spreadsheet or an app.
How do you get people to actually read it?
The best KPI dashboard in the company is still unread if it depends on people remembering to open a browser tab. Delivery matters as much as design.
- Send it, don’t host it. Schedule the page as a PDF or image to arrive by email, Slack, WhatsApp or Telegram at a fixed time — Monday 07:00 for the weekly review, the first working day of the month for the monthly pack.
- Send it to the meeting, not the person. If the Monday sales meeting starts at 09:00, the report lands at 08:30 and the meeting runs from it. Dashboards read in meetings get maintained; dashboards read alone get forgotten.
- One page per audience. A rep gets their own figures; the manager gets the team. With row-level permissions applied to the schedule, that is one dashboard and one schedule, not ten.
- Keep the link. The delivered snapshot says "open live" for anyone who wants to click into a number.
See scheduled reports for how delivery works in Klayara.
The mistakes that stop KPI dashboards being used
- Too many numbers. The most common failure. Cut to 7 and put the rest on a second page.
- No target or comparison. A number on its own is a fact, not a signal.
- Vanity KPIs. Page views, followers, leads with no revenue attached. If it only ever goes up, it is not a KPI.
- Different definitions. Finance and sales each bring "revenue" and spend the meeting reconciling. Define it once.
- Built by someone who never reads it. Have the actual audience use it for two weeks before calling it done.
- Never retired. Review the KPI set each quarter. If a number has not changed a decision in three months, remove it.
In Klayara, a KPI is defined once as a formula and reused in every tile, chart, scheduled report and AI answer, so the number on the Monday PDF is the number on the dashboard. Start from the executive overview template, or ask our BI developers to build the first page for you.