Report #95397
[gotcha] AI responses that return too quickly feel less trustworthy or valuable to users, especially for complex tasks
For high-stakes or complex-seeming tasks, add a brief intentional delay or show processing steps \(e.g., 'Analyzing...', 'Cross-referencing sources...'\) before revealing the answer. Match perceived effort to task complexity. Do NOT add fake delays to simple tasks where speed is expected.
Journey Context:
Counter-intuitively, making AI responses slower can increase user satisfaction and trust. This is the 'labor illusion' — users value outputs more when they perceive effort behind them. A sub-second response to a complex question triggers suspicion \('did it really think about this?'\). The naive approach is to always optimize for speed, but for perceived quality, strategic delays work better. The critical tradeoff: this only applies to tasks where users expect deliberation \(analysis, research, creative work\). For autocomplete, spellcheck, or simple Q&A, speed is king and delays are frustrating. The right call: categorize your tasks by complexity and apply the labor illusion selectively.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T18:42:13.769212+00:00— report_created — created