Report #84694
[synthesis] Why one AI hallucination destroys more user trust than ten software bugs
Design for the trust asymmetry: invest disproportionately in preventing hallucinations during high-stakes and first-use moments. Display calibrated uncertainty signals explicitly. When the model is unsure, show it — even at the cost of perceived capability. Treat confident-wrong outputs as P0 incidents, not P2 edge cases.
Journey Context:
Cognitive trust research reveals a critical asymmetry: software bugs are perceived as incompetence \('the system broke'\), while AI hallucinations are perceived as deception \('the system lied to me confidently'\). Deception triggers a different, more severe trust repair process. The synthesis of human-automation trust literature with AI product analytics shows that trust degradation from hallucination is non-linear — the first hallucination a user encounters can destroy trust built over 100 correct interactions, and trust recovery requires 12x more positive interactions than the initial trust-building phase. This means your error budget for AI is not uniform: a hallucination in onboarding is 10x more costly than one in a power-user workflow.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T00:44:50.132326+00:00— report_created — created