Skip to content
UI/UX15 min read

How to Conduct a UX Audit: A Step-by-Step Guide

A step-by-step UX audit workflow: set goals, gather evidence, run expert and user reviews, rate severity, prioritize fixes and write a report teams act on.

01

Quick answer

To conduct a UX audit, agree what the audit is for and which journeys it covers, then collect evidence before forming opinions: analytics for where people drop off, and feedback, recordings and support tickets for why. Next run an expert review against usability heuristics and walk every key task end to end, including error paths. Test the most important tasks with real users if you can. Log each issue in the same format, rate its severity, prioritize by impact and effort, and deliver a short report with specific recommendations. Retest once fixes ship.

02

What This Guide Covers

This is the execution guide: the order of work, what to produce at each step and how to turn findings into decisions. If you're still deciding whether you need an audit or what one typically includes, start with UX audit: what it is, what it includes and how it works, which also contains a website UX audit checklist.

The workflow below works for websites, online stores, SaaS products and mobile apps. Scale it up or down: a focused audit of one checkout flow uses the same steps as a full product audit, with less ground to cover.

03

The UX Audit Workflow at a Glance

Each step produces something the next step depends on. Skipping ahead usually means reworking findings later.

StepWhat you doWhat it produces
1. Goals and scopeAgree why the audit exists and what it coversA one-page audit brief
2. Users and tasksIdentify who uses the product and their top tasksA prioritized task list
3. AnalyticsFind where people drop off or struggleFunnel and behaviour notes
4. FeedbackRead support, reviews, surveys and recordingsThemes with examples
5. Expert reviewHeuristic evaluation and area-by-area reviewCandidate issues
6. User testingWatch users attempt key tasksConfirmed issues and causes
7. Issue logRecord every issue in one formatA single source of findings
8. SeverityRate how serious each issue isSeverity scores
9. PrioritizationWeigh impact against effort and confidenceA ranked backlog
10. RecommendationsWrite specific, testable fixesActionable changes
11. ReportPackage and present the findingsReport and walkthrough
12. Follow-upMeasure and retest after fixesEvidence the fixes worked
04

Step 1: Define Audit Goals and Scope

An audit without a goal turns into a list of everything that could be better. Start by interviewing the people who own the product and its numbers: product, marketing, sales, support and engineering. Ask what's not working, which metrics matter, what has already been tried, and what is off limits, such as a platform that can't change this year.

Write the answers into a short audit brief: the business question (for example, “why do trial users rarely invite teammates?”), the journeys in scope, the devices and audiences, the evidence available, the deliverables and the date for the readout. Being explicit about what's out of scope protects the time you have for what's in it.

Pro tip

Phrase the goal as a question the audit can answer. “Improve the UX” can't be finished; “Find what stops mobile visitors completing checkout” can.

05

Step 2: Understand Users and Their Key Tasks

Audit the product the way its users experience it, not the way the org chart divides it. List the main user groups and the handful of tasks that matter most to them and to the business. For an online store that might be finding a product, choosing a variant, checking delivery and paying. For a SaaS product it might be signing up, completing setup, inviting a colleague and producing the first report.

Use existing research if you have it, including personas, interview notes and user research, but keep it light. The output you need is a ranked task list with the entry points, devices and context for each task. Every later step refers back to it.

06

Step 3: Review Analytics

Quantitative data tells you where to look. Check the tracking first: missing events, duplicated page views and unfiltered internal traffic are common, and conclusions built on broken data waste the whole audit.

  • Funnels for each key task, with drop-off at every step
  • Device, browser and screen-size splits for the same funnels
  • Top landing pages and their exit rates
  • Internal search terms, especially searches that return no results
  • Form analytics: fields that cause errors, hesitation or abandonment
  • Field performance data such as Core Web Vitals for key templates
  • Changes over time around releases, campaigns or redesigns
07

Step 4: Review User Feedback

Qualitative sources explain the numbers. Read a sample of support tickets and chat transcripts, product reviews, survey comments, sales call notes and app store reviews. Tag each piece of feedback with the task and the kind of problem, then count the tags. Recurring “how do I…” questions often point to findability or labelling problems; recurring “I didn't know…” complaints often point to missing information at the moment of decision.

If you use session recordings or heatmaps, watch recordings filtered to the drop-off points you found in step 3 rather than browsing at random. The heatmap analysis guide covers how to read this data without over-interpreting it.

08

Step 5: Run the Expert Review

Start with a heuristic evaluation: review each key task against an established set of usability principles, usually Nielsen's 10 usability heuristics, and note every violation. Several evaluators working independently find more problems than one, so combine their findings afterwards; Nielsen Norman Group's guide to conducting a heuristic evaluation covers the method in detail.

Then make a second pass area by area. Heuristics are broad; this pass makes sure specific parts of the experience get looked at deliberately.

