Local Maxima in UX

A local maximum in UX (user experience) design happens when a product or experience hits a point where further small improvements seem beneficial but actually block bigger, better changes. Designers fall into this trap by optimizing existing features so much that they miss out on exploring radically better alternatives. For example, a team might keep tweaking a checkout button’s color or shape when the real fix requires rethinking the entire checkout flow.

Local maxima can be difficult to notice. Teams can be so close to the content of their project or have “lived” with a design for so long that they can only focus on fine-tuning existing material. To avoid a rude awakening on the release of a final product, teams should carefully conduct usability tests or user interviews to uncover deeper pain points. For those who are stuck at a local maximum, the results users give should help instill the insight and “courage” to ask: “What if we started from scratch?”

Discover a wealth of insights and tips in our Master Class How to Get Started with Usability Testing with Cory Lebson, Principal and Owner - Lebsontech LLC.

You know your UX has hit a local maximum when improvements stop moving the needle. Users still face frustrations, but A/B tests on minor tweaks—like color changes or microcopy edits—show little to no impact. This plateau signals that you've optimized within a flawed system, not redesigned the system itself. Another problem is that web analysts often don't bother to measure the statistical significance of the result, or they ignore it. So, if they see a 2–3% improvement and think they have achieved something, but if the result isn't statistically significant, they'll likely get this amount of change and not improve the design.

Watch for these signs: Conversion rates stagnate. Feedback repeats the same issues. The team spends time refining details, not questioning core flows. If your design reviews focus on polish, not purpose, you're likely stuck. It's like trying to improve a car with a weak engine by making the interior more luxurious and seats more comfortable. It's time to zoom out and see what the “real deal” is with friction points and unmet needs.

Get the lowdown on effective research methods and more to help gain the altitude to spot local maxima, in our course Data-Driven Design: Quantitative Research for UX.

Yes—user feedback can trap you at a local maximum if you only listen to what users say, not what they need. Users often suggest tweaks to existing features, like “move this button” or “make it faster,” instead of challenging the core experience. If you act solely on these suggestions, you’ll polish flaws instead of solving root problems.

Even those few users who might see the deep-lying problems and believe a larger-scale fix or rethink is in order may not say so. It’s largely because they won’t want you to take offense. Many will be too polite to suggest anything so drastic. Watching users closely in tests will tell you much more than listening to their words. Use feedback as a clue, not a roadmap.

Empower your design process by being aware of 4 Common Pitfalls in Usability Testing and How to Avoid Them to Get More Honest Feedback.

To escape a local maximum in UX design, stop refining and start reimagining. You can’t reach a radically better solution by endlessly tweaking the current one. Instead, step back and challenge your assumptions. Ask: “If we started fresh, how would we solve this problem?”

Use journey mapping to spot friction points. Conduct field studies or diary studies to uncover what users actually do—not just what they say. Run design sprints to prototype bold alternatives and test them early.

Tip: Collaborate with people outside your team, like customer support or sales. Their fresh perspectives can spark breakthrough ideas that shake you loose from the local maximum.

One of the perils of local maxima is that designers are often too close to a project to be able to recognize deep-lying problems. Confirmation bias might keep them on the lookout for user feedback that looks positive, while they ignore feedback that says otherwise. It’s like a rotten apple that still looks fine on the outside; hoping users will like it won’t save it.

Explore the constraints of confirmation bias and learn how to overcome it.

You recognize that radical change is necessary when minor fixes no longer deliver results and users face the same core issues. If conversion rates plateau, engagement drops, or usability tests show repeated confusion, it’s a signal: optimization alone won’t cut it.

Ask yourself: “Are we solving the right problem, or just tweaking the wrong solution?” When your team starts debating button colors instead of customer pain points, it’s time to rethink. As annoying as it might seem to have to abandon work on the finer points and return to the “drawing board,” it can save your product from marketplace failure.

Tip: Apply user research and tools like 5 Whys or assumption mapping to uncover root causes. Validate your hunches with field studies or generative interviews. If current workflows no longer support user goals, a redesign (not a revision) is your next step.

User research reveals better directions beyond a local maximum by uncovering unmet needs, hidden pain points, and workarounds that users never articulate. Observing users in context, through field studies, usability tests, or diary studies, lets you spot friction in real time. These insights expose flaws that surface-level tweaks can’t fix.

When you dig deeper with generative methods like ethnography or open-ended interviews, you discover what users want in reality—not just what they say they want. These moments often spark bold design ideas that break free from incrementalism.

Tip: Look for mismatches between what users do and what they say. Those gaps often highlight opportunities for game-changing redesigns. Also, create personas that accurately reflect who needs your product and why. Personas (fictitious representations of real users) can point the way to fundamental changes in a design.

Learn how to research and build personas that promote empathy, align teams, and drive user-centered design in our course, Personas and User Research: Design Products and Services People Need and Want.

