A few years ago, I sat in meetings where the same sentence kept appearing in different forms:
“That’s not really my role.”
A designer couldn’t run research because there was a researcher.
A design manager couldn’t make mocks because they were managing.
A PM couldn’t prototype because they didn’t know Figma.
An engineer couldn’t talk to customers because that belonged to Product.
The work moved slowly, but everyone stayed inside their lane.
For a long time, this made sense.
Organizations become more efficient through specialization. As companies grow, roles get clearer. Teams form around expertise. Job descriptions get longer.
The problem is that the world changed.
AI dramatically reduced the cost of execution.
Thanks for reading AI/UX Playground! Subscribe for free to receive new posts and support my work.
Today, a PM can create a prototype in an afternoon.
A researcher can build a working demo before scheduling a study.
A designer can generate a first draft of a product strategy.
An engineer can create a customer-facing presentation.
The barriers that once required specialized teams are disappearing.
What’s left is judgment.
And judgment has never belonged to a job title.
I’ve been tracking this shift on AI UX Playground—patterns, prompts, skills, workflows, and a growing Playground of vibe-coded projects. The more I catalog it, the less this feels like a career trend and the more it feels like a new default for how product work actually happens.
The new divide
The divide is no longer between designers, PMs, researchers, and engineers.
It’s between people who wait and people who build.
A tool we actually use for builder work
When the deliverable is a live marketing site or portfolio—not a product codebase—we often reach for Framer. It’s the fastest way we’ve found to ship motion, responsive layout, and marketplace components, If you’re experimenting with yearly Pro, our partner code partner25proyearly adds three free months.
When faced with a problem, some people immediately start asking:
Who owns this?
Which team should do this?
Do I have permission?
Is this my responsibility?
Others ask:
What is the fastest way to learn?
What is the smallest thing I can build?
How do we move this forward today?
One group sees boundaries.
The other sees obstacles.
Only one group creates momentum.
That’s the through-line in The prototype is the deliverable in the AI era: when the artifact that moves a team forward is a deck or a spec, ambiguity survives longer than it should. Builders shorten that distance on purpose.
Leaders operate at every level
I’ve heard this framed a few ways in leadership conversations. The version that stuck is simple:
Leaders operate at every level.
Not because they have to.
Because they can.
The best leaders don’t hide behind organizational structure.
They don’t say:
“I would do it, but I’m a manager now.”
“I would help, but that’s another function.”
“I don’t have the right title.”
They use whatever tools are available to solve the problem in front of them.
Sometimes that means strategy.
Sometimes that means research.
Sometimes it means opening a blank design file at 11 p.m.
The role changes.
The responsibility doesn’t.
Builders win
One of the biggest misconceptions about leadership is that leadership is about directing work.
Increasingly, leadership is about reducing the distance between an idea and reality.
The leaders I see having outsized impact today are builders.
Not because they personally do everything.
But because they are capable of doing almost anything when necessary.
They can write.
They can prototype.
They can analyze.
They can interview customers.
They can facilitate alignment.
They can use AI to fill gaps in their expertise.
Most importantly, they don’t wait.
They create momentum before the organization realizes momentum is needed.
That’s what “reducing the distance between an idea and reality” looks like in practice: you pick the right medium for the job, and you ship something real. For a product flow or agent prototype, that might be Cursor and a runnable UI. For a live marketing site or portfolio—something shareable tomorrow, with motion and polish—it’s often Framer. We use it in the same builder spirit: marketplace components, responsive layout, interactions you’d spend days hand-coding. Not because it’s “the best tool,” but because it closes the gap fast when the deliverable isn’t a codebase. If you’re trying yearly Pro, code partner25proyearly adds three free months.
The Rise of the Design Engineer in the Era of AI is the craft version of this story: taste, systems thinking, and the ability to shape experiences directly. This piece is the org version: permission, identity, and who actually moves work forward.
The excuse that no longer works
For years, specialization provided a reasonable excuse.
“I don’t know how.”
That excuse is getting weaker every month.
You may not know how to code.
But AI can help you build a prototype. 7 AI Prototyping Prompts for UX Designers is a practical starting point.
You may not know research methodology.
But you can talk to five customers this week. How to Prompt AI for User Research handles the tedious synthesis so you can focus on the conversations.
You may not know how to create a presentation.
But you can generate a first draft in an hour.
The limitation is increasingly not capability.
It’s willingness.
Willingness to learn.
Willingness to look inexperienced.
Willingness to step outside a role that once felt safe.
If you’ve vibe-coded anything lately, you’ve felt the shift. 10 Prompting Rules I Learned After Vibe Coding 113 Interactive Demos isn’t really about prompts—it’s about learning to steer when the medium is interactive.
What this means for designers
Ironically, this may be the most exciting moment for design in decades.
Because design was never really about screens.
Design is the practice of identifying problems and creating better outcomes.
The medium has always been secondary.
Sometimes the output is a wireframe.
Sometimes it’s a conversation.
Sometimes it’s a strategy.
Sometimes it’s a prototype built with AI.
The designers who thrive won’t be the ones protecting the boundaries of the profession.
They’ll be the ones expanding beyond them.
How AI Is Changing the UX Designer Role (And What to Do About It) maps the emotional side: fear, identity, and what actually changes on the ground. The job isn’t disappearing. The default deliverable is changing.
Hiring language is catching up. Companies like Ramp are hiring AI-first designers walks through what “AI-first” means in a job description—and we published the AI Native Product Designer skill as a rubric you can install and adapt.
And taste still compounds. In a flood of AI launches, The Week I Realized I Was Learning the Wrong Thing is a useful gut-check: trust, clarity, and decision quality aren’t outdated—they’re the filter.
The future belongs to high-judgment generalists
Not generalists in the traditional sense.
Not people who know a little about everything.
People with deep expertise who aren’t constrained by it.
People who can move between strategy and execution.
Between thinking and making.
Between leadership and craft.
The future won’t ask what your title is.
It will ask:
Can you identify the right problem?
Can you make progress without permission?
Can you turn ambiguity into momentum?
The people who can do that will have an unfair advantage.
Not because AI replaced specialists.
Because AI removed the walls that separated them.
How to practice builder mode this week
Abstract talk is cheap. Here’s a small, concrete loop:
1. Pick one problem you’d normally route.
Don’t open a ticket. Don’t schedule a meeting. Name the smallest learnable thing.
2. Build the smallest artifact that advances it.
A clickable prototype. A five-customer interview guide. A one-page strategy draft. A workflow you can rerun next time.
3. Encode judgment so you don’t re-explain it.
Agent skills are one way to package expertise for Cursor or Claude Code—accessibility, critique, UX writing, design systems—so your standards travel with the work.
4. Show the artifact, not the role.
Let the prototype end the debate. That’s the whole point of prototype as deliverable.
If you want reference implementations for what modern craft feels like—not inspiration porn, but taste in motion—browse the Playground. Small tools and experiments that are thoughtful, weird, useful, and human.
Further reading
On Substack
On AI UX Playground
Patterns catalog · Prompts · Skills · Workflows · Playground
Thanks for reading AI/UX Playground! Subscribe for free to receive new posts and support my work.
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.