People Have Always Wanted to Skip UX Design. AI Just Makes It Easier.

I've spent years in product leadership watching the same cycle play out. A company builds something functional, ships it without much design thought, and then either gets lucky because their users don't care that much, or gets punished because their users absolutely do. AI has only given that impulse more ammunition. Now, when someone wants to cut the design phase, they can still achieve baseline usability, almost automatically.

That impulse isn't always wrong.

Stakeholders who push back on design budgets aren't villains. They're doing their jobs. Fiscal prudence is a legitimate responsibility, and if you're building a product where users just need it to work—where experience isn't your differentiator and nobody's choosing you because of how good it feels to use—then scrutinizing what you spend on design makes sense. Sometimes that skepticism comes from a genuine misunderstanding of what UX delivers. But sometimes it comes from a clear-eyed assessment that their product simply doesn't need to win on experience. Both deserve a real answer. AI just makes that question a lot more urgent.

AI Didn't Kill UX. It Raised the Floor.

Here's the reality: AI-generated interfaces aren't bad. They're actually getting more and more competent at producing layouts, flows, and component structures that follow established patterns. If your product needs a settings page, a data table with filters, or a standard onboarding flow, an AI can give you something that works. And honestly? For a lot of products, that's enough.

The fact of the matter is that not every product is competing on experience. Insurance platforms, financial dashboards, internal enterprise tools—these products live and die by their data, their reliability, and their compliance posture. Their users don't need a delightful experience. They need a functional one that follows the patterns they already understand.

For these companies, AI as a UX tool is genuinely useful. It lowers the barrier to satisfactory user experience in the same way that component libraries and design systems did before it. It's a rising tide. Developers who previously shipped interfaces with no design consideration at all can now ship something that at least follows conventions. That's progress.

The Trap: Mistaking "Good Enough" for "Good"

Here's my prediction: a significant number of companies are going to use AI to generate their user experience, see that it works, and conclude that they've solved design. They'll cut their UX budgets, reassign their designers, and move on.

Some of them will be right to do so. The ones selling commodity software, the ones whose product value is in data accuracy or integration depth rather than user interaction—they'll probably be fine. Their AI-generated patterns will serve their users adequately, and the cost savings will make sense on the balance sheet.

But the companies whose product is the experience? The ones competing in crowded markets where switching costs are low and user expectations are high? They're going to find out the hard way that pattern-based design doesn't differentiate. It can't. By definition, it produces what already exists. It gives you the aggregate solution, and the aggregate is not how you win.

What Actually Changes (and What Doesn't)

What changes is the role. I think we're heading toward a world where many product teams don't need a UX designer creating screens from scratch for every feature. What they need instead is a UX expert who can audit, direct, and elevate what AI produces. Think of it less like an architect drawing every blueprint and more like a structural engineer reviewing the plans and catching what the automated tools missed.

Even in industries where AI-generated patterns are perfectly appropriate—finance, insurance, enterprise SaaS—there should still be someone with UX expertise in the room. Not necessarily designing every interaction, but ensuring that the sum of all those pattern-based decisions actually creates a coherent experience. AI is excellent at solving individual interface problems. It's not great at understanding how those solutions connect to form a product that feels intentional.

What doesn't change is the fundamental truth that has always driven this tension: companies have always wanted to spend less on design because its value is hard to quantify until it's absent. AI doesn't change that dynamic. It just gives companies a more convincing way to tell themselves they don't need it.

The Honest Advice

If you're leading product at a data company, a B2B platform, or an enterprise tool where your users expect convention over innovation, lean into AI for UX. Equip your developers with AI tools that generate solid, pattern-based interfaces. You'll ship faster and your users will be well-served; but keep a UX expert on retainer, even if you don't keep one on staff. Have someone who can look at what the AI produced and tell you where the gaps are, where the assumptions break down, and where your users are going to get stuck in ways that no pattern library anticipated.

And if your product competes on experience? If user interaction is your moat? Then AI is a tool for your design team, not a replacement for it. The companies that understand this distinction are going to pull ahead. The ones that don't are going to spend the next few years wondering why their perfectly adequate interfaces aren't winning anyone over.

The desire to skip design isn't going away. AI just means we need to get smarter about when that instinct serves us and when it costs us everything.

If you're not sure which side of that line your product sits on, Tech9 can help.

Let's talk.