The Case for Fewer Sizes

Open most mature design files and you will find forty type sizes. Nobody decided on forty. They accumulated, one nudge at a time, each defensible on its own. The result is a system that cannot be maintained and a product that reads as slightly off without anyone being able to say why.

A ramp is a set of meanings

Each step should correspond to a role, not a pixel value. Display, headline, section lead, body, caption, legal. Six or seven steps covers almost everything. If a designer needs an eighth, the honest question is whether the content has a genuinely new role or whether the layout is compensating for something else.

Nudging is a symptom

When someone drops a heading two pixels to make it fit, the ramp is not the problem. The container is too tight, the copy is too long, or the hierarchy is wrong. Fixing the real cause keeps the system intact and usually improves the page.

Fewer sizes make hierarchy louder

Distinct steps read as distinct levels. Sizes that sit close together read as noise, and the eye stops trusting size as a signal at all. Larger jumps between fewer steps make the structure legible at a glance, which is the entire point.

Pair the ramp with a spacing scale

Type sizes without matching spacing values produce rhythm by accident. When both come from the same system, vertical rhythm holds across pages built by different people, and nobody has to eyeball margins.

Constraint speeds teams up

Fewer options means less deliberation on every screen. Designers compose instead of tuning. New contributors produce on-brand work in their first week because the decisions are already made. Consistency stops depending on who happened to build the page.

How we do it at Monaro

We define a ramp of six named steps tied to spacing tokens, document what each is for, and enforce it in components rather than in a PDF. When a request for a new size arrives, we look at the content first. Nine times out of ten the existing ramp already had an answer.