Which metrics belong on a KPI dashboard — and which don't

Which metrics belong on a KPI dashboard — and which don't

A KPI dashboard is a single view of the metrics your team uses to track progress and make decisions. Instead of pulling numbers from different tools or waiting for a weekly report, everyone sees the same data at the same time.

The gap between a dashboard people use and one they ignore is rarely about the tool. It's usually about what's on it. Most teams build dashboards by exporting whatever is easy to get. The more useful approach is to start with one question: what does this team need to decide faster?

What belongs on a KPI dashboard

Before choosing metrics, it helps to be clear on what a KPI actually is. A metric is any number you can measure — page views, tickets opened, hours logged. A KPI is a metric tied to a goal that matters. "Tickets opened today" is a metric. "Tickets resolved within SLA this week" is a KPI, because it tracks something the team is accountable for. Every dashboard should answer one specific question. Write it down before choosing any metric.

A marketing team running a campaign might ask: "Are we going to hit the April 30 deadline across all active campaigns?" That question points to a short list — campaigns on track vs. at risk, subtasks completed vs. total, tasks blocked by another team, high-priority items due this week. We use exactly this setup as an example later in the article, with a real screenshot from Vaiz.

An ops team managing service delivery might ask: "Are we meeting our response commitments?" Their view looks different — tickets resolved this week, average first-response time, SLA breach rate, open tickets by priority.

Four to seven KPIs per view is usually the right range. If a metric is interesting but doesn't change what the team does next, it belongs in a report, not on a dashboard.

Each number also needs a reference point. "340 tickets" tells you almost nothing on its own. Pair it with a target (goal: 300), a trend (up 12% from last week), or a threshold (flag if above 400). Without that context, the number is just noise.

If you're still deciding which outcomes to measure, the OKR template covers how to define objectives and key results before building the view — which often makes the metric choice much clearer.

Dashboard types: match the view to the decision

Not every KPI dashboard is designed for the same audience. The most useful one is always built around the decision it needs to support.

The most common mistake is building one screen for all three uses. A leadership view and a day-to-day execution view need different levels of detail. Combining them usually makes both weaker.

Leading and lagging indicators: balance both

Most teams build dashboards full of lagging indicators — revenue closed, tickets resolved, projects delivered. These tell you what already happened. They're easy to measure but hard to influence in the moment, because the result is already in.

Leading indicators are signals that predict the result before it lands. For a sales team, revenue is lagging; meetings booked and qualified pipeline value are leading. For support, customer churn is lagging; first-response time and tickets reopened are leading. A strong dashboard pairs both — leading indicators to act on, lagging indicators to check whether the work is paying off.

If your dashboard only shows lagging numbers, you're reading the score after the game has ended. Adding two or three leading indicators usually changes how the team uses the view.

How to build a KPI dashboard

• Write the decision first. One sentence: what should people decide faster after looking at this?
• Choose one audience. A single dashboard rarely serves leadership and execution at the same time.
• Pick four to seven metrics, with at least two leading indicators in the mix.
• Pair each metric with a reference point — target, trend, or threshold.
• Sketch the layout before you build. A rough draft shows whether the screen will feel balanced or cluttered.
• Check the data source. If numbers arrive late or in inconsistent formats, the dashboard will lose trust quickly.
• Test with real users. Ask what they would act on first. Strong dashboards improve through small edits after people start using them.

Common mistakes

One screen for every audience. A dashboard built for both leadership and execution usually serves neither well.

The wrong chart for the job. A visual should match the question behind the metric. A chart that takes effort to read slows the dashboard down before the data becomes useful.

Activity over progress. A team can look busy and still be moving in the wrong direction. Track numbers tied to outcomes, not effort.

In most cases, a cluttered dashboard improves faster when something is removed rather than added.

A KPI dashboard in Vaiz, end to end

In Vaiz — a work management platform — you can build a dashboard view directly inside the workspace where your team's work lives. Each task already carries the data the dashboard needs: priority, owner, due date, status, blockers, and subtask progress. The dashboard pulls from those task fields directly, so the numbers stay current without anyone exporting or refreshing anything.

Take a marketing team running a Q2 email campaign. The campaign lives as a task in the Marketing project — with an owner, a deadline, a priority, four subtasks, and a blocker linking it to design work. From those task fields, a KPI dashboard for the campaign manager could pull four cards:

• Campaigns on track vs. at risk — a counter card grouped by priority and due-date health, drawn from the same priority and date fields visible on each task.
• Subtask completion rate by campaign — progress percentage based on subtask status, so the manager can see which campaigns are stalling under the surface.
• Tasks blocked by another team — a list view filtered to tasks with active blockers, like the one on the Q2 email campaign waiting on design.
• High-priority tasks overdue or due this week — a leading indicator that flags problems before they hit the campaign deadline.

Three of these cards reflect the current state of work. The fourth — high-priority tasks due this week — is leading, because it shows where attention is needed before deadlines slip. When someone updates a task's status, priority, or blocker in Vaiz, the dashboard updates immediately. The view never drifts away from what the team is actually doing.

A KPI dashboard earns its place when people check it without being prompted — because it consistently helps them decide what to do next. Start with four metrics and one question. Add a leading indicator or two. Revisit as priorities shift.

If you're building a project-level view rather than a company-wide one, project dashboard examples covers the layouts and what different teams put on them.