When a KPI Misses Its Target: What Should You Do Next?

Your KPI is red.

Someone asks, “What are we going to do about it?” Before you launch a project, stop.

A missed KPI target is a signal—not a solution. The number tells you that performance isn’t where you want it to be. It doesn’t automatically tell you why performance changed, whether the change is meaningful, or what action will actually improve the result.

That distinction matters. Effective KPI management isn’t just about tracking numbers. It’s about turning performance information into better decisions—and connecting those decisions to meaningful improvement.

A useful process is:

Check → Understand → Decide → Act → Verify

Here’s how to use it.

1. First, Check: Is the KPI Miss Real?

When a KPI falls below target, the first instinct is often to investigate the process.

But first, check the measurement itself.

Ask:

• Is the data accurate?
• Was the metric calculated consistently?
• Did the reporting method change?
• Is there missing or delayed data?
• Was there a one-time event?
• Is the result simply normal process variation?

This last question is particularly important.

A KPI can move in the wrong direction without anything fundamentally changing in the process.

Don’t confuse variation with a problem

Every process has variation.

If you’re tracking cycle time, defects, customer complaints, production output, or another operational KPI, individual data points will naturally move up and down.

That doesn’t necessarily mean the process has improved—or deteriorated.

Statistical Control Charts help distinguish normal variation from signals that may warrant investigation. Control charts use statistical limits to identify unusual patterns and potential special-cause variation.

The question isn’t simply:

“Did the number change?”

It’s:

“Did something meaningful change in the process?”

That difference can prevent teams from launching improvement projects to solve problems that don’t actually exist.

2. Check Whether the Target Still Makes Sense

Suppose the data is accurate and the KPI really has moved.

The next question is:

Is the target still appropriate?

Targets aren’t permanent.

Business conditions change. Customer expectations change. Processes change. Strategies change.

A target established two years ago may no longer reflect what the organization needs today.

Ask:

• Has the business strategy changed?
• Has customer demand changed?
• Has the process changed?
• Have external conditions changed?
• Was the original target based on an assumption that is no longer valid?
• Does the target still support the organization’s current goals?

This is an important part of KPI tracking and management.

A KPI needs context. As KPI Fire explains, performance should be considered in relation to its target, previous performance, and strategic goals—not simply viewed as an isolated number.

In other words:

You can measure a KPI perfectly and still be measuring against the wrong target.

3. Determine Whether You Have a Performance Gap

Now assume:

• the data is accurate,
• the change is real, and
• the target is still relevant.

You may have a genuine performance gap.

But there’s still an important distinction to make.

One bad result isn’t necessarily a systemic problem.

Consider two scenarios.

Scenario A:

A delivery KPI misses its target once after an unexpected supplier disruption.

Scenario B:

The same KPI has missed its target for six consecutive reporting periods.

Both are red.

But they probably shouldn’t trigger the same response.

The first might require monitoring or a short-term corrective action.

The second deserves deeper investigation.

This is where KPI management needs to move beyond status reporting and into problem solving.

Instead of asking only:

“Why is this KPI red?”

ask:

“What pattern are we seeing, and what does the data tell us about the problem?”

4. Find the Cause Before Choosing the Solution

This is where many improvement efforts go wrong.

A team sees a KPI miss and immediately proposes a solution.

“Our defect rate is too high. Let’s retrain everyone.”

“Customer response time is too slow. Let’s hire more people.”

“Production is behind target. Let’s add overtime.”

Those might be appropriate solutions.

But they might not.

The KPI tells you what happened. It doesn’t necessarily tell you why it happened.

A better sequence is:

Metric → Problem → Cause → Improvement Opportunity

Start with the problem

Be specific.

Instead of:

“Quality is bad.”

Try:

“First-pass yield has fallen from 94% to 87% over the past eight weeks.”

Now you have something you can investigate.

Then ask what is driving the result

This is where root-cause analysis becomes valuable.

