Audit Before You Redesign

Most redesign projects start with the same brief: the existing design is not working, the client wants something new, the budget is available. The instinct to start fresh is understandable. It is also usually the most expensive response to what is often a containable problem.

The redesign instinct

A redesign feels like the right answer because it is legible. The deliverable is obvious. The before and after is easy to show. The creative process is satisfying. None of this is a reason to redesign — it is a description of what makes redesigns easy to sell.

The question that a redesign brief rarely answers is: which part of the existing design is actually failing, and how do you know? 'It feels outdated' is an aesthetic reaction, not a diagnosis. 'Conversion is low' is a business metric, not a design problem statement. Without a structured audit, a redesign applies a solution to an undiagnosed problem.

What an audit finds

A structured UX audit applied to an existing design before a redesign brief is written typically finds one of three situations. First: the design is fundamentally sound and the problem is a small number of specific failures that can be addressed without a full redesign. This is the most common finding and the least comfortable one to present. Second: the design has systemic problems that require architectural changes — restructuring information hierarchy, replacing a navigation system, rebuilding a form flow. A redesign may be warranted, but the scope is now defined by evidence rather than aesthetic preference. Third: the design is failing because the underlying strategy is wrong — the product positioning, the content model, or the conversion goal does not match the audience. A redesign will not fix this.

Using the Themex UX Audit instrument

The UX Audit instrument scores a design across five dimensions: visual hierarchy, navigation clarity, content legibility, interaction feedback, and accessibility. Each dimension contains four scored questions. The output is a category-level score and a prioritised list of critical issues — issues that scored one or two out of four on any question.

Run the audit before the redesign brief is written. Share the output with the client. Use the category scores to define the scope of the engagement. A project that scores well on navigation and content but poorly on interaction feedback does not need a new visual language — it needs better state management and feedback patterns. That is a different project than a full redesign, at a different cost and timeline.

When the audit recommends a redesign

The audit output sometimes supports a full redesign — when scores are low across multiple categories and the issues in each category are architectural rather than surface-level. In this case the audit does not prevent the redesign; it validates it. You are no longer redesigning because the existing design feels wrong. You are redesigning because a structured evaluation found that it is wrong, in specific ways, for documented reasons. That is a better brief. It produces better work.