We spent a decade hiding behind the interface. Now it’s gone.
Eight months ago, the questions started showing up in meetings I wasn’t supposed to notice them in.
“Can’t Figma AI just do that?”
“We used Claude for the mockups — do we still need to bring in a designer?”
“If the AI can generate the screens, what exactly are we hiring for?”
I am Head of Design at a global restaurant technology platform. I built design teams at Walmart and Capital One. I have spent years in rooms where I had to fight for design to be treated as something other than a screen factory — the team you call when engineers need something to build and the team you cut when the budget gets tight.
And for eight months, I have been fielding versions of the same question.
It stings. But here is the thing nobody wants to say out loud:
They are not entirely wrong to ask.
Not because design doesn’t matter. Because for most of the last decade, a significant portion of what design teams actually produced — the thing designers were hired, evaluated, and promoted for — was exactly the kind of work AI can now do faster, cheaper, and without a Slack message.
We built the conditions for this. We just didn’t think we were building a trap.
Peter Merholtz recently wrote what a lot of us in design leadership have been thinking but not saying out loud: design didn’t lose its strategic seat because organizations took it away. Design traded it — incrementally, for salary bands and delivery velocity and the comfortable feeling of being needed, right up until the moment it wasn’t. He’s right. I’ve been a design executive for over a decade at Walmart, Capital One, and now Byte by Yum!, and I have watched design leaders — myself included — make that trade without fully examining what we were giving up.
This is not a piece about Peter being wrong. It’s a piece about what comes next.
We Built This Trainwreck Ourselves
Design built the conditions of its own displacement starting in the 2010s when design thinking began its big boom. By the time I joined my first corporate job, I was inheriting the wreckage of that boom — corporate halls that saw design thinking as a workshop instead of a way to shape industry.
Design scaled. Teams of ten became teams of hundreds. Salaries doubled. Org charts moved design closer to the C-suite and it looked, from the outside, like design had finally arrived. We had seats at tables we had spent years being excluded from.
What was actually happening was narrower than that.
Design was scaling to support agile delivery. Every product team needed a designer. Every designer needed to keep engineers unblocked. The greatest professional sin was being the bottleneck — the person who slowed the sprint, the one whose work wasn’t ready, the designer who wanted to do more research before the thing shipped.
So we got fast. Really fast. We got good at producing screens quickly, consistently, in volume. We built design systems so nobody had to make decisions twice. We shipped. We hit our velocity numbers. We got promoted for it.
And while all of that was happening, something else was quietly leaving the building.
Not design. Design was everywhere. I mean the part of design that cannot be templated: the judgment that looks at a brief before a line of code is written and says this will fail someone, and here is how. The instinct that holds a whole system in your head while everyone else is staring at the feature in front of them. The willingness to say the uncomfortable thing in the room where the decision is actually being made.
Those capabilities did not disappear because organizations stopped valuing them.
They atrophied because we stopped practicing them. We were too busy shipping to build the muscles that would have made shipping matter.
I was in those rooms. I made versions of that trade. I know exactly what it felt like to choose velocity over the harder conversation — and to tell myself I would get back to the harder work later, when things settled down.
Things did not settle down. They never do.
Design didn’t get disrupted. It got what it built.
AI automates what is lowest value first. For design, that was UI.
Not because UI is easy. It isn’t. But because it is repeatable. Learnable. Describable enough to train a model on. The things that made a designer valuable inside an agile team — the ability to produce good enough material quickly enough, consistently enough, without dropping the sprint — are exactly the things that translate cleanly into a prompt.
The problem is that a significant number of designers built their entire professional identity around being fast at that.
Not because they were lazy. Because they were rewarded for it. Velocity was the metric. Screens shipped was the proof of value. The designer who could turn around ten high-fidelity mockups by Thursday was the one who got promoted, got the raise, got pointed to as the example. We built a profession that selected for throughput and then acted surprised when throughput got automated.
I watched it happen from inside it. I have sat in performance reviews where the conversation was entirely about delivery. How many products did the team touch. How quickly did designs move to handoff. Whether the design system was being used consistently enough to speed up the next sprint. Rarely did anyone ask: did we design the right thing? Did we see what was coming before it shipped? Did we prevent anything?
We did not have language for prevention. We had language for production.
So when AI arrived and production got cheap, a lot of designers did the only thing they knew how to do: they got faster. They learned the new tools. They optimized their prompts. They competed on the dimension that was being commodified.
That is the wrong bet.
AI didn’t expose a weakness in design. It exposed a lie we told ourselves to survive.
For thirty years, the field has said the same thing in every executive briefing, every conference keynote, every hiring conversation where we were trying to justify the budget: design isn’t how something looks. It’s how something works.
We meant it. And we also couldn’t fully prove it, because the interface was always in the way.
The screen was the only thing that made the invisible visible. You couldn’t show a CEO how a system worked without first showing them what it looked like. You couldn’t get engineers aligned on a concept without mocking it up. You couldn’t get stakeholders to feel the experience without rendering it. So we rendered it. Constantly. We spent the majority of our professional hours producing the visual proof of thinking that lived somewhere deeper — because without the visual, nobody could see the thinking at all.
AI just made that part cheap.
And what’s becoming clear, now that the scaffolding is gone, is that for a lot of people who called themselves designers — the scaffolding was the only skill the job ever asked them to develop.
I want to be precise here, because this is not an argument that UI is easy or that the people who do it well are somehow less than. UI is hard. Doing it well requires a depth of craft that takes years to build — visual hierarchy, interaction logic, accessibility, the thousand small decisions that make something feel effortless to use. That work matters. It has always mattered. But UI is the translation layer, not the thing itself.
What the last decade did, in its sprint toward velocity, was quietly stop rewarding everything else. The job became: be fast at the primary thing. Ship. Repeat. The T-shape that design education preached got flattened into a single vertical line.
But if you spent the last decade learning to show the work without learning to do the work — if the mockup was the thinking and not the artifact of the thinking — then what AI took from you wasn’t a tool.
It was the thing you were hiding behind.
I don’t say that to be cruel. I say it because I have sat across from talented, hardworking designers who are genuinely terrified right now, and the terror is specific. It is not my tools are changing. It is I don’t know what I am without the tools.
That is the question the field needs to answer.
The market is repricing the value of design.
This is not a story about AI eliminating design. It is a story about companies being forced to change what they optimize for — and design needing to change with it. Right now, in most organizations, the optimization is around speed, risk reduction, margin, and adaptability. The ability to move fast without breaking things that cost a fortune to fix later.
In that environment, certain work gets automated first. Not because it’s unimportant — but because it’s describable. Repeatable. Trainable. Production work. Visual execution. Variations at scale. Pattern application. The things designers used to spend 40 to 50 percent of their time on.
That work is now cheap. Which means competing on it makes you cheap.
When anyone can generate twenty concepts in ten minutes, concept generation is no longer premium. When any product manager can mock up a flow before the meeting, fidelity is no longer the proof of expertise. When the tool does the production, the person running the tool is overhead.
What becomes scarce — and scarcity is where leverage lives — is judgement.
What to pursue. What to kill. What not to build at all. When to move fast and when moving fast is the most expensive decision in the room. How to walk into a brief that says “use AI to improve trust” when nobody in the room can define trust, and move the work forward anyway.
That kind of judgement cannot be prompted. It cannot be templated. It does not get cheaper as the models improve.
And it lives in four specific skills that design has always claimed to value — and largely underdeveloped.
Ambiguity tolerance. The brief is incomplete. The stakeholders disagree. The problem isn’t defined well enough to solve yet. You move forward anyway — not recklessly, but deliberately. You define the thing nobody else wanted to define, because leaving it undefined was more expensive than the conversation.
Systems thinking. The thing you’re designing changes more than the UI. It changes the workflows, the staffing, the legal review, the data contracts, the things that break before they visibly break. You hold the whole system in your head while everyone else is focused on the feature.
Risk interpretation. The feature technically works. You see how one wrong answer at scale becomes a headline, a support ticket avalanche, a trust problem that takes years to repair. You are the person who asks what happens when this fails while it is still being built.
Organizational alignment. You get product, engineering, legal, and leadership pointed in the same direction before anything goes live, so nobody is surprised when it does. Not because you are a skilled meeting facilitator. Because you understood the political architecture of the organization and you navigated it on purpose.
These are not soft skills. They are not the nice-to-haves at the end of the curriculum after the Figma tutorials.
These are the skills that don’t get automated.
These are the skills that don’t get cheap.
And these are the skills that move you from interface altitude — to influence.
AI just gave you 40% of your time back.
You can look at what has been stripped away and say: 40% of my job got automated. What am I going to do.
Or you can say: I just got 40% of my time back. What am I going to build with it.
Those are not the same question. And which one you ask will determine what the next decade of your career looks like.
Most designers, when automation accelerates, respond in one of three ways. They try to get faster. They try to master every new tool. They try to out-produce the machine. I understand the instinct. It is the only move the last decade trained us to make.
But you cannot win an efficiency war against automation. The harder you run on that track, the more replaceable you become. The machine will always be faster. That is not a temporary gap. That is the point.
The time you got back is not a buffer. It is not a grace period before the next disruption. It is the first real investment window most designers have had in a decade — unrushed, non-sprint, not already spoken for by Thursday’s handoff.
What you put into it is a choice. Not a passive one.
Design said for thirty years it wasn’t about how something looks — it was about how something works. That designers were builders, not decorators.
The scaffold we hid behind is no longer load-bearing.
The crossroads is not coming.
You’re already standing in it.
Jessa Parette is Head of Design at Byte by Yum! and an advisor to design and product leadership teams. She works at the intersection of AI-driven systems, organizational complexity, and experience design at scale. Speaking and advisory: www.jessaparette.com
AI just called design’s bluff was originally published in UX Collective on Medium, where people are continuing the conversation by highlighting and responding to this story.
