Inside out: designing transformation around the people living it

There are two ways to think about where good service comes from.

The conventional view is that you design the customer experience, build the processes and technology to deliver it, and then train the people inside the organisation to operate it. The direction of travel is outside in – the external experience defines what the internal operation needs to look like.

That logic makes sense on a whiteboard. In practice, it produces organisations where the customer promise and the colleague reality don't match. The website says one thing; the person answering the phone is working with a system that does another. The strategy deck describes a seamless experience; the team delivering it is navigating workarounds, legacy processes, and a change programme that was designed without asking them what they needed to make it work.

The alternative is to start from the inside. Understand how the people inside the organisation actually work – their processes, their pain points, their knowledge, their capacity for change – and design the transformation around that reality. Not because internal experience matters more than external experience, but because internal experience determines external experience. You can't deliver a service you haven't equipped your people to provide.

This is what we mean by "inside out."

It draws on a discipline – service design – that most people associate with external services. Service design is how organisations research and redesign the experiences they deliver to customers, citizens, patients, users. Its methods are well proven: qualitative research, journey mapping, co-design, prototyping, testing. The starting point is always the people whose experience you're trying to improve.

We apply those same methods to the people inside the organisation. When a company restructures, deploys AI, shifts its operating model, or responds to regulation, the people most directly affected aren't customers – they're colleagues. Teams whose roles are changing. Managers whose responsibilities are being redefined. Specialists whose expertise is being augmented or, in some cases, made redundant.

These people are the users of the transformation. And like any users, they have detailed knowledge of how things actually work, insight into where change will break down, and ideas about what would make the new way of working viable. Ignoring that knowledge is the single most common reason change programmes fail to deliver their intended outcomes.

Working from the inside out changes what a change programme looks like at every stage.

At the research stage, it means interviewing the people whose work is about to change – not just their sponsors or their managers – and mapping their actual experience rather than the documented process. It means identifying change fatigue, capability gaps, and the informal practices that keep things running but don't appear on any process diagram.

At the design stage, it means co-designing solutions with the people who will use them. Not consulting them on a finished plan, but bringing them into working sessions where they help shape the approach. The result is a programme that's been tested against reality before it launches – and one where the people affected have a stake in its success because they helped build it.

At the delivery stage, it means placing people with the right expertise directly into the teams doing the work. Not external consultants who produce a report and leave, but service designers, UX researchers, change leads and people operations specialists who work alongside internal teams and transfer capability as they go. When the engagement ends, the expertise stays inside the organisation.

That last point matters more than it might seem. The traditional consulting model – land a team, expand the scope, bill by the day – creates dependency by design. The client organisation doesn't build capability; it rents it. We take a different view. We'd rather build your team's muscle than bill for ours indefinitely. If we place a service designer into your change team for six months and your people can run the same kind of research and co-design workshops themselves afterwards, that's a successful engagement. Not because we've lost a client, but because we've done what we were brought in to do.

This approach matters more now than it has in years, because AI is changing the nature of transformation itself. Previous technology shifts added new tools to existing workflows. AI reshapes the workflows. It changes what roles involve, what skills matter, and how decisions get made. The pace is faster than traditional change management methods were designed for, and the uncertainty is higher – people don't just need to learn a new system, they need to navigate a fundamental shift in what their work looks like.

You can't cascade that kind of change through a communications plan and a training schedule. You have to understand how it's actually landing on people – role by role, team by team – and design the transition around what you find.

The organisations that do this well will deliver better outcomes for their people and, as a direct consequence, better outcomes for their customers. Because the quality of the service you deliver externally is determined by the experience, capability and confidence of the people delivering it internally.

That's the inside-out logic. Start with the people. Design around what they need. The external outcomes follow.