How to Run a UI Audit: Lessons from Designing User Interfaces

Before you redesign, audit. A UI audit tells you what is actually broken versus what is merely unfashionable, and Designing User Interfaces includes one of the most practical treatments of the process. Here is the method, distilled.

What is a UI audit?

A screen-by-screen review of an interface against explicit craft criteria. Not “do I like it” but “does it follow the rules it claims to follow.” The criteria: spacing consistency, typography scale, color discipline, hierarchy, component states, and pattern consistency across the product.

How do you run one?

1. Inventory the screens. You cannot audit what you have not seen. Screenshot every screen and state, including the ugly ones nobody demos.

2. Define the criteria before judging. What spacing scale should this product use? How many type sizes? Auditing without stated standards produces opinions, not findings.

3. Check the fundamentals in order. Spacing first, then type, then color, then hierarchy, then states. Fundamentals compound; a hierarchy problem on top of a spacing problem needs the spacing fixed first.

4. Capture evidence, not adjectives. Every finding gets a screenshot, the principle violated, and the fix. “Violates the 8-point spacing scale in 14 places” is actionable. “Feels messy” is not.

5. Prioritize by user impact. Consistency failures on core flows outrank polish issues on settings pages.

What do teams gain?

A fix list executable without a redesign, and a baseline to measure against. Teams are often surprised how much of the “needs a redesign” feeling dissolves after fixing spacing and consistency alone.

Why does Tremoloo share this book?

Because UI audits are core to how we work, and the book’s checklist approach matches our own criteria closely. Sharing it helps clients understand what our audit reports are measuring and why.

Want a professional audit of your interface? Our UX audit service delivers exactly this, with evidence.