Building Service Capability: Why Most Service Transformations Fail

19th March 2026

Johann Diaz

Every now and then, I read something in Harvard Business Review that makes me stop and think, finally, someone has described the real problem.

The article I came across recently explored why some organisations steadily improve their operations while others seem stuck running wave after wave of improvement programmes that never quite deliver the results leadership hoped for.

The research points to a simple conclusion: the organisations that truly improve don’t rely on isolated initiatives. They build internal capability to continuously improve their operations.

That observation will sound obvious to anyone who has spent years inside large organisations. But in practice, it’s rarely how improvement actually happens.

And that’s where the real problem begins.

The uncomfortable truth about “transformation”

Most organisations are not short of transformation programmes;

·       There’s usually a customer experience initiative underway

·       A digital transformation programme

·       An automation effort

·       An operational efficiency project

·       Maybe even a service improvement initiative

Leadership teams invest serious money and effort into these programmes. Consultants are brought in. New tools are implemented. Project teams work flat out.

Yet if you walk into the contact centre, the service desk, the field service team or the operations floor, the story often sounds very different.

Frontline teams are still navigating multiple disconnected systems.
Customers are still repeating the same information to different teams.
Problems still fall between organisational boundaries.

People are working hard. But the system itself hasn’t really changed.

This is the painful reality many senior leaders eventually confront: despite all the improvement initiatives, service still feels harder to deliver than it should be.

Why improvement efforts keep falling short

The reason is usually not a lack of effort. It’s fragmentation.

Different parts of the organisation launch improvement efforts independently.

m

·       Operations optimise processes

·       IT deploys new technology

·       Customer experience teams measure sentiment

·       Finance focuses on cost

Each effort has value. But they rarely connect into a single operational system.

So what happens?

The organisation becomes busier.

Projects multiply.
Technology stacks grow.

But service — the thing customers actually experience — often remains inconsistent.

That’s when leadership teams start asking the question I hear so often:

“Why are we investing so much in transformation, yet customers still struggle to get reliable service?”

What the HBR research highlights

The HBR article offers a useful perspective.

Organisations that improve consistently don’t rely on programmes alone. They develop capabilities that allow them to diagnose operational problems, coordinate improvements and learn continuously.

In other words, improvement becomes part of how the organisation works, not a periodic initiative.

That idea aligns closely with something I’ve seen repeatedly in service organisations.

The businesses that succeed long term treat service as a system that must be designed, managed and continuously improved.

Those who struggle tend to treat service as a collection of functions.

And the difference between those two approaches is enormous.

Service is where fragmentation becomes visible

Service is where all an organisation's internal complexity shows up.

·       Sales sell the product

·       Operations delivers it

·       Support handles problems

·       Field service fixes failures

·       Finance invoices it

From the inside, those functions appear separate. From the customer’s perspective, they are all part of one experience.

When those parts of the organisation don’t connect properly, customers feel the friction immediately.

·       The installation that doesn't go as planned

·       The support case that gets transferred three times

·       The engineer who arrives without the correct information

Each issue may appear operational.

But often the root cause is structural. The organisation has never designed its service system to work end-to-end.

When organisations finally see the real problem

I remember working with the CEO of a mid-sized technology company that had reached breaking point.

Customers were leaving. Service teams were firefighting. Departments were blaming each other.

Every function believed it was doing its job well.

But no one owned the outcome of service from beginning to end.

Once the leadership team recognised that truth, the conversation shifted.

Instead of asking which department needs to improve, they began asking:

How does our service actually work across the whole organisation?

That change in perspective was the turning point.

Because improving service rarely comes from fixing one process or deploying one tool.

It comes from understanding and redesigning the service system itself.

Building service capability deliberately

This is exactly where many organisations struggle. They know service needs to improve. But they don’t have a structured way of thinking about service as an organisational capability.

Over the years, I’ve seen organisations attempt to solve this through:

·       New technology platforms - whether ITSM, CRM, ERP or others

·       Customer experience programmes

·       Operational excellence / service improvement initiatives

·       Automation projects

Each of those can help.

But none of them on their own creates the capability required to design and run great service consistently.

What’s missing is a way of bringing those elements together into a coherent operational model.

The role of the Customer Service Revolutionizer (CSR)

This is precisely the challenge that led me to develop the Customer Service Revolutionizer (CSR) framework.

CSR is not another improvement programme. And it’s certainly not about launching yet another transformation initiative.

It’s a structured way of helping organisations build the capability to design, operate and continually improve service end-to-end.

The framework focuses on the elements that must work together if service is going to perform reliably:

·       Leadership and Service Strategy

·       Operational Design and Ownership

·       Technology and Automation

·       Data and Insight

·       Culture, Behaviours and Accountability

When those elements are aligned, service becomes far easier to deliver.

·       Teams understand how their work connects

·       Problems get diagnosed properly

·       Improvement becomes continuous rather than ad hoc

In other words, the organisation develops the capability highlighted by the HBR research as essential.

The question every leadership team eventually faces

At some point, many organisations reach a moment of recognition.

They realise that running more improvement programmes is unlikely to solve the underlying problem. They realise that what they actually need is the capability to design and run service properly.

That’s the point where the conversation shifts from:

“What initiative should we launch next?”

to

“How do we build the capability to run great service consistently?”

For organisations willing to ask that question honestly, the opportunity is enormous.

Because once service capability is built deliberately and strategically, operational improvement stops being a struggle.

It becomes part of how the organisation works naturally.