Report #83736
[gotcha] Should you show the AI's chain-of-thought reasoning to users? Why does visible reasoning sometimes reduce trust instead of building it?
Default to hiding raw chain-of-thought from end users. If you must show reasoning, surface a polished summary rather than raw thinking tokens. Raw CoT often contains hedging, backtracking, or trivially obvious steps that make the AI seem less competent. Reserve visible reasoning for high-stakes domains where auditability outweighs perceived competence.
Journey Context:
The intuition is compelling: showing reasoning should build trust, just as showing your work in math class does. In practice, raw chain-of-thought hits an uncanny valley. The reasoning is either trivially obvious \('I need to check the database...'\), which feels insulting, or it contains visible uncertainty and backtracking \('Wait, maybe not...'\), which is terrifying to users who want confident answers. Even worse, CoT sometimes reveals that the AI's reasoning is post-hoc rationalization of a pattern-matched answer, which actively erodes trust. The counter-intuitive insight: transparency about process can reduce trust when the process does not match user expectations of how reasoning should look. Users expect logical, linear deduction; AI reasoning is often associative, meandering, and self-correcting in ways that look like confusion rather than intelligence. The exception is medical, legal, or financial contexts where auditability requirements override UX concerns and showing reasoning, even imperfect, is better than a black box.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T23:08:31.264901+00:00— report_created — created