Have a clear hypothesis for each test
Each test should have a clear hypothesis on what you think the user problem is and how you’re going to confirm or debunk it.
(I have specific examples of how I have done this in the past, it would be good to include those here eventually.)
Graph:
- 122.08.07 PM User Testing - Have a clear hypothesis for each test to 125.010 Books - Inspired - Marty Cagan
- 122.08.07 PM User Testing - Have a clear hypothesis for each test to 122.01.09 PM Skillset - Thinking qualitatively and quantitatively
- 122.08.07 PM User Testing - Have a clear hypothesis for each test to 122.02.03 PM Why - Successful products require iterations
- 122.08.07 PM User Testing - Have a clear hypothesis for each test to 122.03.09 PM Responsibilities - Share learnings openly and often
- 122.08.07 PM User Testing - Have a clear hypothesis for each test to 122.07.06 PM Discovery Process - PPSS - Universal questions during product discovery
- 122.08 PM User Testing - User testing to 122.08.07 PM User Testing - Have a clear hypothesis for each test
- 128.001 Management - Communication is the number one job to 122.08.07 PM User Testing - Have a clear hypothesis for each test
- 128.005 Management - KPIs are the best way to have clarity around impact to 122.08.07 PM User Testing - Have a clear hypothesis for each test