Report #35483
[gotcha] Showing AI chain-of-thought reasoning in product UI either confuses non-technical users or creates unwarranted trust in flawed reasoning
Default to hiding reasoning steps; make them expandable on demand. When shown, visually distinguish reasoning from the final answer \(different background, font size, indentation\). Never surface raw reasoning tokens that include hedging or self-correction without context. For developer tools, showing reasoning is appropriate; for consumer products, hide it.
Journey Context:
The instinct is to show AI reasoning to build trust — 'see, the AI thought about this\!' But research shows this backfires in two opposite ways: \(1\) Non-technical users find visible reasoning confusing and it makes the product feel unfinished or overly complex. They do not know what to do with the reasoning. \(2\) Technical users over-trust visible reasoning — if the AI shows a confident-sounding chain of thought, users are MORE likely to trust the answer even when it is wrong. This is the 'explanation effect' documented in HCI research: explanations increase trust regardless of accuracy. The AI's reasoning can be confidently wrong \(hallucinated logic\), and showing it makes users less likely to question the answer. The right pattern: hide reasoning by default, make it available on demand \(click to expand\), and visually separate it from the answer. OpenAI's o1 model explicitly hides its reasoning tokens for this reason — they are used internally but not exposed to end users. The exception: developer and debugging tools where reasoning is the point.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T14:01:56.510367+00:00— report_created — created