Most products accumulate design debt the same way codebases accumulate technical debt: gradually, through incremental decisions that each made sense at the time. A design audit is how you find out how much has accumulated and what it’s costing you.

What a Design Audit Is

A design audit is a structured review of a product’s visual and interaction design against defined criteria. Unlike a usability test (which observes users completing tasks), a design audit is expert-led: an experienced designer reviews the product systematically against:

  • Consistency standards — Do interface elements look and behave the same across the product?
  • Usability heuristics — Does the design follow established principles (Nielsen’s 10 heuristics are the standard reference)?
  • Accessibility requirements — Does the design meet WCAG 2.1 AA standards?
  • Brand alignment — Does the product accurately express the current brand?
  • Performance factors — Do design choices (heavy images, complex animations) create technical performance problems?

What Triggers a Design Audit

Companies typically commission design audits when:

  • Conversion rates are declining without an obvious explanation
  • Customer support volume is high around tasks that should be self-explanatory
  • A product has been through multiple teams and consistency has suffered
  • The brand has been updated but the product hasn’t caught up
  • Planning a major redesign and wanting to understand the current state before proposing changes

How a Design Audit Works in Practice

A thorough audit takes 1–3 weeks depending on product size. The typical process:

1. Define scope and criteria. Which parts of the product will be audited? Against which standards? Being specific here prevents the audit from becoming a vague “things could be better” document.

2. Inventory the UI. Capture screenshots or export designs for every screen, state, and variation. This is tedious but necessary — you can’t audit what you haven’t seen.

3. Apply evaluation criteria systematically. For each screen/flow, document issues against the criteria. The output at this stage is a log of raw findings.

4. Prioritise findings. Not all issues are equal. A missing error state on a rarely-used admin function is different from an inconsistent button style on the checkout flow. Issues should be classified by severity and user impact.

5. Create an actionable report. Group findings by theme. Include screenshots. Make specific recommendations, not just observations. “This button doesn’t match the brand” is less useful than “Update the CTA button on the checkout confirmation page from #3D4EF0 to the brand blue #5B4CF5.”

6. Present and prioritise with the team. An audit report that sits unread delivers no value. The audit findings should be translated into a prioritised backlog with effort estimates.

Business Impact of Acting on Design Audit Findings

The measurable impact depends on what the audit finds, but common categories of improvement:

Conversion rate improvements. Inconsistent or confusing checkout flows, unclear CTAs, and form friction are common findings. Fixing these has direct revenue impact. A 1% improvement in conversion rate on a £1M revenue stream is £10,000 — often more than the audit cost.

Support cost reduction. When users can’t figure out how to complete common tasks, they contact support. Design improvements that reduce confusion reduce support volume.

Development efficiency. Design inconsistency means engineering teams implement variations of the same component instead of reusing a standard. Resolving inconsistency creates the foundation for a proper design system, which speeds up future development.

Reduced churn. For SaaS products, confusing UX that causes users to give up is a churn driver. Design improvements that increase task completion rates improve retention metrics.

What a Good Audit Report Contains

A design audit report should be:

  • Specific. Name the screen, the element, the issue, and the recommendation.
  • Prioritised. Not everything needs to be fixed immediately. A severity classification helps teams triage.
  • Actionable. Observations need to become recommended changes, not just documented problems.
  • Visually documented. Annotated screenshots showing the issue are far more useful than text descriptions.

If you receive an audit report that is mostly general observations without specific recommendations, you’ve received a document that produces conversations but not change.

When to Do a Design Audit vs. a Full Redesign

An audit makes sense when:

  • The product’s core architecture and flow is sound
  • Specific areas of friction are creating measurable problems
  • There’s budget for targeted improvements but not a full redesign

A redesign makes sense when:

  • The product has fundamental structural problems that incremental fixes can’t solve
  • The brand has changed significantly and the product needs a complete update
  • The target audience or use case has shifted substantially

Often, an audit reveals whether a redesign is actually necessary — which is another reason to start there.

If you’re experiencing conversion or usability issues and want to understand the root cause before committing to a redesign, a design audit is the right first step. Talk to us about your product.