The first 5 minutes determine the next 5 months. This is the full essay exploring the nuances, the tradeoffs, and what we've learned from doing this across dozens of products.
The Core Distinction
Most teams conflate these two practices because they both involve “looking at the product” and “finding problems.” But the altitude is completely different, and confusing them leads to spending resources on the wrong kind of insight at the wrong moment.
A UX audit is expert-driven: you bring in someone who knows the principles, the patterns, the research literature, and they apply structured heuristics to your interface. It's systematic, repeatable, and doesn't require users to be present. A usability test is user-driven: you observe real people attempting real tasks.
“The audit tells you where the walls are. The usability test tells you where people walk into them.”
When to Choose an Audit
An audit works best when you need a fast, structured inventory of known violations. You're not discovering what users want — you're cataloguing what your interface is definitely doing wrong by established standards.
The Answer Is Usually Both
For most mature products, the right answer is a sequenced approach: audit first to eliminate obvious violations and establish a baseline, then test to validate your hypotheses about the more complex behavioral problems.
Writes about design, strategy, and what it actually takes to ship things that work.