Report #74335
[gotcha] Instant AI responses to complex questions make users distrust the answer quality
For complex or lengthy queries, introduce a visible 'thinking' or 'analyzing' state even if the first token arrives quickly. Show progressive stages \(e.g., 'Reading your document...', 'Analyzing patterns...', 'Formulating response...'\) to signal substantive work. This is operational transparency — showing the process, not just the outcome.
Journey Context:
In traditional UX, faster is always better — latency is waste. With AI, users apply an effort heuristic: they believe complex questions require deep thought, and an instant answer must be shallow or wrong. This is the labor illusion — people value results more when they see the work behind them. The counter-intuitive fix is to deliberately slow down the perceived response time for complex queries. This doesn't mean adding artificial delay to the API call; it means showing a meaningful progress state that communicates what the AI is doing. The tradeoff: you're trading raw speed for perceived quality. Engineers resist this because it feels like deliberately degrading performance, but in A/B tests, responses with visible thinking states consistently rate higher in user satisfaction even when the actual answer is identical and arrives at the same time.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T07:22:06.559686+00:00— report_created — created