IDIA 750.185 humans, computers, and cognition
overview calendar assignments resources class list


spring 2003 assignments

assignment two: usability testing and test report

Each team will recruit four participants and perform four tests. At least two of these tests must be video-taped. The other two may be captured using Camtasia.

writing the report

Presumably, the web team will revise the site as necessary based on the results of your testing. Your job is to provide the results of your testing as persuasively as possible, in order to overcome the web team's natural temptation to ignore this feedback.

The focus of your report should be on helping your audience reconcile user needs with business goals and available human and technical resources. Analyze your audience carefully

  • who they are
  • what their goals are (connect your suggestions to their goals, address their concerns)
  • what decisions do they actually have power to make
  • how will they read their report (skim it all, skim some sections, assign it to someone else)

It's your job to make sense of the mass of information, to figure out the relationship between your observations and the underlying problems or errors or design flaws, to figure out which problems are the most urgent or will provide the highest payoff if fixed, then present that information to designers and decision-makers effectively and persuasively. You'll want to put the errors you identify into categories, such as issues related to layout, navigation, functionality, or visual tone. You may also use categories that reflect different areas or functionalities of the site.

Once you've identified and categorized usability problems, you need to evaluate how important they are. Evaluate problems in terms of their

  • criticality (how much do the problems impact the site's success)
  • severity (how hard will the errors be to fix)
  • frequency (how often do the errors occur)
  • cost (how much will the errors cost to fix; how much will the errors cost if unfixed)

You should also suggest possible solutions to the problems you identify. Deciding what revisions to make involves reconciling user needs with business goals and technical resources, reconciling cost with increased user satisfaction, reduced support costs, increased sales, more registration, or whatever the benefits will be. If appropriate, define qualitative and quantitative usability goals to be achieved through redesign.

It's your job to make the users real to your audience. As you evaluate your results, look for memorable quotes or images (fotos or video clips) from the tests, or artifacts from the user's workplace, that you can use to enhance your report or presentation. Use these quotes or images to make the users vivid and real to designers and executives.

usability report sections

  • executive summary
  • description of test methodology and test circumstances (perhaps in appendix)
  • test participants
  • test tasks
  • results--sorted into categories, prioritized, with recommendations
  • appendices (screener, script, other test materials, perhaps methodology, participants)

usability report checklist

  • Have you written an executive summary that covers the major positive and negative results of your test?
  • Does your executive summary speak effectively to decision-makers? Does it focus on the decision-makers' priorities and concerns?
  • Have you described the circumstances of the test? (physical location, number of test participants, equipment, connection, version of interface, test team description, etc.)
  • Does your report help readers to visualize the users as real people? Were you able to include a videotape of the highlights of the test?
  • Have you identified the areas of the interface that need attention?
  • Are your observations thorough and persuasive?
  • Are your recommendations persuasive and courteous? Do you address feasibility issues?
  • Have you categorized your observations into logical categories that accurately reflect the patterns you saw in your testing? Do your categories also relate logically and effectively to the concerns of the site owners and stakeholders?
  • Have you categorized your observations appropriately in terms of their seriousness? Do you maintain credibility by not exaggerating or minimizing the importance of the problems you've found?
  • Have you included an appendix containing your test script, screener, and any pre- or post-test questionnaires?
  • Have you included an appendix of summary information about your test participants?
  • Is your usability report professional and attractive in appearance? Are major sections clearly marked? Have you made the report accessible with effective use of headings and white space?

 

assignment one: contextual interviews

Each group member should participate in three or four contextual interviews. Contextual interviews should be conducted in pairs.

Structure of the contextual interview

introduction (15 mins)

You'll spend the first 15 minutes building a comfortable relationship with the participant. You explain who you are, what your focus is, promise confidentiality, get permission to do an audio tape.

Get an overview of the job and the work that the participant is about to do, but wait to ask follow-up questions until the next stage, when the participant is actually involved in concrete work.

transition

Explain that while you watch the participant doing her work, you might interrupt to ask questions, but that you want the actual work to be the focus. Explain that you want to act like an apprentice who is learning the best way to do the work, and the reasons behind the work. You don't want to slip into interview mode, where you ask questions and get answers. You want to stay as concrete as possible.

observation (about an hour)

Observe, ask questions, share your interpretation of what you're seeing. Look at artifacts, analyze them, ask questions about what you see. Ask for retrospective accounts, but make sure you keep those retrospective accounts as concrete as possible (see suggestions in BH pgs 47-51).

wrap-up (15 mins)

Summarize what you saw and what you think it means. This is your chance to share your interpretation with the participant and get it corrected or amplified.

Ask for copies of any artifacts that might be appropriate to take with you.
 
 

Questions to answer as you observe

Questions for researching user goals and tasks
  • What are the users' goals?
  • What do they currently do to achieve these goals? (tasks)
  • What are the user characteristics that might affect their work? (Personal, social, cultural traits; previous knowledge about subject matter, tasks, or tools)
  • What is the user's physical environment?
  • How do users relate tasks to goals?
  • What resources (help desk, information, artifacts) are available to users as they work?
  • How do users interact with each other? With customers? With managers?
Questions for researching user tasks
  • What information do users need to do this task?
  • Where do users get it?
  • What do users do when they get stuck?
  • What are the steps of the task (task sequence)?
  • What tools does the user use now to perform the task?
  • How did the user learn to use these tools?
  • How easy to use are their current tools?

Reporting your results

Based on your interviews, your team will create user profiles, task lists, a workflow, and task flows.

documents
create as complete a task list as you can for the users you observed
create task flows for tasks your team was able to observe
create user profiles for the users you observed
create a workflow for the work that you observed
 Announcements

3/20
We are still scheduled to do contextual observations of kids doing homework on Thursday afternoon, 3/27, at 2:30 pm. Watch for an email cancellation if there is any problem.

Shannon, Jay, and Betsy will be performing their contextual interview with Jon Shorr on 3/19 at 11:30

Holly, Rahul, and Amit will be performing their first contextual interview with Nancy Kaplan and Carmen Wooden on 3/12 at 10 am.

On 3/13 we will attend the STC usability lecture at JH Applied Physics Lab.

I will let you know by email as soon as I have scheduled the visit to the library to talk to children. We will NOT be videotaping these interviews, so you'll need to take good notes.

The usability testing on the UBalt college sites will hopefully take place between April 7 and April 18. Each group will be in charge of scheduling their own tests, but try to keep your calendar as open as you can during that time.



©2002 Kathryn Summers overviewcalendarassignmentsresourcesclass list