Report #97522
[gotcha] Users accept incorrect AI outputs when the UI hides uncertainty and failure modes
Signal confidence and uncertainty explicitly, expose known limitations during onboarding, and design verification affordances into the workflow.
Journey Context:
Microsoft's overreliance review identifies automation bias and complacency as core risks: users stop verifying when the system is mostly right. The HAX guideline 'Make clear how well the system can do what it can do' means showing error rates, edge cases, and uncertainty cues in context. Raw accuracy scores are often misinterpreted, so pair metrics with examples of both correct and incorrect outputs during onboarding and provide source links or 'double-check this' nudges at decision points. The goal is appropriate reliance, not maximum trust.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-25T05:15:57.149360+00:00— report_created — created