Is AI Killing User Experience?

The following article was written by Scott A. Snyder, a senior fellow at the Wharton School and author of Your AI Life, and Mike Welsh, chief storyteller at Bridgenext and author of The Backstory on Storytelling.

AI has changed the pace of product design almost overnight. Ideas that once took weeks to sketch, prototype, and test can now be made visible in hours. A product manager can describe a workflow and get a working prototype. A strategist can turn a client’s rough concept into a clickable experience before the meeting ends. A founder with no technical background can “vibe code” a beta version of their product for an investor pitch.

This is not a small shift. It compresses time, lowers barriers, and gives more people the ability to participate in creation. For organizations trying to move faster, it feels like a gift.

Yet the customers on the receiving end are not sold. Despite the perceived gains in speed and personalization, only 17% of consumers believe their experiences are getting better, according to a March 2026 Medallia report. A separate February 2026 Pega study found that more than 60% of consumers lack confidence in how businesses use AI to interact with them.

The more AI accelerates the making of experiences, the more important it becomes to understand who those experiences are for. We can generate customer journeys, personas, screens, content, and front-end code faster than ever. None of that guarantees we have understood the end user’s moment or the context around it and the emotion underneath it.

So the question is not really whether AI is killing user experience (UX). The better question is whether AI is exposing the parts of UX that organizations have been treating as optional.

UX Has Never Been Just the Interface

For years, organizations have used the language of user experience while narrowing the practice to screens, flows, and usability. Those things matter. A confusing interface can ruin a great idea. A broken flow can erode trust in seconds. But UX at its best has never been limited to the surface of the product.

Good UX begins before the wireframe. It begins with curiosity: Who is this person? What are they trying to do? What is getting in their way? What do they believe before they arrive? What would make them feel understood?

Those are not just design questions. They are story questions.

Every useful product experience — whether an internal enterprise tool or a customer-facing app — has a narrative structure. There is a character, a tension, a desired outcome, and a path through uncertainty. Sometimes the story is simple: I need to pay a bill without friction. Sometimes it is emotional: I need to understand a medical result without panicking. Sometimes it is social: I need to complete this task without looking foolish in front of my boss or my customer.

UX is where that human story becomes operational. It connects business strategy to human behavior. It translates brand promise into lived experience. It blends data and observation, analytics and empathy, system performance and emotional resonance.

AI can help with much of that. It can summarize research, analyze patterns, generate prototypes, and propose design alternatives. But it does not automatically know what matters. It does not stand in the rain watching customers struggle with a broken process. It does not hear the sigh before someone abandons a transaction. It does not feel the subtle difference between “This works” and “This understands me.”

The better question is whether AI is exposing the parts of UX that organizations have been treating as optional.

The Speed Trap

The most seductive promise of AI is time compression. Teams can move from idea to artifact faster than ever, test more options, and abandon weak ideas quickly. In many cases, AI will make teams more creative, more collaborative, and more productive.

But there is a trap inside that speed. Just because we can build something in an hour does not mean it is good. It does not mean it solves a real problem. It does not mean anyone will use it. And it certainly does not mean the organization has done the hard work of understanding why the experience should exist in the first place.

When every team has access to similar tools, similar prompts, and similar model-generated patterns, expect more sameness, not less. AI can help organizations produce a lot of competent work. It can also help them produce a lot of me-too experiences that look finished before they are truly thought through.

That is where UX becomes more valuable, not less. The role of UX in an AI-powered world is not to slow everything down for the sake of process. It is to protect brand meaning and differentiation while the organization moves faster — to ensure rapid creation does not become rapid confusion, and to help teams distinguish between a prototype that looks plausible and an experience that earns trust.

AI can accelerate the what. UX has to defend the why.

The Risk Is Shallow Understanding

The most valuable moments in UX often live in the in-between spaces. They are not always obvious in clickstreams or neat rows in a spreadsheet. They emerge from watching real people navigate real situations with all the impatience, improvisation, and emotion that come with being human.

Without getting out from behind the screen and walking in the shoes of your users, designers will likely fail to get to the deep insight needed to create experiences that people love.

UX field research for a growing convenience store that offered gas and quick-service meals revealed a hidden behavior: Consumers felt guilty leaving their cars at the gas pump and blocking other cars while waiting for their food to be prepared.* Overcoming this “pump anxiety” was a key design point in their mobile app that allows customers to order ahead and know that their food will be ready when they pull in. A purely AI-driven UX process would have missed this.

AI tools can create a persona, draft a journey map, propose a service blueprint, and summarize user pain points. Those outputs can be useful starting points. But they can also create a false sense of confidence. The artifact looks like research. The prototype looks like design. The deck looks like strategy. The interface looks complete.

