UX Audit Methodology

Why audits are underused

UX audits are underused relative to their value because they feel like a step backward — analysis before action. In a project context where clients want to see progress, an audit at the start of an engagement can feel like a delay. This is a framing problem, not a methodology problem. An audit at the start of a redesign project is the research phase. It is not slower than starting with design — it is faster, because it prevents the most expensive mistake: redesigning the wrong thing.

The five audit dimensions

The Themex audit methodology evaluates designs across five dimensions: visual hierarchy (does the design communicate priority clearly?), navigation clarity (can users find what they are looking for?), content legibility (is the text readable and scannable?), interaction feedback (does the interface respond to user actions in ways that build confidence?), and accessibility (does the design work for users with disabilities and in challenging conditions?). Each dimension is independently scoreable, which allows the audit to identify targeted problems rather than producing a single quality verdict.

Scoring protocol

Each question in the audit is scored on a 1–4 scale: 1 is a critical failure (the design fails this criterion in a way that will cause user errors or abandonment), 2 is a significant issue (the design underperforms on this criterion in a way that creates friction), 3 is adequate (the design meets the basic standard but has room for improvement), 4 is strong (the design meets or exceeds best practice on this criterion). The scoring is calibrated so that a score of 3 across all dimensions represents a competent but not exceptional design.

From scores to priorities

The audit output should drive a prioritised recommendation list. Critical issues (score of 1) are addressed first regardless of category. Significant issues in the dimensions most critical to the project's primary conversion goal are addressed second. Adequate performance that could be improved to strong is addressed last, or deferred to a future phase. The prioritisation logic prevents the common mistake of starting with visual refinements (easy, visible) rather than structural fixes (harder, more impactful).

Presenting audit results

Present audit results to clients in category-level terms before showing item-level scores. Lead with: 'The design is strongest in content legibility and weakest in interaction feedback.' This framing gives the client a mental model before they receive the detail. Item-level scores without category context produce defensive reactions. Category context first, item detail second.