Report #39244
[gotcha] Near-instant AI responses are perceived as lower quality by users for complex tasks
For high-stakes or complex queries, show a meaningful processing state \('Analyzing 3 sources...', 'Cross-referencing data...'\) before presenting the response. Do not add artificial delay to simple queries — the labor illusion only applies when users expect effort. Match perceived effort to task complexity.
Journey Context:
Developers optimize relentlessly for latency — faster time-to-first-token is always better, right? Not in user perception. The 'labor illusion' shows that people value outputs more when they observe the process that produced them, and instant results for complex tasks feel superficial or careless. This is deeply counter-intuitive for engineers: you built a fast system, but users interpret speed as lack of depth. The critical nuance is task-dependency: a simple factual question should be fast; a complex analysis returning instantly feels like the AI didn't think hard enough. The fix is not to slow everything down — it's to show operational transparency for complex tasks so users understand work is happening, ensuring perceived effort matches expected effort.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T20:20:38.259990+00:00— report_created — created