AreaWhat to check
NavigationLabels in users' language, clear current location, key destinations reachable, search available where expected
ContentClear value proposition, answers to decision questions, scannable structure, consistent terminology
InteractionObvious controls, feedback after every action, predictable behaviour, undo for mistakes
FormsVisible labels, only necessary fields, helpful inline validation, input preserved after errors
Error and empty statesSpecific error messages with a fix, designed empty states, no dead ends
AccessibilityContrast, keyboard access, focus visibility, labels, alt text, target size against WCAG 2.2
MobileLayout, touch targets, sticky actions, keyboard types, performance on a mid-range phone
Conversion pathsFriction, surprises and missing reassurance between entry and goal
09

Walk Each Task End to End

Walk every key task yourself on the devices your users use, with realistic data. Create an account, use a long name, enter an address in another country, apply an expired discount code, let the session time out, pay with a card that will be declined in test mode. Most serious problems hide in these alternative and error paths, and they rarely show up in a design review of the ideal screens.

Record each walkthrough. Screenshots or short clips become evidence in the issue log and save arguments later.

10

Step 6: Test With Users

Expert review predicts problems; watching users confirms them and shows how serious they are. Where budget allows, run a small round of usability testing on the two or three most important tasks, especially where the evidence is disputed or the fix would be expensive.

Keep the test focused on the audit's goal. Write tasks as realistic scenarios, recruit people who match your users, and note where they hesitate, misread or fail. If testing isn't possible, say so in the report and mark which findings rest on expert judgment alone.

Want a second pair of eyes on your product?

ZSpace Labs runs UX audits that combine expert review, analytics and user testing, and ends with a prioritized list of fixes.

Start a Project
11

Step 7: Log Every Issue the Same Way

A consistent issue log is what makes an audit usable. Record one issue per row, even if it appears on several screens, and link the evidence rather than describing it from memory.

FieldWhat to record
ID and titleShort, specific name, such as “Delivery cost hidden until payment step”
LocationPage, screen or component, plus device
Task affectedWhich key task it disrupts
DescriptionWhat happens and why it's a problem for users
EvidenceScreenshot, recording, analytics figure, quote or test observation
PrincipleHeuristic, guideline or WCAG criterion it relates to
SeverityRating on your agreed scale
ReachRoughly how many users or sessions encounter it
RecommendationThe proposed fix
Effort and ownerRough size of the fix and who owns it
12

Step 8: Rate Severity

Rate every issue on one scale so that problems found by different methods can be compared. A widely used option is Jakob Nielsen's 0 to 4 severity rating scale, which combines how often a problem occurs, how badly it affects users when it does, and whether it persists once users know about it.

Rate after the review sessions, not during them, and have evaluators rate independently before agreeing a final score. Nielsen Norman Group notes that evaluators give weaker ratings while they're focused on finding problems, and that one evaluator's ratings alone are too unreliable to trust, while the average of three evaluators' ratings is good enough for many practical purposes.

RatingMeaningTypical action
0Not a usability problemRemove from the log
1CosmeticFix if time allows
2MinorLow priority
3MajorHigh priority
4CatastropheFix before release or immediately
13

Step 9: Prioritize the Findings

Severity alone doesn't set the order of work. A major issue on a rarely used settings page can wait behind a minor issue on the checkout that every buyer sees. Weigh severity against reach, business impact, effort and how strong the evidence is, then sort findings into a few buckets.

BucketWhat goes in it
Fix nowSevere or widespread issues that are cheap to fix, such as copy, labels, missing information or broken states
PlanHigh-impact issues that need design and engineering work
ValidateIssues with weak or conflicting evidence; test before investing
MonitorLow-impact issues worth tracking but not scheduling yet
14

Step 10: Write Recommendations Teams Can Act On

A recommendation should say what to change, where, and how you'll know it worked. Vague advice gets agreed with and then ignored.

WeakActionable
Improve the checkoutShow estimated delivery cost and date in the cart, before the address step
Make errors clearerReplace “Invalid input” on the phone field with a message showing the expected format, and keep the typed value
Fix mobile navigationAdd a visible search field to the mobile header and move “Sale” out of the third menu level
Simplify onboardingDefer team and billing setup until after the first project is created
15

Step 11: Build the UX Audit Report

Most readers will read the first two pages, so put the decisions there. Walk stakeholders through the top findings live; recordings of users struggling persuade faster than any slide.

  • Summary: the five to ten most important problems and what to do first
  • Scope, goals and methods, including what wasn't tested
  • Top findings, each with evidence, severity and recommendation
  • Quick wins listed separately so they ship early
  • What already works well, so it isn't lost in a redesign
  • A proposed sequence of fixes and what to test next
  • Appendix: the full issue log, analytics notes and test details
16

What You Should Receive

Whether you run the audit in-house or hire someone, use this table to check the output before signing it off. It turns the steps above into a list of deliverables, what a good version looks like and the warning signs of a weak one.