KPI Fire’s 5 Whys Root Cause Analysis provides a simple way to move beyond symptoms and investigate the underlying cause of a problem.

You can also use tools such as:

• 5 Whys
• Fishbone diagrams
• Pareto analysis
• Process mapping
• Value stream mapping
• Statistical analysis

The goal isn’t to find someone to blame.

The goal is to find something you can improve.

5. Look Beyond the KPI: What Drives the Result?

A useful way to think about KPI problems is:

What inputs or conditions are driving this outcome?

This is the idea behind the Lean Six Sigma concept y = f(x).

The output (Y) is influenced by a set of inputs (X).

KPI Fire’s article on y = f(x) explores this relationship and how identifying the critical Xs can help teams move from reacting to problems toward understanding what actually drives performance.

For example:

Y = Customer complaints

Potential Xs could include:

• Product defects
• Shipping errors
• Response time
• Order accuracy
• Training
• Process adherence

Instead of simply saying:

“Complaints are too high.”

you can start asking:

“Which factors are contributing most to the increase?”

That gives the team something much more useful: a potential improvement opportunity.

6. Decide: Does This KPI Miss Actually Require a Project?

Here’s the decision many organizations skip.

Not every KPI miss requires an improvement project.

Sometimes the appropriate response is simply to monitor the metric.

Other times you need a corrective action.

And sometimes you have a systemic problem that warrants a structured improvement initiative.

A simple decision framework looks like this:

This is an important principle for continuous improvement:

Don’t create a project just because a number turned red.

Create a project when there is a meaningful problem, a credible improvement opportunity, and enough potential value to justify the effort.

7. Prioritize the Improvement Opportunity

Suppose your investigation reveals five possible improvement opportunities.

You probably don’t have the resources to tackle all five at once.

So now the question changes from:

“What could we improve?”

to:

“What should we improve first?”

This is where prioritization matters.

Consider:

• Potential impact
• Required effort
• Strategic alignment
• Risk
• Expected benefits
• Available resources
• Urgency

KPI Fire’s Idea Prioritization content recommends evaluating improvement ideas using factors such as expected outcomes, effort, and impact before allocating resources.

The Idea Funnel provides another useful framework for moving improvement ideas from submission through prioritization and into active projects. KPI Fire’s approach includes evaluating effort, impact, risk, strategic alignment, and expected benefit.

The principle is simple:

Don’t chase every problem. Focus improvement resources where they can create meaningful results.

8. Connect the Improvement Project to the KPI

Once you’ve decided that a project is warranted, make the connection explicit.

Ask:

Which KPI is this project supposed to improve?

For example:

Goal

Improve operational reliability.

KPI

Unplanned equipment downtime.

Performance gap

Downtime is 18% above target.

Root cause

Recurring failures caused by inconsistent preventive maintenance.

Improvement project

Standardize preventive maintenance scheduling and operator inspections.

Expected result

Reduce unplanned downtime by 20%.

Now there’s a clear line of sight:

Goal → KPI → Gap → Cause → Project → Result

That’s much more useful than having a KPI dashboard in one system and a project list somewhere else.

KPI Fire’s platform is designed around connecting goals, metrics, and projects so teams can see how improvement work contributes to business objectives. Its goal functionality can also connect metrics and improvement ideas directly to goals.

9. Use Lead Measures to Monitor the Change

Once an improvement project begins, don’t wait until the end to find out whether it’s working.

This is where lead and lag measures become important.

Your problem KPI is often a lag measure.

It tells you what has already happened.

For example:

Lag KPI: Unplanned downtime.

But you might also track lead measures such as:

• Preventive maintenance completed on time
• Equipment inspections completed
• Maintenance issues resolved before failure
• Operator checks completed

KPI Fire’s Lead vs. Lag Measures explains how lead measures help teams monitor the activities and conditions expected to influence future results, while lag measures show the eventual outcome.

This creates an important distinction:

Lag measures tell you whether you achieved the result.

Lead measures give you something to manage along the way.

