Report #95061
[gotcha] Adding confirmation dialogs for every AI action creates automation bias where users blindly approve
Reserve explicit confirmation for irreversible or high-stakes actions only. For reversible or low-stakes actions, let the AI proceed and provide an undo mechanism. Use progressive trust: confirm the first few actions, then reduce confirmations as the user demonstrates comfort with the feature.
Journey Context:
The instinct when building AI-powered features is to add confirmation dialogs for safety: 'AI wants to delete this file. Approve?' But human factors research consistently shows that when users are constantly asked to confirm, they develop automation bias—they stop reading and just click approve. The confirmation becomes security theater that adds friction without adding safety. The better pattern is 'ask forgiveness, not permission': let the AI act, but make actions reversible via undo. The tradeoff is between perceived safety \(confirming everything\) and actual safety \(undo \+ selective confirmation\). The right call: confirm only irreversible actions; for everything else, act first and provide undo. This is the same insight that made Gmail's 'Undo Send' more effective than a 'Are you sure?' dialog.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T18:08:25.541378+00:00— report_created — created