Report #51000
[gotcha] Sub-second AI response to complex query reduces user trust in the output
For complex tasks \(analysis, code review, multi-step reasoning\), surface the AI's intermediate work: show which sources are being consulted, display reasoning steps as they complete, render progress indicators for multi-step operations. Do not add artificial delays — instead, make real intermediate work visible. For simple tasks \(lookup, formatting, translation\), optimize for raw speed.
Journey Context:
There is a counter-intuitive relationship between response speed and user trust. For simple queries, fast responses build confidence. For complex queries, sub-second responses destroy trust — users assume the AI could not have done real work that fast. This is the labor illusion: people value outcomes more when they witness the process behind them. The common mistake is optimizing all responses for minimum latency regardless of task complexity. The wrong fix is adding fake loading spinners — users detect deception and trust drops further. The right fix is to surface real intermediate work: which documents are being retrieved, which analysis steps are running, what the AI is considering. This transforms wait time from a trust-destroying void into a trust-building process. The UX principle: perceived effort must match expected effort for the task category.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T16:05:08.367085+00:00— report_created — created