10. Verify: Did the Improvement Actually Work?

Here’s where the improvement cycle comes full circle.

You’ve:

• identified the KPI gap,
• investigated the cause,
• selected an improvement,
• launched the project,
• changed the process.

Now comes the most important question:

Did performance actually improve?

Don’t answer that question based on whether the project was completed.

A completed project is an activity.

An improved KPI is a result.

Compare performance against your baseline.

Look at the trend.

Consider whether the change is statistically meaningful.

And check whether the improvement holds over time.

KPI Fire’s SmartCharts content describes how statistical visualization can help teams distinguish genuine improvement from normal variation and evaluate the impact of a change.

For example:

Before project:
Average cycle time = 14.2 minutes

After project:
Average cycle time = 11.8 minutes

That’s encouraging.

But don’t stop there.

Ask:

• Is the new performance stable?
• Did the improvement persist?
• Did another KPI get worse?
• Did the process change become standard work?
• Are teams still following the new process?

The objective isn’t simply to make the KPI green.

The objective is to improve the underlying system.

11. Don’t Let a Green KPI Fool You

There’s another side to this problem.

A KPI turning green doesn’t automatically mean everything is working perfectly.

For example, a team could hit its sales-call target while producing fewer profitable customers.

A production team could hit its output target while quality deteriorates.

A service team could reduce average call time while customer satisfaction falls.

This is one reason KPI Fire’s coverage of Goodhart’s Law is important.

When a measure becomes the target, people can optimize the measure rather than the underlying business outcome.

A KPI should therefore be viewed in context.

Ask:

Is the KPI improving because the business is improving—or because we’ve learned how to improve the number?

Good KPI management isn’t about making every metric green.

It’s about making sure the metrics you’re managing actually represent the outcomes the business cares about.

The KPI-to-Action Loop

At this point, the entire process can be summarized in one loop:

1. Measure
   Track the KPI.

↓

2. Detect
   Identify a meaningful performance gap.

↓

3. Validate
   Check the data, target, and variation.

↓

4. Investigate
   Find the underlying cause.

↓

5. Decide
   Determine whether action or a project is warranted.

↓

6. Prioritize
   Choose the improvement opportunity that deserves resources.

↓

7. Improve
   Implement the change.

↓

8. Verify
   Measure the result.

↓

9. Sustain
   Make the improvement the new standard.

↓

Repeat

This is where KPI management and continuous improvement come together.

A KPI shouldn’t simply tell you what happened.

It should help your organization decide what to do next.

What Should Happen When a KPI Turns Red?

When a KPI misses its target, don’t immediately reach for a project charter.

Start with five questions:

1. Is the data accurate?

If not, fix the measurement first.

2. Is the change meaningful?

Separate genuine signals from normal variation.

3. Is the target still relevant?

Make sure you’re solving the right performance problem.

4. What’s causing the gap?

Investigate the process rather than guessing at solutions.

5. What action will actually improve the result?

Choose the appropriate response—from monitoring to corrective action to a structured improvement project.

Then measure again.

That’s the difference between tracking KPIs and managing performance.

From KPI Management to Continuous Improvement

A KPI dashboard can tell you that something is wrong.

A strong management system helps you do something about it.

The real value comes from connecting the pieces:

Strategy → Goals → KPIs → Performance Gaps → Improvement Projects → Results

That’s the connection that turns performance data into action.

And it’s why KPI management shouldn’t exist as a reporting exercise separate from continuous improvement.

When teams can see the connection between the goals the business cares about, the metrics that measure progress, the problems those metrics reveal, and the projects designed to solve those problems, KPIs become more than numbers on a dashboard.

They become a trigger for improvement.

Ready to Turn KPI Insights Into Action?

Request a demo of KPI Fire to connects goals, metrics, ideas, and improvement projects in one system—giving teams a clear line of sight from strategic priorities to measurable results.

Don’t just track what’s happening. Connect performance to the work that changes it.