Short answer: A UX audit examines how effectively and controllably concrete user tasks can be performed in the documented system state. It turns interaction observations into reproducible findings and keeps those findings separate from broader judgements about user experience.

Examine usability in context rather than as a matter of taste

Usability depends on user group, task, system state and operating context. The same interface can support one workflow well and obstruct another. A useful audit therefore starts with the concrete tasks and conditions that matter.

The examination documents observable interaction behaviour, feedback, error recovery, user control and relevant criteria. Subjective impressions can be included as evidence where appropriate but should not be confused with technical findings or medical conclusions.

Typical reasons for an assignment

before redesign, migration or release where critical user flows should be reviewed
when recurring interaction problems or error states are reported but not yet structured technically
when an independent expert review is needed in addition to internal UX work
when user tests or support feedback should be connected to reproducible system findings

Typical technical questions

Which user groups and tasks define the relevant usage context?
Where do navigation, feedback, error handling or user control create observable interaction problems?
Which findings can be reproduced in the documented version and environment?
Which observations are technical findings, which are user perceptions and which remain interpretation?

Examination scope: The audit scope defines user groups, tasks, system version, relevant environments and agreed evaluation criteria. Findings are limited to that scope and do not imply universal usability across all users or contexts.

From user task to a traceable usability finding

1 Define context & scope Specify users, tasks, system state and relevant evaluation conditions.

2 Observe interaction Examine task paths, errors, timing, feedback and relevant user evidence systematically.

3 Apply criteria Compare observed interaction with suitable usability and dialogue criteria.

4 Separate finding & assessment Keep observation, interpretation, professional assessment and statement boundary distinct.

A single user statement is evidence of that user’s experience, not proof of a universal system property. Likewise, an expert review does not replace user testing when actual user performance is part of the question.

The audit combines systematic expert review with additional user evidence where required by the examination question.

Typical examination material

documented system version and concrete user flows
task descriptions, interaction paths and observed error states
screen recordings, screenshots or reproducible steps where useful
support tickets, user feedback or test observations where relevant
reference criteria from usability, software ergonomics or project-specific requirements

What you receive

Finding catalogue: reproducible interaction problems tied to concrete tasks and system states
Prioritisation: relevance of findings for critical user tasks and workflow impact
Evidence trail: documented observations, criteria and reproduction conditions
Statement boundaries: explicit distinction between observed system behaviour, user perception and broader interpretation

Statement boundary: The UX audit is a technical and methodological assessment of usability and interaction. It does not make medical diagnoses, establish health causation or guarantee conversion, customer satisfaction or business success.

Related services

UX, Software Ergonomics & Accessibility — Overview Accessibility Audit Web & Mobile Assessment Analysis & Assessment

Relevant knowledge

Examine usability systematically

Connect study design, observations, measures and interpretation boundaries.

Define the usage context

Treat user, task, environment and system state as part of the subject of examination.

Interaction principles and dialogue quality

Assess dialogue quality against concrete interaction and reference criteria.

Error states and user control

Examine feedback, recovery options and loss of control technically.

Frequently asked questions

Is a UX audit the same as user testing?

No. A UX audit can be performed as a structured expert review. User tests are an additional evidence source where real user reactions or task performance form part of the examination question.

Can a UX audit prove that an interface is “good” or “bad”?

Not in the abstract. Reliable findings are tied to user group, task, system state and criteria. The assessment should make those conditions explicit.

Are psychological burdens evaluated medically?

No. Problematic UX patterns and user perceptions can be described. Medical diagnoses or health-causation claims are outside this technical audit.

Define a useful UX audit scope

For an initial assessment, the main user groups, critical tasks, current system version and known problem areas are useful. A reviewable UX audit scope can then be defined.

Send enquiry