Define Before Design

Production is not design. It never was.

❝ The name of the song is called ‘Haddocks’ Eyes.’ / ‘Oh, that’s the name of the song, is it?’ Alice said, trying to feel interested. / ‘No, you don’t understand,’ the Knight said, looking a little vexed. ‘That’s what the name is called. The name really is ‘The Aged Aged Man.’
— Lewis Carroll, Through the Looking-Glass¹

Something arrives in your inbox, and it’s not a brief, not a diagram, not even a wireframe with annotations. What you received was a a link to a finished screen, functional, navigable, mostly coherent, built by the product owner using AI in an afternoon between two other meetings. The implicit question hanging over it was: Can you make this work?

Which is, of course, the wrong question. But let’s not get ahead of ourselves.

The Wrong Question

The design industry has reacted to this moment the way it tends to react to most threats, by producing advice. Make the tradeoffs visible, don't gatekeep, expand your value beyond execution. Sensible counsel, every item of it, and also, in a way that is easy to miss on first reading, a complete surrender to the premise. Value yourself correctly. Justify your seat at the table.

This is survival discourse, which, by definition, cannot ask whether the table itself was ever arranged correctly. So let me ask it: what if designers were not displaced by AI at all, but displaced themselves, gradually and systematically, across a decade of standup meetings and sprint reviews, by agreeing to be the people who make things rather than the people who define what should be made?

How It Actually Happened

There is a particular kind of bureaucratic entropy, one that Pynchon identified across many of his novels, though he gave it other names, in which systems drift quietly and without anyone intending it toward their least meaningful version of themselves, like the post office² that forgets it is about correspondence and remembers only the sorting. Design, somewhere along the way, forgot it was about definition and remembered only delivery, and it did not happen maliciously so much as it happened through a thousand small steps: the designer who did not push back on the brief because the deadline was real, the team that skipped the problem definition session because the stakeholders already knew what they wanted, the discipline that spent fifteen years perfecting its handoff process, annotated specs, developer-ready components, pixel-perfect deliverables, and somewhere in the perfecting, stopped asking whether the thing being handed off needed to exist at all.

This is the empty area the product owner walked into with AI.

Let Us Be Precise

Let us be precise about what actually happened, because precision here is not pedantry but obligation. The product owner did not steal the designer’s job, but encountered a gap in the process, a space where the question “what are we actually trying to do?” should have been and was not, and filled it with the most available tool. The fact that this feels like a threat is revealing. Designers had already handed over the work of definition, kept only the work of execution, and are now caught off guard to find that execution is exactly what the tools do best.

The screen you received is not the problem; it’s the symptom, and the problem preceded it by years.

The Medium and the Decoy

McLuhan³, who was right about nearly everything and credited for almost none of it in the rooms where it matters, argued that the content of any medium is the least interesting thing about it, that the real work happens in the structure, in the conditions the medium creates before we've noticed it has created them.

Design did something similar with its tools, spending so much time perfecting what it made and how it made it, that it stopped asking why it was making it at all, and by the time the frame of making had quietly shifted, the question of purpose had already been answered by someone else, or left unanswered entirely, which amounts to the same thing.

Define Before Design is a recognition that the act of definition is the design, that every decision made before a single element is placed on a canvas is more consequential than anything that comes after it, and that the discipline which abandons that act will eventually find itself standing in front of a screen someone else made, wondering what it is supposed to do with it.

Two Ways of Being in the Room

This is where the survival framing fails most completely, because it assumes the goal is to remain in the room, to be present at the table where decisions are made, and it is not wrong about this, only shallow, because there are different ways of being in a room. You can be there as the person who refines what has already been decided, who catches the edge cases, patches the inconsistencies, makes the incoherent passable, or you can be there as the person who makes the first decision, the one that precedes all the others: what is this for?

The product owner using AI did not make a design decision. The product owner made a production decision in the absence of a design decision, and those are genuinely different things, with the difference being not aesthetic but ethical, the difference between a thing that came into the world because someone defined the problem it should solve and a thing that came into the world because the tools to make it were available and the deadline was Thursday. Design without a preceding definition is not a faster or more democratic version of design; it’s simply production, and production was never the point.

A Prior Obligation

None of which is easy to say in a sprint review, with the machine already running, the screen already existing, the product owner already proud of it. And this is perhaps where designers have the most uncomfortable work ahead of them, not in the craft, which was never really under threat, but in the conviction required to arrive earlier, before the AI session, before the afternoon between meetings, and say clearly: we have not defined this yet, and until we do, making it is only motion.

Define Before Design. Not a principle, not a framework, not a methodology to be borrowed, rebranded, and sold back to you. A prior obligation, one that design has been quietly outsourcing for years, and is only noticing now because someone else picked it up.

NK

☉

1. Charles Lutwidge Dodgson, better known by his pen name Lewis Carroll, was an English author, poet, mathematician, photographer and reluctant Anglican deacon.

2. The Tristero / Thurn und Taxis, in The Crying of Lot 49. The entire novel is built on a postal conspiracy, which is itself a perfect metaphor: a communication system that has drifted so far from its original purpose that it now exists primarily to perpetuate itself and suppress alternatives. The bureaucracy of mail delivery becomes indistinguishable from the bureaucracy of control. Nobody can tell anymore whether the system serves correspondence or whether correspondence serves the system.

3. Marshall McLuhan was a Canadian philosopher and media theorist best known for his profound insights into communication and the impact of media on society. His famous provocation, The Medium is the Message, was never really about technology. It was about attention: where we direct it, and what we miss while we are directing it there. Designers spent a decade attending to the message inside their tools, the screens, the components, the systems, and missed the message of the tools themselves, which was that the act of definition was being quietly redistributed to whoever opened the file first.