A surprising amount of whether an AI feature succeeds has nothing to do with the model and everything to do with the interface around it. Teams pour months into model quality and then bolt on a chat box at the end, only to watch adoption stall. Usability research — much of it from the Nielsen Norman Group's ongoing work on AI UX — points to a consistent set of patterns that earn trust, and a few that quietly destroy it.
Why AI UX is genuinely different
Traditional software is deterministic: the same input produces the same output every time, so users gradually build a reliable mental model of what the system will do. Click the button, get the result, learn the rule. That predictability is the bedrock most interface conventions quietly assume.
AI breaks that assumption. It is probabilistic — it can be wrong, it can give two different answers to the same question on two tries, and it tends to sound equally confident whether it's right or hallucinating. A user can't form a stable rule for "when does this work," because there isn't one. So the central job of AI design shifts from teaching a rule to helping users calibrate their trust: leaning on the system when it's reliable, and staying appropriately skeptical when it isn't. Almost every good AI UX pattern is, at heart, a tool for that calibration.
A concrete contrast
Picture two versions of the same AI assistant that summarises a long contract. Version A returns a clean paragraph and nothing else. Version B returns the same paragraph, but each key claim links to the exact clause it came from, a small note flags one section as "low confidence — wording is ambiguous," and an Edit summary button sits right there. The model behind both is identical. Yet users trust Version B far more — not because it's more accurate, but because when it is wrong, they can see where, check it, and fix it. That difference is entirely interface, and it's the difference between a feature people rely on and one they quietly stop opening.
Patterns that build trust
- Show your sources. When an answer cites where it came from, users can verify it themselves — and will forgive the occasional miss. This is a big part of why retrieval-based systems feel trustworthy.
- Signal uncertainty. A system that can say "I'm not sure about this part" or surface a confidence cue beats one that is relentlessly certain — especially in the moments when it happens to be wrong.
- Make output easy to edit, not just accept. Treat AI output as a draft the user refines, not a verdict they must take or leave whole. Editable beats final.
- Keep the human in control. Preview before action, easy undo, and clear "are you sure?" moments for anything consequential or irreversible. (More on human-in-the-loop design and designing for AI UX.)
Patterns that destroy trust
- Confident wrongness with no escape hatch — a wrong answer presented as fact, with no way to correct, flag or undo it.
- Hiding that it's AI, then being caught. Users forgive a disclosed limitation; they don't forgive feeling deceived, and one obvious error erases the credibility of everything else.
- Over-automation — the system acting before the user is ready, taking a step that should have waited for a confirmation.
Users don't expect AI to be perfect. They expect to stay in control when it isn't. That single principle resolves the large majority of AI UX decisions you'll face.
Why trust is the whole game
It's worth dwelling on why trust, specifically, is the metric that matters. A user who doesn't trust an AI feature does one of two equally bad things: they ignore it entirely, so all your model investment is wasted, or — worse — they trust it blindly and ship its mistakes downstream. Calibrated trust is the narrow, valuable middle ground where the user knows roughly when to lean in and when to double-check. Every pattern above is really a lever on that calibration. Sources and confidence cues lower trust at the right moments; easy editing and undo raise willingness to engage because the cost of a mistake drops. Designed well, the interface quietly teaches the user the model's actual reliability, which no amount of model improvement can do on its own.
An honest caveat
These are patterns, not laws. Citations and confidence cues add visual weight, and piling on too many warnings can erode trust as surely as hiding the AI — a system that hedges everything teaches users to ignore the hedges. The right amount of friction depends on the stakes: a throwaway draft tool can be lightweight, while anything touching money, health, or legal exposure earns more guardrails. Calibration applies to the design as much as to the user.
The takeaway
The model is only half the product. The interface decides whether people trust it enough to keep using it — which makes UX a core part of any serious AI build, not a coat of paint applied at the end. If you're shaping an AI feature and want a second pair of eyes on the experience around the model, we'd be glad to help. Looking forward, as models grow more capable the interface becomes the main thing users actually judge you on — so the teams that treat trust as a design problem, not just a model problem, are the ones whose AI features stick.
Sources
- Nielsen Norman Group — AI & Machine Learning UX research