UX teams across the country are being told to stop talking about their work the way they have for years. The message, delivered in a New York report dated July 3, is blunt: report business outcomes, not activity. The advice is concrete, and for teams that follow it, the next steps are equally concrete.
The first decision is immediate. Any UX team preparing for a budget meeting this quarter needs to scrub its presentation.
Data from usability tests and user quotes are valid, the report states. But valid doesn’t mean persuasive. Executives think in terms of revenue, retention, and cost savings.
So the next step is translation. A finding that “users can’t find the cancel button” becomes “the redesign reduced cancellation-related support calls by a measurable amount.” That shift is the whole point.
The timeline for change is tight. Budget conversations happen on a cycle. If a team waits until the week before the meeting to reframe its work, it has already lost.
The practical upshot is a shift that has to happen now, inside the team, before any executive sees a slide. Teams need to decide which metrics they will track and how they will tie their research to those numbers. Did the conversion rate move?
Did support tickets drop? Did customer churn improve?
Those are the questions that get answers in a budget meeting. There is a second consequence for the average person. The apps and websites used every day are shaped by these internal conversations.
When a UX team loses a budget fight, the features that could make life easier — clearer navigation, simpler checkout flows — don’t get built. The report makes this explicit.
So the next time an app update feels useless, the reason might trace back to a team that reported the wrong numbers. For UX managers, the next step is a hard look at their own reporting. The problem is not that their work isn’t valuable.
The report says that outright. The problem is how the work gets framed. A product manager walks into a budget meeting and says the team ran several usability sessions and found that users struggled with the checkout flow.
That statement is true. It also gets a polite nod and then gets skipped over when real allocation happens.
The fix is not doing better research. The fix is describing the research differently. There is no single date to watch.
Instead, there is a pattern. Every budget cycle is a test.
Teams that make the shift will get the line item. Teams that don’t will keep getting the polite nod. The report gives the example of a usability finding about a cancel button.
One version gets a shrug. The other gets a line item in next quarter’s budget. That is the only metric that matters.
The advice is not about abandoning user-centered methods. It is about translating those methods into the metrics that drive business decisions.
The next step for any UX team is to decide which metric to chase. Revenue. Retention.
Cost savings. Pick one.
Then prove the work moved it.
