After completing 5 think aloud tests and participating in an in-class critique, we received similar feedback regarding the labeling and uses of our features.
Labeling
When interacting with our application, at this point called MyMenu instead of MyMeals, users were unclear about some of the labeling and functions of the different features. First, participants did not know that selecting recipes to add to MyMenu was for planning an entire week of meals, as they felt the name gave it the connotation of a dinner party or multiple-course meal. This was exacerbated by the match feature, whose functionality was also not immediately obvious to users. Because of this, we renamed MyMenu to MyMeals.
Along with the labeling of the features, users also noted that some of the on-screen text was not easily noticeable, as with the store comparison tool. Participants did not even recognize that we had included the item availability and price points for the items at each store, as the font was so small. We ultimately redesign the layout of the stores and their details. Participants also expressed that they would want the option sort store based on distance, price, or item availability, depending on their needs at the time. We did implement this feature in our high-fidelity prototype.
Additional Suggestions
Participants noted that having a weekly planner or having the ability to synch to other calendar would be useful to emphasize the planning aspect. They also suggested allowing users to find matches for specific ingredients that they already already have, instead of an entire recipe. To avoid feature creeping, we prioritized the features that we had already designed and refine them further based on feedback. Depending on user feedback, we will consider updated these features in the future.
Value Proposition = Confirmed
When asked whether the store comparison tool would be worthwhile to refine, our participants answer "Yes, especially for students on a budget and busy schedule." Although the features and their functions were not immediately clear to participants, the majority expressed interest once they were explained and could visualize it working with their current habits.
After completing our final high-fidelity prototype, we used Maze to conduct asynchronous, unmoderated usability testing with 15 participants.
The results, which are detailed below, provided very positive feedback.
There were some discoverability issues with the Shopping List and Stores Comparison features. These were resolved by (1) adding a tab to the bottom navigation bar and (2) fixing the position of the "View Shopping List" button on the MyMeals page, which you can see in the image to the right.
Participants had various responses to "What feature stood out to you the most?" with the social media upload and store comparison features getting the most attention.
Uploading Recipes
Shopping List