...
There are five sections to this usability interview:
| Table of Contents |
|---|
...
1. Friendly Welcome
The person will be a bit nervous. Make them comfortable.
...
Do you have any questions before we begin?
...
2. Context Questions
Understand more about the user and their background. The goal here is several fold. First, it is to help gather backgrounder information about the user and their behaviours. (These are Who? Where? When ? What? Why? How? type questions). Second, it is to help put them more at rest, by being small talk. Spend a few minutes here, based on the time you have.
...
To begin, please just take a look at [this screen]. What are your first impressions of what this is?
3. Tasks
Tasks are specific things the user is asked to accomplish. Watching how a user is able to accomplish the tasks provides valuable feedback.
...
For instance, the task may be for the user to return to the overview of the patient chart. Instead of using the application's navigation to get there, they may use the back button on the browser. This is ok, let them do so. After the user has completed the task using their first method. Have the user return to the page of interest, and ask, "Is there another way you would do __________"
Don't say the word on screen
The task question should not include the word written on the screen.
For instance:
Bad: "Click the Help button"
Good: "What would you do if you needed assistance?"
Bad: Register a new patient. (if the screen has a button labeled "Register new patient")
Good: How would you create a new patient record?
...
4. Debrief
The debrief provides an opportunity to comment more broadly on the prototype and tasks they have performed.
...
What types of people does each of these versions seem to be designed for?
Don't Lead
Questions should be objective, and now influence how the user will respond.
Michael Margolis gives examples of leading questions:
Bad: "Is this good?
Bad: You program your home thermostat to save energy, right?
Good: Do you program your home thermostat?
Bad: Would you rather use the old version or this new, improved design?
Bad: Is this version better?
Good: How would you compare these two?
Good: What are the pros and cons of these prototypes?
...
5. Cool Down & End
Summarize the session briefly for the user.
...
I really appreciate your taking the time to come in, and answering all of my questions.
Thank you
-
...
Resources
See the OpenMRS Wiki Usability Testing Links & Resources page for all resources.
This script draws upon, and directly mirrors in areas, the work of Michael Margolis in his Google Venture's Usability Testing work