The production trap

A junior designer I was mentoring last year sent me a message at 11pm on a Tuesday. She had been working at a product studio for eight months, she was good, her manager liked her work, and she had just watched a colleague generate a complete set of UI screens from a text prompt in about twenty minutes.

"I spent three days on something that just took him twenty minutes," she wrote. "What am I even doing here?"

I did not have a quick answer. Which is how I knew it was the right question.

The debate running through design communities right now is framed as tool versus threat. AI is either a productivity multiplier that frees designers to do higher-order thinking, or it is an accelerant compressing the bottom of the profession until entry-level roles stop existing. Both camps are loud. Both have evidence. Both are, in a specific and important way, missing the point.

But the question was never tool or threat.

The question is: what do you think design actually is?

The question is: what do you think design actually is?

If your answer is production, the threat is real and it is already here. But if your answer is judgment, the tools change the shape of the work without threatening the value of doing it well. The distinction matters more than anything else being said in this debate right now.

I fell into the production trap myself, early in my career. I was at a large enterprise, designing complex B2B software, and I was proud of how quickly I could turn around polished deliverables. High-fidelity screens, annotated specs, detailed component documentation. Stakeholders complimented the quality. My manager mentioned it in reviews. I thought that was the job.

But it took a senior product leader pulling me aside after a presentation to say something I have not forgotten: "Your screens are beautiful. But you're solving the wrong problem."

She was not being unkind. She was being accurate. I had been so focused on producing good work that I had stopped asking whether the work I was producing was good to produce. That is the production trap in full: you get so fast at making things that making things becomes the goal.

Here is what the AI anxiety in design is actually surfacing, if you look at it without flinching.

A generation of designers were trained, implicitly, to believe their value lived inside the artifact. The screen. The system. The prototype. The thing you could put in a portfolio, show in a case study, and hand off to engineering with a Figma link.

But that was never the full job. It was the visible part of the job. And visibility got confused with value so completely that most designers never separated the two.

The designers who are genuinely at risk right now are not necessarily the ones with weaker skills. They are the ones whose entire professional identity sits inside production, because the thing they have optimised for is the thing being automated fastest. And they never built the second layer.

But the second layer was always the real job.

The second layer is everything that happens before the screens exist. The framing of the problem. The pushback on the brief when the brief is wrong. The ability to walk into a room full of stakeholders who all want different things and leave with a shared definition of what success looks like. The judgment to know when a user research finding should change the product direction and when it is noise.

You cannot prompt your way to that. Not because AI isn't capable of surprising things, but because judgment requires stakes. It requires having been wrong before in ways that cost something. It requires scar tissue from decisions that looked right on the surface and failed in practice.

AI tools do not have scar tissue. But more importantly, the people who hired you don't need your scar tissue replaced. They need it applied.

When I think about what to tell junior designers right now, I resist the instinct to offer false comfort. The profession is changing. Some of what took days will get faster. Some of what took weeks will get automated. That is not a rumour.

But the change is also revealing something true that the profession has been obscuring for years: design was never primarily about making things. It was about deciding things. The making was how you proved you decided correctly.

The designers I have watched stay relevant through disruption, across every industry I have worked in, had one thing in common. They were never just the person who made the screens. They were the person who understood why those screens existed, what problem they were actually solving, and what would happen to real people if the team got it wrong.

No tool replaces that. Not because it isn't possible in principle. But because the organisations that need design are full of competing incentives and partial information and people who have not yet fully understood their own problem. Getting through all of that requires presence. It requires being in the room.

The junior designer who messaged me at 11pm replied to my response with: "So I need to stop thinking of myself as someone who makes things?"

Close, I told her. Think of yourself as someone who decides things. The making is just how you prove you decided correctly.

She still makes things. She has just stopped believing that is why she matters.