I understand the idea behind having the more likely to be used action on a page slightly larger or in a different style in order to guide the user to it (for example having a button for save but a small text link for cancel).

When say an administrator hits delete I have a confirmation dialog appearing asking if they are sure they want to do that and presenting them with two options, 'Yes, Delete this' and 'No, Keep this'. At the moment these are the same size and style and therefore the same weight on the page.

I was wondering if that should be the case or should I assume that the administrator is not an idiot and that if they have hit delete confirming this action is the most important part of his next step and therefore should be given a greater weighting on the page?

2 Answers 2


Luke Wroblewski wrote an article called Primary & Secondary actions on web forms that talks specifically about this problem. His data is based on research from eye-tracking studies.

The conclusion is basically that there should be differences in visual weight between the two so that you can interpret, at a glance, which call to action is more significant. He also talks a bit about positioning and order.

Visual weight in forms

As for which button should have more weight, it's up to you to determine the situation. It's usually good practice to be very conservative about buttons when dealing with CRUD operations like deleting something, but you probably know best (or you should test) which situation is more likely to occur. If deletion happens more frequently, then perhaps it should be the primary action.

See Michael's answer below for some good references to platform guidelines which specify how you should decide which should be the primary action.

For more discussion on similar issues with buttons, see these questions:

  • Thanks for the brilliant answer and links, I will check them out.
    – Toby
    Oct 12, 2010 at 10:28
  • Rahul, do you have any more GUI design references? A lot of people just point to the Apple style suggestions, but something more intricate would be nice. Especially if it is a book.
    – Nic
    Oct 12, 2010 at 14:51
  • What kind of GUI design references? Certainly you should read LukeW's book on web form design if you care about things like button placement and error messages.
    – Rahul
    Oct 12, 2010 at 14:56
  • I would think that anything that is destructive, like a delete, should not be the primary or default behavior. This is one of the few cases where it's better to make what the user wants to do difficult, because you would never want this to happen by accident. Oct 13, 2010 at 15:59
  • 2
    @RussellUresti It's easy to say that, but if the destructive behaviour is something users do very frequently and want to be able to click through easily, maybe it should be. The answer lies with asking them, rather than guessing or assuming.
    – Rahul
    Oct 13, 2010 at 16:44

If this is a desktop thick-client app, or it’s important to be consistent with desktop apps, then the Windows 7 UX guidelines specify that for risky actions, the most visually prominent button should be the “safe choice” (page 384). Specifically, the safe choice should be the default button, which is both more visually prominent than other buttons, and also activated by the Enter key. Similarly, Apple’s HIG says the most prominent button should that which “represents the action that the user is most likely to perform if that action isn’t potentially dangerous. [emphasis in original].” It specifically recommends against making a button prominent “if it causes a loss of user data” (p245).

So, the more prominent button should be "No, Keep This," right?

On the other hand, I have to agree with you that chances are the user is not an idiot and 90%+ of the time they really want to delete the object. The result is that users will get in the habit of clicking the confirm button of your confirmation message without really thinking or even reading the message, a habit many users already have. That defeats the purpose of having the message in the first place. Furthermore, with the exception of slips-of-the-mouse, users often don’t know that they’re making a mistake until after the action is committed and they see the result in the parent window (e.g., “Oops. Deleted the wrong thing”). Such confirmations do little other than waste user effort and teach bad habits.

If at all possible don’t have any confirmation for delete. Instead, have a clear and easy way to undo deletes.

  • I like the way you answered his question directly before gently reframing the problem. Oct 12, 2010 at 12:46
  • Thank you for your thorough answer and backing it up. I am not sure I like the idea of no warning though even if there is a way of undoing it.
    – Toby
    Oct 12, 2010 at 13:03
  • "Think-client" or "thick-client"?
    – Rahul
    Oct 12, 2010 at 14:50
  • @Michael, that blog post you linked to is insane. Props for that. Will subscribe to your blog, you look to have a lot of experience developing desktop apps.
    – Rahul
    Oct 12, 2010 at 14:53

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.