Home Calendar | Syllabus | Projects | Contact | Links  

English 413, Electronic Documents and Publications -- Dr. Jablonski -- UNLV -- Course Website Link to UNLV home page

Calendar

Old
Announcements


Syllabus

Online
PDF

Projects

Webzine Project
Doc Re-Purposing
Web Site Evaluation
E-Portfolio

Lab Assignments

Lab #1
Lab #2
Lab #3
Lab #4
Lab #5
Lab #6


Lab #5: Usability Testing

What You Need to Complete this Lab

  1. Access to the Internet
  2. Knowledge of the readings assigned for today:
    • Steve Krug, Don't Make Me Think (ch. 1-11)

Lab Overview
For this lab, you will practice the basic process of usability testing. As Steve Krug explains, the basic idea of usability testing is simple:

If you want to know whether your software or your Web site or your VCR remote control is easy enough to use, watch some people while they try to use it and note where they run into trouble. Then fix it, and test it again. (p. 143)

User testing should be conducted early and often in the development of a Web site. You don't have to test scores of users, just 3-5 at a time. The testing begins with understanding the audience and purpose of the site. Tests are designed to assess how well average users can perform the main functions/purposes of a Web site. To test an airline's Web site, ask users if they can easily make online travel reservations. If the site also aims to provide destination information, check to see if users can find worthwhile information about cities, hotels, and car rentals. And what if users get stuck? Check to see if they can find information about user assistance, site policies, and contacting the company.

Testing is simple too, as Krug explains. You need enough money to pay the people you test a modest stipend and you may want to record the actual tests on video (Krug, p. 144). After you set up your user test (Krug, pp. 151-153), you simply want to sit back and watch how the people react to the simulated tasks you ask them to perform—without any help from you. Before they begin, you'll want to ask them some basic background information (age, gender, Internet experience and habits) to see how closely your test subjects match the profile of intended users of the site. During the tests, you'll want to take notes about what users click on, what they say out-loud, and how long it takes them to perform the tasks.

Once the tests are complete, compile the results, analyze the data for trends that reveal what's not working (and what's working), and determine what changes to make based on the test results. Then fix it, and test again (see Krug, pp. 172-180).

Lab Activity
To get experience conducting user tests, for this tutorial you'll be grouped into teams of "usability consultants." Each team will be assigned a Web site to evaluate with pre-arranged tests (provided with this lab), using classmates from other groups as the user test subjects.

Task Hint Sample

1. Divide into teams of 3-5 students.

Each team will be assigned a Web site to test.


 
2. As a group, conduct a preliminary site analysis.

Review the Web site and have a recorder write up brief notes about the following:

  1. Site Purpose
  2. Site Audience(s)
  3. Site Information Architecture
  4. Site Design
See Keith Instone's "User Test Your Web Site"

3. As a group, review the usability tests provided for each site.

(Dr. J will distribute print copies of the tests in class.)

Try the test yourselves by having one team member perform the test while the rest observe. Discuss and record any problems you anticipate test users might encounter.  

4. Conduct the user tests:

  • Each team must conduct 3 tests
  • Each test must be conducted by at least 2 people
  • Results must be recorded on the user test sheets provided.

Remember Krug's advice for testing (pp. 155-177):

  • Be nice
  • Don't give hints
  • Try to see the "balloons forming over their heads"
  • Probe what users are thinking
  • Don't be afraid to improvise
  • Take notes
See Keith Instone's "Conduct Your First User Test"
5. Compile and analyze the test results in an informal report.

Your write up must include:

  • summary of the test data—compile/tabulate results
  • test highlights—list trends revealed by the tests
    • How many problems were identified by all users tested?
    • How many unique problems were intentified?
  • recommendations— list at least 3 usability issues and suggest solutions, based on the test results.

See Krug's example on p. 173

See also "Report Your Findings," Part 4 from Seth Gordon's "User Testing: How to Plan, Execute, and Report On a Usability Evaluation."

6. Submit your team's site analysis notes, test data sheets, and final report to Dr. J    

top


Home Calendar | Syllabus | Projects | Contact | Links