The Hidden 95% of Lean That Actually Drives Performance

Over the last few weeks, our Managing Director Andy Cheshire has been sharing a series of posts on Strategic CI Tools. The series was put together with a specific purpose in mind – to help organisations connect their improvement initiatives to their overall strategic goals, with the tools themselves playing an important role in making that connection possible.

As the series developed, a theme kept surfacing alongside the tools. A more fundamental question sitting underneath all of them: why do so many improvement programmes generate real activity, but limited results? Why does the effort rarely seem to match the impact?

It’s a question that runs through much of what Andy has shared, and it felt important enough to address directly in its own post because even the right tools work differently when the foundation beneath them isn’t in place.

If your organisation has been running a Lean programme for a year or two and you’re not seeing the shift you expected, there’s usually a straightforward explanation.

You’re probably only doing 5% of it.

A Familiar Pattern

It’s a conversation that comes up regularly.

Walk through many manufacturing sites or office environments today and you’ll see all the hallmarks of a Lean organisation. 

Visual boards neatly laid out with green KPIs, hourly production charts tracking performance in real time, dashboards around compliance and call statistics and tiered meetings structured around SQDCP metrics. 

Workstations are spotless, tools precisely arranged on shadow boards, walkways clearly defined, and standard work displayed at every point of use. Improvement boards showcase ideas, A3s and before-and-after wins, signalling a culture that appears engaged and in control.

But look a little closer, and a different picture can emerge. Boards are updated but rarely used to drive decisions. Metrics are reported, but not challenged. Standards exist, but are bypassed when pressure builds. Improvement activity is visible, yet impact is limited. The environment looks Lean – but the underlying capability, behaviours and thinking that sustain real continuous improvement are often missing.

The frustration is understandable. But the issue isn’t that Lean doesn’t work, it’s that what’s been implemented only scratches the surface of what Lean is really about.

The Part Most Organisations Never Reach

Think of it as an iceberg. Above the waterline, you’ll find the visible elements: the boards, the tools, the one-time training events, the waste walks. These things are recognisable, and they’re not without value. But they represent roughly 5% of what genuine Lean systems look like.

The other 95%, the part that actually transforms performance, sits below the surface.

That deeper layer is the Lean Operating System. It’s built on stable, standardised processes that people genuinely follow, not just in principle, but in practice. Standards are clear enough that deviation becomes visible before it becomes a problem. Leaders and teams have a regular rhythm of reflection, looking honestly at what’s working and what isn’t. Strategic intent connects to the work being done today, through structured approaches like Hoshin Kanri, rather than sitting in a document nobody references. 

None of this is complicated in concept. All of it takes sustained effort to embed.

Why the Surface is Where Most Effort Stays

The reason most improvement initiatives stay at the surface isn’t lack of commitment. It’s that the visible elements are easier to implement. They have a start and an end point. They generate activity. They’re tangible enough to report on. And so organisations invest in them, see limited returns, and sometimes conclude that Lean simply isn’t for them.

What they haven’t done is build the system underneath.

The Real Capability Challenge

The shift required isn’t primarily a technical one. It’s a behavioural one. It’s leaders who ask different questions on the shop floor or in the daily stand-up. It’s problem-solving that starts with data rather than opinion. It’s a cadence of reflection that builds over time into something that actually changes how work gets done.

That’s a different kind of capability challenge and a different kind of development conversation. 

If your Lean programme isn’t delivering the results the effort deserves, it may be worth considering which layer you’re actually working in.

If this resonates with where your organisation currently is, a practical next step might simply be exploring what your operating system layer might look like in practice and what it would take to start building it.

Back to top