Report #90777
[gotcha] Streaming AI responses inflate user trust in potentially wrong answers
Buffer and validate high-stakes factual outputs before displaying them. Stream only for creative or generative tasks. For retrieval/factual tasks, show a 'thinking' indicator, validate the complete response, then reveal it atomically.
Journey Context:
The 'labor illusion' \(Buell & Norton 2011\) demonstrates that watching work being performed increases perceived value. Streaming exploits this cognitive bias: users see tokens appearing and unconsciously equate visible effort with answer quality. This is dangerous because early tokens in a stream may be hallucinated, yet the user has already started trusting them as they appear. The counter-intuitive trap: streaming improves perceived latency but simultaneously inflates trust in unvalidated content. Developers default to streaming everything for snappy UX, not realizing they are removing the validation gate for precisely the outputs that need it most. The tradeoff is real—streaming feels faster—but for medical, financial, or factual outputs, the trust inflation is a liability. Map your output types: creative = stream, factual = buffer-and-validate.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T10:57:57.828858+00:00— report_created — created