Why Isn't My KPI Dashboard Improving Performance?

A scoreboard is there so you can have a conversation

If you remember nothing else, remember this: A scoreboard is there so that you can have a conversation. It looks like a spreadsheet. But it is not really a spreadsheet. Not only a spreadsheet. Its value is in helping managers ask: What is happening? What pattern can we see? What deserves attention?

What do we think is causing it? What should we do next? Who owns that? By when? And did our action make any difference? That is where the value sits. Numbers by themselves don't change businesses. People do.

Stop collecting numbers just because you can

Modern businesses can produce staggering amounts of data. Power BI. Xero. CRMs. Operational systems. Spreadsheets. Your accounting software may offer you 400 reports. Wonderful. I don't want 400 reports. I want to know: What are the handful of measures that tell this team whether it is winning?

That is a much better question. If your dashboard contains 57 measures, I am not entirely convinced you have a dashboard. You may have a data dump. Because if everything is important, nothing is particularly important.

Start with what matters

Imagine a sporting scoreboard. It tells you the score. Perhaps time remaining. Perhaps a few other important indicators. It does not tell you how many light bulbs were used in the stadium this quarter. Businesses should apply similar discipline.

What genuinely tells this team whether it is performing? The answer will differ depending on the audience. The leadership team needs one view. Sales may need another. Operations another. A store manager another.

The purpose is not to create one giant spreadsheet containing everything anybody might ever want to know. It is to make the few measures that matter to this team visible enough to manage. Can the people looking at the KPI actually influence it? This is another question businesses often overlook.

There is not much value in holding people accountable for a measure they have virtually no ability to influence. A useful KPI connects what people do with the outcome the business is trying to create. Take revenue. Revenue matters. But revenue is an outcome.

It is the result of lots of things happening. If revenue rises, ask: Why? More customers? Existing customers buying more? Price increases? Better conversion? One unusually large job? And what happened to margin? One number rarely tells the whole story. The useful management work happens when we understand the drivers beneath the headline.

The number tells you where to think

I once looked at retail performance where revenue was running significantly ahead of budget. Easy response: Fantastic. Green. Nothing to see here. Except conversion was improving while average transaction value was moving the other way. Now we have a conversation. Why is the average basket falling?

Are we discounting? Are we missing opportunities? Are we attracting different customers? Is margin quietly leaking while everyone celebrates the headline revenue number? That is the point. The number doesn't tell you what to think. It tells you where to think.

Get curious before you get judgmental

A red number is not automatically evidence that somebody is doing a bad job. And a green number does not automatically mean everything is wonderful. The number is a clue. Get curious. Suppose customer complaints double. Do not immediately begin with: "Who is responsible for this?"

First ask: What kinds of complaints? From which customers? About what? When did the change begin? Is it concentrated in one location? One product? One person? One process? Or have we simply become better at recording complaints? That is possible too. The measure has done its job.

It has directed your attention towards something worth investigating.

Managers should bring thinking, not explanations

This is where a good dashboard can help develop better managers. If a number has moved, I don't want somebody arriving at the weekly meeting with nothing but an excuse. I want thinking. Ask: What did you notice? What do you think is driving it? What evidence do you have? What have you already tried?

What do you recommend we do next? Now the dashboard is doing more than measuring performance. It is developing management capability. The manager is learning to interpret evidence, identify causes, think through options and recommend action.

That is far more valuable than simply colouring a cell red.

Move from anecdotes to evidence

Without useful measures, management conversations often sound like this: "Customers seem pretty happy." "The team seems better." "Communication has improved." "Everybody's really busy." "We've had a few issues." Maybe. But what does the evidence say?

If you think a site is improving, what would you expect to see? Fewer paperwork errors? Better equipment care? Fewer complaints? Faster turnaround? Better communication? Less rework? Can we actually see the difference? Because when we can see it, we can discuss it.

And when we can discuss it, we can make a better decision about what happens next. That is stronger than: "I reckon things are going okay."

Look for patterns, not isolated events

One bad week does not necessarily mean crisis. One brilliant week does not necessarily mean you have cracked the code. Look for patterns. Is the number moving consistently? Is the gap growing? Is the same issue appearing again and again? Did something change at a particular point?

What else happened at the same time? This is where good data people can be enormously useful. I sometimes describe the finance role as the chief pattern display officer. Their job is not necessarily to fix everything the data reveals. Their job may be to help everybody else see the pattern.

Here's what's happening. Here's where it started. Here's how often. Here's where it's concentrated. Here's what's changed. Then the manager who owns that area can respond. The person producing the dashboard does not necessarily own the performance This is an important distinction.

