![]() |
IDIA 750.185 humans, computers, and cognition | ||||
|
|
|
assignment two: usability testing and test reportEach 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 reportPresumably, 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
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
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
usability report checklist
assignment one: contextual interviewsEach group member should participate in three or four contextual interviews. Contextual interviews should be conducted in pairs. Structure of the contextual interviewintroduction (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. transitionExplain 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 observeQuestions for researching user goals and tasks
Questions for researching user tasks
Reporting your resultsBased on your interviews, your team will create user profiles, task lists, a workflow, and task flows.
|
|
| ©2002 Kathryn Summers | overview calendar assignments resources class list |