How to Do a UX Audit: A Practical Step-by-Step Process

A UX audit is a structured review of an existing product to identify usability problems. It's not a redesign proposal. It's a diagnosis — you document what's broken, how badly, and what to do about it.

Done well, a UX audit gives your team (or your client) a prioritized list of improvements grounded in evidence rather than opinion.

What a UX audit is not

It's not a full usability study. You're not recruiting participants and running sessions. A UX audit is an expert review — you evaluate the product against established heuristics, real usage data, and your own UX knowledge.

It's also not a list of everything you'd personally redesign. Keep your taste out of it. The question is always: does this create confusion or friction for the user?

The framework: Nielsen's 10 Heuristics

Jakob Nielsen's 10 usability heuristics from 1994 still hold. They're the most widely used framework for expert reviews. Evaluate your product against each one:

1. Visibility of system status — does the product tell users what's happening?
2. Match between system and real world — does it use language and concepts users understand?
3. User control and freedom — can users undo mistakes and exit states easily?
4. Consistency and standards — does the product follow platform conventions?
5. Error prevention — does the design prevent mistakes before they happen?
6. Recognition over recall — do users recognize options rather than having to remember them?
7. Flexibility and efficiency of use — are there shortcuts for expert users?
8. Aesthetic and minimalist design — is irrelevant information removed?
9. Help users recognize, diagnose, and recover from errors — are error messages specific and helpful?
10. Help and documentation — is support available and easy to find?

For each section of the product you review, note which heuristics are violated and how severely.

Gathering data before you start

An audit purely based on your own walkthrough is useful, but pairing it with real usage data makes it much stronger.

Use Hotjar to pull:

• Heatmaps — where users click, tap, and scroll to. Dead zones and rage clicks tell you a lot.
• Session recordings — watch real user sessions to spot where people hesitate, backtrack, or drop off.
• Funnel reports — if you have a signup or checkout flow, see exactly where users abandon.

Try Hotjar Free

Spend an hour in Hotjar before you start your heuristic review. It will direct your attention to the right areas and give you concrete evidence to pair with your expert opinion.

Documenting issues

Every issue you find should be documented with four things:

1. Description. What is the problem? Be specific. "The error message on the login form says 'Invalid credentials' without specifying whether the username or password is wrong, and without a link to reset the password."

2. Heuristic violated. Which of Nielsen's 10 does this break? In this case: heuristic 9 (help users recover from errors).

3. Severity rating. Use a 0–4 scale:

• 0 = Not a usability problem
• 1 = Cosmetic issue only — fix if time allows
• 2 = Minor usability problem — low priority
• 3 = Major usability problem — high priority
• 4 = Usability catastrophe — must fix before launch

4. Recommendation. What should be done? Keep it actionable. "Update the error message to specify whether the username or password is incorrect, and add a 'Forgot password?' link directly in the error state."

Using Figma to annotate screenshots

Take screenshots of the problematic UI and bring them into Figma. Add annotation labels with issue numbers, and use colored overlays or arrows to highlight the specific element.

Group your annotated screenshots by flow or screen — login flow, onboarding, dashboard, settings, etc. This makes the document scannable and gives developers a clear reference when fixes are being implemented.

Structuring the audit report in Notion

Your final report should be a Notion document (or similar) that includes:

• Executive summary — 3–5 sentences on the overall state of the product's UX. Mention the most critical issues and the general severity picture.
• Methodology — how you conducted the audit, which sections of the product were reviewed, what data sources you used.
• Issue log — a table or database with all issues, their severity ratings, the heuristic violated, and the recommendation. Sort by severity descending.
• Annotated screenshots — embed or link to your Figma file.
• Priority recommendations — the top five to ten actions you'd take first if resources are limited.

Try Notion Free

A Notion database works well for the issue log because you can filter by severity, assign owners, and track which issues have been resolved over time.

Presenting findings to stakeholders

Lead with the executive summary, not the full issue list. Stakeholders don't need to hear about every severity-1 cosmetic issue before they've understood the bigger picture.

Structure your presentation as: here's the overall health of the UX, here are the three to five critical issues, here's the evidence, here's what we recommend doing first.

Anchor everything in user impact, not design opinion. "Users are rage-clicking the submit button because there's no loading indicator" is more persuasive than "the loading state could be improved."

Be ready for pushback on severity ratings. Some issues you rate as critical will be deprioritized due to technical constraints or business priorities. That's fine — your job is to surface and quantify the problems, not to control the roadmap.

The audit is a starting point

A UX audit gives you a list of problems, not a set of solutions. Each critical issue needs its own design exploration. Use the audit output to build a backlog, prioritize with your team, and start designing fixes.

The most valuable audits are the ones that lead to action. Keep your report tight, your severity ratings honest, and your recommendations specific.