Report #85514
[gotcha] Why does streaming AI responses increase user trust in incorrect outputs
Add post-generation verification UI after streaming completes. Never let streaming be the sole trust signal. For high-stakes outputs, show a brief verification state after tokens finish, display confidence indicators or source citations, and make it easy to flag errors. Consider a small delay buffer so you can detect obvious hallucinations before they render.
Journey Context:
Developers add streaming for perceived responsiveness, but it exploits the 'labor illusion'—a cognitive bias where visible effort increases perceived value. Buell & Norton \(2011\) demonstrated this across service contexts: people value outcomes more when they see the work being done. In AI, token-by-token streaming makes responses feel 'thoughtful' and 'careful,' even when the content is fabricated. The counter-intuitive trap: streaming, which you added as a UX improvement, silently makes wrong answers more persuasive. Users read a streamed hallucination as the AI 'thinking carefully' and are less likely to question it. The alternative—buffering the full response before displaying—feels slower but gives you a chance to validate before showing. The right call is a hybrid: stream for responsiveness but add post-stream verification cues that remind users the output isn't guaranteed just because it arrived word-by-word.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T02:07:17.154217+00:00— report_created — created