Technology can make a customer experience considerably better. It can also make it considerably worse, and the difference isn't the technology. It's whether anyone designed the service before they bought the software.
That's the thing I'd want a leadership team to hold onto, because the usual conversation runs backwards. Someone spots a tool - a chatbot, a recommendation engine, a portal - and works out afterwards where it might fit. Which is a bit like buying a kitchen and then designing the house around it.
Start with service design, not the stack
Service design is the discipline that stops this happening, and it rests on a handful of principles that are worth stating plainly.
It's user-centred - it starts from what people actually need, not what you'd like them to want. It's co-creative, bringing in customers, employees and partners, because the people delivering a service usually know exactly where it's broken and are rarely asked. It treats services as sequences - interconnected actions in an order, rather than a set of features. It's about evidencing, turning something intangible into something a person can see and hold. And it's holistic: it considers the whole ecosystem rather than one screen in it.
Disney is the obvious illustration. Every interaction is designed - the layout of the park, the behaviour of staff, the queue you don't notice you're in. None of that is a technology decision. All of it shapes how the day feels.
The process, briefly
Research, to understand what people actually need rather than what you assume. Ideation, to generate options. Concept development, to turn the good ones into something coherent. Prototyping, to test cheaply before you commit. Implementation, which almost always means changing how the organisation works, not just what it sells. And evaluation - the step most commonly skipped, and the one that turns a project into a capability.
Skip any of those and technology will amplify whatever you got wrong.
Buying technology before designing the service is like buying a kitchen and then designing the house around it.
The service blueprint
If you take one tool from this, take this one. A service blueprint maps not just what the customer does, but everything that has to happen behind the scenes for their experience to work.
It has layers. Customer actions - the journey as they experience it. Frontstage interactions - the moments where they touch you directly, whether that's a conversation, an app, or a form. Backstage interactions - the internal processes and decisions that make the frontstage possible, and which the customer never sees. Support processes - the systems, vendors and infrastructure underneath it all. And the evidence - the physical or digital artefacts that prove the service happened.
What makes a blueprint valuable is that it exposes the connection between the two. When a customer waits three days for an answer, the blueprint shows you why: an approval step, a system that doesn't talk to another system, a handoff between two teams who don't share a queue. You can't see that from the front. And you certainly can't fix it by redesigning the front.
Where technology earns its place
Once you have that map, technology decisions become obvious rather than fashionable. You can see which backstage bottleneck is causing the frontstage pain, and pick the tool that removes it.
Personalisation is the classic example of getting this backwards. Data analytics and recommendation engines can genuinely improve an experience - but only if they're applied to a journey that works. Personalising a broken process just means the customer gets a well-targeted version of a bad time.
And two constraints that shouldn't be afterthoughts. Respect for privacy and data security is not a compliance box; it's part of the experience, and customers notice when it's treated casually. And technology should complement human interaction rather than replace it - the moments that matter most to a client are usually the ones where they need a person, and those are precisely the moments most likely to be automated away in the name of efficiency.
The question
Could your team draw the backstage of your most important customer journey right now - the systems, the handoffs, the approvals? If not, then any technology you buy to improve that journey is a guess. It might be a good guess. But you won't know until you've spent the money.
If you'd like help mapping it properly, book a short discovery call with the team at Distinction. No pitch, just an honest look at where the experience actually breaks.
