The Hidden Risks of Over-Optimisation

We often think of optimisation as something inherently positive. It brings to mind reducing waste, simplifying work and making better use of time and cost which is exactly what Lean and continuous improvement are designed to achieve.

However, there can be a point as organisations build capability and structure around improvement that the focus gradually shifts towards the processes themselves and less on the value and purpose they are designed to support. 

This is where challenges such as over-optimisation can begin to emerge.

Included in This Blog:

What is over-optimisation? 

What does over-optimisation look like?

What are the symptoms of over-optimisation?

How to Refocus Your Improvement Activity 

Finding the Balance Between Efficiency and Continuous Improvement

Over-optimisation happens when the improvement process itself becomes more complex, resource-intensive and/or time-consuming than the problems it was designed to solve. 

Utilising tools like DMAIC, Kaizen, 5S and Value Stream Mapping shift from being ways of thinking to things that need to be completed. 

This is what we refer to as the “aesthetics of Lean”, the visible elements: tools, templates, boards and routines that are completed day to day. Alongside this sits the “Lean Operating System”, the underlying behaviours, decisions and problem-solving activities that actually drive meaningful change and application of these tools. 

When the focus tilts too heavily towards the aesthetics, improvement activity can become something that is done, rather than something that continuously improves or adds value.

Over-optimisation can look different across industries, from manufacturing and healthcare to finance, logistics and service operations. The context changes, but the pattern is often similar; a growing gap between the activity of improvement and the outcomes it is meant to deliver.

In many organisations, this only becomes visible when you step closer to the day-to-day work.

If we take for example a mid-sized manufacturing business that a few years ago trained staff across functions to Lean Six Sigma Green Belt Level, have a clear governance structure and have regular review cycles. On the surface, this looks strong.

However, closer to the work, a different picture often emerges. Projects are launched on a set schedule, not always because a specific problem needs solving, but because the calendar calls for it. Practitioners spend significant time preparing documentation and attending reviews, with some projects running for months without a clearly defined outcome.

This is what over-optimisation can look like in practice: plenty of activity, but a growing gap between effort and meaningful outcomes.

One of the challenges with over-optimisation is that it doesn’t always look like a problem from the inside. In fact, it can look like progress. That’s why it helps to step back and look for a few consistent patterns.

Volume over Impact

A high volume of improvement activity often reflects strong engagement and organisational commitment to change. The opportunity is to ensure that this activity is consistently connected to measurable outcomes, so effort translates more clearly into operational impact.

Framework-Led Activity

Structured frameworks can provide valuable discipline and consistency in how improvement is delivered. The focus is to ensure they remain flexible enough to respond to real operational needs, so they continue to support problem-solving rather than unintentionally shaping it.

System Maintenance Over Improvement

A well-functioning improvement system requires ongoing attention, which is often a sign of maturity and governance strength. The opportunity is to maintain a healthy balance so that system support does not begin to outweigh time spent on delivering improvement itself.

Fragile Standards

Well-defined standards are a key foundation of operational excellence. Where they are occasionally adapted under pressure, it can highlight opportunities to strengthen ownership, embedding, and day-to-day consistency across teams.

Reporting Without Reflection

Regular reporting is a positive indicator of transparency and control within the system. The next step is often to deepen the use of that information, turning data into structured reflection, learning, and more confident decision-making.

The aim is not to reduce structure, discipline, or the use of improvement methods. It is to ensure that all activity remains anchored to a clear and practical question: what problem are we trying to solve, and how will we recognise when it has been solved?

When that question is kept central, it naturally guides a number of useful shifts in how improvement is designed and delivered.

Start with the Problem, Not The Tool. 

Clear, well-defined problems create the foundation for effective improvement. When the problem is understood properly, the most appropriate method becomes much easier to identify whether that is a structured DMAIC project or a smaller, faster improvement.

Keep Flow and Value at the Centre. 

Lean thinking is most powerful when it stays closely connected to value from the customer’s perspective. Focusing on flow, and understanding where it is disrupted, helps ensure improvement activity remains practical, relevant, and grounded in real operational needs.

Build Capability, Not Just Activity.

Sustainable improvement is driven by people who are confident in defining problems, interpreting data, and improving how work is done. Tools and frameworks play an important supporting role, but the real strength comes from developing capability within the organisation.

Review the Improvement process itself. 

A healthy improvement system evolves over time. Periodically reviewing governance, reporting, and structure helps ensure they remain proportionate to the value they create. In some cases, simplifying how improvement is managed can itself be a meaningful step forward.

Real operational excellence comes from finding the right balance between efficiency and continuous improvement. 

While efficiency focuses on standardisation, consistency and waste reduction, continuous improvement depends on curiosity, challenge and experimentation. 

Too much structure can unintentionally limit the space for learning and adaptation, while too little can reduce stability and control. The organisations that manage this best are intentional about the balance, maintaining enough structure to create consistency while still allowing space for problem-solving and innovation. 

There is no fixed point of equilibrium, it shifts with context, pressure and capability but being aware of that balance is key to ensuring improvement remains both practical and meaningful.

It’s important to keep referring to that simple question: is this helping us improve the work, or just helping us manage the improvement process?

Back to top