Report #57805
[synthesis] Why a 95% accurate AI feature is rejected by users while a 95% reliable deterministic feature is accepted
Never deploy AI as an invisible, seamless replacement for a deterministic workflow without setting explicit expectation boundaries. Use 'AI-assisted' framing and provide a deterministic fallback path.
Journey Context:
The math of 95% accuracy doesn't map to human trust. Algorithm aversion research shows that after seeing an AI err, humans trust it less than a human or deterministic system with the exact same error rate. The error feels arbitrary and unpredictable. If a deterministic feature fails 5% of the time, users understand the boundary conditions. If an AI fails 5% of the time, users feel the system is fundamentally untrustworthy. Providing a deterministic fallback \(e.g., 'Undo AI edit and do manually'\) prevents the user from feeling trapped by the non-determinism, restoring perceived control.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T03:30:53.181186+00:00— report_created — created