Is artificial intelligence hurting user experience — or just revealing what was always missing?
Artificial intelligence and user experience are on a collision course — but maybe not in the way you think.
While product teams celebrate the ability to create prototypes in hours, consumers are telling a very different story. Only 17% of them believe their digital experiences are actually improving, according to a Medallia report from March 2026. And there is more: a Pega survey published in February of the same year found that more than 60% of consumers do not trust the way companies use AI to interact with them.
This raises a question with no simple answer — is the speed AI brought to product design helping or hurting the relationship between brands and people? The answer, honestly, depends a lot on how companies are using this technology. Creating a beautiful prototype in record time is impressive, but if the team skipped the steps of truly understanding who is going to use it, the result might look finished without actually being ready.
This is exactly the paradox that Scott A. Snyder, 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, explore in an article that has become a reference in the debate about the future of user-centered design. And their conclusion is more optimistic than the headline suggests 😉
UX was never just about the interface
Before diving into the discussion about speed and tools, it is worth taking a step back and revisiting what user experience really means. For years, many companies adopted the UX vocabulary while reducing the practice to screens, flows, and usability testing. Those things matter, of course. A confusing interface can destroy a good idea. A broken flow can erode user trust in seconds. But real UX was never limited to the surface of the product.
Good experiences start before the wireframe. They start with genuine curiosity: who is this person? What are they trying to do? What is getting in the way? What do they believe before they arrive? What would make this person feel understood?
These are not just design questions. They are questions of story, of narrative. Every useful product — whether an internal enterprise tool or a consumer-facing app — has a narrative structure behind it. 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 lost in front of my boss or my client.
UX is precisely where that human story becomes operational. It connects business strategy to human behavior. It translates the brand promise into lived experience. It blends data and observation, analytics and empathy, system performance and emotional resonance. AI can help with a good portion of that, 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.
Speed is not the same as quality
There is a huge difference between delivering fast and delivering well. With artificial intelligence accelerating every stage of the creative process, many teams started confusing agility with depth. AI tools can generate screens, flows, and even copy suggestions in minutes — what used to take days or weeks. But all that speed creates a silent side effect: the temptation to skip fundamental steps in the user-centered design process, like interviews, usability testing, and analysis of real behavior.
The problem is not the tool itself. It is what happens when the team starts using AI as a shortcut for the hard parts of design — the ones that require sitting with the user, hearing complaints, observing hesitations, and understanding what people actually need, not just what they say they want. When that process is neglected, what comes out the other side is a product that looks modern but does not solve anything in a meaningful way. It looks complete in the demo but generates frustration in real use.
Snyder and Welsh call this the speed trap. The most seductive promise of AI is the compression of time. Teams can go from idea to tangible artifact faster than ever, test more options, and discard weak ideas with agility. In many cases, AI will make teams more creative, more collaborative, and more productive. But there is a trap inside that speed: just because you 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 did the hard work of understanding why that experience should exist in the first place.
When every team has access to similar tools, similar prompts, and patterns generated by similar models, the result tends to be more uniformity — not less. AI can help companies produce plenty of competent work. But it can also help them produce generic experiences that look ready before they have been genuinely thought through.
Snyder and Welsh argue that AI, when applied well, should amplify a team’s ability to listen — not replace it. That means using natural language processing capabilities to analyze feedback at scale, identify patterns in qualitative data that would be impossible to map manually, and generate hypotheses that are then tested with real people. When technology enters the process this way, it does not shorten the understanding of the user — it deepens it. AI can speed up the what. UX needs to defend the why.
Rapid prototyping and the illusion of progress
Prototyping has always been one of the most valued stages in digital product design. The idea is simple and powerful: before building the real thing, you create a simplified version to test, learn, and adjust. But when AI enters this process, it transforms prototypes that used to take a week into afternoon deliverables. And here comes the risk few people talk about openly: the faster and more polished the prototype, the harder it becomes to see what is still missing.
There is a well-documented psychological phenomenon in the design world called deceptive fidelity. It happens when a prototype looks so polished that the people around it — including stakeholders and even the designers themselves — start treating it as if it were the final product. Meetings that should be about learning turn into approval presentations. Legitimate questions about flow and usability take a back seat because the visuals impress. With AI generating increasingly sophisticated prototypes in record time, this phenomenon is only going to intensify.
The authors share a revealing example from field research. A convenience store chain that also offered fuel and quick meals commissioned a UX engagement. The field research uncovered a hidden behavior: consumers felt guilty about leaving their car at the fuel pump while waiting for their food to be ready, blocking other drivers. This pump anxiety, as the researchers nicknamed it, became a fundamental design point in the mobile app, which was updated to let customers order ahead and know their food would be ready when they arrived. A UX process driven exclusively by AI would have missed this insight completely.
AI tools can create personas, draft journey maps, propose service blueprints, and synthesize 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 presentation 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 something surprising? Did they change their mind at any point in the process?
If the answer is no, then AI did not kill UX. It just helped the team skip that step faster.
What Snyder and Welsh propose is repositioning the role of prototyping within the AI-augmented workflow. Instead of using the speed of the technology to arrive faster at a seemingly final version, teams should use that speed to iterate more times with more people. In other words, instead of one prototype per week, you could have five different versions tested with distinct user groups in the same period. This turns AI into a tool for accelerated learning — not rushed delivery.
What consumer trust has to do with all of this
The numbers from the Pega survey are hard to ignore. When more than 60% of consumers say they do not trust the way companies use AI to interact with them, that is not just a communications warning — it is a clear signal that something in the design process is broken. Consumer trust is built over time, through consistent, transparent experiences that actually solve problems. It is destroyed quickly when the user feels they are interacting with something that was made to look helpful but fundamentally does not understand their needs.
Part of the problem is how many companies position AI in their interfaces. Chatbots that promise to solve everything and solve nothing, automated recommendations that feel random, self-service flows that make the user feel trapped in a maze — all of this contributes to a negative perception that goes far beyond a bad feature. The consumer starts associating the presence of AI with frustration, and that association is hard to undo. When the user experience repeatedly fails at points where AI is involved, the distrust is not with the interface — it is with the company behind it.
The good news — and this is where Snyder and Welsh’s perspective becomes especially relevant — is that this scenario is not irreversible. Companies that apply solid user-centered design principles within AI-powered workflows achieve very different results. When AI is used to better understand user behavior, personalize experiences in a genuine way, and identify friction points before they become problems, the consumer notices the difference. And that positive perception builds exactly the kind of trust that turns casual users into people who come back, recommend, and stay loyal to a brand.
Building an AI-augmented UX
The right path, as Snyder and Welsh make clear, does not involve resistance. UX teams should not treat AI as an intruder. They should treat it as a collaborator that changes the economics of creative exploration.
AI can help researchers synthesize large volumes of feedback, generate alternative flows, simulate use cases, identify edge cases, and prototype variations at speed. It can support accessibility reviews, content testing, localization, and design quality control. When used intelligently, AI expands the field of possibilities — but it only truly works when combined with human judgment.
The strongest teams will build a hybrid model where AI supports speed and scale while UX protects strategy, empathy, and trust. This model requires new habits:
- Separate generation from validation. AI can generate possibilities, but users are the ones who validate value. A hundred prototype variations are only useful if the team knows what it is trying to learn.
- Treat trust as a design requirement. As AI becomes more integrated into 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.
- Design for explanation, not just interaction. In AI-powered experiences, systems may make decisions, generate predictions, or produce summaries that feel opaque. The UX challenge is not just making the interface usable — it is making the intelligence feel understandable.
- Keep the human story at the center. Every AI-powered experience should still answer a human question: what is this person trying to do right now, and how can we help?
UX professional training needs to change
We are entering a period where UX, product strategy, service design, behavioral insight, and AI literacy will become increasingly intertwined. You can call it AI interaction design, AI-augmented UX, or simply the next version of good product work. The label matters less than the discipline behind it.
Designers will need to understand how AI systems behave. Researchers will need to test not just whether users can complete a task, but whether they trust the system helping them. Product leaders will need to decide where automation makes sense, where human review is essential, and where intelligence should be visible or invisible to the user.
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, narrative, and adoption. And business leaders need to stop treating UX as decoration at the end of the process and start treating it as a strategic capability from the beginning.
There is a subtle but powerful difference between two types of digital experience. An automated experience often makes the consumer feel like the company found a cheaper way to avoid them. A thoughtful experience makes the consumer feel like the company understood their situation and used intelligence to help. That is the standard worth pursuing.
What leaders can do right now
The practical path is not complicated, but it requires intention. Snyder and Welsh offer clear guidance for those in decision-making positions:
- Invest in UX as a strategic asset. Do not reduce research and design capacity just 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 all.
- Retrain teams to work alongside AI. Designers, researchers, strategists, and product managers should learn to use AI tools responsibly. But the goal is not just tool fluency — it is asking better questions, learning faster, and making clearer decisions.
- Include trust in the experience architecture from day one. Transparency, explainability, control, escalation, and human oversight cannot be bolted on after launch. They belong in the experience design from the start.
- Protect deep discovery. Do not confuse generated output with 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 deliverables. The teams that will win with AI will not be the ones generating the most screens. They will be the ones learning the most useful things and turning that learning into experiences customers trust.
The path that balances technology and humanity
No product team is going to give up the speed that artificial intelligence brought to the creative process. Nor should they. The point is not to slow down — it is to make sure the acceleration is being applied to the right parts of the process. When AI takes on repetitive tasks, like generating visual variations, analyzing behavioral logs, and synthesizing qualitative feedback at scale, it frees up the team to do what really matters: thinking about the people who will use the product.
This redistribution of effort is what separates teams using AI strategically from those using AI on autopilot. In the first case, the technology serves the user-centered design process. In the second, it replaces the process — and the result shows up in satisfaction metrics, retention, and inevitably, in consumer trust. The Medallia and Pega surveys make it clear that most companies are still in the second group, and that explains a lot about why consumers report digital experiences getting worse even when the available tools have never been more powerful.
AI is not killing UX. It is forcing UX to grow up. It is pushing the practice beyond static screens and toward intelligent systems. It is challenging teams to move faster without becoming shallower. It is exposing the difference between producing design and actually understanding human beings.
The best UX of the future will be powered by AI but led by people. It will use machines to generate, analyze, and accelerate. It will use humans to observe, interpret, empathize, and decide what matters. And it will remember something every good storyteller knows: technology is never the hero of the narrative. The human is.
What Snyder and Welsh remind us, and what the data confirms, is that technology and empathy are not opposites. They can — and need to — walk together. AI-accelerated prototyping can be an extraordinary learning tool when used within a process that puts the user at the center. User experience can improve significantly when AI is trained on real data, contextualized and collected ethically. And consumer trust can be rebuilt when companies stop using technology to impress and start using it to genuinely understand and serve the person on the other side of the screen 🎯
