The UX Paradox

The better UX teams become at their jobs, the harder it can become for organizations to recognize their value.

If UX contributes to better products, improved customer experiences, and stronger business outcomes, shouldn’t its impact become more obvious over time?

The better UX is at preventing poor experiences, the less evidence remains that those problems existed in the first place.

Organizations increasingly recognize the importance of UX. Leaders invest in research, hire designers, and seek to build more customer-centered products and services. Yet many continue evaluating UX using management approaches designed for predictable, repeatable work — systems optimized to measure outputs rather than the absence of problems. In my experience, this is where the paradox becomes visible: the investment is real, but the measurement system can only see what gets built, not what gets prevented.

Historically, organizations measured success through production: delivering planned quantities to required specifications on schedule. These approaches work exceptionally well in environments characterized by predictability, repeatability, and control. UX presents a different challenge.

The Village and the River

A well-known public health parable illustrates the problem.

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.

Rescuers and Bridge Builders

UX teams often function as bridge builders.

Organizations naturally celebrate rescuers. They reward the teams that solve urgent problems, recover troubled initiatives, respond quickly to customer complaints, and rescue failing projects. These contributions are visible, immediate, and measurable.

Bridge builders operate differently.

• Researchers challenge assumptions before development begins
• Designers simplify experiences before customers become frustrated
• Teams prevent abandonment, support calls, costly rework, and failed initiatives before they occur

Customer support is one of the clearest places this paradox appears. Support teams see usability issues, onboarding friction, unmet expectations, and workflow breakdowns early — but they are usually measured by resolution speed, not by how much future demand their insights help prevent.

The challenge is that organizational incentives often favor downstream work. It is visible, urgent, and easier to measure. Upstream work requires curiosity, patience, and a willingness to invest before problems fully materialize. Yet this is often where UX creates its greatest value — not by rescuing customers from avoidable frustrations, but by helping organizations prevent those frustrations from occurring in the first place. These incentives are rarely designed on purpose — they’re inherited from whenever and however a discipline first entered the room.

The Paradox

Ironically, success can make this work increasingly difficult to recognize. When prevention works, little evidence remains.

• The confusing workflow is redesigned before release
• The unnecessary feature is never built
• The customer completes their task without frustration
• The support ticket is never submitted
• The expensive rework never occurs

Organizations searching for visible proof of value often overlook preventative work precisely because it succeeded.

Prevention creates a measurement problem: the most valuable outcomes are often the ones that never visibly happen.

Most organizations are better equipped to count activity than to recognize avoided cost, reduced friction, or prevented failure. The earlier a risk is retired, the cheaper it was to fix — and the less anyone can see that there was ever anything to fix. Preventative work rarely generates dramatic stories or obvious metrics. Yet its impact may be no less significant.

Perhaps this is why organizations sometimes struggle to recognize the value of UX. The more effectively UX teams identify opportunities, challenge assumptions, and improve experiences before problems materialize, the fewer visible reminders exist that their contributions mattered in the first place.

After all, no one remembers the boys who never fell into the river.

The implication for UX leaders is clear: prevention cannot remain invisible and still compete for investment.

Making Preventative Work Legible

The paradox is real, but it isn’t unsolvable. The core challenge is that preventative work is invisible by design—when it succeeds, there’s nothing left to point to. So the work of a senior design leader isn’t just doing the preventative work. It’s making it legible to the people who control resources and set priorities.

I approach this in a few ways. The first is documenting before intervention, not after. When I identify a risk—a confusing workflow, a misaligned assumption, a feature likely to generate support load—I write it down before we fix it. I capture what the customer behavior indicated, what the likely downstream effect would have been, and what we changed instead. That record becomes evidence of value that would otherwise disappear.

The second is building visibility into the research process itself. Rather than presenting findings at the end of a discovery cycle, I create lightweight, ongoing touchpoints: a weekly synthesis of what we’re learning, a shared assumption log that stakeholders can see evolving, a short pre-launch risk review that gives names to the problems we didn’t build. These practices make the work of prevention visible to people who aren’t in the room when it happens.

The third is connecting upstream decisions to downstream outcomes, in both directions. When a support ticket reflects a workflow we simplified six months earlier, I note it. When a retention metric improves after an onboarding redesign, I attribute it. Over time, this builds an organizational memory that preventative work is real—that the bridge builder’s contribution is as meaningful as the rescuer’s, even when the river is running quiet.

The organizations I’ve seen do this well treat UX metrics as a leading indicator of product health, not a trailing measure of design output. Getting there requires deliberate practice, not just goodwill. That’s the work I help teams build.