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 service or app 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?

  • Signing up — Sharing the signing up page from the prototype to show the private information required
  • Exploring and navigating — Sharing the navigation page from the prototype
  • Listing highlights and filters — Showcase different filters and identify which are preferred (filter based on price, location, space...)
  • Payment methods — Understand the tester's payment preferences
  • Sustainability thinking — Understand how likely it is for the testers to host spaces in their households

What will you ask them to do?

What will you ask users to do with your prototypes?

  • What are the filters that you find necessary to narrow down your decision?
  • What descriptions are necessary to convince the customers to book the opportunity?
  • How do customers feel about having over 50 options in their desired area (are they overwhelmed by having too many choices)?
  • Are customers willing to provide private information?

What will you observe?

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

  • Observing their first reaction to the prototype
  • Is the prototype clear and easy to understand?
  • The way they interact with the different features of the product.

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?

  • Do you feel like something substantially is missing to convince you to use and pay for our service?
  • How often would you use our service on average? Once per week/month/year/...?
  • For what would you use our service the most? For work, family lunches, accessing lake to relax, partying, ...
  • Would you mind having built-in advertisements or featured listings?
  • Would you prefer a flat rate fee or a percentage fee?