Most companies already have journey maps, personas, and data. That part is done. The gap now isn’t insight. It’s execution.
At the same time, AI has noisily moved from “feature” to “infrastructure”.
Put those together and you get the current state of service design: less about designing touchpoints, more about designing systems that actually run the business.
AI is no longer a layer. It’s the system.
AI used to sit on top of services. Chatbots, recommendations, a bit of automation and potentially some machine learning.
Now it’s embedded across the entire journey.
- Routing decisions
- Predicting intent
- Triggering actions
- Supporting humans in real time
You’re not just designing experiences anymore. You’re designing decision flows.
That means:
- Defining logic, not just flows
- Shaping behaviour, not just interfaces
- Thinking in systems, not screens
But the industry has an execution problem
Everyone knows what’s broken. They’ve got:
- CX dashboards
- NPS scores
- Research reports
But nothing changes.
This is the real shift: service design is being pulled into delivery and operations. If it's not shippable, it doesn’t matter anymore.
That means:
- Tighter links between product and engineering
- Ownership of outcomes, not outputs
- Shorter loops between insight and fixes
AI + human is the actual model.
Automation isn’t replacing people. It’s restructuring where people are useful. The split is becoming clear.
AI handles:
- Speed
- Scale
- Repetition
- Prediction
Humans handle:
- Ambiguity
- Emotion
- Recovery
- Edge cases
Good service design now is about knowing where not to automate. That’s where most teams get it wrong.
The best service is still invisible.
There’s a noticeable shift away from “delight”. Nobody cares about clever UX if the thing is broken.
The focus now is:
- Reducing effort
- Removing steps
- Fixing problems before they happen
That means the the goal has changed from “designing interactions” to eliminating them.
Therefore, the idea of omnichannel is dead.
The idea of channels is fading. Users don’t think in “app vs web vs support”. They think in outcomes. What matters now is continuity.
One service. One flow. No resets.
That pushes service design into:
- Orchestration
- Backend logic
- System consistency
Not just front-end experience.
And that experience needs to be trusted.
People are more aware of how their data is used. And more sceptical. You can’t bolt trust on later.
It needs to be designed into:
- How data is collected
- How decisions are made
- How transparent the system is
If users don’t trust the system, the experience breaks—no matter how polished it looks.
So personalisation has had to grow up.
Most “personalisation” has been surface-level. Name in an email. Basic recommendations.
Now it’s shifting toward:
- Context-aware decisions
- Timing
- Next best action
The difference is subtle but important:
It’s not about changing the interface. It’s about changing what the service does.
Service design is going all in on business design.
This is the big one. Service design is no longer a layer on top of the business. It’s becoming the structure of the business itself.
Because:
- Experience drives retention
- Retention drives revenue
- Operations define experience
So service design now touches:
- Pricing models
- Operational workflows
- Internal tools
- Staffing decisions
We’re not just designing journeys. We’re designing how the company runs.
And it’s all becoming continuous.
Everything is:
- Real-time
- Adaptive
- Constantly changing
Static journeys don’t exist anymore.
That means service design isn’t a project. It’s an ongoing system.
More like product. Less like consultancy deliverables.
The trends we're seeing.
- AI is reshaping how services operate.
- Execution matters more than insight.
- Friction removal beats experience design.
- Systems thinking beats touchpoint thinking.
Everything else is noise.
Where do we go next?
The opportunity isn’t in more research or better journey maps.
It’s in:
- Connecting CX to operations.
- Designing AI-enabled service systems.
- Helping companies actually implement change.
That’s where the value is moving.
And that’s where most teams aren’t set up yet.