Closing the leadership gap that stops CI delivering results

Speaking from experience, many CI programmes don’t work as intended because the leadership behaviour that the programme needs doesn’t materialise. By the time this flaw is realised, it’s often too late. Even with the right methodology and a capable team, this is one hurdle that needs addressing before you can overcome it.

It’s the problem that practitioners feel most acutely and talk about least publicly. Leadership says all the right things, the budget gets approved, and the launch gets the right people in the room.

Then the gap opens between what leadership endorses and what leadership does. And the CI programme starts hollowing out from the middle.

Why CI culture depends on behaviours

Culture is the word most organisations reach for when improvement stalls. “Build the culture”, “change the culture”.

The framing sounds reasonable, but it locates the problem in the wrong place. When a CI programme loses momentum, the cause is usually rooted in behaviour misalignment rather than a values deficit.

OpX founder Chris Dando sat down with Rob Regan, who’s led CI programmes across manufacturing and financial services for over two decades, for a conversation on scaling continuous improvement. He names it precisely:

"I describe it as strategic or leadership incongruence. I've had examples where CEOs or senior execs talk with real passion and conviction about the need for continuous improvement, and that's where that involvement ends. It's the classic words and deeds, and for me, that's probably one of the key culture killers."

The problem is rarely that leaders do not care. It's that the system does not require them to demonstrate it.

The middle management layer feels this the most

When leadership incongruence takes hold, it travels downwards. Middle managers end up caught between two contradictory signals: a leadership team that endorses CI in principle, and a frontline that is watching to see whether any of it is real.

Rob describes what this produces:

"They're taking a lot of flak from the guys at the frontline and trying to manage up that everything's great. The leaders at the very top are not going to the work. So you end up with this ecosystem of mistrust."

Middle managers in this position aren’t the problem. They’re absorbing the consequences of a gap they didn't create and can't close. Pressuring them harder doesn't help. The fix has to come from above, and it has to be visible.

See how OPX keeps CI visible at every level of your organisation

Going to the work is not optional

The most consistent difference between CI programmes that hold and those that hollow out is straightforward: senior leaders who go to the work.

Not performatively. Not a quarterly walkabout. Chris Dando is direct about what genuine engagement looks like:

"My natural bias is: understand the work, go to the work, find the data, go to the data. Role model behaviours by asking 'show me, don't tell me.'"

I remember my first improvement role, where I was still learning the ropes. My manager was obsessive about going to see for himself, so much so that he validated everything that he was told with his own eyes and ears. This obsession, coupled with brilliant people skills made him an exceptional improvement professional. I learned lots from his approach.

When leaders go to the work, they build the understanding that makes their support credible. When they don't, the frontline notices, and trust erodes faster than any engagement initiative can recover it.

An example of when the frontline stopped believing

The moment trust breaks is often specific and small. Rob describes one:

"A load of frontline colleagues had been building lists and lists of issues that go nowhere. Here's a list of 150 things, if we could just fix 10 of them, the level of engagement we'll get will go through the roof. But the response was: we're going to build this fancy app. The minute they see you saying the right things and doing the wrong things, game over, trust gone."

Those 150 issues went nowhere because nobody was tracking whether they moved, and no leader was held to acting on them.

This is the exact gap OpX is built to close. When frontline issues are logged, tracked, and visibly actioned in one place, "we'll get to it" stops being a promise and becomes a record. The frontline can see what leadership did with what they raised.

Leadership presence erodes in the same way. Rob's observation is hard to argue with:

"The first playback, you've got the whole exec there. The second one, there's four. The third, there's two. By the fifth wave, you might have one senior leader there because their calendar is full of other stuff."

The frontline reads this. They always do.

I saw this play out in a very high-profile transformation programme at a global oil company. When we transformed the first value stream, we had 30+ very senior people in the room, all interested and nodding with intent. By the time we got to value stream three we had just 6 remaining.

How OpX closes the leadership gap

The leadership gap is closed by building a system that makes leadership behaviour visible, and visible in both directions.

Leaders can see what's actually happening across the programme, rather than a status update that's been gradually optimised on the way up. And the frontline can see whether leadership is showing up.

This is what human-led, not platform-led means in practice. OpX doesn't manufacture the behaviour, but it removes the places the gap can hide. It gives CI programmes a shared operating layer where improvement work, frontline issues, and leadership engagement all live in the same place. It sets a consistent cadence for leadership review, so presence becomes part of the record rather than a diary item that slips. And it removes the excuse of not knowing.

There's a further payoff. Because the work carries its own evidence, leadership buy-in stops depending on belief and becomes something you can prove.

That's the difference between a programme that survives a change of sponsor and one that gets cut the moment the board asks a hard question, which is exactly what we explored in “Why your CI reporting doesn't survive the boardroom”.

A programme that can only prove leadership buy-in with a slide deck and good intentions is a programme that's one leadership change away from being cut.

OpX is the operating software for improvement. It’s built to give CI programmes the visibility and evidence layer that makes that conversation unnecessary.

If you’d like to explore how OpX can keep your improvement visible, connected and auditable, you can request access and book a demo using the link below.

Request access to OpX