I'm working on an app that requires someone to rate the how they did at recalling an item (to which they are shown the correct answer before they rate the item). The three options are: wrong, right, and easy. With easy meaning that it was right they didn't have to think about it to get the answer.

I'm open to suggestions of name changes that improve the clarity, but this question is more about how to make it easier for users to scan them without having to read the text each time - with particular interest on the "easy" option.

Two example mockups we have so far are:

and

How would you represent these 3 buttons, and what improvements can you suggest over the current ones, with emphasis on the easy option?

4 Answers
4

PhilipW is right in that you don't need to say right, because that implies that easy might not also be right. I'm assuming a task has to be completed to get to this stage and that users have some indication of right and wrong, and that they have some element of measurement by which they can consider the task to be easy or hard?

Based on the information given, here's a visual that might be easier to scan:

[edit1] added comparison following Gilbert's comment

[edit2] and here's a couple of options that group the hard and easy as both not being wrong (ie right!)

Nice visual buttons. I'm concerned that making the Easy button green sends a subliminal message to the user that the tasks are supposed to be easy. Maybe yellow would be better?
–
Gilbert Le BlancSep 16 '11 at 12:46

good point (and assuming they aren't all supposed to be easy.) @JohnGB - what is the outcome (and for whom) when the user clicks more on hard than easy.
–
Roger AttrillSep 16 '11 at 12:52

1

It's answers like this that make me love coming here...
–
John NSep 16 '11 at 14:11

+1 I disagree with the "difficult" or "hard" button labels as even if something wasn't easy/obvious - I think someone judging their own effort won't tick "difficult" or "hard" even if they had to think for a while...
–
Oskar DuvebornSep 16 '11 at 14:28

I'd make the three options refer specifically to difficulty - "Couldn't do it!", "Difficult!", "Easy!". This makes more sense to the user (there's three comparable options), but because your options now easily fit a 'sliding scale', you can use imagery based on traffic-light schemes or numbers.

For instance, you could now use a set of coloured faces (red / angry - impossible, yellow / neutral - tricky, green / happy - simple) or sets of one, two and three domain-relevant icons, with the number signifying difficulty (eg, for recipes, one chef's hat for easy, two for tricky, and three for impossible).

Larger buttons, shorter synonymns. There's a couple of things you could do. What's important is that the three options are directly comparable (e.g on a sliding scale), both for user perception (makes more sense to the reader) and because it provides more opportunities for iconography.
–
Jimmy Breck-McKyeSep 16 '11 at 12:09