Designed for the Happy Path: Why Customers Judge You on What Goes Wrong
Most organisations can describe their customer journey in detail. Far fewer can describe what happens when it fails — and the failure route is the one customers remember, talk about and judge you on.
Most organisations can describe their customer journey in detail. Far fewer can describe what happens when it fails.
The journey is mapped, funded and owned. The failure route is whatever the organisation happened to end up with.
Which is awkward, because the failure route is the one people remember.
Where the Money Goes
The bulk of customer experience investment goes into the path where everything works — the app, the onboarding, the portal, the redesigned website.
It is easy to see why. That work is visible, it demonstrates well to a board, and it can be finished. A new portal goes live on a date, and somebody can stand up and show it.
Nobody can point at a screen and say the exception handling is done.
So the smooth case gets designers, research and a product owner. The broken case gets a process — written by whoever was closest at the time.
The Only Time They See the Whole Organisation
When a service works, the customer is dealing with a product. When it fails, they are dealing with the organisation.
They find out how many departments there are, how differently each one records the same information, and how many of them can explain that the problem started somewhere else. They discover whether anybody is willing to own something that is not theirs.
That is where the opinion forms — and it is the only part most customers will ever describe out loud to somebody else.
Exceptions Are Designed by Nobody
The happy path has an owner. Somebody was accountable for how the sign-up flow feels, and was given research, a budget and a date.
The exception route has no such person. It accretes — a workaround left over from a system migration, a policy written after a complaint, a script added when volumes spiked one winter, a rule nobody can now explain.
I have never seen an exception path that somebody designed on purpose. I have seen a great many that simply grew.
Failure Crosses the Lines on the Chart
Exceptions are difficult precisely because they refuse to stay inside one function.
A disputed bill touches billing, operations, the field team and complaints. A missed appointment touches scheduling, a contractor and the contact centre. Each of those functions may be competently run and comfortably hitting its own targets.
The customer is the only person who experiences the whole sequence — and nobody is measured on it.
What the Numbers Do Not Show
Satisfaction is usually measured at the end of a completed journey. The cases that broke are counted somewhere else, as complaints — and complaints are managed as an operational workload rather than read as design feedback.
So the reporting improves while the experience does not. Scores rise among the people who got through. The people who did not are somewhere else entirely — a different report, a different owner, a different meeting.
An organisation can be getting better at the journey and worse at the experience, and see nothing unusual in its numbers.
What Actually Shifts It
Four things change the picture:
- Rank the exceptions by volume, and treat the top handful as products rather than incidents.
- Name one person accountable end to end for each, whichever functions the work passes through.
- Measure elapsed time to resolution for the customer, not response time inside each team.
- Feed every exception back into the design of the thing that failed.
The last one is where the value compounds. Handling a failure well is service. Removing the cause of it is design — and only one of those gets cheaper over time.
The Uncomfortable Part
All of this asks a function to accept accountability for work happening outside its boundary, and to be measured on an outcome it does not fully control.
Most organisations avoid that, and not unreasonably — it cuts directly against the way budgets, targets and bonuses are set. Changing it is a decision about accountability, which means it belongs to the executive rather than to whoever owns the customer experience programme.
It is also why so many of those programmes deliver a better website and an unchanged reputation.
Nobody talks about the transaction that worked. They talk about what you did the day it didn’t.