Some tips on how to approach testers who will facilitate the tests for both you and those who test. It will create a positive experience and those who test will feel that they are contributing to a valuable idea.
1. Be welcoming
You want those who test to feel comfortable and safe. It will help you get good and honest answers.
Take it easy, you want to start the test with a good atmosphere. Introduce yourself and your test partner and thank the tester for participating.
Explain the purpose of the test. Tell about what the need or challenge is that you are trying to find a solution for, describe the idea briefly and why you need the tester's opinions and thoughts. Try to explain with three sentences.
Be careful not to over-explain the idea or prototype and do not try to convince the tester of the value of your particular idea. You just want to test and see how the prototype is experienced.
2. Give clear and simple instructions
Now that the tester understands why, it's time to explain how it will test.
- Be clear and clear about what will happen during the test.
- Explain that they are the prototype not being tested by the tester.
- You want to hear what feels good, strange, confusing or bad about the prototype. All opinions are welcome.
Tip! Ask the tester to think aloud while working on the prototype. A bit like a sports commentator, they can describe what they are watching, what they think about what they see and why they do as they do, when they use the prototype.
3. Be ready to ask your questions
Prepare questions that will give you good answers from those you test with. The questions should be linked to what you want to learn and how to evaluate the test.
It is often a good idea to follow up on your questions with "why questions". It helps you understand the feeling or thought behind an answer or a behavior.
- The tester - "I would rather have information via the web than through a brochure."
- You - "Aha, why that?"
- The tester: "Because I want to go through it before the first meeting with the supervisor, and I can also share the info more easily with the child's father."
Remember not to over-explain the prototype. You do the test to see how the prototype is experienced by testers. If the tester does not understand your prototype and gets confused, it is a good lesson on how to adjust the prototype later.