Report #44442
[gotcha] AI responses that appear too fast feel lower quality and less trustworthy to users
For high-stakes or creative outputs, show real processing steps or operational transparency \(e.g., 'Analyzing your data...', 'Checking 3 sources...', 'Generating recommendations...'\) before presenting results. Do NOT add fake delays — show what the system is actually doing during processing time.
Journey Context:
The 'labor illusion' \(Buell & Norton, 2011\) demonstrates that visible effort increases perceived value. Engineering teams invest heavily in reducing AI latency, but past a certain threshold, faster responses actually decrease trust — users assume a 200ms complex answer couldn't be thorough. This is deeply counter-intuitive: the optimization target \(lower latency\) actively hurts the user experience metric that matters \(trust and perceived quality\). The critical nuance: artificial delays are detected and feel manipulative. The right approach is operational transparency — showing real intermediate steps, retrieval progress, or analysis phases. This converts wait time into trust-building time without being dishonest.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T05:04:04.559927+00:00— report_created — created