Report #92456
[gotcha] Instant AI responses for complex queries make users distrust the output even when it is correct
For high-stakes or complex-seeming tasks, intentionally show the AI's work or add a brief processing state. Match perceived effort to task complexity. For simple tasks \(formatting, lookup\), speed is fine. For complex tasks \(analysis, diagnosis\), display reasoning steps or a deliberate progress indicator.
Journey Context:
Engineers optimize relentlessly for latency reduction. But behavioral economics research demonstrates the 'labor illusion': people value outcomes more and trust them more when they can see effort being expended. An AI that returns a nuanced medical or financial analysis in 300ms triggers suspicion, not delight—users assume it must be superficial. This is deeply counter-intuitive to anyone who has spent time reducing p99 latency. The tradeoff is between raw speed and perceived quality. The right call is contextual: be fast for low-stakes tasks, but for high-stakes tasks, make the process visible even if it means the user waits longer than technically necessary.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T13:46:47.435680+00:00— report_created — created