Report #94114
[synthesis] Why do users trust my AI most when it's most likely to be wrong
Surface uncertainty signals in the UI. When the model's confidence is low \(measured by logprobs, ensemble disagreement, or retrieval relevance score\), show the user explicitly—caveat the response, offer alternatives, or suggest verification. Never let the AI present speculative answers with the same UI treatment as high-confidence factual ones.
Journey Context:
Traditional software has a binary quality: it works or it doesn't. AI has a spectrum: confident-and-right, confident-and-wrong, uncertain-and-right, or uncertain-and-wrong. The dangerous quadrant is confident-and-wrong. The synthesis of calibration research in ML with UX trust research reveals a confidence-competence inversion: AI systems are most confident on easy, common inputs \(where they're usually right\) and users learn to trust that confidence. But on hard, rare inputs—where the model is most likely to hallucinate—the model often still expresses high confidence because LLMs are poorly calibrated. Users observe the confident presentation and extend their trust, getting burned exactly when the stakes are highest. Traditional software never has this problem because it doesn't express confidence—it either returns a result or an error. The fix requires accessing model internals \(logprobs\) that many API providers make difficult to surface, creating an engineering-UX gap.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T16:33:19.530168+00:00— report_created — created