One thing I’ve learned about user experience is that customers don’t always tell you when something is difficult.

They might complete a task without complaining. They might develop a workaround and carry on. They might even tell you the product is easy to use because they’ve become accustomed to its limitations.

But that doesn’t mean the experience is frictionless.

Some of the most valuable UX insights come from noticing what users do, rather than relying entirely on what they say.

Watch for Hesitation

When users pause unexpectedly, reread instructions, or move their cursor back and forth between options, something may not be clear.

A pause doesn’t automatically mean confusion. Users may simply be thinking.

But repeated hesitation at the same point across multiple sessions can reveal an issue worth investigating.

During usability testing, pay attention to where users stop, what they look at, and whether they need help deciding what to do next.

These moments can reveal uncertainty that a direct question might miss.

Look for Repeated Actions

Users sometimes repeat an action because they aren’t sure it worked.

They click a button twice, refresh a page, resubmit a form, or reopen a section to check whether their changes were saved.

From an analytics perspective, these may look like ordinary interactions.

From a UX perspective, they could indicate unclear feedback, slow responses, or a lack of confidence in the system.

Ask whether the interface makes the result of each action obvious.

Find the Workarounds

One of the strongest signals of UX friction is the workaround users create.

They export data into spreadsheets, maintain separate notes, copy information between tools, or ask colleagues to complete steps the product should support.

These behaviours often reveal gaps between how the product works and how customers actually work.

For example, if users repeatedly export reports just to combine information manually, the issue might not be the export feature itself. They may be struggling to get a complete view of the information they need.

The workaround is a clue. The underlying problem requires investigation.

Pay Attention to Abandonment

When users leave a workflow halfway through, it’s easy to assume they lost interest.

But abandonment can have several causes.

The process may be too long. A required field may be unclear. Users may discover an unexpected cost. They may not have the information needed to continue.

Look at the exact step where users leave, then combine analytics with usability testing or customer interviews to understand why.

A drop-off metric tells you where to look. It rarely explains the cause by itself.

Notice When Users Ask for Help

Repeated support questions can reveal friction that isn’t obvious from product usage data.

If customers regularly ask how to complete the same task, the problem may be more than a documentation gap.

Perhaps the interface uses unfamiliar terminology. Maybe an important action is difficult to find. Or the workflow requires knowledge users shouldn’t need.

Before adding another help article or tooltip, investigate why users need help in the first place.

Sometimes the best support improvement is removing the confusion from the product.

Don’t Assume Every Behaviour Is a Problem

This is important.

A long pause isn’t always friction. Repeated clicks aren’t always confusion. Abandonment isn’t always a usability issue.

Users have different goals, levels of experience, and working environments.

Treat behavioural signals as hypotheses, not conclusions.

Look for recurring patterns, observe real sessions, and validate your interpretation with customers.

The goal isn’t to eliminate every pause or reduce every interaction. It’s to remove unnecessary effort from meaningful tasks.

Connect Friction to Customer Outcomes

Not every UX issue deserves immediate attention.

Prioritize friction based on how often it occurs, how severe it is, which users experience it, and what happens as a result.

A confusing label on a rarely used setting may be less important than an unclear action that prevents new customers from completing onboarding.

Connecting UX friction to task completion, time to value, adoption, or support volume helps product teams make better trade-offs.

Final Thought

Users don’t always report friction because they may not recognize it, may have learned to work around it, or may simply decide the effort isn’t worth explaining.

That’s why good product teams look beyond feedback forms.

They observe behaviour, investigate workarounds, and pay attention to the moments when users hesitate, repeat actions, or give up.

What users tell you is valuable. What they struggle to do can be just as revealing.