Service systems
The customer journeyis also an operating model.
Every smooth customer experience depends on ownership, rules, data and work inside the business. When those elements are not designed together, the interface makes promises the organisation cannot consistently keep.
Sandy Galabada
Service systems
4 min read
Business transformation becomes credible when the organisation stops treating visible experience problems as isolated design tasks and starts examining the system that produces them.
The screen is the visible edge of the service
Checkout, onboarding, support and delivery appear to customers as interfaces. Behind them sit policies, teams, payment rules, inventory, fulfilment, data and exception handling. A redesign that ignores these dependencies can improve appearance while preserving the actual friction.
Map promises to responsibilities
For every promise in the journey, identify the owner, information required, system involved, expected time and fallback. This reveals where the customer experience depends on manual workarounds or ambiguous ownership.
The blueprint
Above the line, a promise. Below it, the work that keeps it.
Vertical connectors
Each customer moment is held up by a specific owner, rule, system and expected time.
The orange node
A delayed approval with ambiguous ownership. Operational friction surfaces as customer friction.
Redesign both sides
Change the customer action and the responsibility beneath it together, or neither holds.
Operational friction becomes customer friction
A delayed approval becomes a slow onboarding step. Fragmented inventory becomes an uncertain checkout. Poor data visibility becomes inconsistent support. The customer journey is therefore a diagnostic view of the operating model.
Every promise in the interface creates responsibility somewhere inside the business.
Redesign both sides of the line
The strongest transformation connects customer actions above the line with staff actions, business rules and systems below it. The result is an experience that is not only clearer to use, but also easier for the organisation to deliver repeatedly and at scale.
The useful outcome is not a better layer on top of the same business. It is a business that can make and keep a stronger promise.