DeliverableWhat good looks likeRed flag
Audit briefOne page: the business question, journeys, devices, audiences, evidence used and what is out of scopeNo stated goal, or scope agreed only verbally
Task listRanked key tasks with entry points and devices, used throughout the auditFindings organised by page or team rather than by user task
Evidence summaryFunnel drop-offs, feedback themes and a note on tracking qualityAnalytics quoted without checking the tracking works
Issue logOne row per issue with location, task, evidence, principle, severity, reach, recommendation and ownerA slide deck of screenshots with no log behind it
Severity ratingsOne named scale, rated after review and by more than one evaluator where possibleEverything rated "high", or no scale at all
Prioritised planFix now, plan, validate and monitor buckets, with quick wins listed separatelyAn unranked list of every possible improvement
RecommendationsSpecific changes: what, where and how success will be measured"Improve the checkout" or redesign mock-ups with no link to a finding
What works wellStrengths to keep, so a redesign does not remove themOnly problems, so the team cannot tell what to protect
Method and limitsWhich methods were used and which findings rest on expert judgement aloneNo mention of whether users were tested
Readout and retest planA walkthrough with stakeholders, baselines for key tasks and a date to re-measureA file sent by email with no follow-up

Pro tip

A sample issue-log row, using the step 7 fields: "UX-014 Delivery cost hidden until payment step | Checkout, mobile | Complete a purchase | Shipping cost first appears on the final step | Session recordings show exits at that step; a test participant said she felt tricked | Visibility of system status | 3 (major) | Every mobile checkout | Show estimated delivery cost in the cart | Small; front-end team". The content is illustrative.

17

Step 12: Follow Up and Retest

An audit is only finished when the fixes are measured. Record baseline numbers for each key task before changes ship, then compare afterwards. Retest the same tasks with users to confirm the problem is gone and nothing new was introduced. Where traffic allows, measure bigger changes with A/B testing.

Keep the issue log alive as a backlog. Re-auditing the same journeys after significant releases is much faster than the first audit because the baseline already exists.

18

How Long Does a UX Audit Take?

It depends on how many journeys and platforms are in scope, how usable the analytics are, whether new user testing is included and how many evaluators take part. A focused audit of one flow on one platform is much smaller than a full product audit across web and apps with testing. Agree the scope in step 1 and the timeline follows from it.

19

Common Mistakes When Running a UX Audit

  • Starting the review before agreeing goals and key tasks
  • Trusting analytics without checking the tracking
  • Reviewing only ideal screens and never the error paths
  • Recording opinions without evidence or location
  • Mixing personal visual preferences in with usability problems
  • Delivering a long unranked list instead of a prioritized plan
  • No baseline, so nobody can tell whether the fixes worked

Need a UX audit that ends in a plan, not a list?

Talk to ZSpace Labs about a UX audit, paired with conversion analysis for commercial journeys.

Start a Project
20

Conclusion

A good UX audit follows a clear order: goals, users and tasks, evidence, expert review, testing, a consistent issue log, severity, priorities and specific recommendations. The value is in the ranking and the follow-through, not the length of the report. For the wider design workflow the audit feeds into, see the UX design process.

FAQ

Common questions.

Agree goals and scope, identify users and their key tasks, review analytics and user feedback, run an expert review against usability heuristics, test key tasks with users where possible, log every issue with evidence, rate severity, prioritize by impact and effort, and deliver a report with clear recommendations. Then retest after fixes.

Goals and scope, user and task definition, quantitative evidence, qualitative evidence, expert review, user testing, issue logging, severity rating, prioritization, recommendations, reporting and follow-up testing.

Lead with a short summary of the most important problems and what to do first. Then explain scope and method, present the top findings with evidence, include the full issue log, separate quick wins from larger changes, note what already works well, and propose a sequence of fixes.

Yes. Many audits combine expert review with analytics, session recordings and support data. Without testing you'll know where problems occur and often why, but user testing gives stronger evidence for the most important or disputed issues.

Heuristic reviews find more problems when several evaluators work independently. Nielsen Norman Group's heuristic evaluation guide says that ideally three to five people should evaluate the same interface independently. A single reviewer can still run a useful audit, but expect some issues to be missed.

Access to your analytics, a session recording or heatmap tool if you have one, support and feedback data, accessibility checkers such as axe or Lighthouse, PageSpeed Insights for performance data, a spreadsheet or board for the issue log, and a testing platform if you run remote tests.

Rate each issue's severity, estimate how many users it affects and what it costs the business, then weigh that against the effort to fix and your confidence in the evidence. Severe, widespread and cheap fixes go first.

A heuristic evaluation is one method: experts inspect an interface against usability principles. A UX audit is broader and usually includes heuristic evaluation alongside analytics, user feedback, testing, accessibility and performance checks.

Before a redesign, after major feature additions, when key metrics drop, and periodically on products that change often. Smaller focused audits of one flow can run whenever that flow is about to be reworked.

Unprioritized lists of personal preferences, visual redesign proposals without evidence, and findings with no location or reproduction steps. Those make a report long without making it useful.

Get in touch

Have a project in mind?

Whether you're building a new digital product, improving an existing website, or looking to automate part of your business — let's talk.