USER
TESTING
— Task Testing —
Task your user to do an action in the application, tell them to talk out-loud, then watch and observe.
Do not help them, unless they are really really stuck!!!
PROJECT
HOW
THE
Lean UX is all about testing all the time at every stage of your design.
You don't know the impact of your design decision unless you test it.
Testing is how you will know your design works or not.
Think like a scientist and decide like a lawyer.
If your not user testing, your accumulating risks every time you make a design decision.
All the time and as much as possible.
In the industry, it's best to test once a week or every other week. Always be testing (ABT) YOUR DESIGN DOES NOT NEED TO BE PERFECT or complete at all, to test it. Don't wait until it's too late.
Do concept level testing with paper prototypes, tons of testing during wire-frame level and in the visual stage too.
If you add a bunch of new screens or change existing interactions, then you should test and Iterate.
WHY
WHEN
THE
THE
1st
2nd
3rd
What are the scenarios you're going to task people to do in
your application?
Write a User-testing script that has a set of tasks and a series of questions that relate to each task(s), screens and content that you're showing. The goal is to have the user talk out-loud and the questions are just a safety net for you to ask if needed. Most of the time if you have the user talk out loud they'll answer your questions.
• Enter a budget of $4,000 and find a travel trip to Tokyo.
• Engage the chat group called "plant help" and send the group a message.
—This one would require some context
• Select the Gucci pants and engage in the "smart size" feature.
Task:
Enter a budget of $4,000 and find a travel trip to Tokyo?
Q. Talk out loud, tell me what everything on this screen means to you.
Q. What would you expect to see on the Tokyo trip details page?
Q. Is there anything missing on thy Tokyo trip details page that you would like to see?
Q. How would you share this trip with someone?
Task:
Engage the chat group called "plant help" and send the group a message.
Q. Talk out loud, tell me what everything on this screen means to you.
Q. How do you know how many people are in this group chat?
Q. How do you know if there are group members who are on the app right now?
Q. Was there anything confusing about this over-all task?
Q. What in the task did you find most valuable or easy-to-use?
examples
examples
USER
TESTING
SCRIPT
THE
TESTING
CONDUCTOR
TEST CANDIDATE
NOTE TAKER
ONSITE
RECORDING
TOOLS TO RECORD A DESKTOP SCREEN
USE ZOOM
DESKTOP
NOTE TAKER
CONDUCTOR
TEST CANDIDATE
PHONE
TOOLS TO RECORD A MOBILE SCREEN
Zoom can record on phone
You can also set up another Phone
to record the user and them interacting with the app
CONDUCTOR
TEST CANDIDATE
NOTE TAKER
REMOTE
RECORDING
REMOTE SCREEN SHARING STEPS:
SEND LINK TO PROTOTYPE RIGHT IN THE BEGINNING OF THE SESSION.
HAVE THEM PRESS THE ZOOM
SCREEN SHARING.
HAVE THEM READ THE TASK ON SCREEN
AND START THE TASK.
HAVE THEM TALK OUT LOUD.
USE ZOOM FOR RECORDING
TEST
CANDIDATE
SCREEN SHARE - DESKTOP
NOTE TAKER
CONDUCTOR
TESTING ON MOBILE REMOTELY
IT'S NOT 100% CONCLUSIVE AND IS
ONLY DONE TO VALIDATE CONTENT
ORDER NOT USABILITY.
SCREEN SHARE - MOBILE
CONDUCTOR
NOTE TAKER
DISCUSSION
NOTES
AND
OBSERVATION
AND
OBSERVATION
NOTE TAKER
CAN SET UP
A RECORDING
STATION
1. ADD THE SCREENS YOU'RE SHOWING TO THE MIRO BOARD
Not every interaction but any new screens that you're showing...
Add topics like that may not related to the screens you're showing. Mostly you'll find these three work:
• General Pains
• General Request
• Wish list
2. CREATING THE USER BUCKETS
Remember to capture observation as well.
Example: User tried to tap the icon first before going to the action button.
LISTEN TO YOUR RECORDING,
SCRUB BACK AND FORTH AND WRITE IMPORTANT INSIGHTS THAT RELATE TO THE USABILITY & CONTENT YOU'RE TESTING.
PLACE EACH INSIGHT THAT RELATES TO THE TASK UNDERNEATH THE SPECIFIC SCREEN
THAT IS RELEVANT FOR THAT INSIGHT.
YOU DON'T HAVE TO WAIT FOR AT LEAST 3 INTERVIEWS TO
START PUTTING INSIGHTS UNDER THE SCREENS. YOU CAN
START DOING THAT AT THE FIRST INTERVIEW
WHEN DO YOU STOP USER-TESTING & START ITERATING?
WHAT IS A GOOD NUMBER OF PEOPLE TO TEST WITH TO GET
THE "JUST ENOUGH TESTING" IN?
WHAT DO YOU DO IF YOUR FIRST INTERVIEW FINDS A LOT OF THINGS
ARE CONFUSING OR DOESN'T EASILY COMPLETE THE TASK?