User Testing

Monday, February 25, 2019
Hawes 203

Guests: Janelle Estes,



No product can be tested too often! Last session, we focused specifically on the onboarding process to think about longtime stickiness of your products. Now, let’s zoom out a bit and think more broadly about testing other assumptions and theories about use of your application. We will be doing LIVE testing in class using testers from

Before next session, your team should discuss what type of test you want to do with an audience via Consider testing one of the following possible scenarios:

  1. Online prototype of your app or some part of it - Invision or g-doc OK ( not supported)

  2. Alternative / competitive site you want to learn from

  3. Questions for which you want objective feedback.

By Monday, Feb 25 at 10:00am:

  1. At least one team member per team must register for using this link. Access codes to use the app will be provided in our class session.

  2. Post a brief test approach (g-doc preferred) to the Assignment Master in the February 25 - User Testing tab. Include:

    1. 1-2 paragraphs citing the type of test you will do in our session, including desired learnings.

    2. A short list of questions/criteria defining *who* you’d like to gather feedback from and how you will recruit for them on the UserTesting panel (a.k.a. “Screening criteria”)l. In the UserTesting app, you will be able to filter by: age, gender, household income, parental status, employment status, company size, industry, job role, job level, countries (location), web expertise, OS, web browsers, and social networks. If your target audience has requirements outside of the provided filters, you need to formulate additional screener questions. Read this blog post for screener question best practices.

Required Reading

Recommended Reading (books)

Session Prep

Come to class with…

  • Laptops - Each team should have at least one laptop to conduct their test.

  • Your test plan for this session (see above)

Two teams will be selected for critiques in this session. Selected teams will be notified before Friday, Feb 22.