The UX Paradox
The better UX teams become at their jobs, the harder it becomes for organizations to recognize their value.
It sounds absurd.
If UX contributes to better products, improved customer experiences, and stronger business outcomes, shouldn’t its impact become more obvious over time?
In practice, the opposite often happens.
Design, especially UX, is frequently introduced into organizations with the best intentions. Sometimes leaders have experienced the benefits of working with design elsewhere and want to recreate that success. Other times, they encounter research demonstrating the connection between design maturity and business performance. Either way, organizations increasingly recognize that design matters.
Yet good intentions rarely change existing systems.
When leaders ask:
- How much value does UX provide?
- How should we measure UX’s impact?
- How much should we invest in UX?
the answers are often filtered through management approaches designed for a different kind of work.
Historically, organizations measured success through outputs: the production of planned quantities to required specifications within expected timeframes. These measures worked exceptionally well in environments characterized by predictability, repeatability, and control.
UX presents a different challenge.
A village stood beside a dangerous river.
One day, villagers spotted a drowning boy and rushed to pull him to safety. Soon another appeared. Then another.
Leaders organized rescue efforts.
More volunteers were recruited.
The village became increasingly efficient at saving drowning boys.
One leader quietly walked upstream.
Hours later she returned.
The boys had been attempting to cross the river on unstable rocks. She had begun building a bridge.
The villagers were confused.
“Why weren’t you helping us save the boys?” they asked.
“I was,” she replied.
Organizations naturally celebrate rescuers.
They reward the teams that solve urgent problems, recover troubled initiatives, and respond quickly to customer complaints. These contributions are visible. Immediate. Measurable.
Bridge builders face a different reality.
Researchers who challenge assumptions before development begins.
Designers who simplify experiences before customers become frustrated.
Teams that prevent support calls, abandonment, and costly rework before they occur.
Their successes leave little evidence behind.
This reveals the UX Paradox:
The better UX is at preventing poor experiences, the less evidence remains that those problems existed in the first place.
The confusing workflow never reaches production.
The unnecessary feature is never built.
The customer never abandons the task.
The support ticket is never submitted.
Organizations searching for visible proof of value often overlook preventative work precisely because it succeeded.
After all, no one remembers the boys who never fell into the river.