Monday, March 5, 2018
Janelle Estes, Usertesting.com
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 usertesting.com.
Before next week, your team should discuss what type of test you want to do with an audience via Usertesting.com. Consider one of the following possible scenarios:
Online prototype of your app or some part of it - Invision or g-doc OK (proto.io not supported)
Alternative / competitive site you want to learn from
Questions for which you want objective feedback.
By Monday, March 5 at 10:00am:
Post a brief test plan (g-doc preferred) to the Assignment Master in the March 5 - User Testing tab. 1-2 paragraphs citing the type of test you will do, including desired learnings.
One team member must complete this questionnaire per team for usertesting.com to ensure there are testers at the ready for your live test.
At least one team member per team must register for usertesting.com. Access codes to use the app will be provided in our class session.
Why You Only Need to Test with 5 Users, Jakob Nielsen
User testing v. usability testing: the recurring mix-up, Lindsay Burke, Fresh Tilled Soil
(for fun) Why You Should Test Your Mobile App With Drunk People, Fast Company