When a team brings us in to help with their product, the conversation usually starts with the roadmap. What should we build next? How do we improve retention? Why is conversion underperforming? These are the right questions. But before we answer any of them, we ask to audit the product first.
More often than not, the audit changes everything.
What we find in almost every audit
In fifteen years of auditing digital products, certain patterns appear with remarkable consistency. Onboarding flows that assume too much prior knowledge. Navigation that made sense to the people who built it but confuses everyone else. Error messages that describe a system state rather than helping a user recover. Forms with unnecessary fields that quietly kill conversion.
None of these issues are the result of bad intentions. They are the result of proximity. When you are close to a product for long enough, you stop being able to see it as a new user does. The audit restores that perspective.
The cost of skipping it
Teams that skip the audit and go straight to building new features consistently make the same mistake: they add solutions on top of undiagnosed problems. New features do not fix broken foundations. They obscure them.
We have worked with teams who spent six months building a retention feature, only to discover through an audit that the core reason users were leaving was a confusing onboarding step that took two weeks to fix. The audit would have cost them three weeks. They spent six months instead.
What a good audit delivers
A well-executed UX audit gives you three things: a clear picture of where users are experiencing friction, a prioritised list of changes ranked by effort and impact, and a shared language across design, product, and engineering for what needs to change and why.
It replaces opinion with evidence. Instead of debating what might be wrong, you know what is wrong. That clarity is worth more than almost any feature you could build.
When to commission one
Before a major roadmap planning cycle. Before a rebrand or redesign. When metrics are declining and you do not know why. When a new leadership team inherits a legacy product. These are the moments when an audit pays for itself many times over.
The best time to audit was before you started building. The second best time is now.
When teams ask what to build next, we start by auditing the product.
Roadmaps, retention ideas, and conversion experiments are important, but they sit on top of something more fundamental: how the current product actually works for real users. Without that understanding, teams end up shipping features onto shaky foundations.
What audits usually uncover
Across fifteen years of audits, the same issues appear again and again:
- Onboarding that assumes too much prior knowledge.
- Navigation that makes sense to the builders, but not to new users.
- Error messages that describe system states instead of helping users recover.
- Forms with unnecessary fields that quietly destroy conversion.
These problems don’t come from incompetence; they come from proximity. When you live inside a product, you internalise its logic and lose the ability to see it as a first-time user. A good audit restores that lost perspective.
The cost of skipping the audit
Teams that skip the audit and jump straight into feature work repeat the same pattern: they layer solutions on top of undiagnosed problems. New features don’t repair broken foundations; they hide them.
We’ve seen teams spend six months building a retention feature, only to discover that churn was driven by a single confusing onboarding step that took two weeks to fix. An audit would have taken three weeks. They spent half a year instead.
Features are visible and celebrated. Friction is invisible until you measure it. The audit makes friction visible.
How a good audit works
A strong audit blends expert review with real user data:
- Heuristic evaluation to check the product against established usability principles.
- Analytics funnels to pinpoint where users drop off.
- Session recordings to see what users actually do.
- Search terms and support tickets to surface the problems users care enough to ask about.
The power comes from triangulation. No single source is enough, but together they tell a coherent story about where users struggle and why.
The output is not a raw list of issues. It’s a prioritised action plan: what to fix first, why it matters, and how much effort it will likely take. Long, unstructured issue lists paralyse teams. Prioritised roadmaps get them moving.
What a good audit delivers
A well-run UX audit gives you:
- A clear map of where users experience friction.
- A prioritised backlog of improvements, ranked by impact and effort.
- A shared language across product, design, and engineering about what needs to change and why.
It replaces opinion with evidence. Instead of debating hypotheses in circles, the team aligns around a single, evidence-based starting point.
When to commission an audit
An audit pays for itself at key inflection points:
- Before major roadmap planning.
- Before a rebrand or redesign.
- When metrics are slipping and the cause isn’t clear.
- When new leadership inherits a legacy product.
- Before investing heavily in growth, to ensure the product can convert and retain the traffic you’re about to buy.
Teams that audit regularly don’t wait for crises. They catch issues when they’re still cheap to fix, instead of wrestling with them once they’ve hardened into expensive, systemic problems.
The best time to audit was before you started building. The second best time is now.
When teams ask what to build next, we start by auditing the product.
Roadmaps, retention ideas, and conversion experiments matter, but they all sit on top of something more fundamental: how the current product actually works for real users. Without that understanding, teams end up shipping features onto shaky foundations.
What audits usually uncover
Across fifteen years of audits, the same issues appear again and again:
- Onboarding that assumes too much prior knowledge.
- Navigation that makes sense to the builders, but not to new users.
- Error messages that describe system states instead of helping users recover.
- Forms with unnecessary fields that quietly kill conversion.
These problems don’t come from incompetence; they come from proximity. When you live inside a product, you internalise its logic and lose the ability to see it as a first-time user. A good audit restores that lost perspective.
The cost of skipping the audit
Teams that skip the audit and jump straight into feature work repeat the same pattern: they layer solutions on top of undiagnosed problems. New features don’t repair broken foundations; they hide them.
We’ve worked with teams who spent six months building a retention feature, only to discover that churn was driven by a single confusing onboarding step that took two weeks to fix. An audit would have taken three weeks. They spent half a year instead.
Features are visible and celebrated. Friction is invisible until you measure it. The audit makes friction visible.
How a good audit works
A strong audit blends expert review with real user data:
- Heuristic evaluation to check the product against established usability principles.
- Analytics funnels to pinpoint where users drop off.
- Session recordings to see what users actually do.
- Search terms and support tickets to surface the problems users care enough to ask about.
The power comes from triangulation. No single source is enough, but together they tell a coherent story about where users struggle and why.
The output is not a raw list of issues. It’s a prioritised action plan: what to fix first, why it matters, and how much effort it will likely take. Long, unstructured issue lists paralyse teams. Prioritised roadmaps get them moving.
What a good audit delivers
A well-run UX audit gives you:
- A clear map of where users experience friction.
- A prioritised backlog of improvements, ranked by impact and effort.
- A shared language across product, design, and engineering about what needs to change and why.
It replaces opinion with evidence. Instead of debating hypotheses in circles, the team aligns around a single, evidence-based starting point.
When to commission an audit
An audit pays for itself at key inflection points:
- Before major roadmap planning.
- Before a rebrand or redesign.
- When metrics are slipping and the cause isn’t clear.
- When new leadership inherits a legacy product.
- Before investing heavily in growth, to ensure the product can convert and retain the traffic you’re about to buy.
Teams that audit regularly don’t wait for crises. They catch issues when they’re still cheap to fix, instead of wrestling with them once they’ve hardened into expensive, systemic problems.
The best time to audit was before you started building. The second best time is now.
