A UX audit is a structured review of a digital product's user experience — where it confuses people, where it costs them time or money, and where the risk of a costly mistake is highest. Done well, it produces prioritized, evidence-backed findings you can act on. Done badly, it's a Nielsen-10 checklist with a different logo on the cover.
This page explains what a UX audit actually is, the process, a practical checklist, and how to tell whether you need one. If you're ready to commission one, see the Full UX Audit service.
What a UX audit actually is
A UX audit is not a usability test (you're not watching users), and it's not a visual-design critique. It's an expert review that scores an existing product against how much each interaction matters — then tells you what to fix first.
The audits that change anything share three traits:
- Scored, not narrated. Every screen gets a number, so you can compare and prioritize instead of reading 40 pages of prose.
- Risk-weighted. Findings are ranked by what a mistake actually costs the user and the business — not by how "ugly" something looks.
- Prioritized output. You get a short list of the highest-leverage fixes, each labeled P0/P1/P2, not an undifferentiated backlog.
A UX audit's job is to tell you what to fix first — not to list everything that's wrong. A list of 80 issues with no priority is a liability, not a deliverable.
When you need a UX audit
Commission a UX audit when:
- Conversion or activation is leaking and you can't see where.
- You're about to redesign and want a baseline of what's actually broken (so the redesign fixes problems instead of moving them).
- Stakes are rising — payments, healthcare, compliance, anything where a user error is expensive or irreversible.
- The product has grown and clarity has eroded as features piled up (the classic SaaS-dashboard-at-scale failure mode).
Skip the audit if you're pre-product-market-fit (go run a usability test instead) or building a pure-engagement consumer product where "risk" is engagement-defined, not harm-defined.
The UX audit process
- Scope the surfaces. Identify the flows that carry the most weight — onboarding, checkout, the core task loop — rather than auditing every screen equally.
- Score each surface on three axes. Stakes (worst-case cost of an error), reversibility (how long until a mistake is irrecoverable), and cadence (how often users perform the action). Regulation and best-practice fall out of these — not the other way around.
- Gather evidence. Annotated screens, the rule or heuristic each issue violates, and the realistic consequence.
- Prioritize. Rank findings P0 (ship this sprint), P1 (next quarter, monitored), P2 (backlog).
- Report. A scored rubric, 3–5 prioritized findings, and a one-page exec summary for the person who has eight minutes between meetings.
The full scoring methodology is written up in What a real UX audit looks like.
UX audit checklist
A quick checklist to pressure-test any audit — yours or a vendor's:
- [ ] Is every finding tied to a consequence, not just a guideline?
- [ ] Are findings prioritized (P0/P1/P2), or is it a flat list?
- [ ] Does it score by risk and frequency, not aesthetics?
- [ ] Can a stakeholder grasp the top issues in one page?
- [ ] Does it say what to do first — and what to ignore?
- [ ] Are the highest-stakes flows (payments, irreversible actions) covered first?
If an audit fails half of these, it's a heuristic walkthrough wearing an audit's name.
What you get from a UX audit
A real UX audit leaves you with three things: a scored rubric (one number per screen per axis), 3–5 prioritized findings with evidence and a proposed fix, and a one-page executive summary. That's enough to decide, sequence, and ship — without reading a report nobody has time for.
Ready to commission one? Apply for a Full UX Audit →