Service design – when UX isn't enough

What service design is really about

At its core, service design is about designing how a service works as a whole. Not only how it is experienced when using a product, but how it is created, delivered, and held together over time.

UX design focuses on the user’s direct interaction with a product: flows, interfaces, and behaviors. Service design takes a step back and looks at the conditions behind the experience. What steps are required for something to work? Who is responsible for what? Which systems and processes need to work together?

These are not competing disciplines. They are two perspectives on the same reality, operating at different levels.

The experience upfront, the structure behind it

One useful way to understand service design is to distinguish between what is visible to the user and what happens behind the scenes.

What users encounter is often clearly addressed in UX work. Interfaces, instructions, communication, and support touchpoints are things that can be designed, tested, and improved relatively directly. For this to work, however, there also needs to be an underlying layer of processes, system support, ownership, and collaboration between teams.

When that layer does not hold together, problems arise that are easily interpreted as UX issues. In practice, it is often the structure behind the experience that is not aligned with how the service is actually used.

Service design makes these relationships visible, so friction can be addressed before it reaches the user.

UX and service design in practice

UX design is highly effective when the problem lies in the interaction itself. When something is unclear, difficult to understand, or requires unnecessary effort, there is often significant value in improving interfaces and flows.

But there are many situations where a better UI does not solve the underlying problem.

Onboarding is a clear example. UX can create a logical and pedagogical flow within the product. But if onboarding also involves manual steps, training, internal approvals, or multiple systems, optimizing the interface alone is not enough. The entire service needs to function as a coherent whole.

The same applies to support. Improved error messages and help texts matter, but when the same types of issues keep recurring, the root cause is often that processes, ownership, or information flows are not designed for how people actually work.

When service design becomes essential

Service design becomes particularly relevant when the experience can no longer be owned by a single team or solved within a single system. When users move between products, channels, and contexts, yet still expect everything to hang together.

This is common in onboarding, installation, operations, and support. It is also common in professional and industrial environments, where digital tools are tightly connected to physical products, internal processes, and organizational structures.

In these situations, problems rarely arise in isolation. They arise in handoffs.

Intunio’s perspective

At Intunio, we rarely talk about service design as a separate discipline. At the same time, we often work with problems that require a service design perspective to be solved properly.

When the experience extends beyond a single interface, we need to understand the entire chain. How decisions are made, how systems interact, how responsibility is distributed, and what the user’s actual context looks like. Otherwise, even good UX risks becoming a cosmetic solution to a more fundamental problem.

That is where UX, product design, and service design meet in practice. Not as labels, but as different ways of understanding and shaping the same whole.