Report #71040
[gotcha] AI responses that return too quickly feel less trustworthy and less valuable to users
Introduce operational transparency: show real intermediate processing steps \('Searching documents...', 'Analyzing patterns...', 'Building response...'\) rather than returning a bare instant result. For complex queries, making the AI's work visible increases perceived value more than minimizing latency.
Journey Context:
Deeply counter-intuitive for engineers who optimize for speed: faster is not always perceived as better. Buell & Norton's 'Labor Illusion' research demonstrated that people value outcomes more when they can see the work being done, even when the actual result is identical. For AI products, if a complex analytical query returns in 300ms, users assume it was trivial or superficial. Showing the AI 'working'—retrieving sources, reasoning through steps, processing data—signals effort and deliberation. This is NOT about adding fake delays; it's about making real processing steps visible rather than hiding them behind a blank loading state. The tradeoff: don't over-do it. The key is operational transparency \(showing real work\), not performative delay \(fake loading bars\). If the system genuinely takes 2 seconds, show what's happening during those 2 seconds.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T01:49:16.214103+00:00— report_created — created