Usability Testing Protocol
- 1 Krug's “Lost our lease testing”
- 2 Recruitment Text
- 2.1 Part 1: Introduction Text
- 2.2 Part 2: Looking at the Device and Unaided Exploration (i.e., see what the user can do by themselves)
- 2.3 Part 3: Goal-directed tests
- 2.4 Part 4: Trunk test
- 2.5 Part 5: In the dark test
- 2.6 Part 6: Dual task
- 2.7 Part 7: Destructive Testing
- 2.8 Part 8: Open-ended suggestion period
Krug's “Lost our lease testing”
- Number of people: 3-4; at least one morning a week
- Recruitment: Grab anybody; don't do anything that will reduce the # of tests
- Where to test: anywhere (no disturbances)
- Planning: no planning or schedule needed
- Preparation: decide what you are going to show
- What/When to test: continually through the process
- Cost: $50-100/user (I think we can safely do $10)
- Summary: 3-4 tests in the morning; debrief over lunch the same day
- Triage: review problems and decide what needs to be fixed
- Ignore kayak problems (fix themselves almost immediately)
- Subtract, don't add
- Fix head slappers: obvious problems with easy solutions
- Fix anything with little to no effort that are highly visible
- Problem solving: fix problems
- Triage: review problems and decide what needs to be fixed
- Reports: find and note problems, don't worry about the write-up
- Use a screen recorder for clicks/audio like camtasia
We need to have a few people look at our Web site and give us some feedback. It’s very easy, and would take about forty-five minutes to an hour. And you’ll be paid $___ for your time.
Part 1: Introduction Text
Hi, X. My name is Y, and I'm going to be walking you through this session.
You probably already know, but let me explain why we've asked you to come here today. We're testing an electricity display that we're working on so we can see what it's like for actual people to use it.
I want to make it clear right away that we're testing the display, not you. You can't do anything wrong here. In fact, this is probably the one place today where you don't have to worry about making mistakes.
We want to hear exactly what you think, so please don't worry that you're going to hurt our feelings. We want to improve it, so we need to know honestly what you think.
As we go along, I'm going to ask you to think out loud to tell me what's going through your mind. This will help us.
If you have questions, just ask. I may not be able to answer them right away, since we're interested in how people do when they don't have someone sitting next to them, but I will try to answer any questions you still have when we're done.
We have a lot to do, and I'm going to try to keep us moving, but we'll try to make sure that it's fun, too.
Before we look at the device, I'd like to ask you just a few quick questions. First, what's your occupation?
Roughly what do you know about your electricity use?
Do you know your bill, kWh?
How do you feel about learning about your electricity use?
Part 2: Looking at the Device and Unaided Exploration (i.e., see what the user can do by themselves)
First, I'm just going to ask you to look at this device and tell me what you think it is, what strikes you about it, and what you think you would do first.
For now, don't actually do anything. Just tell me what you would do.
And again, as much as possible, it will help me if you can try to think out loud so we know what you're thinking about.
Let them interact and think out loud
--When done: If you had to take a guess, what do you think it is about?
Ok. Now, if you were at home, what would you do first?
Notes (just let them explore, but take notes on these items):
- How much can the person do with no instruction; just “use the device”?
- Without any instruction, what do they think the purpose of the device is, the features are, the buttons do?
- Can the person tell the state of the device just by looking at it?
- Can the person tell the action alternatives just by looking at the device?
- What is the mental model of the participant? Does this match the designer's model and the system image?
- What are the errors people make? How do we fix them? Are they detectable, minimal consequences, and reversible?
- What are the mappings between controls and functions?
- What is the gulf of execution? What is the difference between intentions and allowable actions?
- What is the gulf of evaluation? What is the amount of effort required to interpret the physical state of the system and determine whether intentions have been met?
- Can the person determine the functions of the device unaided?
- Can the person tell what actions are possible unaided?
- Can the person determine the mapping between intentions and physical movement unaided?
- Can the person perform intended actions unaided?
- Can the person tell if the system is in the desired state unaided?
- Can the person determine mapping from system state to interpretation unaided?
- Can the person tell what state the system is in unaided?
- Can the person determine the relationships between actions and results?
- Can the person determine the relationship between the controls and their effects?
- Can the person determine the relationship between the system state and what is visible?
- Can we adjust the arrangement so as to reduce the number of labels while improving c comprehension (i.e., can we find natural mappings)?
- Can people muddle through without reading the instructions or help from the experimenter?
Part 3: Goal-directed tests
- Can you think of something you'd like to learn from the device? If you wanted to learn that, what would you do?
- Can you access the calendar?
- Can you show a bar graph of monthly consumption?
- What is the monthly bill?
- How much electricity is being used right now?
- What is the current price of electricity?
- Can you switch from calendar to bar graphs and back?
- How many kWh were used yesterday?
- How many kWh are projected to be used tomorrow, next week, month...
- Can you switch from bar graphs to pictures?
- Can you switch from pictures to bar graphs?
- Can you switch from calendar to pictures?
- Can you switch from pictures to calendar?
- Can you switch from bar graphs to calendar?
- Can you switch from calendar to bar graphs
Part 4: Trunk test
Have participant close eyes and take them to randomly selected pages (actually use a random number generator for this). Can they answer the following questions?
- What is this?
- What page am I on? (page name)
- What are the major sections of this site? (sections)
- What are my options at this level? (local navigation)
- Where am I in the scheme of things? (“you are here indicator”)
- How can I get back to pictures and the default page?
Part 5: In the dark test
Turn off the lights. Secretly give them the control upside-down. Can they still use the device?
Part 6: Dual task
Can participants dual task (e.g., n-back) and also use the IHD?
Part 7: Destructive Testing
Can they break it? Not physically.
Part 8: Open-ended suggestion period
Just discuss it open-ended with them. Take suggestions.