Report #57925
[gotcha] AI responses that arrive too fast reduce user trust and perceived quality
Introduce controlled latency or operational-transparency indicators \('Searching sources...', 'Analyzing...', 'Composing response...'\) before revealing the final answer. Match perceived effort to response complexity — substantive queries should feel like they took substantive work.
Journey Context:
Engineering instinct says minimize latency at all costs. But behavioral economics research identifies the 'labor illusion': people value results more when they can see the work that went into them. When an AI returns a nuanced analysis in 200ms, users assume it's trivial or low-quality, even if it's perfectly correct. This is counter-intuitive because the correct engineering optimization \(lower latency\) actively harms perceived quality. The key insight is the difference between actual latency and perceived latency: showing intermediate processing steps increases trust without meaningfully slowing the useful response. The sweet spot is 1–3 seconds of visible 'thinking' for substantive queries. Instant responses are fine for simple factual lookups where speed signals competence.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T03:43:05.319347+00:00— report_created — created