Divergent thinking helps overcome local maxima by pushing designers to explore a wide range of possibilities—not just what seems immediately feasible. Instead of narrowing in on quick fixes, divergent thinking encourages big-picture, “what if” ideas that challenge the status quo.

By generating many diverse solutions, you shift focus from refining a flawed design to imagining entirely new directions. This mindset unlocks breakthroughs that incremental changes can't reach. You can gain a perspective that will help you walk away from the problematic approach to one that can work well.

Tip: In ideation sessions, defer judgment. Aim for quantity over quality first. Use tools like mind mapping or “Crazy 8s” to stretch your thinking beyond the obvious.

Expand your mind to accommodate the power and scope of divergent thinking and how it can supercharge your design process.

To pitch a redesign when stakeholders are content, show, don’t just tell, why change matters. Highlight data: stagnant metrics, user pain points, or missed opportunities. Use usability test clips or customer quotes to make the issues real. Stakeholders may not see the cracks because the current design “works,” but that doesn’t mean it works well.

Frame the redesign as a way to unlock value, not just fix flaws. Show how it aligns with business goals: higher conversion, better retention, or expanded reach. Even the most reluctant stakeholders should understand that it’s worth the trouble to do the redesign. How you communicate with them is essential; the facts and figures should be able to convince them.

Tip: Prototype your vision. A quick mockup or interactive flow makes the case far more effectively than a slide deck.

Watch as Todd Zaki Warfel, Author, Speaker and Leadership Coach discusses how to present design work to clients:

Staying too long at a local maximum stifles innovation and leaves your UX vulnerable to disruption. When teams focus only on small optimizations, they risk ignoring deeper user needs. Meanwhile, competitors who address those needs will pull ahead. Users may tolerate friction now, but if a better-designed alternative emerges, they’ll switch.

Over time, your product can become bloated, inconsistent, or outdated because no one questioned the core design. Stagnation invites decline, so it’s essential to strive for the vision to see a product for what it is and be bold enough to do what needs to be done before it’s too late. Your product’s users and brand will be glad you did, too.

Tip: Set regular checkpoints to review the entire user journey—not just performance metrics. Ask, “If we started from scratch today, would we design it the same way?”

Discover exciting new design territory and travel to get some helpful distance on what users and customers really want, with a customer journey map.

Cross-functional teams help break out of local maxima by combining diverse perspectives to challenge assumptions and spark bold ideas. Designers, developers, marketers, and customer support each see the product from different angles. This variety leads to richer insights and more innovative solutions than a siloed team could achieve.

When everyone contributes to ideation and problem-solving, the team is more likely to reframe problems and uncover hidden opportunities. These collaborations shift the focus from tweaking features to redesigning systems. Professionals from different backgrounds can notice things designers themselves might not; the phenomenon called deformation professionnelle can constrain how people view the world.

Tip: Involve cross-functional peers early in discovery—not just during implementation. Host workshops where each role shares user insights and friction points they observe.

Discover what can happen when careers constrain viewpoints and other issues that can affect design teams in our article Deformation Professionnelle and the Dunning-Kruger Effect – When Expertise Isn’t So Great.

KPIs and metrics play a crucial role in spotting local maxima; they show when performance plateaus despite ongoing tweaks—like when conversion rates or engagement stay flat after minor updates. These signals tell you that you’ve likely optimized as far as possible within the current design constraints. It’s like finding a map that tells you what you thought was a mountain is actually a hill.

However, numbers alone won’t explain why growth has stalled; so, pair metrics with qualitative research to uncover root causes and new opportunities. From there, you’ll have a “compass” to find where the real mountain you need to climb is.

Tip: Track more than surface metrics. Watch for deeper indicators like task success rate, time on task, and user frustration signals to spot hidden UX issues.

Explore more about KPIs to see how they can work for your brand, product, and—of course—users.

GeeksforGeeks. (2024, May 14). What are local maxima in UX? GeeksforGeeks.

This article explains the concept of local maxima in UX, highlighting how over-reliance on A/B testing and data-driven approaches can lead to design stagnation. It suggests methods like innovative testing and radical redesign to overcome these challenges, promoting a more user-centric approach to achieve optimal user experiences.

Porter, J. (2010). The local maximum. 52 Weeks of UX.

Joshua Porter discusses the limitations of incremental design improvements and the concept of local maxima. He illustrates how small, data-driven changes can prevent designers from achieving significant breakthroughs, advocating for a balance between optimization and innovation to enhance user experience.

90 Percent of Everything. (2011, January 6). Local maxima and the perils of data-driven design.

This article explores the dangers of a strictly data-driven design approach, using Facebook's experience to illustrate how it can lead to local maxima. It emphasizes the need for a data-informed strategy that considers broader user contexts to avoid design stagnation and achieve more impactful user experiences.