The difference between fixing UX and fixing the product

Some are product problems. I've been brought into projects where the brief was to improve the experience, but within a short time it became clear that the issue wasn't how things were presented. It was what was being presented.

In one case, users were abandoning a journey halfway through. The assumption was that the flow was confusing or the interfaceglossary×InterfaceAn interface is the point of interaction between a user and a system, where inputs are made and outputs are received. It can be visual, physical, or conversational.Open glossary term→ needed simplifying. When we looked closer, users weren't dropping off because they were lost. They were dropping off because what they were being offered didn't feel right at that point in the journey. No amount of UX refinementglossary×RefinementRefinement is the ongoing work of clarifying, breaking down, and sizing backlog items before they enter development. It is where ambiguity gets resolved while resolving it is still cheap.Open glossary term→ fixes that.

Fixing UX is about improving how something works. Fixing the product is about questioning whether it should work that way at all. You can refine a journey so it's easier to follow, make decisions clearer, and reduce frictionglossary×FrictionFriction refers to anything that slows users down or makes it harder for them to complete a task. It can be caused by poor design, unnecessary steps, unclear messaging, or technical issues.Open glossary term→ between steps. All of that improves the experience. But if the underlying proposition is off, those improvements only go so far. You're making something smoother, not necessarily better.

There is a rough way to tell which one you are looking at. If you fixed every usabilityglossary×UsabilityUsability is how easy and efficient it is for users to complete tasks within a product. It focuses on clarity, simplicity, and reducing effort so users can achieve their goals without confusion or friction.Open glossary term→ issue on the list, would the numbers move enough to matter? When the honest answer is no, the problem is not in how the thing is presented, and more refinementglossary×RefinementRefinement is the ongoing work of clarifying, breaking down, and sizing backlog items before they enter development. It is where ambiguity gets resolved while resolving it is still cheap.Open glossary term→ will keep confirming that expensively.

In eCommerce, it often surfaces as users hesitating at the point of purchase. The instinct is to optimise the checkout, reduce steps, improve trust signalsglossary×Trust SignalA trust signal is any element that increases user confidence in a product, service, or decision.Open glossary term→. Sometimes that helps. But when the issue is pricing clarityglossary×ClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term→, deliveryglossary×DeliveryDelivery is the process of building, testing, and releasing a product or feature.Open glossary term→ expectations, or product information, the friction isn't coming from the UX layer. It's coming from the product itself.

In more complex systemsglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→, it can be even more pronounced. Journeys are designed around how the organisation works, rather than what the user needs. UX can make those journeys easier to navigate, but it can't remove the mismatch between the product and the user's expectations.

The patternglossary×PatternA pattern is a reusable solution to a design problem that recurs across products and contexts. It captures an approach already shown to work, so a team solves the problem once rather than every time it appears.Open glossary term→ is usually visible in where people leave. Drop-offglossary×Drop-offDrop-off refers to users leaving a journey before completing a desired action or reaching the next step.Open glossary term→ spread evenly across a journey tends to be frictionglossary×FrictionFriction refers to anything that slows users down or makes it harder for them to complete a task. It can be caused by poor design, unnecessary steps, unclear messaging, or technical issues.Open glossary term→, and friction is a UX problem. Drop-off concentrated at one point, immediately after a specific piece of information appears, is usually the product, and it is telling you something about the offer rather than the interface.

You end up constantly refining the interfaceglossary×InterfaceAn interface is the point of interaction between a user and a system, where inputs are made and outputs are received. It can be visual, physical, or conversational.Open glossary term→ without ever addressing the root causeglossary×Root CauseA root cause is the underlying reason a problem exists, as distinct from the symptom it presents as. Removing it stops the problem recurring; addressing only the symptom means meeting the same issue somewhere else.Open glossary term→. The experience improves incrementally, but the core issue remains, and users continue to feel it. Over time, that leadsglossary×LeadA lead is a potential customer who has shown interest in a product or service, typically by providing contact information or engaging with content.Open glossary term→ to a lot of effort with limited impact.

It also quietly damages the credibilityglossary×CredibilityCredibility is the perceived trustworthiness and authority of a product, brand, or system.Open glossary term→ of design work. After a few rounds of improvements that did not move anything, the organisation concludes that UX does not deliver, when what actually happened is that UX was asked to solve something outside its reach.

The framing usually comes from how the work was commissioned. A brief that arrives as improve the checkout has already decided the checkout is the problem. A brief that arrives as work out why people are not buying leaves room for the answer to be somewhere else.

The shift happens when you're willing to step back. To look at the journey and ask whether it's structured in the right way. Whether the product is solving the right problem at the right point. Whether the user is being asked to do something that could be handled differently.

That's not always a comfortable conversation, because it often challenges decisions that have already been made. But it's where the real value is. The most effective work comes from being able to move between both: improving the experience within existing constraintsglossary×ConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term→, but also recognising when the problem sits deeper and needs a different approach.

Sometimes it's about refining. Sometimes it's about rethinking. Knowing the difference is what stops you spending time fixing the wrong thing.

Raising it well matters as much as spotting it. Arriving with the interfaceglossary×InterfaceAn interface is the point of interaction between a user and a system, where inputs are made and outputs are received. It can be visual, physical, or conversational.Open glossary term→ problems solved, and the evidence that solving them changes little, is a very different conversation from opening with the proposition being wrong. The first is a finding. The second sounds like an opinion about somebody else's decision.