Refactoring UI: Practical Visual Design Rules That Anyone Can Learn

There is a myth in product teams that visual design is taste: you either have the eye or you do not. Refactoring UI by Adam Wathan and Steve Schoger dismantles that myth completely. Good UI, they show, is mostly a set of learnable decisions, and the gap between amateur and professional work is smaller and more systematic than anyone expects.

What is the core lesson of the book?

Visual design problems are usually systematic, not artistic. An interface looks off because of identifiable causes: too many font sizes, no spacing system, color used without restraint, hierarchy carried by decoration instead of structure. Each cause has a concrete fix. The book’s format mirrors this: before-and-after examples where a few targeted changes transform a screen, with the reasoning spelled out.

The deepest lesson is about hierarchy. Amateur designs emphasize things by adding: more color, borders, icons, badges. Professional designs emphasize by removing: de-emphasize the secondary, and the primary stands out on its own.

What do designers take away from it?

• Start in grayscale. If the hierarchy works without color, color becomes an amplifier instead of a crutch.

• Use systems, not instincts. A spacing scale, a type scale, a limited palette. Constraints produce consistency, and consistency reads as quality.

• Emphasize by de-emphasizing. Make secondary elements quieter before you make primary ones louder.

• Details compound. Nobody notices one padding fix. Everyone notices the cumulative effect of forty of them.

Why does Tremoloo share this book?

Because it is the fastest way to raise the floor of a whole team. Developers who read it stop shipping interfaces that look accidental; designers sharpen instincts into rules they can teach. We recommend it to nearly every client team we work with.

Want your product’s UI to look as professional as it works? Our product design team can take it there.