Service Design

There's something odd about how most organisations handle human-centred design.

When it comes to services and products, the thinking is sophisticated. Teams spend weeks understanding user needs. They map journeys. They prototype and test. They redesign around what people experience rather than what the organisation finds convenient. And when it works - when a service is genuinely designed around the person using it - the results are remarkable. People engage more, complain less, return more often. McKinsey's Business Value of Design research (2018) tracked 300 companies over five years and found that top-quartile design performers saw 32% higher revenue growth than their peers.

But here's what's hiding in plain sight. Those same organisations that design so carefully for their customers often don't apply any of that thinking to the people delivering the service. The working environment - how teams are structured, how decisions are made, how information flows, what it feels like to come to work - is designed for the organisation's convenience, not for the people inside it.

Two entirely different modes. One for the people outside the building, one for the people inside it.

Why the design lens stops at the front door

It's not that leaders don't care about their people. Most do, deeply. The gap isn't one of intent - it's one of habit. The tools and mindsets that organisations use to think about services and customers come from a design tradition. The tools used to think about the internal organisation come from a management tradition. Different language, different assumptions, different starting points.

The management tradition starts with structure. Org charts. Processes. Role descriptions. Performance frameworks. It asks: how should the work be organised? The design tradition starts with experience. It asks: what is this like for the person in the middle of it?

Both questions matter. But when the second question is only asked about customers - never about the people doing the work - you end up with organisations that are beautifully designed on the outside and accidentally designed on the inside.

This matters more than it might seem. The quality of a service is inseparable from the conditions in which it's delivered. A customer experience that feels warm, responsive, and human doesn't happen because someone wrote it into a service standard. It happens because the people delivering it are working in conditions where warmth, responsiveness, and humanity are possible. When those conditions are absent - when people are overstretched, underinformed, disconnected from the purpose of what they're doing - no amount of service design on the customer-facing side will compensate.

The same skill, turned inward

Here's where it gets interesting. The skills that make someone good at service design are the same skills that make someone good at creating the conditions for people to do their best work. The translation is closer than most people realise.

Empathy - understanding what something is like from the inside. In service design, this means spending time with the person using the service, understanding their experience, noticing what the organisation can't see from its own perspective. Applied to leadership, it means the same thing: understanding what it's like to work here. Not from the org chart or the engagement survey, but from the lived experience of the people doing the work. What's it like to join this team? To raise a concern? To try something new? To navigate the gap between what's expected and what's possible?

Experience mapping - following the whole journey, not just the moments you designed. In service design, you learn quickly that the moments between the designed touchpoints are often where the experience is won or lost. The same is true inside organisations. The formal processes - inductions, appraisals, team meetings - are the designed touchpoints. But the experience of working somewhere is shaped just as much by what happens between them. How information travels. How decisions get made when nobody's watching. Whether people feel safe enough to say "I don't know" or "this isn't working."

Designing conditions rather than prescribing behaviours. This is perhaps the most powerful translation. Good service design doesn't try to script every interaction. It creates the conditions - the environment, the information, the tools, the freedom - that enable people to respond well in situations the designers couldn't have anticipated. Good leadership works the same way. You can't script how a team should respond to every situation. But you can create the conditions - trust, clarity, autonomy, connection - that mean they'll respond well when the moment arrives.

Prototyping and iteration - trying things and learning from what happens. Service designers don't build the final version first. They test, observe, adjust. Leaders who bring this mindset to organisational design - treating a new process or structure as a prototype to be learned from rather than a solution to be implemented - tend to build environments that adapt and improve rather than calcifying around the first attempt.

What this looks like in practice

A leader who thinks like a designer doesn't need new tools or a different job title. They need to ask a different set of questions.

Instead of "how should we restructure the team?" they might ask "what is the experience of being in this team, and what's shaping it?" Instead of "how do we improve performance?" they might ask "what conditions would need to be in place for performance to improve naturally?" Instead of "how do we manage this change?" they might ask "what is this change going to feel like for the people going through it, and what would make it easier to navigate?"

These aren't soft questions. They're design questions applied to culture - and they tend to surface things that structural or process-led questions miss entirely.

Consider what happens when an organisation merges two teams. The management lens focuses on structure: reporting lines, role clarity, process alignment. The design lens asks: what will this be like for the people involved? What will they lose? What do they need to make sense of what's happening? Where will the friction be, and what would reduce it? Both lenses are needed. But when the design lens is applied only after the structural decisions have been made - as an afterthought rather than a starting point - the merge is likely to look good on paper while feeling chaotic for the people inside it.

Or consider how organisations approach hybrid working. The structural question is about policies: how many days in the office, which meetings are in person, what technology do we need. The design question is different: what does a good working week feel like for someone in this team? What kind of work needs proximity, and what kind needs focus? What would make people want to come in rather than have to? Organisations that started with the design question tended to arrive at arrangements that worked. Organisations that started with the policy tended to end up negotiating compliance.

Both halves, together

There's a reason this matters beyond better management practice. Organisations that apply human-centred thinking to both sides - to the experience of the person receiving the service and the experience of the person delivering it - create something that neither side can achieve alone.

When people work in conditions that are designed around their experience, they naturally create better experiences for the people they serve. Not because they've been told to. Because the conditions allow it. A social worker who feels trusted, informed, and supported will create a different experience for the family they're working with than one who feels overwhelmed, disconnected, and under surveillance. A GP receptionist who works in conditions designed for empathy will create a different experience for patients than one who works in conditions designed for throughput.

This is what we mean by both halves, together. Service design and customer experience work on how people experience what you offer. Culture change and organisational development work on the conditions in which people deliver it. When both are informed by the same human-centred lens, they reinforce each other. When they're treated as separate disciplines - one led by designers, the other by HR - the gap between service promise and service reality persists.

McKinsey's design research found that more than 40% of companies weren't even talking to their end users during development. The equivalent finding on the organisational side would be more striking still. How many organisations design their internal environment - their structures, processes, working conditions - with the same depth of human understanding they bring to their products?

An underused skill

The intriguing thing about this is that the skill already exists in most organisations. Somewhere - in a service design team, a UX function, a customer insight group - there are people who know how to understand experience from the inside, design conditions rather than prescribe behaviours, and iterate toward something that works. The skill is there. It's just pointed in one direction.

The invitation isn't to turn every leader into a designer. It's to notice that the lens already being used to create better services is the same lens that creates better organisations. Empathy doesn't change when you turn it inward. The discipline of understanding experience doesn't stop being useful when the experience in question is your own team's working life. The practice of designing conditions rather than dictating behaviours is as powerful inside the organisation as it is in the service you deliver.

The organisations that figure this out - that stop treating service design and organisational development as separate conversations - tend to find that both sides improve. Better conditions for people create better experiences for customers. Better customer insight creates more purposeful work for the people delivering it. The two halves turn out to have been one thing all along.

The question isn't whether your organisation practices human-centred design. It's whether that practice stops at the front door - or runs all the way through.