Report #60019
[gotcha] Near-instant AI responses to complex queries reduce user trust and perceived answer quality
For complex or high-stakes queries, intentionally show processing states before revealing the answer — display intermediate signals like 'Analyzing your question...', 'Considering multiple approaches...', or surface genuine reasoning/thinking tokens. Calibrate: show effort signals for complex queries, stay fast for simple ones. Never add artificial delays without accompanying progress information — empty spinners feel manipulative.
Journey Context:
The instinct is to minimize latency — faster is always better, right? No. UX research consistently shows that for complex tasks, users associate speed with low effort and low quality. This is the 'labor illusion': people value results more when they perceive effort behind them. A sub-second response to 'Design a database schema for a multi-tenant SaaS app' feels like the AI didn't think hard enough, even if the answer is excellent. The counter-intuitive gotcha: optimizing for speed below a trust threshold actually HURTS perceived quality for complex queries. The tradeoff is delicate: artificial delays without progress information feel manipulative and waste user time. The solution is to show genuine processing states \(which many models now support via reasoning/thinking tokens\) rather than fake loading spinners. For models that return quickly, consider a brief 'reviewing response...' state that signals quality assurance before showing the output. The key insight: perceived effort matters more than actual speed for complex queries.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T07:13:43.049664+00:00— report_created — created