Seven signs your product needs a UX audit

Do you need one?

You probably need a UX audit if people regularly get stuck on an important task and your team can’t agree why, or what to do about it. That second part matters. A product with known problems and a clear plan doesn’t need an audit. A product with a vague sense that “something’s off” and five competing opinions usually does.

Here are the signs we look for when a team gets in touch.

1. Support keeps answering the same questions

“How do I add a colleague?” “Where do I find last month’s report?” When the same questions arrive every week, the product is telling you where it’s unclear. Support tickets are some of the best free evidence you have, and an audit can connect each recurring question to the exact screen or state that causes it.

2. People sign up but never get going

Sign-ups look healthy, but too few accounts reach the point where the product becomes useful: data connected, a colleague invited, a first request completed. Something between “account created” and “first real outcome” is losing people. Analytics can show you where. It usually can’t show you why.

3. Your analytics show where, but not why

You can see a drop-off on step three of a setup flow. Is it a confusing field? A permission the user doesn’t have? A document they need to fetch from someone else? An expert walk through the journey, with your data alongside it, narrows that down quickly.

4. The team has a long list of ideas and no agreement

Product wants a new dashboard. Engineering wants to fix the forms. Sales says the onboarding is the problem. Everyone has a point, and nobody has a shared basis for choosing. A good audit gives you a ranked list with the reasoning attached, so the decision becomes about evidence rather than who argues best.

5. A feature that started simple has grown awkward

It began as one form. Then came approvals, then exceptions, then a second user role, then a bulk action. Each addition made sense on its own. Together, they’ve turned a simple task into something people avoid. That’s very common in B2B products, and it’s hard to see from the inside.

6. You’re about to commit to a redesign

An audit can help avoid committing engineering time to the wrong problem. Before you spend a quarter rebuilding something, a focused review can give you evidence to decide where that effort belongs. On a supervision platform for a global investment bank, the research separated interface problems from technical and operational ones before any redesign started. That kept the design effort on the issues design could fix.

7. Your designers are too close to it

This isn’t a criticism. When you’ve lived with a product for two years, you stop seeing the rough edges, and you know the workarounds by heart. A fresh, experienced pair of eyes can spot what your team has learned to step around.

When you don’t need one

Skip the audit if:

• You already know what’s wrong and have evidence to support it. Go straight to design.
• You don’t yet understand your users or their context. Start with research instead.
• You need a formal accessibility conformance report. That’s a specialist WCAG audit, which is a different job.

Not sure which fits? Tell us about the workflow and we’ll give you an honest view, even if the answer is that you don’t need us.