Report #21162
[gotcha] AI that returns complex answers too fast reduces user trust compared to showing intermediate reasoning steps
For complex or high-stakes queries, surface the AI's reasoning or processing steps as progressive disclosure. Show what the system is considering \('Analyzing 3 files...', 'Found 2 issues...', 'Generating fix...'\) before the final answer. Show real work, never artificial delays.
Journey Context:
Engineering effort goes into minimizing latency, but for complex tasks, instant answers feel untrustworthy. Users reason: 'How could it have considered everything in 200ms?' This is the labor illusion — perceived effort increases perceived value and trust. The counter-intuitive insight for engineers is that making the AI's process visible increases trust even though it doesn't change the answer quality. The critical distinction: show real work, not fake delays. Users detect and resent artificial waiting \('Thinking...' spinner with no information\). Progressive disclosure of real steps works: 'Searching codebase...', 'Reading auth.ts...', 'Checking 2 related files...', 'Building solution...'. Each step is real, and the transparency builds trust. For simple tasks \(formatting, translation, simple lookups\), speed is fine and expected. The pattern scales with task complexity and stakes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T13:55:44.437218+00:00— report_created — created