1.31.2013

unit five reading

READING SUMMARY

Chapter 8 is a pretty short chapter and it really just covers the uselessness of arguments about usability. We've all heard the saying, different strokes for different folks, and this is the primary focus of this chapter. Unfortunately, when it comes to making decisions between a group of people emotions and personal likes/dislikes come to the table. It is almost impossible to just have a bias-free discussion about why or why not something works. One of the solutions the book offers is instead of having the mindset "do users like this..." aim for a more productive question, "does this thing with these objects work in a way that makes visiting this page a good experience for most people who might use this website..." It might seem like it's more work, but in reality opinions are like assholes. Excuse my french.

So what should you do instead of  unproductively arguing endlessly? Two words: usability testing.
This bring us to chapter 9, Usability testing on 10 cents a day. Maybe you've seen the movie Kate and Leopold (don't worry if you haven't). In this movie, Meg Ryan plays a very successful market researcher. Her position focuses on testing viewing audiences and changing advertisements to please them. This is very similar to usability testing.

A focus group is not the same thing as a usability test, though. A focus group is usually a small group of people that react to different ideas and designs together. In a usability test only one person at a time is being tested, usually by an individual doing the testing, and they are usually physically working through a design. I know that sounds a bit confusing but I promise to clear that up a bit.

Usability testing does not have to be a big, expensive ordeal. In fact, the more simple and inexpensive you do it, the more times you can test! All you really need is a camera or some sort of software that records what is happening on the computer screen and what is being asked of the user. To set up a test, you should set up a computer at a desk. Bring the user in the room while the design is not visible. The lead will talk the user through the process, making sure it feels comfortable for the user. Comfort is VERY important here, mostly because you want the user to feel okay if they make a mistake or can't complete the task you've asked since this is the VERY reason why you are testing: to make your design better! After a short introduction of the project and background questions for the user, you may show the user the design. Before instructing the user to click around, you can ask questions like what do you think this design is for, is it obvious, what would you click on first, etc. This will get an initial feel if the user understands the point. The rest of the test can continue in a similar fashion, with you asking the user to complete a task, while observing how the user reacts with the design.

This sort of testing is not used to prove or disprove any part of a design, but rather to inform the designers of potential hiccups for users. Most people involved will have some sort of emotional tie to the project, and this really allows them to step back and see it through the eyes of their potential client. Testing is a HUGELY important part of a design process, and it should be done EARLY and OFTEN by really any users of the web, not necessarily only by your target audience.

These chapters were really eye opening for me. I have previously coded my own website, and have done my own version of testing without even knowing it. When I showed my site to an instructor, I watched as he clicked around to understand how my "simple" website worked. It was interesting to take notes on places he often clicked to navigate around the site, although they were not what I intended. I think this process really is as important as the book makes it out to be and should be done repeatedly.

ADDITIONAL RESOURCES
Usability 101
Usability Testing Demystified
5 Second Usability Testing
Introduction To Website Usability
Website Usability Tools
Usability Testing Myths

No comments:

Post a Comment