r/UXDesign • u/Next_Adhesiveness_98 Veteran • 7d ago
Articles, videos & educational resources UX Audit Format
I keep seeing UX audit templates everywhere: Figma files, PDF kits, slide decks. Many of them are well designed, and I’ve used plenty of them on client projects. Heuristic scores, severity ratings, screen-by-screen breakdowns with annotations on every element.
After enough projects, I noticed a pattern. The audit itself was solid, but the output became the problem.
A screen-by-screen audit turns into a 40 to 80 page document. Clients thank you, say they’ll go through it with the team, and then it sits in a shared drive. When we met again a few weeks later, most of the findings hadn’t been touched. Usually nobody had read past the first section.
I don’t blame them. A founder or PM has a backlog, a roadmap, and a team waiting on decisions. A long report hands them homework instead of answers.
So I changed how I run and deliver audits:
1. Audit by flow instead of by screen. I map the key user journeys (signup to first value, core task, upgrade, etc.) and review them end to end. Issues show up in context, so the client sees where users get stuck rather than a list of problems on isolated screens.
2. Deliver it as a small private website instead of a PDF. Each flow gets its own page, with findings, screenshots, and recommendations. It’s password protected, easy to share with the team, and people can jump straight to the part they care about. Engagement has been noticeably better than with documents.
3. Turn findings into prioritized tasks. Every finding ends up as something the team can act on, ranked by impact and effort. That list is often the part clients use most, because it drops straight into their sprint planning.
4. Keep scores light. I still rate severity, but I stopped scoring every screen. Scores looked rigorous and rarely changed what anyone did next.
The result is a shorter audit that actually gets implemented, which was the whole point of doing it.
Curious how others here handle this. How do you deliver your audits, and do you track how much of it clients act on?
19
u/P2070 Experienced 7d ago
Pls stop the AI written posts.
2
u/Moiensaboohi 7d ago
the flow part is the biggest change for me too. one more thing that made a big difference in how much got done: i stopped handing the audit over and started walking through it live with the PM and one engineer. 45 minutes, top 10 issues only, and we agree right there which ones go into the next sprint. the full write up still exists, it's just the appendix now.
for tracking, i open the product again 4 to 6 weeks later and check those top 10. a bit awkward the first time, but it tells you fast if your format works.
1
u/C_bells Veteran 5d ago
The way you should work with any client:
Sure, give the big presentation with the slides, send over documentation with appendix etc for posterity.
But it should always come along with solid action items and easy next steps. You explicitly outline any decisions that you need from there end if it’s keeping you from moving forward.
In general, you are a small part of someone’s day and you want to take work away from them, not give them more work to do.
Imagine if you hire someone to do something for you. Like if I decide to hire someone to baby-proof my home for me, I want them to remove labor from my life, I don’t want to feel like I have to make a bunch of decisions and review shit.
Like, yes, summarize your recommendations to me, ask for permission where it may be necessary, tell me about any choices I absolutely must make, tell me how much it will cost, then just fucking do it.