Report #21264
[gotcha] AI responses that return too fast feel untrustworthy to users
For high-stakes or complex queries, add a brief 'processing' phase \(1-3 seconds\) with progressive indicators of work \('Analyzing your code...', 'Checking patterns...', 'Generating suggestions...'\). Match perceived effort to task complexity. Do NOT add artificial delay to simple factual queries.
Journey Context:
There is a well-documented HCI phenomenon called the 'labor illusion'—users value outputs more when they can see effort being expended. AI that returns a complex architectural analysis in 200ms feels like it did not think hard enough, and users second-guess the result. This is deeply counter-intuitive to engineers who optimize for speed. The fix is not to add fake delay everywhere—it is to match perceived effort to task complexity. Simple lookups should be instant; complex reasoning should show its work progressively.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T14:05:47.780698+00:00— report_created — created