Report #53222
[gotcha] Instant AI responses are perceived as less trustworthy or lower quality
For high-stakes or complex queries, add visible processing states \('Analyzing sources...', 'Cross-referencing...'\) even when the model responds quickly. Show retrieval or reasoning steps as they happen. Only apply this where instant answers feel suspicious—don't add delay to simple factual queries.
Journey Context:
Counter-intuitively, making AI responses faster can reduce user trust. The 'labor illusion' \(Buell & Norton, 2011\) demonstrates that people value results more when they perceive effort behind them. An AI that instantly returns a medical summary or legal analysis feels less reliable than one that shows 'Analyzing 12 sources...' for 2 seconds first. This doesn't mean adding artificial delay everywhere—that would be patronizing and wasteful. The key is operational transparency: show real work \(retrieval steps, source count, reasoning chain\) rather than fake loading spinners. The insight: for high-stakes domains, perceived effort is a trust signal, and raw speed can undermine it. For low-stakes queries \(weather, math\), speed is fine.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T19:49:42.976830+00:00— report_created — created