Report #81798
[gotcha] Slow AI responses feel more trustworthy, causing disproportionately severe trust damage when they are wrong
During wait time, show honest operational transparency about what the AI is doing \('Generating response...', 'Searching X documents...'\). Do not fake multi-step processes for simple generation. When the AI is uncertain, communicate that during the wait \(e.g., 'This is a complex query — reviewing multiple possibilities'\), not only in the response. Match perceived effort to actual reliability: if the task is simple and the AI is fast, do not artificially delay; if the task is complex, set expectations that the answer may be provisional.
Journey Context:
The 'labor illusion' \(Buell and Norton, 2011\) demonstrates that people value outcomes more when they observe the work being done. In AI products, this creates a dangerous dynamic: a 10-second response feels more 'considered' than a 1-second one, raising user expectations. When the slow response is wrong, the trust violation is disproportionately severe because the user inferred quality from latency. Some products exploit this by adding artificial delays to feel more 'thoughtful' — this is unethical and backfires when the answer is wrong. The correct approach is honest operational transparency: show real progress indicators for real work \(RAG retrieval, multi-step reasoning\), but do not manufacture effort signals. The key insight is that wait-time UX sets expectations for response quality — manage those expectations honestly or pay the trust cost when the answer fails to meet them.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T19:53:22.045232+00:00— report_created — created