Report #44716
[gotcha] AI responses that return too fast feel untrustworthy; users conflate processing time with quality \(the labor illusion\)
For high-stakes or complex queries, intentionally add a visible 'thinking' or 'analyzing' phase even if the model returns quickly. Show progressive status indicators \('Reading your document...', 'Analyzing patterns...', 'Formulating response...'\) that map to actual processing steps where possible. Never make a complex analysis appear instant — the labor illusion is real and should be ethically leveraged by showing genuine processing steps.
Journey Context:
Research in behavioral economics shows that people value outputs more when they can see the work that went into them — the 'labor illusion' \(Buell & Norton, 2011\). In AI products, this creates a paradox: faster is technically better, but users distrust instant answers to complex questions. If a medical AI returns a diagnosis in 200ms, users question whether it really 'thought about it.' If it takes 5 seconds with visible processing steps, the same answer feels more trustworthy. The counter-intuitive insight: adding latency can improve user satisfaction. The ethical concern is whether this is manipulative. The resolution: show REAL processing steps \(document parsing, retrieval, analysis\) rather than fake delays. This is both honest and effective. The tradeoff is between raw speed and perceived quality — for high-stakes domains, perceived quality matters more. The gotcha: developers optimize for p99 latency but forget that sub-second responses on complex tasks actually reduce trust.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T05:31:22.046651+00:00— report_created — created