Operational Excellence Simplified

Learning objective: Understand why KPIs can weaken performance when disconnected from real processes, and learn how to design performance measures that guide better work, protect value, manage risk, and support Operational Excellence.

Many organisations set KPIs with good intent. Leaders want visibility. Managers want accountability. Teams want to know what “good performance” looks like. On paper, this sounds simple: choose the numbers, report them regularly, and act when performance moves in the wrong direction.

In real operations, it can work differently.

A KPI can improve performance when it helps people do the right work in the right way. But a KPI can also create pressure in the wrong place. A team measured only on speed may rush a customer handover. A department measured only on volume may push incomplete work downstream. A manager measured only on short-term cost may delay preventive work that protects quality, safety, or service reliability.

The problem is not measurement itself. Performance measures are essential. Harvard Business Review has argued that metrics help give strategy a practical form but also warns that metrics are imperfect proxies for what organisations truly care about. When performance management becomes disconnected from real work, metrics can pull people away from the outcomes they were meant to support.

That is why strong process KPIs must be built into the work, not added on top of it.

The KPI Problem Starts When Measures Sit Outside the Process

Many KPI problems begin with separation.

A leadership team defines targets. A reporting team builds dashboards. Department heads cascade numbers. Then frontline teams are expected to deliver results through processes that may not have been designed to support those results.

This creates a practical gap. The KPI says what needs to improve, but the process does not show how to improve it.

For example, an operations team may receive a target to reduce turnaround time by 20%. The dashboard shows delay. The weekly report shows missed performance. But the actual process still contains unclear handovers, duplicated checks, missing role ownership, weak prioritisation rules, and rework loops.

In that situation, the KPI is not wrong. The target may be completely reasonable. The issue is that the measure has been placed outside the process instead of being designed into the process.

A useful KPI should help people answer practical questions:
What work must be done differently?
Which step creates the performance gap?
Who owns the decision or handover?
What control protects quality, safety, or customer value?
What trade-off should never be made just to improve the number?

When those questions are missing, people often create their own answers. They speed up the visible work. They delay less visible work. They create informal workarounds. They focus on the number that gets reported and give less attention to the process conditions that create sustainable performance.

Good KPIs Guide Behaviour, Not Just Reporting

A KPI is never neutral. It influences attention, decisions, and behaviour.

This is why KPI design is not only a reporting activity. It is a process design activity.

If a call centre measures only average handling time, employees may feel encouraged to finish conversations quickly, even when the customer needs proper resolution. If a maintenance team is measured only on short-term downtime, it may postpone preventive tasks that protect long-term reliability. If a procurement team is measured only on unit cost, it may select suppliers that increase quality issues, delays, or operational risk elsewhere.

The positive alternative is to design KPIs that guide better operational decisions.

Speed can be measured alongside first-time-right quality. Cost can be measured alongside service reliability. Output can be measured alongside safety, customer experience, and rework. Productivity can be measured in a way that encourages flow, not just activity.

This does not mean every process needs a large scorecard. Too many measures can create confusion. The goal is to choose a small set of measures that reflect how value is actually created.

Lean Enterprise Institute describes value-stream mapping as a way to see the steps and information flows required to bring value to the customer. It also notes that value-stream mapping helps organisations see the flow, understand sources of waste, create a common language, and form the basis of an implementation plan.

That is the point: strong KPIs start with seeing the work.

Once the work is visible, the organisation can measure what matters in context. The measure becomes part of how the process is managed, not just how performance is reported.

Build KPIs Around Process Design, Roles, and Controls

A process KPI should connect to the way work is designed.

That means the organisation needs to understand the process steps, inputs, outputs, handovers, decision points, controls, and ownership before finalising the measure. Otherwise, the KPI may encourage performance improvement in one area while creating hidden loss somewhere else.

ISO’s guidance on the process approach in ISO 9001:2015 is useful here. It explains that a management system integrates processes and measures to meet objectives, and that processes should define interrelated activities and checks to deliver intended outputs. It also connects process management with risk-based thinking, planning, controls, monitoring, and improvement.

This matters because KPIs are most useful when they are linked to the operating model around them.

A well-built process KPI should connect to five things.

First, it should connect to process design. The measure should reflect the actual flow of work, not just an executive reporting category.

Second, it should connect to roles. People should know who owns performance, who acts on signals, who removes barriers, and who escalates risks.

Third, it should connect to controls. If a KPI creates pressure to move faster, the process should include controls that protect quality, compliance, safety, and customer outcomes.

Fourth, it should connect to decision routines. A KPI needs a review rhythm. Teams need to know when they discuss it, what action is expected, and how they test whether changes worked.

Fifth, it should connect to improvement. A KPI should not only show whether performance is good or bad. It should help the team identify where to improve the process.

