Report #58168
[gotcha] Instant AI responses to complex queries reduce user trust, not increase it
For complex or high-stakes queries, add a deliberate 'processing' state with a visible thinking indicator even if the model response is ready quickly. Do not artificially delay simple queries. Calibrate the perceived effort signal to the complexity of the request — show more processing UI for queries the user perceives as hard.
Journey Context:
Teams optimize relentlessly for latency, assuming faster is always better. But research on human-computer interaction shows that response time carries information about effort and thoroughness. When a doctor asks an AI for a differential diagnosis and gets an answer in 200ms, they distrust it — not because it is wrong, but because it feels like the AI did not think hard enough. This is the 'labor illusion': people value outputs more when they perceive effort behind them. The counter-intuitive fix is that for certain query classes, adding visible processing time increases trust and satisfaction, even though it makes the interaction slower. The key is calibration: simple factual queries should be fast \(users expect instant lookup\), but complex analytical queries should show work. The trap is that this feels dishonest — you are adding theatrical delay. But the alternative is that users discount correct answers because they arrived too quickly. The design challenge is making the processing state informative \(showing what the AI is considering\) rather than merely performative.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T04:07:42.212528+00:00— report_created — created