USABILITY TESTING
Testing Tips
OPENING LINE
When a users starts or sees a new screen say:
"Walk me through this screen and tell me what everything means to you"
TEST THE EXPECTATION
When user goes to click/tap on anything, before they do ask them
"Is this clear? What do you think that will do for you?
After you get their expectation say "okay great, go ahead and proceed"
VERBIAGE
If your users keeps referring to something in the application that is named differently in the UI it's a good idea to stop at somepoint and change the verbiage to what they describe it as. Example:
"Oh that button that says "slow-mo", I'm guessing that will "slow down" the video"
SMILE & HAVE FUN
Even if the ships on fire and nothing is going well. Just be cool, remind the user that their doing great, tell them this is exactly the feedback we're looking for, and continue the show—essentially detach from your designs and embrace the learnings!
BODY LANGUAGE
This isn't a one size fits all but some cues to look for:
Lean in = might be excited or may like
Lean back = might be confused or thinking about something
Arms folded = showing signs of being uncomfortable or not open to what's going on
PLAY AROUND WITH CONTENT
Show missing content to get the user to describe what they were expected to see
Say "oh the designer forgot to put content in this section, hum…what would you want to see in this section as it relates to "domain/application context" then after you got their expectations, show them what the section looks like with content and say "oh there it is" and have them give feedback on order and importance—either way you will have some expectation of what they wanted to see. Example Below:
MAKING MISTAKES
It's okay to make mistakes or immediately start seeing problems in your prototype. Just don't run off right afterwards and make changes after only one data point—keep testing and get validation first.
CLARIFY VAGUE RESPONSES
User says "oh that's nice or I really like that"
Follow up and say "just so I understand, can you elaborate a bit on why you like that"
DIVE DEEPER ON POINTS OF CONFUSION
User says "hum, this is kinda confusing" and they don't continue to explain their point.
Ask "just so I understand, what is confusing about that or what triggered you to be a
bit confused?"
USER ASK "WHAT DOES THIS DO?"
I get this a lot. Anytime a user asked a question regarding what something is, the intentions,
how it works or what it does. Take note on this (as it's not performing well or matching the user's mental model, and then tell them "I'll tell you, but first take a guess at what you think that does" or "what you think that is?"
ALLOW FOR AKWARD SILENCE
Give space for people to think —if they continue without saying anything, then you may ask:
"Wait, was there something you saw that you were thinking about?"
SET REMINDERS
• Remind them that their doing great and smile
• Remind them to "talk out loud" if this is that type of session
• Remind them that they can point out anything confusing (if only talking joys)
• Remind them of time "we have just a couple more things to get your feedback on"
• At good stopping points,— ask the note taker if they have any questions before proceeding