Before you start your testing, you need to prepare for it. This means not only creating natural settings, but also putting your mind in the right place.
Keep in mind what goals you set for your prototype and which aspects of it to test. If your tester doesn’t understand how the prototype works or doesn’t find it useful – don’t try to persuade them. Try to understand what you could change to make the product useful and more intuitive.
Do not test the tester – test your solution.
Before testing, explain what your project is about, but give as much information, as would be freely available after you launch your solution. Don’t explain all the details how the process works – see how the tester can (or can’t) figure out the usability.
Watch how your tester interacts with the product and make notes when you have any insights. Clarify whether your observations are right after the test.
After the test, ask the tester about their honest feedback, thoughts and suggestions. Do not expect only praise for how amazing the solution is. Look for opportunities to improve and accept all constructive feedback with gratitude and appreciation. This is your chance to improve your solution – not to shine yet. The real shine comes when a mass (or target niche) market accepts and welcomes your product after the launch. And for this, you need to be critical during testing.
Based on your canvas, build and test the prototype with your selected user group.
Fill in the last box in the canvas .
What did go well? What did go wrong? What did you learn? How can you use it in your next prototype session?