This is where many organisations struggle. They do not lack data. They lack a structured way to turn measurement into better work.

Connect Performance Measures to Customer Value and Operational Risk

The strongest KPIs protect value.

They help the organisation deliver what customers, patients, employees, regulators, or internal stakeholders actually need. They also help leaders see risk early enough to act.

A KPI that improves a number while reducing customer value is not a good KPI. A KPI that improves output while increasing errors, safety exposure, complaints, or rework is not a complete KPI. A KPI that makes one department look efficient while pushing waste into another department is not supporting Operational Excellence.

This is why performance measures should be reviewed against customer value and operational risk.

For each major KPI, leaders and improvement professionals can ask:
Does this measure reflect an outcome the customer or stakeholder values?
Could improving this number create pressure to skip an important step?
What quality, safety, compliance, or service controls must stay protected?
Which upstream or downstream teams could be affected?
What balancing measure should be used to prevent local optimisation?

This is also where Operational Excellence becomes more than “improvement projects”. It becomes management discipline.

McKinsey’s 2024 research on operational excellence highlights that productivity challenges often become visible at the operating level and that operational excellence requires practices that help organisations build performance, capability, and resilience. McKinsey also describes next-generation operational excellence as being built around continuous improvement, high performance, productivity, resilience, and shared commitment across the organisation.

That is directly relevant to KPI design. Measures should not only track performance after the fact. They should help the organisation manage the conditions that create performance.

Why KPI Design Needs a Management System, Not a Dashboard

Dashboards are useful. Reports are useful. Scorecards are useful.

But they are not enough on their own.

A dashboard can show that performance is moving. It cannot, by itself, define process ownership, clarify roles, redesign handovers, build controls, align improvement priorities, or create a disciplined review rhythm. Those activities require a management system.

This is where a structured Operational Excellence approach becomes valuable.

PATH OEMS™ is a self-directed Operational Excellence Management System from Operational Excellence Simplified. It is designed to help organisations, professionals, and consultants deploy Operational Excellence step by step through Plan • Align • Transform • Hold.

For KPI design, that structure matters.

In the Plan stage, users can clarify the operational problem, define the current situation, and understand which processes need attention.

In the Align stage, they can connect improvement priorities to roles, responsibilities, expectations, and management direction.

In the Transform stage, they can redesign the way work is performed, controlled, measured, and improved.

In the Hold stage, they can support sustainability through review routines, ownership, standardisation, and continued improvement.

This is the difference between tracking performance and managing performance.

A team that only tracks KPIs may know when results are off target. A team using a structured Operational Excellence Management System is better positioned to understand why performance is off target, what process conditions need to change, who should act, and how the improvement should be sustained.

That is why KPI conversations should not sit only in management meetings. They should be built into process improvement, daily management, role clarity, operational controls, and continuous improvement routines.

Conclusion: Make KPIs Part of the Way Work Is Done

KPIs improve performance when they help people manage the work that creates performance.

They become weaker when they are created in isolation, disconnected from process design, roles, controls, customer value, and operational risk. In those situations, teams may still work hard, but the measure can pull attention towards the number instead of the outcome.

The practical answer is not to avoid KPIs. It is to build better ones.

Strong process KPIs help teams see the work, protect value, manage risk, and improve with discipline. They connect measurement to action. They help leaders move from reporting performance to improving performance.

If your organisation is trying to make KPIs, process improvement, and Operational Excellence work together more effectively, the free PATH OEMS™ webinar is a practical next step. It introduces PATH OEMS™ — a self-directed Operational Excellence Management System — and explains how structured deployment can help you understand where to start, what to do next, and how to turn improvement activity into a managed system.

Join the free PATH OEMS™ webinar to see how structured Operational Excellence can help you connect performance measures to real process improvement.

Source List
1. Harvard Business Review — The Tyranny of Numbers and Don’t Let Metrics Undermine Your Business, 2019. Used to support the point that metrics are useful but imperfect proxies and can create unintended consequences when disconnected from strategy and work.
2. International Organization for Standardization — The Process Approach in ISO 9001:2015. Used to support the connection between process design, measures, controls, risk-based thinking, PDCA, monitoring, and management systems.
3. Lean Enterprise Institute — Value Stream Mapping. Used to support the importance of seeing the whole flow of work, understanding waste, creating common language, and forming an implementation plan.
4. McKinsey & Company — Breaking Operational Barriers to Peak Productivity, 2024. Used to support the connection between operational excellence, productivity, operating-level discipline, and performance improvement.
5. McKinsey & Company — Next-Generation Operational Excellence. Used to support the article’s framing of Operational Excellence as continuous improvement, high performance, productivity, resilience, and shared organisational commitment.