015 The Rise of AI Builders

🎧 Listen to this episode on Apple Podcasts, Spotify, or your favorite platform.

AI Builders Need More Than Better Tools

There is a strange thing happening in product and design work right now.

AI is making it easier to build faster prototypes, faster ideas, faster summaries, and faster experiments. Faster everything.

Meanwhile, many of us are being asked to respond accordingly: move faster, learn faster, ship faster, adapt faster.

That sounds exciting, and well, it can be exciting.

It also raises a question we may not be asking loudly enough:

If AI makes it easier to create more things, how do we make sure we are creating better things?

In this episode of Pixels & Priorities, we sit down with Shane Ward, Manager of Product Design at Storable to discuss the new world of AI builders. Shane works across design vision and product strategy, which makes him the perfect person to talk with about this new blurry territory where product, design, engineering, and AI-assisted building are all bumping elbows at the same crowded table.

One of Shane’s clearest concerns was quality.

“How do we keep the quality in our work? How do we keep the quality in our decision-making?” — Shane Ward

Because when AI can generate endless options, product work can start to feel like walking through Bellatrix Lestrange’s Gringotts vault under the Gemino curse: touch one idea, and suddenly the room is filling with copies faster than anyone can sort what’s valuable from what’s just multiplying.

AI Is Blurring Product and Design Roles

For years, product and design roles had more defined lanes.

Product management often focused on business goals, roadmaps, metrics, prioritization, and value. UX design focused on user experience, usability, interaction patterns, and whether people would actually want to use the thing being built.

Those lanes were never completely separate, of course. The best product and design work has always required overlap.

AI is accelerating that overlap.

Shane described a shift toward “AI builders,” where design, product, and engineering all become more capable of creating and experimenting directly. That can be energizing, because it gives people more access to skills and tools that used to sit behind role boundaries.

It can also get messy. Maybe it's already feeling messy for you.

If everyone can generate ideas, prototypes, flows, content, and analysis, then teams need more than access. They need clarity.

Who owns quality?
Who validates the work?
Who decides what ships?
Who notices when the AI output looks plausible but is quietly wrong?

Product and design are not only about making things. They are about making choices.

Faster Production Can Create Slower Judgment

One of the most important ideas from the episode is that AI may reduce production friction while increasing decision friction.

Shane put it this way:

“The difficult part is not so much creating things now… It’s how do we get through the massive amount of stuff that we can produce now, find the quality bits, and put them together in a way where we have a good product in the end?” — Shane Ward

The bottleneck used to be production. We needed time to design the screen, write the document, create the prototype, generate the options, summarize the research, or build the test.

Now, AI can help produce many of those outputs quickly.

So the bottleneck moves.

The new bottleneck is discernment.

For product managers and UX professionals, discernment means being able to evaluate whether an idea is useful, ethical, feasible, aligned with user needs, and connected to business goals. It means knowing when something is merely polished versus genuinely valuable.

AI can generate options. It cannot automatically create team alignment around which option matters.

AI Will Not Fix Broken Communication

J offered a brutally useful analogy: a couple having trouble communicating decides that a baby will fix the relationship.

That is how some organizations seem to be approaching AI.

A team already has unclear decision-making, cross-functional tension, reactive planning, weak alignment, and constant firefighting. Then AI enters the room wearing a tiny superhero onesie, and everyone hopes the new one will magically create focus.

It probably will not.

“The same struggles we have now when we’re trying to communicate with each other effectively as designers and product are only going to be magnified by AI.” — J Schuh

AI does not erase existing team dynamics. It often exposes them.

If product and design are already struggling to make decisions together, AI may simply give them more artifacts to disagree about. If leadership already makes reactive choices without transparency, AI may accelerate those decisions without improving the reasoning behind them.

That is why AI adoption is not only a tooling conversation. It is a leadership conversation.

Knowledge Is Not the Same as Understanding

AI can give someone vocabulary. It can summarize concepts. It can explain a framework. It can produce something that looks like a product strategy, research synthesis, or design recommendation.

That does not mean the person using it understands the tradeoffs.

“Knowledge does not equal understanding.” — J Schuh

Understanding comes from experience: failed launches, usability tests, stakeholder conversations, messy constraints, customer nuance, technical realities, and all the tiny paper cuts that teach us how real product work behaves outside the slide deck.

AI can help us learn, support our thinking process, and accelerate exploration.

AI should not become a shortcut around understanding.

Decision-Making Needs More Transparency

As I listened to our conversation, I kept returning to the "why" behind decision-making.

“I am most concerned about our ability to make decisions in a way that is not reactive and is not in a vacuum.” — Metsy Rose

Product and design teams need to understand why decisions are being made. Why this AI platform? Why this product direction? Why this feature? Why this customer segment? Why this tradeoff?

Without transparency, AI can become another layer of mystery. Another black box. Another reason teams are asked to trust decisions without understanding the information behind them.

AI outputs can sound confident even when they are wrong.

“It is still ultimately a set of tools and useful technology, and not a reason to outsource our own brains.” — Metsy Rose

That may be one of the most important principles for product and design teams right now.

Use AI. Learn with it. Experiment. Build. Explore.

Keep your brain in the loop.

Practical Takeaways for Product and Design Teams

If we want AI to help us build better products, not just faster ones, we need stronger habits around how we work.

A few places to start:

• Define what quality means before generating more options.
• Clarify who makes decisions and what information those decisions require.
• Use AI to expand thinking, not replace expertise.
• Keep research, user interviews, and customer empathy close to the process.
• Make AI outputs reviewable, explainable, and challengeable.
• Treat cross-functional communication as part of the AI workflow, not an afterthought.

The future of product and UX work may involve smaller teams, broader roles, and faster experimentation.

That makes collaboration more important, not less.

Questions for Reflection

1. Where is our team using AI to move faster without first defining what “better” means?
2. Which decisions in our product process need more transparency, context, or shared understanding?
3. Are we using AI to support human judgment, or quietly outsourcing decisions we should still own?

Key Takeaways

• AI is blurring the boundaries between product, design, and engineering.
• Faster production creates a greater need for quality standards and decision clarity.
• AI will magnify broken communication if teams do not address it directly.
• Knowledge from AI is not the same as understanding built through experience.
• The strongest AI-assisted teams will still rely on human judgment, community, and collaboration.

Final Thoughts

The rise of AI builders is exciting because it gives product and design teams new ways to imagine, test, and create.

It is also challenging because building faster does not automatically mean building wisely.

The teams that thrive will not simply be the ones using the newest tools. They will be the ones asking better questions, communicating more clearly, protecting quality, and refusing to let speed outrun judgment.

As Shane said near the end of the conversation:

“We get past this with community.” — Shane Ward

That feels like the right place to land.

Not with panic. Not with blind optimism. With people learning together, challenging each other, and building useful things with care.

– Metsy
Co-host, Pixels & Priorities

Stay Connected

🎧 Listen to new episodes every Tuesday on Apple Podcasts, Spotify, or your favorite podcast platform. Please leave us a rating, submit a review, and share with a friend. It helps more people find the show and join the conversation.

Connect on LinkedIn: Metsy Rose | J Schuh | Pixels & Priorities