Mon, Feb 21, 2005

Evaluating experience design

by Austin Govella

Evaluate the design of any kind of experience - online or off - using five, universal facets that describe the entirety of an experience.

Comments

I edited this post to clarify how the facets would be used based on a conversation with Paula Thornton.

One of the most limiting factors in Design isn’t the splintering of specialist groups, nor the emergence of specialised vocabularies. We lack common language for discussing Design, for communicating and evaluating the creation of experience.

We all contribute to the overall user experience, but we don’t have a clear definition for what we do: what is experience? We have fuzzy definitions. Several models are emerging (I’m working on one as well), but we still lack an objective means for evaluating experience design. We may not understand it, but we know what it looks like, what it feels like, its general shape. I think we can use several facets to evaluate the resulting user experience:

  1. Personal: How well does the experience relate to the individual user? A conversation with your best friend compared to talking to the clerk at the DMV.
  2. Desirable: How much do the users desire the experience? How much do they want to experience it? How much do they need it? A triple heart bypass versus having your ears pierced.
  3. Enjoyable: How much do users enjoy the experience? A chore versus something you enjoy doing.
  4. Accessible: How accessible is the experience for the user? How understandable, comprehendable, physically available? Climbing Mount Everest versus climbing the curb.
  5. Negotiable: How able is the user to negotiate the experience to better communicate with them? How customizable?

Theoretically, you could survey a group of users to evaluate a given experience in much the same way psychological surveys are performed. A numeric value can then be given to the experience in question. Two quick examples illustrate how you can evaluate different kinds of experiences using these facets:

Two examples using the five facets to evaluate two different experiences: a rubix cube and heart surgery.

  • Heart surgery: A very personal experience and very desirable (if you want to live), but not enjoyable.
  • Solving a rubix cube: A very personal experience, and very negotiable, but not very accessible. Anyone can try, and almost everyone can manipulate the cube, but very few can solve them.

Evaluating successful experiences

A successful experience evaluates differently for different purposes. Successful sales and education require the almost perfect transmission of mental models. The better sales or education evaluate across all five facets, the more effective the sales and education will be.

Evaluating two learning experiences: learning on your own versus learning how to program your VCR.

Compare learning on your own to learning how to program your VCR, and you can see why so many people have learned how to do the latter. I think one can say that communicative experiences, experiences where the primary goal is to communicate, should evaluate highly on all five facets in order to be successful.

Evaluating two expereinces: jail time as a derrent versus jail time for a recidivist.

Other experiences evaluate differently for success. The success of jail time’s deterrence requires it be neither desirable, nor enjoyable. And we work at making it undesirable: restricted freedoms; small, overcrowded quarters; and a culture of violence and racism. But, in the eyes of someone trapped in a recidivist culture, jail time loses many of its deterrent features.

None of these facets are mutually exclusive. If we assign values for a given experience, there’s an interaction among these values, but no zero-sum interplay. Improvement along one facet may improve or worsen an experience’s value for another facet. And a high value in one facet might suggest high values in another, but this is not always the case.

The more enjoyable sex becomes, the more desirable the experience will be. But desirablity won’t always correlate with enjoyment. A divorce may be very desirable, but it’d be foolish to suggest it’s an enjoyable experience.

Most importantly, just as no two users ever have the same experience, these evaluations are highly subjective and can only measure the users perception of a future experience (their expectation), or it can measure their perception of the past.

Secondly, though we assign values for an experience for each of these facets, we’re not making value assessments. A successful experience does not necessarily achieve a good end. Nazi propaganda had great design, fulfilled goals, successfully transmitted mental models: it’s a stunning portfolio piece. Nazi propaganda was a successful experience even though the result was far from “good.” Tobacco advertising is another example.

Also, “accessibility” has everything and nothing to do with web accessibility. It has to do with how able I am to participate in the experience. For example, when communicating with my cat, I can enter the same room, and even pet her. She’s physically accessible, but verbal communication isn’t possible. I don’t speak Meow. Who knows what she’s saying, or what she’s thinking. We could say the same thing about my girlfriend.

Finally, these facets for experience should work independent of device or medium. Most of us work on the web, but experience happens with everything, so evaluation methods should work any where. We should use the same method to evaluate using a watch as we use for reading a novel, having sex, or ordering books from Amazon. Experience is independent of devices or objects. It happens in the head, so we need to evaluate the way a given experience interacts with what some have come to call a user’s infospace.

