UX audit in practice: from friction to fix
summary
Audit workflow applied to a live employee app called Peoplehub uses Figma + a Word report template, annotated screenshots, numbered tags and a copy-with-toggle pattern to track fixes. A 1,000-user baseline shows saving five minutes per day translates to 18,300 hours saved. Concrete changes include making the active nav bold and filled, consistent icons, clearer link labels, a table for vacation history, and show/hide pay slips; prioritization uses an impact–effort matrix and MoSCoW, and small fixes restore task completion.
AI-written summary · about
chapters (20)
- 0:00Introduction and speaker background
- 2:20What is a UX audit and why do it
- 7:59Setting up the audit context
- 10:28Mapping the solution visually
- 15:08Key areas to test in an audit
- 17:37Conducting the user journey test
- 21:30Evaluating UX writing and terminology
- 22:54Assessing accessibility issues
- 26:27Addressing privacy and sensitive data
- 27:53Testing system feedback and statuses
- 28:58Improving information hierarchy
- 30:04Ensuring visual consistency
- 30:49Refining user flow and interactions
- 31:53Documenting all findings
- 32:57Prioritizing fixes with impact effort
- 35:56Turning findings into improvements
- 43:21Before and after comparison
- 43:41Creating the audit report
- 47:37Free UX audit template overview
- 49:44Final summary and Q&A
