The data on UX ROI is, broadly speaking, correct. Every second of extra friction has a measurable cost. Confusing flows kill conversion. Good design retains users. All of this is true and quantifiable.
And yet most product teams still don't invest consistently in UX. It's not ignorance. The problem is how they're using the metrics.
- Presenting UX data without linking it to a specific decision is noise, not an argument.
- The real challenge isn't proving that UX matters — it's knowing when and where it matters most.
Influence: The Work Nobody Teaches Designers
The biggest obstacle to UX impact inside an organisation isn't technical. It's political. The designers who generate the most value aren't necessarily the ones who produce the best interfaces — they're the ones who know how to translate user findings into product decisions.
A usability insight that doesn't land at the right moment in the right conversation changes nothing. A designer who understands their company's decision-making cycle, and knows when to surface which evidence, moves things forward. At Room 714, when we audit digital products, the first thing we look at isn't the design itself — it's how user information flows toward strategic decisions. There's almost always a serious disconnect there. If this sounds familiar, the issue may be how the UX role is defined in your team, not the quality of the work being done.
Priority: The Friction That Costs Most Isn't Always the Most Visible
The classic mistake when measuring UX ROI is optimising what's already easy to measure: click-through rates, time on screen, NPS. Those are symptoms. The cause is usually further upstream — a confusing label on a form, an expectation the product sets but doesn't fulfil, a flow that breaks before users even get to the measurable part.
The friction that destroys the most value is the kind the user doesn't even name in tests. The kind that makes them leave without ever telling you why.
Identifying that friction requires qualitative research, not just dashboards. And it requires teams that have the mandate and time to go beyond delivery sprints. The lean team with surgical focus model we advocate here fits well: fewer features in volume, more depth on critical pain points. Usability as a decision filter is exactly that approach applied to the daily work of the team.
If your product has friction you can't name — or if your UX metrics aren't connected to any real decisions — it's time for a proper review. Not to hire more designers, but to change how you use the evidence you already have.
