White space: a practical guide

The gap between knowing this and actually doing it is where most teams lose ground. This guide covers what white space actually involves, where it usually goes wrong, and how to tell whether yours is in reasonable shape.

Consistency is the quiet half of design work: it rarely gets complimented, and its absence is noticed immediately. Nothing below assumes a large team or a large budget — most of it is a decision somebody has to make and then write down.

Why this earns attention

Space is what makes a dense page feel calm. In practice this is a scheduling problem more than a technical one. It is the sort of thing that looks like polish right up until it costs you an enquiry.

For most businesses the question is not whether this matters but how much of it is worth doing right now. That depends on what you are trying to achieve in the next few months, not on best practice in the abstract. It is worth being explicit about, because assumptions differ quietly.

How to approach it

Grouping related elements matters more than adding padding everywhere. It is worth being explicit about, because assumptions differ quietly. The version that survives contact with a real deadline is the simple one.

The measurable part of design is whether people can find what they came for and act on it without hesitating. The version that works in practice is usually less elaborate than the version described in the guides.

Cramped layouts read as cheap even when the design is good. In practice this is a scheduling problem more than a technical one. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

A working checklist

If you want a quick read on where you stand, work through this. Anything you cannot answer confidently is where to start.

• Space is what makes a dense page feel calm
• Grouping related elements matters more than adding padding everywhere
• Cramped layouts read as cheap even when the design is good
• Someone is named as the owner, not just assumed to be
• There is a date in the calendar to review it again
• The decision and the reasoning behind it are written down somewhere findable
• You could explain the current setup to a new hire in five minutes

What to watch for

The most common failure is not doing this badly. It is doing it once, during a launch, and never revisiting it. Circumstances move, the setup does not, and the gap widens quietly until something breaks or somebody notices the numbers.

• It was configured during a launch and has not been touched since
• Different people in the business believe different things are true about it
• There is no way to tell whether the last change helped or hurt
• The only person who understands it has left, or is about to

Design decisions are the ones clients feel most confident arguing about, which makes it worth separating taste from evidence early. Small and consistent beats large and occasional here.

How we approach it

On our projects this gets handled during the build rather than added afterwards, because retrofitting it costs several times more than including it. We write down what was decided and why, so the next person to touch it is not guessing.

If you are working with someone else, the questions worth asking are simple: who owns this, how will we know it is working, and what happens when it needs to change?

Making it stick

Pick the single item from the checklist above that would cause the most trouble if it turned out to be wrong. Fix that one, confirm it worked, then move on. Pick the one that would hurt most if it failed, and start there.