User Testing
Objective
Gain insights on how users interact and their satisfaction with the prototype.
Workshop
Tasks:
- Prior to the user arriving:
- Allow time to prepare the test environment i.e. prototype setup
- Designate who will facilitate and who will be the note-taker
- Facilitator provides instructions to the user
- Note-taker scribes insights during the user test
- Facilitator welcomes the user, explains in brief the purpose of the user test and answers any questions the user may have
- Explain importance of user to think aloud during the user test
- Remind users that it is the prototype being tested and not them as an individual
- Avoid leading phrases and/or questions throughout
- Set expectations that the prototype may not contain all the functionality/screens the product will ultimately have
- Brief periods of silence from the user is acceptable - recognise the difference between “time to think” and wasting time
- Facilitator reads the test scenario aloud prior and provide user with a copy
- User asked to begin working through the test scenario
- Note-taker scribes user behaviours, comments, error and completion rates for the test scenario
- User test will finish when user completes the test scenario or the allotted time for the test scenario is over
- Facilitator thanks the user for their time and asks if they would be interested in participating in future user tests
- Post user test the facilitator and note-taker spend 15 minutes to debrief and capture insights on post-it notes
- Use one post-it note per insight
- Insights will be shared with wider group during user synthesis
Recommendations
Guideline | |
---|---|
Co-located | Preferred |
Time Allocation | 1 hour per user test |
Pre-req | N/A |