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?

  • Casing/aesthetic, show the product via sketch/CAD
  • Angling of panels, show the panels' ability to angle themselves towards the Sun.
  • Foldable Design, show their ability to fold up into the battery casing below
  • App User Interface, show how the audience could control the panels by a sketch of the app.

What will you ask them to do?

What will you ask users to do with your prototypes?

  • Interact with the app
  • Comprehend the fundamental design aspects present in the sketch and CAD.
  • Ask them to view the statistics page (in app)

What will you observe?

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

  • Ease of accessibility of UI in the app - larger navigation for the main features like settings, stats, etc
  • Seeing how well the presentation and images/sketches are organized. (How easily they can navigate them) - Needs some revision, include updated app designs. Include details on control scheme
  • If they look for features/controls/aspects that aren't there - how full the battery is, efficiency throughout the day, app comprehension
  • Comprehensibility of connection system - note 4 (Added for Monday's feedback) (7/12/21

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?

  • What do you think about the appearance of the product?
  • Do you think this is a realistic addition to your house?
  • What aspect overall stood out to you the most?
  • What features to add to the app?
  • What connections to other apps (i.e weather app) would be most useful?
  • Ask about their opinion on a movable/portable version of the product.