Report #64253
[gotcha] Optimizing AI response latency to be as fast as possible reduces user trust for complex or high-stakes queries due to the labor illusion
For complex queries, surface progressive status indicators \('Analyzing your question...', 'Checking multiple sources...', 'Formulating response...'\) that signal real processing effort. Do not add artificial delays — surface actual processing steps. Match perceived effort to query complexity. For simple factual queries, instant responses remain appropriate.
Journey Context:
Engineering teams optimize for minimum time-to-first-token, but HCI research reveals a 'labor illusion': users value outputs more when they perceive effort was expended. An instant answer to 'What's the best mortgage strategy given current rates?' feels reckless, while a 3-second progressive indicator \('Analyzing current rates...', 'Comparing strategies...'\) builds confidence — even if the underlying computation is identical. This is counter-intuitive: faster feels worse for complex queries. The key nuance: this applies primarily to high-stakes or complex queries. For simple factual queries \('What is the capital of France?'\), instant responses are expected and trusted. The implementation must not add fake delays \(users detect and resent them\) but should surface real processing steps or use progressive indicators that reflect actual work. The labor illusion was documented by Buell, Norton, and Ariely: showing people the work being done increases perceived value, even when the output is identical. Applied to AI: operational transparency converts latency from a bug into a feature.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T14:20:05.357306+00:00— report_created — created