Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

Looking at the UX principles that mozilla use as keywords to tag bugs in bugzilla it looks like ux-affordance and ux-discovery are very similar:

ux-affordance — controls should visually express how the user should interact with them. [Source: Norman]

ux-discovery — users should be able to discover functionality and information by visually exploring the interface, they should not be forced to recall information from memory. (This is often the nemesis of ux-minimalism since additional visible items diminish the relative visibility of other items being displayed). [Source: Nielsen]

Are these just two ways of looking at the same problem, or are there UX issues that would fall under one principle but not the other?

Update:

Perhaps the tag-wiki definitions on this site could be updated based on the responses to this question. They are currently:

Affordance is a property of an object that naturally indicates how the object can be used.

And for discovery:

the process by which a user learns what a program can do through affordances in the UX.

share|improve this question
2  
+1 It's good when meta questions like these about usability and UX are brought to light in the forum. I will give users of this forum a greater understanding of what a poster means when she uses these terms. –  AndroidHustle Jul 31 '12 at 13:44
    
I think the definition of "ux-affordance" should probably be updated to say "controls should observably express...", given that affordance is not merely visual. –  zzzzBov Jul 31 '12 at 17:32
    
"I will give"..? no, that's supposed to be "It will give"... =P –  AndroidHustle Aug 5 '12 at 1:10
add comment

3 Answers 3

up vote 10 down vote accepted

They're definitely different principles. Affordance aids discovery, but discovery isn't about the visual look and feel at all; it's not even about expressing what a single control does.

Say you have a delete button, it's red clearly 3D, depresses when you press it, just begs to be touched, and has a big trash can icon on it with the word "DELETE" written clearly on it. Very good affordance. But say that delete button is hidden behind 3 menus, one of which requires an uncommon long-press action. It's not discoverable. But is that a bad thing?

A philosophical difference between Affordance and Discoverability is that pretty much everything should have the best Affordance you can give it. Discoverability is something you have to prioritize; maybe you want that delete button to be hard to find.

See The Myth of Discoverability:

All things can not be easily discoverable because everything is limited. You have limited screen real estate, users have limited attention spans, and abilities to perceive or understand things. Therefore, all design for people is a zero-sum game: tradeoffs must be made and priorities must be set if there’s any hope of a good outcome for customers.

You have to prioritize and make common/important tasks the most discoverable. It's okay for less-common things to be harder to find; a good design still makes it possible to find those features, but leaving destructive features on the front page where they can accidentally be applied is not good for users.

share|improve this answer
add comment

Affordance is related to the object itself. Eg: A button looks clickable.
enter image description here

Discoverability is related to the product/solution. Eg: An image-manipulation toolbar shows all features it is possible to use when you want to work with an image.

enter image description here


A physical example:
If you walk down a corridor, then the affordance of the door-handles will "tell you" how it is possible to interact with each door. (Push, pull, turn, lift etc). But the labels of each door will tell you what you can find behind each door.

enter image description here
Discoverability:
enter image description here - enter image description here

Affordance:
enter image description here

share|improve this answer
add comment

I would say that they are two sides of the same coin.

Affordance is, as you quoted, designing controls in a way that they by themselves convey to the user how the user should interact with them. A common example is a hammer, that has a grip friendly handle and a heavy head, a natural instinct would be to smack down on something with it.

Discoverability is more of a situation that can involve a set of controls that should be easily accessible when performing a task. Bringing back the hammer analogy it could be a toolbox that is includes everything that a user needs for building a house. It's clearly labelled and accessible and suitable for the situation.

share|improve this answer
add comment

Your Answer

 
discard

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.