Writing

The default designer now builds

EssayJul '262 min read

The mockup was always a workaround. AI removed the excuse, and the role is resetting around people who ship.

For twenty years, the deliverable of product design has been a picture of software. Not software, but a picture of it. Mockups, prototypes, redlines, specs. An entire profession organized around describing a thing to the people who would actually make it.

That was never the point. It was a workaround for a real constraint: building was expensive, so we simulated first. The simulation got very sophisticated with component libraries, interactive prototypes, and design tokens, but it was still a simulation, and everyone downstream paid the translation tax.

The constraint is gone. A designer with an agent and a design system can now produce the real thing in roughly the time it used to take to produce the picture of the thing. A branch, in the codebase, running against real data.

Over the last year I watched this go from novelty to expectation inside a large platform company. The designers who leaned in stopped handing off. They opened pull requests. The conversation with engineering shifted from "is this what you meant?" to "here's the behavior, help me harden it." Review cycles that took a week collapsed into an afternoon, because the artifact under review was the product itself.

The hiring market has already repriced this. Founding-designer roles now assume you ship. The interviews I run and the ones I hear about from peers have quietly converged on the same question: show me something real you built. A URL.

Building being cheap makes the non-building parts of design more visible, because they're all that's left to differentiate on:

  • Problem selection. Agents will happily build the wrong thing faster than any team in history.
  • Judgment about behavior. What should happen across states, edges, failure, and recovery. The picture never captured this well anyway; code forces the question. Taste is the bottleneck when production is free.
  • Standards. Someone has to know the difference between shipped and good. That was always the job. When a model is composing the interface, that standard lives in the constraint system — see Generative UI.

The designers in trouble are the ones whose entire value was fluency in the simulation layer: beautiful mockups, immaculate files, and a hard dependency on someone else to make anything real.

This raises the bar and I won't pretend otherwise. "Designers should code" was a debate for fifteen years because it was optional. It's not a debate anymore; it's a default, the way writing was a default before it. You don't need to be a systems engineer. You need to be unwilling to hand your judgment to a translation layer.

The tools have never made that easier. The excuse has never been thinner.