Yesterday I used Google Flights to compare routes, adjust dates, and pick a flight, all in a couple of minutes. I didn’t stop to appreciate any of it. I just made a decision and moved on.
That’s usually how good design shows up: Not as something you notice, but as something that helps you get where you’re going.
A few weeks ago, I read Practical Typography, and I’ve continued to think about one idea in particular. It’s not about typefaces, kerning, or the proper use of em dashes — though Butterick has plenty to say about all of those. It’s more fundamental than that.
Typography is an act of service.
Good typography is essentially invisible. When it’s working, you don’t notice it; you simply understand things clearly and move through content without friction. You only notice it when it fails, when the hierarchy is muddled, and you don’t know where to look.
The measure of great typography isn’t how impressed the reader is with the design. (Though we all appreciate beautiful design!) It’s how little the reader has to think about the design at all.
Butterick opens with a simple charge: Before making a single typographic decision, ask who your reader is and what they need. Not what you want to express. What they need.
That question sounds obvious, but it has a habit of receding once you’re deep in a design review. Designers want to make something beautiful, engineers want to solve something clever, and product managers want to ship something meaningful. These are all good impulses. But they turn inward — away from the person using what you’ve built. When that happens, the reader feels it, even if they can’t name why.
Every time a user has to stop and figure something out, you’ve spent some of their attention. Attention is finite. Every bit spent navigating your interface is a bit that can’t go toward why they came to you in the first place.
Butterick also writes about restraint. Use fewer typefaces, not more. Relax your margins. That blank space gives the eye somewhere to rest. Feature accumulation is the typographic equivalent of using eight fonts in a document. Each addition may be justified in isolation, but the cumulative effect is a product that asks too much: too many paths, too many decisions before reaching the goal. If you emphasize everything, nothing is emphasized.
At Automattic, some of the most important product work is the editing — asking whether a new option or surface actually helps the person we’re building for, or whether it survived the meeting without anyone asking that question.
That’s the test Butterick would recognize: Does this serve the reader?
What I keep coming back to is the ethic underneath it. Butterick has written a style guide, but he’s also made an argument for a particular kind of attention: the kind directed outward, in service of someone else, rather than inward toward your own preferences.
An interface should feel like it was made for the person using it. Not because we happen to share their taste, but because we understood what they needed and had the discipline to build toward that.
Typography is not about you. Neither is your product.
Butterick’s Practical Typography is free to read and worth paying for.