Designing for Consistency

Introduction

Consistency has a bad reputation, and it earned some of it. Applied without judgement it flattens a product into a grid of identical grey boxes, every screen technically correct and none of them memorable. Applied well it does the opposite: it clears away the arbitrary so the deliberate has room to be noticed.

What a System Is Actually For

A design system is not a rulebook, it is a set of decisions already made. Every question it answers in advance — how far apart, which weight, what happens on hover — is a question nobody has to argue about again. The value is not the components. It is the arguments that stop happening.

Which is also the test for whether a rule belongs in the system at all: if two reasonable people would decide it differently and neither answer is better, write it down. If the right answer depends on the screen, leave it out.

Structure Where It Pays, Freedom Where It Matters

The parts of an interface a reader has to relearn on every page are the parts that should never change. The parts they come for are the parts that should.

Hold these steady:

• Spacing, so rhythm carries across screens
• Type scale, so hierarchy means the same thing twice
• Interactive states, so nothing is a surprise

Everything else — illustration, photography, the shape of a hero, the pacing of a case study — is where a product gets to sound like itself.

Making the System Easy to Obey

A system gets followed when it is:

• Faster than not following it
• Named after what a thing is, not where it first appeared
• Documented beside the code rather than in a separate tool
• Allowed to change when it is wrong

The last one is the one that gets skipped. A system nobody is permitted to question becomes a system everyone quietly works around, and then it is documentation of a product that no longer exists.

Consistency and Character Are Not Opposites

Illustration is the clearest case. A house style — one line weight, one palette, one way of drawing hands — lets every new drawing read as part of the same world while still being about something specific.

The rule of thumb:

Systematise the grammar, not the sentences.

Readers notice when the grammar changes. They rarely notice when two sentences are different, which is exactly the point.

Conclusion

Consistency is infrastructure. Done properly it is invisible, and what people see instead is a product that seems to have been made by one mind paying attention — which is the only thing a system was ever trying to fake.