Service design that puts the customer first
"It absolutely has to have an insanely good user experience," everyone says. But what does a good and seamless user experience actually mean, in practice?
In a day-to-day reality shaped by complex systems, multiple touchpoints, and ever-rising user expectations, it's no longer enough to make the surface look prettier. It is increasingly about designing the entire service, from the inside out, so that the experience actually holds together for the customer. This is where service design comes in — and it is also where the boundary between design work and context work starts to disappear.
Service design as context work
Service design, done properly, is not a deliverable — it is a continuous investigation. It maps who the customer is, what they are trying to achieve, what hurts, what constraints shape their choices, where the hand-offs are, and where the internal politics actually live. That is the same territory that a modern AI-supported delivery engine needs as input. Context is not a bonus. It is an active production input. The design work that used to sit in a PDF after the workshop is the raw material the rest of the organisation — and the agents working alongside people — need to do anything useful with the product.
When should you consider service design?
- When the customer experience varies across departments or channels
- When internal processes don't reflect what customers actually need
- When digital solutions are developed in isolation from user context
- When business goals and the user journey don't quite line up
- When you want to work more cross-functionally and data-driven, without drowning in methodology
- When the organisation is about to put AI into customer-facing work and realises, belatedly, that the model will only be as good as the context it is given
From insight to operational input
The honest gap in a lot of service design work is that the insight dies the moment the workshop ends. A great journey map ages into a beautiful artefact nobody opens again. The shift in the way we work is to treat that insight as a living layer — a continuous profile of what the organisation actually knows about its customers, updated as the relationship deepens, accessible both to the humans leading the work and to the agents executing against it.
When service design is plugged into delivery that way, several things change. Design decisions stop being arguments from taste and start being arguments from evidence. Engineering builds against real user context instead of a simplified abstraction. Post-launch, the signals that come back from real use — what works, what doesn't, where friction appears — feed straight back into the context layer instead of evaporating in a quarterly review.
Design is not (only) about how something looks. It is largely about how it works — and how it feels. With service design treated as a first-class production input, rather than a pre-production workshop, you get better services, a smarter business, and a delivery engine that actually has something worth working from.