✏️

Our Testing Protocol / Script for the Testing Sessions

💡

Outline your testing protocol--a description of the steps that anyone on your team can follow to gather feedback from testing. It should include the following sections. IMPORTANT - You should not explain all the features of your product or lead your users thru a demonstration of its design features. For truly useful feedback, allow your users to interact with your prototypes and discover its features. Try to be an observer, not a tour guide. Answer any questions that come up as users interact with the prototypes, but keep in mind that asking "what do think will happen?" or "how do you think that might work?" will solicit very useful information about what's going on in the user's mind. Don't try to sell or pitch your product to your users. You're not trying to convince them that your product is good. Rather, you're hoping to learn from observing and hearing how they feel about your product. Then, after users have had a chance to explore your prototypes, you can ask about any specific issues that you'd like them to share their feedback on.

What will you share with your users to interact with?

For each feature that you're testing, how will you use your prototypes?

In addition to sharing images of our design with our testers, we will also provide a basic overview of all the various features we have developed for the project, sort of like a first introduction to the project when it first comes onto the market. A good degree of explaining is necessary, as one can't exactly interact with features of our product while it's in sketch form.

What will you ask them to do?

What will you ask users to do with your prototypes?

  • Imagine how this product would be useful in their daily lives
  • Provide feedback on whether or not our product would induce a change of behavior that is too sudden or unwelcome
  • Give general observations and opinions on the product and what they would like to see out of it should they find it unsatisfactory.

What will you observe?

What you will be observing and noting as you watch users interact with your prototypes?

  • Whether or not they seem to find the design of the product appealing
  • Whether or not they are receptive to the changes in behavior the product would induce.
  • What kinds of feelings and emotions they seem to be associating with the product (i.e, positive or negative reactions, hope and optimism or cynicism and pessimism, etc)

What will you ask them to share feedback on after the testing?

What questions will you ask your users after they've had a chance to interact with and explore your prototypes?

See testing plan for the general and specific questions we plan to ask our users.