Design is decision-making

Ask someone outside the field what designers do all day and you’ll usually hear about drawing. Choosing colors, nudging shapes, making it look nice. An understandable answer, and wrong in a way that quietly explains a lot of bad websites.

Design isn’t drawing. It’s deciding.

The drawing is real, but it’s the last mile. By the time anything gets drawn, the work that determines whether the thing will succeed has mostly already happened, or failed to happen. Take something as ordinary as a homepage that looks simple. Hiding inside it is a long ledger of calls somebody had to make:

• What a stranger should understand in the first five seconds.
• Which of the nine things the company wanted to say got cut down to three, and who had to be told their favorite didn’t make it.
• What earned the top of the page.
• Where ideas go when nobody has the heart to delete them, which is the footer.
• What happens on a phone. Which is to say, what happens for most people.

Notice that none of these are aesthetic questions. They’re editorial questions, strategic questions, occasionally political ones. Answering them means ranking things, and ranking things means telling someone that what they care about matters less than something else. No font choice will ever be as hard as that conversation, and no font choice can substitute for it either.

The page as verdict

Indecision, meanwhile, has a look. You’ve seen it. The homepage with four headlines at equal size, each one hedging against the others. Three buttons in a row, all shouting, all the same weight, because three departments each needed a win. A navigation bar with eleven items. That page isn’t a design failure, exactly. It’s an unresolved meeting, published.

This is the thing about pixels: they can’t hedge. Copy can be vague, strategy decks can be vague, an org chart can stay comfortably blurry for years. A layout can’t. Something has to be first. One element will be biggest whether you chose it or not, and if you didn’t choose it, the choice gets made by whoever’s least willing to shrink. Every screen renders a verdict on questions the company may have been avoiding for years, which is why the design phase of a project so often surfaces arguments that have nothing to do with design.

We’ve come to think of every finished artifact as a record of decisions, readable by anyone who knows the language. Show us a website and we can make a fair guess at where the politics live, which stakeholder won, what the company is a little afraid of, and whether anyone in the building is allowed to say no. Clarity on a screen means somebody, somewhere, said it and made it stick.

The pixels are a fossil record of the meetings.

Craft still counts

None of this diminishes craft, by the way. Executing a decision beautifully is its own discipline, and we care about it to a degree our families find tiring. But craft applied to an undecided page just produces well-kerned confusion. Polish is a multiplier, and a multiplier needs something to multiply.

It also explains why the best design conversations we have with clients rarely mention design. They sound like strategy sessions, or arguments about the business, or occasionally therapy. What do you want to be known for. Which things are you willing to stop saying. Who is this actually for, once we stop being polite about it. When those questions get real answers, the layout tends to fall into place with almost suspicious ease, because a layout is just a hierarchy, and hierarchy is just a decision wearing clothes.

So if the design phase of your project feels slow, check what kind of slow it is. Slow because the type isn’t right yet is fine; that’s craft doing its rounds. Slow because nobody will say which of the six priorities is the real one: that’s not a design problem, and no amount of drawing will fix it, because the drawing was only ever going to record the answer.

When we hand over a finished design, the file is the receipt. The product was the two hundred decisions behind it.

The drawing is just how we wrote them down.