User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

For the interface I'm working on, users can mark certain rows as "Verified", but they also have the option of marking them "Unverified". To do this, they select several rows by clicking on checkboxes and click on a button called, "Verify".

Should I include a separate button for "Unverify", like so: Exhibit A

Or should I instead use a split button and include "Unverify" as a sub-action of verify, like so: Exhibit B

A is clearer and I don't hide any action, but the objective is to get users to verify rows. I don't want users to accidentally be unverifying rows.

B hides one of the two actions and might be a problem for discovery, but is more space efficient and promotes the objective of verifying a row.


share|improve this question
up vote 1 down vote accepted

(Thinking out loud) I think separate buttons are a must. Regarding the location of the buttons, I think it depends upon whether or not there's any instructional text. Then again, even if instructional text is included, proximity of the buttons with the rows they're addressing could prove to be an issue.

Answer: It's difficult to specify completely without knowing the full context of the experience. Based on what I'm seeing, you could also limit the interface to one button that only indicates which elements are verified. With that approach, however, error mitigation goals can't be accomplished.

I'm still convinced that separate buttons are a must. They should, however, be separated to help avoid people clicking the wrong button. I'll have to stop there with my response though, for the aforementioned reasons.

share|improve this answer
Thanks, Darren! I see what you're saying, and I agree with your reasoning behind it. – hidrees Jan 22 '14 at 14:29


download bmml source – Wireframes created with Balsamiq Mockups

I might suggest putting the "Unverify" action into the context of each row, so that it's clearer that "Verify" is the primary action, and also to avoid accidental Unverifications.

share|improve this answer
Need to perform select checkbox and then click on 'Unverify' button? or if i click on 'Unverify' without select checkbox, what is the use of checkbox here? – Pavan Kumar Jan 21 '14 at 6:11
Thanks for your response, Tim! The rows have individual actions already, the "unverify" button I'm looking to add is for bulk actions. – hidrees Jan 21 '14 at 13:20

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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