Other facets and models

Splitting experience into conveniently digestable bits is nothing new, and I can’t say I’ve even come close to examining every other model (check out “Forlizzi”), but of the few I’ve seen that work independent of device and medium, they inevitably conflate the mechanics of interaction with the experience that results from the interaction. I think this muddles things.

Probably the most well-known model using “facets” and “expereince” in the title is Peter Morville’s “Facets of user experience.” For the most part, the five facets I’ve mentioned here overlap with several of Peter’s seven. For example, that an experience be usable or findable, I would evaluate as accessible and negotiable. However, the center colum for Peter’s UX honeycomb attempts to evaluate the “value” of an experience. For the web and for communicating with clients, I think the honeycomb works great. For other experiences, though, I don’t think usefulness or credibility have anything to do with an experience’s value.

But my partner at Grafofini, Alex, suggests that valuability and credibility represent additional facets we should add to the list. I’m not so sure credibility can’t be reduced and evaluated using the other facets. And isn’t value an abstract conglomeration of how an experience evaluates against all five of these facets for experience?

I’m not sure I have the answer just yet, but my gut says no.

Talk About "Evaluating experience design"

Getting My Bearings said:

Morville's Facets of User Experience Refined? Peter Morville posted his Facets of User Experience diagram almost exactly a year ago. When it came out, there was discussion about the proper arrangement of the hexagons. I remember Peter explicitly said the arrangement of the facets in his…

Thu, Jul 7, 2005

Fred said:

I have recently been exposed to the notion that, in design, the word "user" has a special meaning (jargon) that somehow limits or constrains the designer. By contrast, my experience is that, even in design as I know it, the word "user" means what the dictionary says it means: one who uses.

I think that the concept of designing user experience is a valid one. I think that it is important to explore the concept of experience in all of its aspects and iterations, the better to assist people in accomplishing whatever task may be at hand. And I think that all of these things can and should be done within the common definition of "user."

And if such jargon for the word "user" does in fact exist, my sugggestion is not to get rid of the word, but to get rid of the jargon.

But then, I'm just a guy who sells auto parts. What do I know about helping people get their work done? (8-)

Fri, Mar 10, 2006

Austin Govella said:

I think many designers carry similar definitions of 'user'. Mine might be a little broader: anyone who is affected by the design (so it's more in line with the more general, 'stakeholder').

But in some places, the term has become very constrained, and it's used as a wall to keep designers out, instead of a bridge to bring them in. You're right that choosing a new term isn't necessarily the right choice. New terms probably don't provide the end-run around the wall that we'd like to see.

But… dropping the jargon can be a long difficult process, too.

P.S. Definitely work to live. And extra points for the Shelley! That's one of my favorite passages from him.

Fri, Mar 10, 2006

nowuseit.com | links for 2006-08-20 said:

[...] tr - a parody of Web 2.0 Logos. Pretty cool. (tags: ajax web2.0 webdesign flickr parody) Thinking and Making ?Ǭ

Tue, Aug 22, 2006

Mike Oliver said:

I am currently in a debate between product development and product management. We have a product that will bring Web 2.0 to bear on document management where our content server will support multiple interfaces, Web Folders via Windows Explorer and various Web Browser interfaces including a Web 2.0 AJAX interface. The later was designed by product development to mimic most of the functionality of Windows Explorer including look and feel, iconage, themes and color schemes. Product marketing wants to jazz it up for branding and product development wants to maintain the Uniform User Experience.

I may be wrong but your five points seem to favor the product development viewpoint since having the same look and feel means things work the same on both interfaces (within limits). Am I wrong?

Thu, Dec 21, 2006

Austin said:

Mike,

How like or unlike the interface is to existing interfaces affects how accessible or inaccessible the interface will be to new users (using my terminology from above).

But assuming the Windows Explorer interface is usable just beucase it's ubiquitous is a huge mistake. Many people's eyes glaze over when they hit the folder tree.

Any sprucing up you can do make the interface more inviting, friendlier, more intuitive, or easier to use should definitely be done, regardless of whether or not it ends up looking like the Windows Explorer.

Every interface requires user's learn something, and they're not against learning something enw if it's valuable to them.

Mon, Jan 8, 2007

Subscribe to the feed.