VJOURNAL

DesignGlobal DeskAugust 29, 2026

UX Audit Checklist: What to Review Before a Redesign

For UX audit, this field guide covers live evidence, observable inconsistencies, severity, ownership and a decision record another reviewer can repeat.

Editorial cover: UX audit

Answer in brief

Run representative tasks through success, interruption, error and recovery, separate observation from cause, and rank each issue by user consequence and evidence confidence.

Evidence cutoff: 2 sources

Verified facts

Source review
7 September 2026
Reader need
UX audit checklist before redesign
The “UX audit” review is designed to collect behavioural, content, interface and operational evidence before deciding what a redesign should change.
For the query “UX audit checklist before redesign”, the evidence record separates observations, constraints and assumptions.
The accountable owner can accept, defer or reject the “UX audit” finding with a traceable reason.

UX audit — Set the audit boundary and sample

The audit boundary follows priority tasks and material consequences instead of promising coverage of every screen.

UX audit — Inventory the live surfaces

Analytics, support records, observation and content evidence retain their dates, contexts and separate limitations.

UX audit — Record observable inconsistencies

Findings distinguish visible behaviour, likely cause and the proof still needed before prescribing a remedy.

UX audit — Walk through the critical tasks

A representative journey includes orientation, action, feedback, interruption, failure and recovery around the intended outcome.

UX audit — Rate severity with evidence

Severity combines task consequence, affected reach, recurrence and evidence confidence without collapsing them into taste.

UX audit — Assign corrections and owners

Each correction names a decision owner, delivery owner, verification method and dependency outside the team.

UX audit — Close the audit decision log

The final log explains accepted, deferred and rejected remedies while preserving exclusions and unanswered questions.

Practical checklist

  • Frame the audit around priority user tasks and business consequences rather than a complete screen inventory alone.
  • Combine analytics, support evidence, usability observation and content review while preserving each source’s limitations.
  • Trace one representative journey across entry, orientation, action, feedback, failure and recovery.
  • Label every finding by evidence confidence, affected task, user consequence and likely underlying cause.
  • Recommend research, content, process or technical corrections when they solve the evidence better than visual redesign.