User Testing Script Template
Use this guide to run better usability testing sessions.
Project Doc
Add a link to the project doc
Testing Doc
Add a link to the testing doc
Prototype
Add a link to the prototype
Meeting
Add a link to the meeting id

Preparation

Ensure that the set up is correct and that we are ready to perform user testing. Make sure to do the following:

  • Do we need them to sign an NDA? If so get this done before the session.
  • Do a dry run with the interview room and observation room.
  • Print this guide.
  • Turn on “Do Not Disturb” or mute notifications.
  • Turn off “power save”/sleep mode,
  • Clear your desktop. (Pretend like you’re organised!)
  • Auto quiet new attendees (So observers don’t disrupt).
  • Turn off “chime for attendees joining/leaving.”

Why are we’re performing user testing

Add in the high level reason for why we’re performing the user testing. Example:
“The goal of this usability testing is to put our prototype to the test. We want to answer our sprint questions and validate or invalidate our assumptions with real users. From this user testing, we will have gathered insights from users and validated our ideas.”

We’ve got a mix of sprint questions and prototype questions that we need users to answer. They are the following:

Sprint Questions
  1. Add your question here
  1. Add your question here
  1. Add your question here

Prototype Questions
  1. Add your question here
  1. Add your question here
  1. Add your question here
  1. Add your question here
  1. Add your question here
  1. Add your question here

A few reminders

Remember that we’ve got to be on top of our game so that we run a good user testing session. So make sure to do the following:

  • Be courteous and approachable. A good host should smile and make eye contact. But don’t be weird. We like weird, but sometimes people don’t like weird.
  • Start with a little small talk so that we can build some rapport. Ask them how they’re day is going, how often do they shop etc. etc.
  • Silence is awkward, but that doesn’t mean we should fill it with conversation. Let them do the talking, we’re here to listen, so enjoy the awkward silence.
  • Make sure to ask them “what are you thinking?” and don’t just assume. Make sure to clarify anything they’re saying and ask why.
  • Don’t get offended if they tell you something is shit. And don't blush if they tell you it is great.
  • Don’t ask leading questions, it will ruin the user testing, and we’ll be just wasting everyone’s time and effort.
  • Don’t show users how to interact with the prototype; let them do it. If they fail, that is brilliant, and if they succeed, that is great too.
  • Remember to tell them that we’re not testing them but the product.
  • Keep the questions open - who, what, why, when, and how are the real good ones.
  • Make sure to thank them for their time so that they know we appreciate their time.