Test preparation

4/18/2019

In preparation for the informal testing session that we’ll run during class on Tuesday, we have listed some questions that we want to get answered during the testing session:

• For onboarding, what language/visualization would communicate the overall process and encourage the users to engage?
• For Phase 1, does scrolling and seeing ingredient cards serve as an effective and engaging way to learn about different categories of food?
• Does scrolling allow users to select the target food easily? Is the list view more accessible or redundant? Besides scrolling, is there other ways such as random shuffle, it could be less overwhelming with more surprise.
• How many items are good for scrolling vs. seeing a list?
• How should the food card be designed to provide enough information in an intuitive way?
• After going through Phase 1, do users retain enough information?
• What is the proper way to evaluate their knowledge in order to move to the next phase?
• For Phase 2, what percentage of right vs. wrong options should there be when planning? (if it’s all correct choice, one cannot learn)
• Does a Pie chart for calorie communicate the results of the choice effectively?
• How to visualize different phases and goals?
• Visual and emotion representation — how to use colors represent emotions meantime avoid being discouraging.
• Design pattern for easy switching between different food, avoid being a laborious process.
• Think about the phrasing of phases in a way that patients would feel more engaged.
• How to quickly visual if a meal meets the requirement. (different states of the bento box? Charts next to the plate?)
• Best way to show progress meantime not discouraging if not doing well.

Methods we’re using:

• Business Origami — we want to print out some physical elements and test what are some preferred ways users may want to shuffle food.
• Use physical food card with different information to test.
• (Maybe) Desirability testing, we want to test the need of keeping a food diary, especially with the tradeoffs of taking efforts to keep track of each meal.
• Semantic differential — we want to use this to help reveal the ‘felt’ meaning, to avoid the phrasing of actions from the makers’ mindsets.
• Think-aloud: probably we use this to test user flow and see if people get stuck and confused at certain points.
• User journey maps

Left: business origami, Middle: think-aloud, Right: semantic differential

Some feedback we got from Stacie include:

• Think about different learners, we might want to revisit Dirksen’s reading about different types of learner.
• Think about other forms of the learning experience, an app requires strong motivation to download, and some people may not willing to download.
• Think about semantic differential. Maybe frame messages differently to different patients to make it more personalizable.