Confirmation Dialogs Can Prevent User Errors - NN/G

Find the training option that fits your learning style.
February 18, 2018 · Last reviewed Aug. 7, 2026 2026-08-07
Errors are a big deal for UX. They represent one of the 5 key quality components of usability: error frequency and severity are negatively related to the usability of a system. And error prevention is one of the 10 heuristics for user interface design.
Even though we talk about “user error,” the true culprit is the designer, for having made it too easy for users to get into trouble. We cannot assume that people will always use our design in the intended manner.
There are many ways to prevent (or at least reduce) user errors. Here, we’ll focus on one of the simplest — the confirmation dialog.
In graphical user interfaces, a confirmation dialog usually takes the form of a modal dialog box that pops up and must be attended to before the system will execute the user’s command. (Other interaction styles may use different formats for confirmation dialogs. For example, a voice UI might use a spoken question that the user can reply to with a “yes” or a “no.”) Whatever the format, confirmation dialogs constitute an interruption initiated by the system; they slow down the user’s task flow. If this delay prevents an error, then it’s time well spent, but, if not, they are disruptive and thus annoying.
Windows 10 offers a good example of a confirmation dialog when the user attempts to empty a recycle bin that contains a single file:
However, when the recycle bin contains multiple files, Windows 10 uses a less usable confirmation dialog:
First of all, why does Windows use two different icons to represent the same issue (permanent file deletion)? The X and the exclamation mark are both reasonable icons for this type of warning, but pick one, for the sake of consistency (another top-10 UI heuristic). However, this is a minor issue, since I’m sure users don’t base their response to these dialogs on an analysis of the icons.
The problem with the multiple-file confirmation plagues many confirmation dialogs: lack of specificity. Saying these 2 items doesn’t tell users which files will be deleted. In contrast, the single-file confirmation shows the name of the file, as well as some supplementary info that’ll help the user determine whether the right file will be deleted. (For even better usability, display a thumbnail of the file instead of a generic icon.) Admittedly, it’s hard to provide much detail when many files are being deleted, and stating the number of files is one small amount of specificity.
Let’s go back to basics: why have confirmation dialogs in the first place? To allow users a second chance to check their work before proceeding with a dangerous action. However, it’s not a second chance at all if users automate their response to the conformation and simply click Yes without thinking further.
A confirmation dialog must restate the user’s request and explain what the computer is about to do, with specific information that allows users to understand the effects of their action. Without identifying details it’s useless to ask users to confirm a request, as shown by the video-delete confirmation from YouTube:
When users are asked Are you sure you want to do this? without further details, the only sensible reaction is “of course I want to do the thing I just told you to do,” and hit Yes without further thinking. Such automated behavior provides no protection at all, and only serves to annoy users — and make them pay less attention to future warnings.
There is admittedly a tension between guidelines #1 and #2: you want to warn against serious consequences, but you don’t want to warn so often that the warning is overlooked and the answer becomes an automated behavior. The solution is to conduct a task analysis to determine the severity of different outcomes and the frequency of possible user actions. For example, a banking site might be personalized to only require confirmation for online payments that are at least twice the amount of each user’s normal range of payments: if I usually pay bills that are around $100–$500, then my first request to pay somebody $1,100 could well be an error, and the desired payment might only be $110. Even if I did want to pay $1,100, I might welcome the chance to doublecheck a payment that would be big — and thus scary — for me. On the other hand, somebody who pays $10,000 bills several times per day would be annoyed to be interrupted for a $1,100 payment. (“Twice the usual amount” is just an example, and not necessarily the optimal threshold — determining that requires user research.)
Microsoft provides an even larger set of design guidelines for confirmation dialogs, including how to handle bulk confirms for a sequence of actions. Ultimately, though, I think the most important usability considerations in confirmation dialogs is to not overuse them and to be sufficiently specific that users know what they’re agreeing to. I say again: if you warn people too much, they stop paying attention. If I said this a few more times, you would stop reading.
Finally, for improved total user experience, beyond the design of the dialog box itself, do go to great lengths to provide undo, because some user errors will remain despite the even the best of confirmation dialogs. All you can do is to reduce the number of user errors, but that’s an extremely worthy goal that will increase customer satisfaction, possibly save lives, and definitely increase the business value of your design.
Components, design patterns, workflows, and ways of interacting with complex data
Check Error-Message Quality with a Scoring Rubric
Evan Sunwall · 4 min
Create Efficient Error Messages
Evan Sunwall · 4 min
Tim Neusesser · 3 min
What the Erroneous Hawaiian Missile Alert Can Teach Us About Error Prevention
Kim Flaherty · 6 min
Preventing User Errors: Avoiding Conscious Mistakes
Page Laubheimer · 9 min
Preventing User Errors: Avoiding Unc