Usability testing a very important aspect of UX design where you're essentially testing your product to see how useful it is in the hands of the user.
- We are asking you to try using a website we're working on so we can see weather it works as intended. The session takes approximately 20 minutes.
- The first thing i want to make clear right away is that we're testing the sight not you so there is no right or wrong.
- As you use the site I am gonna ask you as much as possible to try to think out loud
- What you're looking at
- What you're trying to do
- What you're thinking
- Don't worry to hurt our feelings, we're doing this to improve the sight so we need your honest reactions.
- If you have any questions along the way please ask them, I may not be able to answer them right away since we're interesting in how people do when they don't have someone sitting next to them to help, but if you still have question i might be able to help.
- With you're permission we're gonna record what happens on the screen and our conversation.
- The recording is only going to be used to help us figure out how we're going to improve this sight and wont be seen by anyone but me.
Are you ready?
Are you currently looking for work?
Things a tharapist would say
While the participant is doing the tasks, to maintain your neutrality you’re going to be saying the same few things over and over, which turn out to be the same kind of non-directive things a therapist typically says to a patient.
Here’s a handy chart of “permissible” phrases.
When this happens Say this:
You’re not absolutely sure you know what the participant is thinking.
“What are you thinking?”
“What are you looking at?”
“What are you doing now?”
Something happens that seems to surprise them. For instance, they click on a link and say “Oh” or “Hmmm” when the new page appears.
“Is that what you expected to happen?”
The participant is trying to get you to givehim a clue. (“Should I use the _______?”)
“What would you do if you were at home?”(Wait for answer.)
“Then why don’t you go ahead and try that?”
“What would you do if I wasn’t here?”
“I’d like you to do whatever you’d normally do.”
The participant makes a comment, and you’re not sure what triggered it.
“Was there something in particular that made you think that?”
The participant suggests concern that he’s not giving you what you need.
“No, this is very helpful.”
“This is exactly what we need.”
The participant asks you to explain how something works or is supposed to work (e.g., “Do these support requests get answered overnight?”).
“What do you think?”
“How do you think it would work?”
“I can’t answer that right now, because we need to know what you would do when you don’t have somebody around to answer questions for you. But if you still want to know when we’re done, I’ll be glad to answer it then.”
The participant seems to have wandered away from the task.
“What are you trying to do now?”
Acknowledgment tokens. You can say things like “uh huh,” “OK,” and “mm hmm” as often as you think necessary. These signal that you’re taking in what the participant is saying and you’d like them to continue along the same lines. Note that they’re meant to indicate that you understand what the participant is saying, not that you necessarily agree with it. It’s “OK.” Not “OK!!!”
Paraphrasing. Sometimes it helps to give a little summary of what the participant just said (“So you’re saying that the boxes on the bottom are hard to read?”) to make sure that you’ve heard and understood correctly.
Clarifying for observers. If the user makes a vague reference to something on the screen, you may want to do a little bit of narration to make it easier for the observers to follow the action. For instance, when the user says “I love this,” you can say, “The list over here on the right?” (Since you’re sitting next to the participant, you sometimes have a better sense of what they’re looking at.)