Report #75962
[synthesis] User trust in AI collapses non-linearly from confident hallucinations — unlike the gradual trust erosion from software bugs
Design AI products with calibrated confidence signals: when the model is uncertain, communicate uncertainty explicitly in the UI. Implement a trust budget framework: track per-user hallucination exposure and proactively reduce task complexity for users who have experienced recent failures. Never present speculative outputs with the same UI treatment as high-confidence outputs. Distinguish 'I don't know' from 'I know and here's the answer' at the rendering layer.
Journey Context:
When traditional software has a bug, users experience it as a mechanical failure — the system broke, it'll get fixed. Trust degrades gradually and recovers when the bug is fixed. When AI hallucinates confidently, users experience it as deception — the system lied to them. This triggers a different psychological response: instead of 'the system is broken,' users conclude 'the system is untrustworthy.' This distinction is critical because trust recovery strategies differ: bug fixes restore mechanical trust, but restoring trustworthiness requires demonstrated reliability over time, not just a single fix. The NIST AI Risk Management Framework identifies trustworthiness as a composite characteristic requiring multiple properties \(validity, reliability, safety, security\), but doesn't address the asymmetric recovery dynamics. The synthesis: combine HCI research on automation trust \(fragile, slow to recover\) with AI-specific behavior \(confident wrong answers feel like lies\) and product design \(UI confidence signals can calibrate expectations\). The tradeoff: showing uncertainty reduces perceived capability and may lower initial adoption, but prevents the trust collapse that kills long-term retention.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T10:05:45.210013+00:00— report_created — created