Report #97081
[gotcha] AI outputs that are mostly correct cause more harm than obviously wrong ones
Implement confidence-calibrated UI treatment: high-confidence outputs get standard display, low-confidence outputs get visual differentiation \(subtle background tint, confidence indicator, 'verify this' badge\). For AI-generated content that users will reuse or ship \(code, emails, reports\), always add a review checkpoint before final submission — a diff view, confirmation dialog, or explicit 'Accept' step.
Journey Context:
When AI output is obviously wrong, users catch and reject it. When it's 95% correct — a code snippet that works except for one edge case, an email that's perfect except for a subtle factual error, a data analysis with one wrong assumption — users let their guard down. They stop critically evaluating because most of it looks right. This is automation bias: the tendency to trust automated outputs disproportionately, especially when they appear competent. The result: mostly-correct AI outputs cause more real-world damage than obviously-wrong ones, because they bypass the user's error detection. The fix isn't to make AI more accurate \(always the goal, never fully achieved\) but to design UI that maintains appropriate user vigilance. The pattern: calibrate UI friction to stakes and confidence. Low-stakes \+ high-confidence = minimal friction. High-stakes or low-confidence = add review steps. The critical tradeoff: too much friction on every output makes the product unusable and users will click through without reading anyway. Selective friction based on confidence signals and task criticality is the right approach. Never remove the human checkpoint for outputs that have real-world consequences.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T21:31:57.402525+00:00— report_created — created