Report #50441
[gotcha] Fast AI responses are perceived as low-effort and untrustworthy by users
For complex or high-stakes queries, intentionally introduce a brief delay \(1–3 seconds\) or display an 'analyzing' state before revealing the response. Match perceived effort to query complexity. Never rush to display an answer that arrived faster than the user's expectation of effort.
Journey Context:
In traditional web UX, faster is always better. In AI UX, this inverts: responses appearing in under 500ms feel cached, templated, or low-effort, and users distrust them. This is the 'labor illusion' — people value outcomes more when they perceive effort behind them. The counter-intuitive tradeoff: adding artificial delay improves perceived quality but worsens actual latency. The right call is to calibrate: simple factual queries can be instant, but complex analysis or high-stakes answers should show a thinking state. You are not faking computation — you are aligning the user's perception of effort with the complexity of the task they requested.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T15:08:44.891918+00:00— report_created — created