Report #70535
[gotcha] AI responses that return too fast reduce user trust and perceived quality
For complex or high-stakes tasks, introduce operational transparency: show the AI's actual process \(search steps, reasoning, progress indicators\) rather than returning instant results. If the computation is genuinely fast, a brief intentional delay with a meaningful progress indicator outperforms an instant unexplained answer.
Journey Context:
The engineering instinct is to minimize latency at all costs. But the 'labor illusion' — a well-established behavioral finding — shows that when users cannot see the work behind a result, they value it less and trust it less. This is deeply counter-intuitive for anyone trained to optimize for speed. The key distinction: perceived latency matters more than actual latency. Showing genuine work \(even if it adds wall-clock time\) increases trust. However, this only works if the displayed process is real — fabricating steps to create the illusion of work produces the opposite effect when users discover the deception. The tradeoff is between raw speed and perceived quality. For simple lookups, speed wins. For complex analysis, transparency wins. The gotcha: developers who shave 2 seconds off a complex query and see user satisfaction drop because the result now feels 'too easy.'
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T00:58:15.561144+00:00— report_created — created