What service design brings to change management

What service design brings to change management

Most change management follows a familiar sequence. Stakeholder analysis. Communications plan. Training schedule. Go-live date. Then a period of hoping people adopt the new way of working before the programme team moves on.

It works often enough to remain the default. But it has a structural weakness: it designs change for the organisation and assumes the people inside it will follow. When they don't – when adoption is slow, resistance is high, or the new process quietly gets worked around – the usual diagnosis is that the change wasn't communicated well enough, or that middle management didn't buy in, or that the culture wasn't ready.

Those explanations are rarely wrong. But they're rarely the root cause either. The root cause, more often than not, is that nobody researched the people affected before designing the programme that affected them.

This is the gap that service design fills.

Service design is a discipline that originated in the design of public and commercial services – how a customer applies for a mortgage, how a patient moves through a hospital, how a citizen accesses a government benefit. Its methods are well established: qualitative research, journey mapping, persona development, co-design workshops, prototyping, testing. The starting point is always the same – go and understand the experience of the people using the service before you redesign it.

What's less common is applying those same methods inside the organisation, to the people living through transformation. But that's exactly where they're most needed.

When an organisation restructures, deploys new technology, changes an operating model, or introduces AI into existing workflows, the people most affected are internal – teams whose daily work is about to change, managers whose roles are being redefined, specialists whose expertise may be augmented or displaced. These people have detailed knowledge of how things actually work, where the real friction is, and what would make a new way of working viable. They are, in design terms, the users. And yet most change programmes treat them as recipients rather than participants.

Service design reverses that. Instead of starting with the programme plan and cascading it downward, you start with research. You interview the people whose work is about to change. You map their current experience – not the process diagram on the intranet, but what they actually do, day to day, including the workarounds and informal practices that keep things running. You identify where change will land hardest, where capability gaps exist, and where the real resistance is likely to come from – which is often different from where leadership assumes it will be.

Then you bring those people into the design of the solution. Co-design workshops aren't focus groups or feedback sessions. They're structured working sessions where the people closest to the problem help shape the response. The result is a change programme that's been tested against reality before it launches – and one where buy-in is built into the process rather than bolted on at the end.

We've seen this work across a range of contexts. In a management training programme redesign for a large financial services organisation, we ran a 10-week research and co-design sprint across three stakeholder groups. Sixteen interviews and two co-design workshops gave us a clear picture of where the programme was falling short. Managers helped define what good looked like. The redesigned programme ran with 1,200 people managers and delivered a minimum 15% uplift across all four evaluation criteria.

In another engagement, we helped a large enterprise surface and prioritise process improvements at scale. Twenty stakeholder interviews, 18 distinct personas, and two co-design workshops generated 142 ideas. The two that were taken forward were co-designed with the people who would use them. Submission rates from colleagues exceeded all previous team-level solutions.

In both cases, the methodology was the same: research first, co-design second, implement third. The people affected by the change were involved in designing it. That's what made the outcomes stick.

This matters more now than it has in years. AI adoption is accelerating, and the change it creates is different in kind from previous technology shifts. It doesn't just add a new tool to existing workflows – it reshapes roles, redefines what expertise means, and creates uncertainty about the future of work that no communications plan can address. The organisations that navigate this well will be the ones that take the time to understand how AI is actually landing on their people, and design the transition around what they find.

That's what service design brings to change management. Not a new framework. Not a new methodology deck. A fundamentally different starting point – one that treats the people living through transformation as the primary source of insight, not just the audience for a roll-out plan.

It's change management, designed from the inside out.