UX teams are obsessed with metrics. But conversion, engagement, and bounce rates don't equal success. Learn why the industry is solving the wrong problem.
The UX industry has become obsessed with a specific set of problems. Conversion rates. Bounce rates. Time on page. Task completion rates. A/B test results. Heatmaps. Session recordings. The industry measures everything. It optimizes everything. And in doing so, it has completely lost sight of what actually matters.
Most UX teams are solving the wrong problem. They're optimizing for metrics that correlate with success instead of optimizing for actual success. They're measuring behavior instead of measuring outcomes. They're treating symptoms instead of treating the disease.
This has created a strange dynamic in the UX industry. UX teams are more sophisticated than ever. They have better tools. Better data. Better techniques. Yet the products they're designing often feel less thoughtful than products designed a decade ago. User satisfaction hasn't improved. Business outcomes haven't improved. But UX teams have never been busier.
The problem isn't that UX teams aren't trying hard enough. The problem is that they're trying to solve the wrong problem.
Over the past decade, the UX industry has developed a particular orthodoxy. There's a set of metrics that matter. There are specific techniques that work. There's a playbook for success. And most UX teams follow this playbook religiously.
The playbook says: measure everything. Track user behavior obsessively. Run A/B tests constantly. Optimize for engagement. Optimize for retention. Optimize for conversion. Remove friction. Simplify workflows. Make everything faster. Make everything more obvious.
This playbook has produced some real benefits. Websites load faster than they used to. Navigation is more intuitive. Forms are simpler. Transaction completion rates are higher. By almost every metric you can measure, digital products are better optimized than they've ever been.
But something got lost in the optimization. Somewhere along the way, the industry stopped asking what users actually wanted and started asking how to get users to do what the company wanted.
Real example: A B2B SaaS company spent eighteen months optimizing their onboarding flow. They reduced friction. They simplified steps. They ran dozens of A/B tests. Task completion rates went up thirty percent. But customer satisfaction went down. Why? Because the onboarding flow was optimized to get customers to activate quickly, not to help them understand the product. Customers got through onboarding faster but understood less. They were confused. They churned.
The UX team had optimized for the wrong metric. They optimized for task completion. They should have optimized for customer understanding.
The problem with the UX industry's orthodoxy is that it assumes a correlation between the metrics being measured and actual success. If conversion goes up, we succeed. If engagement goes up, we succeed. If bounce rate goes down, we succeed.
But these correlations are often broken. You can increase conversion rates and still lose customers. You can increase engagement and still have churning users. You can optimize for metrics and optimize your business straight into failure.
Real example: A productivity app optimized for session length. They made the interface more engaging. They added subtle notifications to encourage returning. Session length went up fifty percent. But users weren't getting anything done. They were using the app more but accomplishing less. The optimization was counterproductive.
Real example: A social platform optimized for daily active users. They made the feed more engaging. They gamified interactions. DAU went up dramatically. But the community became toxic. Users were spending more time but having worse experiences. The optimization undermined the actual mission of the platform.
Real example: An e-commerce site optimized for add-to-cart rates. They made checkout easier. They reduced cart abandonment. Add-to-cart rates went up. But so did return rates. Customers were adding things to cart impulsively and then regretting purchases. The optimization created short-term metrics wins and long-term business losses.
The UX industry has become skilled at moving metrics. But metrics are not outcomes. And outcomes are what actually matter.
If the UX industry is optimizing for the wrong problem, what is the right problem?
The right problem is: are users accomplishing their actual goals? Not the goals the company wants them to accomplish. But the goals they came to the product to accomplish. Is the product helping them succeed?
This is a fundamentally different question than the ones the industry typically asks. It's harder to measure. It's harder to optimize for. It requires deeper understanding of what users are actually trying to do. It requires research. It requires judgment. It can't be reduced to a single metric.
But this is what actually matters. Users don't care about conversion rates. Users don't care about engagement metrics. Users care about whether your product helps them accomplish what they're trying to accomplish. If it does, they'll use it, they'll pay for it, and they'll tell others about it. If it doesn't, they'll leave regardless of how optimized the interface is.
Real example: A project management tool noticed that users were completing a specific workflow in their app, but then going to a spreadsheet to do the actual work. The workflow was optimized. Task completion was high. But users weren't actually using the system to do the job they were trying to get done. The UX team was solving for the wrong problem. They were optimizing the workflow instead of understanding why users felt the need to leave the tool.
Real example: A learning platform optimized course completion rates. They simplified navigation. They made it easier to consume content. Completion rates went up. But users weren't actually learning. They were going through the motions. The optimization was for the metric, not for the actual goal of learning.
The right problem is helping users accomplish their goals. Not optimizing metrics. Not removing friction for the sake of removing friction. Not simplifying for the sake of simplicity. But genuinely helping users succeed at what they're trying to do.
If optimizing for the wrong problem is counterproductive, why did the industry do it?
The first reason is measurability. Conversion rates are measurable. Engagement is measurable. Task completion is measurable. Whether users are accomplishing their actual goals is harder to measure. It requires research. It requires qualitative understanding. Most organizations prefer what they can measure.
The second reason is control. Conversion rates are within the UX team's control. They can run an A/B test and move the metric. Whether users accomplish their goals is not entirely within the UX team's control. It depends on product strategy, business model, market fit. It's messier.
The third reason is speed. You can optimize a metric in days or weeks. Understanding what users are actually trying to accomplish takes months. Most organizations prioritize speed.
The fourth reason is institutional structure. The UX industry developed around specific roles and responsibilities. UX designers optimize interfaces. Product managers drive features. Researchers understand users. But no one owns the end-to-end problem of whether users are actually succeeding. The specialization creates fragmentation.
The fifth reason is technology. Better analytics tools have made it easier to measure behavior. Heatmaps, session recordings, A/B testing platforms have proliferated. This abundance of measurement capability has created an assumption that if you can measure it, you should optimize it. And if you're optimizing something, you must be improving something. The logic is seductive but flawed.
You can see this problem everywhere if you look for it. Products that are technically well-designed but don't actually help users succeed.
A health app that optimizes for logging frequency. You can log your health data quickly and easily. But the app doesn't help you understand your health or make decisions. It just collects data.
A collaboration tool that optimizes for feature discoverability. Every feature is easy to find. But users don't know which features actually help them work better together. The tool is feature-rich but purpose-unclear.
A financial app that optimizes for investment account openings. Signing up is frictionless. But users don't understand investing. They make poor decisions. They lose money. The optimization was for opening accounts, not for user success.
A communication platform that optimizes for message send rate. Messaging is instant and seamless. But the platform is full of noise. Important messages get lost. Communication actually gets worse even though the tool is technically superior.
In each case, the UX work was sophisticated. But it was solving for the wrong thing.
If the UX industry should stop optimizing for the conventional metrics, what should it optimize for instead?
The answer is user outcomes. Did the user accomplish what they came to the product to accomplish? Are they better off having used the product? Will they use it again? Will they recommend it?
This requires a different approach. It requires understanding not just how users interact with your product but what they're actually trying to achieve. It requires research. It requires empathy. It requires stepping back from the daily optimization grind and asking bigger questions.
Real example: A documentation platform realized users were accomplishing their stated goal (finding information) but not their actual goal (understanding the topic). Users could find answers fast. But they weren't learning. The team shifted focus. Instead of optimizing for search speed, they optimized for comprehension. They added explanations. They added context. They added examples. Search speed went down slightly. But users actually learned. Satisfaction went up. Retention improved.
Real example: A fitness app noticed users were logging workouts regularly (high engagement) but not getting healthier (actual goal). The team shifted focus from engagement metrics to health outcomes. They changed the design to emphasize progress toward health goals instead of logging frequency. Engagement went down. But users got healthier. Retention went up because the product was actually delivering value.
This is what it means to optimize for the right problem. You're optimizing for actual outcomes, not proxy metrics.
The reason the UX industry has been optimizing for the wrong problem is that it has been isolated from product strategy. UX teams optimize the interface. Product teams set the strategy. But the strategy itself is often built around the wrong problem.
If your product strategy is "maximize daily active users," then UX will optimize for engagement. If your product strategy is "maximize conversion," then UX will optimize for friction reduction. The UX team is solving the problem it's been given, even if the problem itself is wrong.
This is why embedded design leadership matters. When design is embedded in product strategy rather than isolated in UX, the entire dynamic changes. Design isn't just optimizing the interface. Design is helping shape the strategy itself.
When Rival embeds into teams, we often find that the product strategy needs rethinking. The business has been optimizing for the wrong metric. The team has been solving the wrong problem. Design can help reframe the conversation around actual user outcomes rather than proxy metrics.
We help teams ask: what are users actually trying to accomplish? What would make them successful? How do we know if they're succeeding? What metrics actually matter? Once you answer these questions, optimization becomes much more productive.
If your UX team has been optimizing for the wrong metrics, how do you shift course?
Start by understanding what users are actually trying to accomplish. Go beyond your product. Understand their broader context. What's the job they're trying to get done? What's their actual measure of success?
Then audit your metrics against this understanding. Which metrics actually correlate with users accomplishing their goals? Which metrics are vanity metrics that feel good but don't matter?
Then reorient your optimization work. Stop optimizing for the proxy metrics. Start optimizing for actual outcomes. If users aren't accomplishing their goals, then you haven't succeeded, even if engagement is up.
Then involve your whole team in this reorientation. Product, design, engineering, data. Make sure everyone understands what you're actually optimizing for and why.
This is what we do at Rival. We help teams step back from the daily optimization grind and think strategically about what actually matters. We help them understand their users' real goals. We help them build products around those goals instead of around proxy metrics.
We also help teams move faster toward this goal. Because while this reorientation takes time, the payoff is huge. Products built around actual user outcomes have better retention, better satisfaction, and better business results than products optimized for vanity metrics.
The UX industry is at an inflection point. The conventional orthodoxy of measuring everything and optimizing metrics has run its course. It's created products that are technically polished but strategically hollow. Products that move metrics but not people.
The next phase of UX maturity is shifting from metrics optimization to outcome optimization. It's about understanding what users are actually trying to accomplish and designing around that. It's about measuring whether users succeed, not whether they click.
This requires a different skillset. It requires less analytics expertise and more strategic thinking. It requires less A/B testing and more customer understanding. It requires less optimization and more intentionality.
The teams that make this shift will build better products. They'll have happier customers. They'll have more defensible businesses. They'll move faster because they're solving the right problem instead of optimizing metrics endlessly.
Because ultimately, UX isn't about metrics. It's about whether your product helps people succeed. And until the industry optimizes for that, it will continue optimizing for the wrong problem.
That's why the UX industry needs to change what it's optimizing for.
Founders ship features. Smart founders make design decisions. Learn why positioning, brand clarity, and customer understanding drive startup valuation.
Clicks aren't intent. Learn why most teams optimize for the wrong metric - and how to design products around what users actually mean, not what they click.