Why Users Don’t Trust Your AI — A 30-Year UX Perspective
By Steven Liu — 30+ years in FDA-regulated medical-device and enterprise UX
I’ve spent three decades designing interfaces for environments where a confusing screen isn’t a bad review — it’s a clinical risk or a six-figure error. So when AI started moving into the products my clients build, I paid less attention to the models and more attention to a pattern I’d seen many times before: the technology worked, and people still didn’t trust it.
AI and good UX are now inseparable. The promise is real — but so are the obstacles, and most of them aren’t algorithmic. They’re experiential. Here are the three I keep running into, and the strategies I use to get past them.
Three reasons users don’t trust AI
1. The black box problem. Most AI makes a decision and shows you the answer, not the reasoning. In a consumer app that’s annoying. In a clinical or enterprise context it’s disqualifying — a clinician will not act on a recommendation they can’t interrogate, and they shouldn’t. I once watched a domain expert override a perfectly correct AI suggestion simply because the system gave them no way to see why it was made. The model wasn’t wrong. The experience was.
2. Complexity dressed up as completeness. AI processes enormous amounts of data, and there’s a strong pull to show all of it. But “accurate” and “usable” are not the same thing. An interface that surfaces everything the model knows hands the user a second hard problem on top of the one they came to solve. Deciding what the human actually needs to see, and when, is the real design work.
3. No path to push back. Many AI interfaces are one-directional: the system decides, the human absorbs. With no straightforward way to question, correct, or teach the system, trust never forms — and the feedback that would improve the model never gets captured. A loss on both sides.
Five strategies that actually work
1. Design for explainability, not just accuracy. Work with the AI team early so the interface can show its reasoning — a confidence signal, the key factors, a plain-language “why.” In regulated environments this is increasingly what human-factors and usability-engineering expectations require. Designing it in is far cheaper than retrofitting after a review finding.
2. Simplify ruthlessly. Distill output into the few insights that drive a decision. Hierarchy, progressive disclosure, clear language — primary screen stays calm, depth is there only when wanted. Test: can the user act correctly in five seconds without reading everything?
3. Build the feedback loop into the interface. An obvious, low-friction way to correct or challenge the system, treated as a first-class data source. Earns trust in the moment; improves the model over time.
4. Stay human-centered, especially under regulation. Compliance is the floor, not the goal. You can satisfy every checkbox and still ship something a tired clinician doesn’t trust at 2am. Research the real context of use — who, under what pressure, with what consequences — and design for that, not the spec sheet.
5. Personalize to context, carefully. Adapting to role, history, and situation is powerful when it cuts noise, counterproductive when it hides something needed. In high-stakes work, personalization must be legible: the user should be able to tell what was tailored and why.
The part the field is only now admitting
In 2026 the whole industry is talking about AI trust, explainability, and calm interfaces. Good — it’s the right conversation. But the uncomfortable version, from someone who has shipped this where the stakes are real: a compliant AI interface is not the same as a safe one. The box-checking is the floor. The judgment about what a human needs to see, when, and how much — that’s the actual work, and it’s the part AI can’t do for you.
The teams that win the next few years won’t have the best model. They’ll be the ones who designed well for the single moment that matters most: when a person has to decide whether to believe what the system just told them.
If you’re building AI into a complex or regulated product and the experience is the bottleneck, that’s the problem I work on. — Steven Liu, Areteworks. clientcare@areteworks.com
Additional Resources: Explore more critical UX principles or learn about empathy mapping trends .