The signs your product has a UX problem

Nobody files a ticket that says "your information architecture is wrong". They file a ticket that says "how do I re-send an invoice", and they file it every day, and each one gets answered politely and closed, and nobody ever sees the full pattern for what it is: a record of exactly where the product fails its users.

Here are the signals worth trusting, where to find each one, and how to confirm what they are telling you before spending money on a redesign.

The signals, in rough order of reliability

Support tickets that ask how, not whether. A "does your product do X" ticket is a marketing gap. A "how do I do X" ticket, when X is something the product does, is a design gap: the capability exists and the interface hid it. Pull a month of tickets and sort them. If the same how-do-I question appears again and again, you have found a screen that is not doing its job, and you know exactly which one.

Drop-off concentrated at one step. Funnel data shows clearly where people give up. A gradual loss of users through a long flow is normal. A sudden large drop at one step identifies the problem: whatever that screen asks, people cannot or will not answer it. The step itself tells you what to test first.

The spreadsheet that replaces the product. When users export your data and run their real work in a spreadsheet, they are telling you the product's model of their work is wrong. They wanted the data; they did not want your workflow. The same signal appears as browser bookmarks that deep-link past your navigation, or as the one power user in the customer's office who operates the product on behalf of everyone else.

Demos that need an expert. If sales cannot let a prospect touch the product, and onboarding requires a call, the interface cannot explain itself. Watch what the sales engineer says while operating it: every phrase like "so what this screen is really showing you" is an explanation for something the design failed to communicate.

Feature usage that never spreads. Analytics showing most users using a small part of the product can mean a focused product. It can also mean the rest is undiscoverable. The sign is the gap between what customers asked for and what they use: when people requested a capability, got it, and still do not use it, the problem is almost never demand.

The signals that are not UX problems

Two similar-looking problems waste redesign money regularly, so name them before spending. Low signups with good activation is a marketing and positioning problem: the people who arrive succeed, there are just not enough of them, and no interface change fixes having too few people at the first step. And high activation with high churn weeks later usually means the product solved a problem people do not have often enough, which is a discovery question about what you built, not a usability question about how. A redesign aimed at either of these will use up three months and change nothing, because the failure happens before users reach the screens.

Confirming it before you spend

Every signal above has an innocent explanation, which is exactly why teams argue about them for months. The way to end the argument is watching real users.

The method is small and public. Recruit a handful of actual users, give them the real task the funnel says they fail at, and watch without helping. Jakob Nielsen's long-standing finding is that about five users find most of the usability problems in a design, roughly 85% of them, which is why the confirmation step costs days, not months. The goal is to see the problem rather than measure it precisely, because a team that has watched three people fail the same way stops arguing about whether the problem exists.

Be strict about one thing: watch behavior, not opinions. Users are polite. They will say the product is fine and then fail the task in front of you. What they do is the data.

What a real fix looks like

A confirmed UX problem is rarely fixed by changing colors and styles, because the look was rarely the problem. The fix usually changes how the product works: reordering a flow around how users think, cutting choices that were only there because they were easy to add, making the important number easy to read and giving less space to the rest.

That last pattern is common in analytics-heavy products. A platform can hold genuinely powerful analytics that everyday users cannot act on, because the screens show everything with equal emphasis. The fix starts by auditing which numbers people actually use, rebuilding the experience around that smaller set, and moving the rest behind a drill-down. Nothing about the underlying data changed. What changed is that users could finally see it.

And the returns on this class of fix are unusually well documented. Nielsen Norman Group's surveys of usability redesign projects found large average improvements in the KPIs the redesigns targeted: 83% in their recent survey, 135% in the earlier one. Your result will be your own, but the direction is clear. Removing the places users fail tends to show up in the numbers that depend on users succeeding.

Deciding what to do next

If the signals are ambiguous, buy the cheap confirmation first: a short round of watched sessions on the core task. If they are strong, the question is scope: one flow, or the product's whole model of the work. One flow is a focused engagement. A wrong model is closer to re-discovery, covered in what product discovery delivers. Either way, agree the metric before the redesign starts, so six months later the argument is not about taste. Choosing who does the work is its own decision, covered in how to choose a product design agency.

Most teams are in the same situation: the evidence arrives daily, spread across inboxes where no single person sees the whole pattern. Collect it once, watch five users, and the argument usually ends in an afternoon.