The difference between fixing UX and fixing the product

Sometimes that works.

But quite often, it doesn’t.

The reason is that not all problems are UX problems.

Some are product problems.

I’ve been brought into projects where the brief was to improve the experience, but within a short amount of 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 journeyglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ halfway through. The assumption was that the flowglossary×DelightMoments that exceed user expectations.Open glossary term→ was confusing, that the design needed simplifying, or that 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→ wasn’t doing enough to guide them. When we looked closer, the real issue was that the product itself wasn’t aligning with what users expected at that point in the journey. They weren’t dropping off because they were lost, they were dropping off because what they were being offered didn’t feel right.

No amount of UX refinementglossary×RefinementRefinement is the process of preparing and clarifying backlog items before development.Open glossary term→ fixes that.

That’s usually the difference.

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 journeyglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ so it’s easier to follow.

You can make decisions clearer.

You can 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→ in how people move from one step to the next.

All of that improves the experience.

But if the underlying proposition is off, if the flowglossary×DelightMoments that exceed user expectations.Open glossary term→ is asking for the wrong things, or if the product doesn’t meet expectations at the right moment, those improvements only go so far.

You’re making something smoother, not necessarily better.

I’ve seen this across different types of work.

In eCommerce, it often shows up as users hesitating at the point of purchase. The instinct is to optimise the checkout, reduce steps, or 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 in cases where 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. Journeysglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ 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.

This is where things can go wrong.

If everything is treated as a UX problem, 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 CauseThe underlying reason a problem exists.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.

The shift happens when you’re willing to step back.

To look at the journeyglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ 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 sits.

In my experience, the most effective work comes from being able to move between both.

Understanding how to improve 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.

Because if the product is wrong, better UX just helps people realise it faster.