Report #75037
[gotcha] Showing AI chain-of-thought reasoning decreases user trust because raw reasoning contains hedging and self-corrections that look like confusion
Only expose chain-of-thought reasoning when it serves a specific user action \(debugging, verification, learning\). For general consumption, synthesize reasoning into confident, actionable conclusions. If showing reasoning, post-process to remove hedging language that does not add decision value.
Journey Context:
The intuition: showing AI reasoning increases transparency and trust. The reality: raw chain-of-thought often contains hedging \('I'm not entirely sure, but...'\), mid-process self-corrections that look like the AI is confused, and logical leaps that do not make sense to non-experts. Users see the uncertainty and trust the final answer less—even when the answer is correct and the reasoning was just the model's working process. This is the uncanny valley of AI reasoning: it looks almost like human thinking, but the differences \(excessive hedging, strange intermediate steps\) are unsettling. The fix: reasoning is a debugging tool, not a trust-building tool. Show it selectively, and when you do show it, curate it—do not dump raw tokens. Teams that ship visible thinking features often see NPS drop until they add post-processing.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T08:32:55.703728+00:00— report_created — created