Finance prepares the dashboard. That does not mean Finance owns every red number. Administration collects the data. That does not mean Administration must solve every operational problem it reveals. The dashboard informs. People perform. The relevant leader owns the response.

Otherwise businesses accidentally turn their finance or reporting team into the people responsible for everybody else's performance. That's backwards.

Put the scoreboard at the beginning of the weekly meeting

This is one reason I put the scoreboard near the beginning of a good weekly accountability meeting. In sport, imagine having a team talk without anybody knowing the score. Ridiculous. But businesses do the equivalent all the time. Start with: Where are we winning? Where are we off track?

What's changed? What deserves attention? Then move beyond the number. Suppose picking errors have increased for three weeks. Fine. What are we going to do? Who owns it? By when? What would we expect to see if the action works? Now you have closed the loop.

Close the loop

This is the crucial part. A useful performance-management loop looks something like: See the pattern. Build the evidence. Have the conversation. Decide what to do. Clarify ownership. Record the action. Follow up. See whether it worked. Then repeat.

Without that loop, you can have the same fascinating conversation about the same red KPI for six months. "Conversion is still down." Really? What did we do about it? That's the question.

A red dashboard is not accountability

This point is worth making very clearly. A dashboard going red is not accountability. It is just a dashboard going red. Accountability is what happens next. Do we discuss it? Do we understand why? Do we agree what needs to change? Does somebody commit to doing something? By when?

Do we write it down? Do we come back to it? Did they do what they said they would do? Did it make any difference? That is accountability. The colour is merely the signal.

Don't weaponise the dashboard

There is another danger. If every red number results in somebody being attacked, guess what people become very good at? Explaining the number. Arguing that the measure is unfair. Hiding the problem. Changing the definition. Manipulating the data. A scoreboard should support accountability.

But accountability and blame are not the same thing. I want people able to say: "This isn't where it needs to be." without immediately needing to defend their existence. Once we agree the measure matters, a miss is useful information. Now ask: What happened? What's within our control?

What isn't? What are we going to do? Where do you need support? When will we review it? That is a productive management conversation. But don't make red meaningless either The opposite mistake is becoming so understanding that a red measure stays red forever. Same miss. Same explanation.

Same action not completed. Week after week. At some point, that stops being a dashboard issue. It becomes an accountability issue. Then ask: Is this the right measure? Is the standard realistic? Does the person understand it? Do they know what to do? Do they have the authority?

Do they have the capability? Have they been supported? Or are we simply tolerating something we repeatedly say matters? The dashboard helps make that visible.

Evidence beats memory

Without data, managers say: "I feel like we've talked about this a lot." With evidence: "Here are the last eight weeks. Here is what happened. Here is what we agreed. Here is the result." That is a much calmer conversation. Patterns are visible. Memory becomes less important. And difficult performance conversations become less about opinion.

Let the team see the score

Imagine playing sport where only the coach knows the score. Every now and then the coach runs onto the field and shouts: "Try harder!" At what? What's the score? Where are we losing? How much time is left? What needs to change?

People perform better when they understand what winning looks like. Where appropriate, let the team see the score. Not as some enormous surveillance mechanism. As useful feedback. This is where we are. This is where we are trying to get to. This is the gap. What do we think? What can we influence?

What are we going to do? Something interesting happens when teams become used to this. The boss stops being the only person who notices. Someone else says: "Hang on, that's been falling for three weeks." Or: "Since we changed that process, errors have halved." Or:

"We keep missing this. What's really going on?" Now the team is thinking about performance rather than waiting for the boss to pronounce whether they are doing well.

Your spreadsheet is not the management system

If you already have a beautiful dashboard, good. But ask: Who looks at it? When? What conversations does it trigger? What patterns are you looking for? Who owns each important measure? What happens when something changes? What decisions come from it? Where are those actions recorded?

Do you come back to see whether they worked? That is the management system. The spreadsheet simply makes the evidence visible.

A simple dashboard management rhythm

Try this.

1. Choose the measures that matter

Not everything you can measure. The handful that tell the team whether it is winning.

2. Make them visible

Create a simple scoreboard.

3. Review them regularly

Ideally as part of the weekly management rhythm.

4. Look for patterns

Don't overreact to every isolated movement.

5. Get curious

What is driving the result?

6. Ask the owner for their thinking

What have they noticed? What evidence do they have? What do they recommend?

7. Agree the action

Who will do what? By when? What should change if the action works?

8. Record it

Do not rely on memory.