A budget meeting is a bad place to bring a usability test transcript. That is the blunt finding behind a new analysis of how UX teams lose funding wars — not because their work is bad, but because they describe it wrong. The report, released this week, argues that UX professionals routinely frame their findings in terms of activity: how many test sessions were run, how many users were interviewed, what quotes were collected.
Executives, the report states, do not think in those terms. They think in revenue, retention, and cost savings.
A product manager who walks in and says “users struggled with the checkout flow” gets a polite nod. Then the budget allocation moves on without them. The fix is a shift in framing.
Instead of reporting what was done, report what changed. A finding that “users can’t find the cancel button” becomes “the redesign reduced cancellation-related support calls by a measurable amount.” One version gets ignored.
The other gets a line item. This is not about doing better research. The report is explicit: UX teams rarely lose budget conversations because the work lacks value.
They lose because of how the work gets reported. The methods — usability testing, user interviews, journey mapping — are fine. The translation is broken.
The forces behind this are structural. UX teams and executives operate on different metrics.
UX measures behavior. Executives measure money. A usability session is a cost center.
A reduction in support tickets is a saving. Until those two languages connect, the budget fight is lost before it starts.
Where this is likely to lead is a quiet reorganization of how UX work gets communicated internally. Teams that adapt will frame every finding as a business outcome before it reaches a decision-maker. Teams that do not will keep losing budget to features that never get built — clearer navigation, simpler checkout flows, fewer support calls — because the case for them was made in the wrong language.
For the average person using an app or website, the report says, these internal conversations shape the experience. When a UX team loses a budget fight, the features that could make life easier get shelved. The user never knows why.
They just know the button stayed hard to find. The analysis does not name specific companies or executives.
It does not cite a single named source. What it offers is a pattern: a recurring mismatch between how work is done and how it is sold. The practical upshot is a recommendation to stop reporting UX activity and start reporting business outcomes.
The report is not asking researchers to abandon user-centered methods. It is asking them to translate those methods into the metrics that drive budget decisions.
That translation is the hard part. It requires UX teams to track what changes after their work — conversion rates, support ticket volumes, churn numbers. It requires them to speak the language of the people holding the money.
And it requires executives to listen for something other than a cost center. The report suggests the burden falls on the UX side. They are the ones losing the argument.
