5 ways to improve your prototype testing
Discussion guide scripts included.
Good prototype sessions can be immensely helpful in getting quick and easy feedback without investing too much time or money into a new feature — but badly run sessions can lead to reconfirming your own biases, and bad investments.
Below is my no-nonsense discussion guide for how to test ideas with users.
1. Set some context.
This is what you should say right after the introductions of names. I can’t stress how important it is to simply set some context for your user before you dive in.
Find the script below:
Hi, thank you so much for taking the time out of your day to speak with us. As we said in our email, we will be testing some prototypes with you. At the end of our session you will be getting an email with compensation for your time.
When we show you the prototypes, it would be most useful for us if you just think out loud about what you’re seeing and what you’re doing. We really value your candid feedback so don’t worry about hurting our feelings, we’re testing to learn how to make it better!
Also, I should note that I’m going to be asking you why a lot — I’m not trying to be annoying, I’m just trying to understand better. I should also let you know that if you ask me any of the questions about the prototype I won’t answer, not because I don’t want to, but I want to see what does and doesn’t make sense for you. At the end of our session we can leave some time for any questions you have.
Any questions about what we’ll be doing today? Let’s get started.
2. Get to know the user.
Before jumping straight into the prototypes, it’s often helpful to get some basic understanding of who you’re talking to. I find the following icebreakers helpful in kicking that off.
First off, why don’t you introduce yourself and tell us what you do.
This is kind of silly, but what is keeping you up at night these days?
Tell me about a time you… (thing you’re curious about)
If the user says something interesting that you don’t quite understand, don’t worry about moving on to the next question, but ask why!
3. Test the prototype/concept.
Now that you know a bit about your user, it’s time to get some feedback! Have your prototype or concepts ready to share and use the script below to kick off the next section.
So now I’m going to show you some of the prototypes I have. Again I’d love to hear you thinking out loud, things you’re confused about, or things you’re curious about. *embrace the uncomfortable silence that may come*
Have a look around and think out loud as much as possible.
If you have a specific task you want them to do, this is the time to explain it.
We’d love if you would use this prototype and try do do X (task). We’d like you to first do A, then B, then C.
Testing Do’s and Don’ts
DO ask clarifying questions:
- “How would you describe what you’re looking at?”
- “Why did you just do X?”
- “What are you looking at?”
- “Tell us what you’re thinking.”
- “I saw you do X, tell me more about why you did that.”
- “What do you think that means?”
DON’T offer the user any scenarios, things like:
- “what would you do if…”
- “How do you feel about this if…”
- “What else would you do on this page…”
- “Is this something you would buy, use, like, etc…”
All of these are leading questions that lead your user to focus on something that they may not have naturally focused on. The point of testing is to see what the user gravitates toward naturally, and what they ignore naturally.
4. Say goodbye.
Just as you introduced yourself and the context of the meeting, it’s just as important to close the meeting and leave some time for questions.
Find the script below:
Thank you again for your time today, it’s been super helpful for us. At this time I’m happy to answer any questions you had, is there something you wanted clarity on?
I also wanted to take this time to ask anyone on the phone or in the room if they had any last minute questions?
Thanks again, have a great rest of your day.
5. Bonus Tips and Tricks
- If the user asks you a question about the prototype, flip the question and ask them what they think the answer is.
- You’re not testing the user, you’re testing the design. Keep reinforcing that with your user.
- There are no wrong answers.
- Embrace the silence!
- Remind the user that all feedback is helpful.
- If they give useful feedback, say ‘that was really helpful’ to indicate that they’re doing a good job being a participant.
- Never tell your user that what they did was wrong in the flow.
Let me know if you have any other user testing tips below!
-G
