Service & UX design – a practical response to CX challenges
Customer experience, or CX, is today an established concept in most organisations. The ambition is clear: customers should have a coherent, clear, and positive experience over time, regardless of channel, touchpoint, or situation. At the same time, CX is often difficult to translate into practice. Despite good intentions, the same problems tend to reappear. Experiences differ between systems. Onboarding works in theory but breaks down in reality. Support becomes overloaded even though the product itself is perceived as well designed. CX is rarely unclear as a goal. It is unclear as execution.
Tobias Rydenhag
Head of Design
What CX is really about
At its core, CX is about how a customer experiences an organisation over time. Not just in a single interface or interaction, but as a whole. How products, services, communication, support, and processes connect and are perceived as one continuous experience.
At the same time, CX is used in many different ways across organisations, which often makes it hard to grasp in practical work. We explore this in more depth in the article Why CX Is Often Hard to Grasp, where we explain why CX is frequently clear as an ambition but unclear as a means of execution.
This makes CX useful as a language for direction, but less useful as a tool for actual change.
Common CX challenges in practice
When CX falls short, it is rarely because no one cares about the user. More often, it is the result of structural gaps.
We commonly see:
- products with strong UX, but unclear handoffs to onboarding or support
- multiple systems that work well individually, but create friction together
- teams optimising their own areas without clear ownership of the whole
- support compensating for shortcomings in processes or structure
From the customer’s perspective, it does not matter where responsibility sits. The experience is perceived as a whole, even when the organisation is divided into silos.
This is why many CX problems cannot be solved by improving a single interface.
Why CX initiatives often stall at ambition
In many organisations, CX is owned at a high level. There are goals, metrics, and clear ambitions. At the same time, execution is often distributed across teams and functions further down in the organisation.
The result is that CX tends to be:
- mapped rather than changed
- measured rather than built
- discussed rather than embedded in everyday decisions
CX often points out where the experience breaks down, but lacks a clear answer to why it happens and how it should be addressed in practice.
Service design as structure for CX
This is where service design becomes relevant. Not as an additional layer on top of CX, but as what makes CX possible to realise.
Service design focuses on how the service actually works behind the scenes. Processes, ownership, handoffs, system support, and collaboration between teams. Elements that are rarely visible to the customer, but that largely determine the experience.
When service design is missing, CX ambitions risk remaining just that. When service design is in place, the experience can be shaped in a way that holds over time, even in complex organisations.
UX design as what the customer encounters
UX design is where CX becomes tangible. In interfaces, flows, feedback, and interactions. This is where users immediately notice whether something works or not.
At the same time, UX design cannot carry CX on its own. When the experience spans multiple systems, roles, or phases of use, optimising what is visible on the screen is not enough.
UX works best when supported by clear processes, ownership, and structure. When service design provides a solid foundation, UX can contribute to an experience that is not only good in the moment, but consistent over time.
Intunio’s perspective
At Intunio, we rarely work with CX as a separate track. Instead, we often work with problems that are, in practice, CX challenges.
We encounter them in onboarding that does not quite hold together. In products where UX is thoughtfully designed but dependencies between systems create friction. In situations where support becomes part of the experience due to structural shortcomings.
Our focus therefore lies in service design and UX design, where the experience is actually shaped. In how the service functions, how systems interact, and how the user’s work is supported in practice. When those elements align, a strong customer experience emerges.
CX as a result, not a discipline
CX is not something added at the end. Nor is it something owned by a single role or function.
CX emerges when service design, UX, and the organisation work together. When structure, ownership, and interfaces pull in the same direction. That is why Service & UX design is not an alternative to CX, but what makes CX possible in practice.