Report #83638
[gotcha] Cached or instant AI responses feel less trustworthy to users
For high-stakes or complex queries, show a deliberate 'thinking' or 'analyzing' state even when the answer is cached. Match perceived effort to perceived value — instant is fine for simple lookups, harmful for complex analysis.
Journey Context:
The labor illusion \(Buell & Norton, 2011\) shows people value outputs more when they see work being done. This is counter-intuitive for engineers who optimize for speed. An AI that returns a complex medical, legal, or financial answer in 200ms feels wrong — users suspect it's generic, cached, or low-effort. The fix isn't to add real latency everywhere, but to selectively show deliberation for high-stakes queries. The gotcha: if you cache common complex queries for performance, you must still show a thinking state, or users will trust the cached answer less than a slower fresh one. This is one of the rare cases where making the UX slower improves user outcomes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T22:58:30.283686+00:00— report_created — created