But did the team actually learn anything? Did they spend time with the people they are trying to serve? Did they understand the emotional context of the moment? Did they test with real users? Did they discover anything surprising? Did they change their minds?

If the answer is no, then AI has not killed UX. It has simply helped the team skip it faster.

This is where leaders need to be careful. AI can make weak discovery look polished, premature ideas look market ready, and average thinking look more sophisticated than it is. The cost rarely shows up immediately. It shows up later as low adoption, customer distrust, support volume, rework, churn, or a product that technically works but never becomes part of the customer’s life.

The future belongs to teams that use AI to deepen understanding, not avoid it.

Every AI-powered experience should still answer a human question: What is this person trying to do right now, and how can we help?

Toward AI-Augmented UX

The right path is not resistance. UX teams should not treat AI as an intruder. They should treat it as a collaborator that changes the economics of exploration.

AI can help researchers synthesize large bodies of feedback, generate alternative flows, simulate use cases, identify edge cases, and prototype variations quickly. It can support accessibility reviews, content testing, localization, and design QA. Used well, AI expands optionality — but only if paired with human judgment.

The strongest teams will build a hybrid model where AI supports speed and scale while UX protects strategy, empathy, and trust. That model requires new habits.

Teams need to separate generation from validation. AI can generate possibilities, but users validate value. A hundred prototype variations are only useful if the team knows what it is trying to learn.

Teams need to treat trust as a design requirement. As AI becomes more embedded in products, users will want to know what the system is doing, why it is making a recommendation, when a human is involved, and how much control they still have.

Teams need to design for explanation, not just interaction. In AI-powered experiences, systems may make decisions, predictions, or summaries that feel opaque. The UX challenge is not only to make the interface usable. It is to make the intelligence feel understandable.

And teams need to keep the story in view. Every AI-powered experience should still answer a human question: What is this person trying to do right now, and how can we help?

Upskilling UX Practitioners

We are entering a period where UX, product strategy, service design, behavioral insight, and AI literacy will become more tightly connected. Call it AI interaction design, AI-augmented UX, or simply the next version of good product work. The label matters less than the discipline.

Designers will need to understand how AI systems behave. Researchers will need to test not only whether users can complete a task but whether they trust the system helping them do so. Product leaders will need to decide where automation belongs, where human review is essential, and where intelligence should be visible or invisible.

UX professionals will need fluency in prompts, agents, model behavior, explainability, bias, and human-in-the-loop design. AI teams will need fluency in empathy, context, story, and adoption. Business leaders will need to stop treating UX as decoration at the end of the process and start treating it as a strategic capability at the beginning.

An automated experience often feels like the company found a cheaper way to avoid you. An aware experience feels like the company understood your situation and used intelligence to help. That is the bar.

AI is not killing UX. It is forcing UX to grow up.

Recommendations for Leaders

The practical path forward is not complicated, but it does require intention:

• Invest in UX as a strategic asset. Do not reduce research and design capacity because AI can produce artifacts faster. The volume of possible output is about to explode — and the organization will need stronger UX judgment to make sense of it.
• Retrain teams to work alongside AI. Designers, researchers, strategists, and product managers should all learn to use AI tools responsibly. But the goal is not tool fluency alone. It is better questions, faster learning, and clearer decisions.
• Build trust into AI experiences from the start. Transparency, explainability, control, escalation, and human oversight should not be bolted on after launch. They belong in the experience architecture from day one.
• Protect deep discovery. Don’t mistake generated output for user understanding. Use AI to accelerate synthesis and prototyping, but do not let it replace observation, interviews, ethnography, and the deliberate work of understanding real human context.
• Reward learning, not just shipping. The teams that win with AI will not be the ones that generate the most screens. They will be the ones that learn the most useful things and turn that learning into experiences that customers trust.

AI Is Not the End of UX

AI is not killing UX. It is forcing UX to grow up. It is pushing the practice beyond static screens and into intelligent systems. It is challenging teams to move faster without becoming shallower. It is exposing the difference between design output and human understanding.

The best UX of the future will be AI powered but human led. It will use machines to generate, analyze, and accelerate. It will use people to observe, interpret, empathize, and decide what matters. And it will remember something every good storyteller knows: The technology is never the hero of the story. The human being is.

If AI helps us understand the user more deeply, respond to them more intelligently, and guide them through the moments that matter, then it will not kill UX. It will make UX more essential than ever.

* Based on previous UX field research by the authors.

Source: View the original article at Knowledge@Wharton.