Download Usability Testing Report - Soma Ray

More documents

Recommendations

Info

For example, with reference to the Create meal plan image, our participants found it difficult to locate the ‘Suggest More Recipes’ button as it is not close to the recipe list. We feel this violates Gestalt’s principles of proximity (Johnson, Jeff) • Most pages look and feel similar to one another and thus add to the confusion our participants faced while navigating a task. Not only did the system not provide adequate navigational information (refer to Finding 1) but the similarity of pages design also added to lack of visual cues. • Other issues include the search box not having a clickable option, the location of the ‘Add sides’ panel and location of recipe filters. Recommendations We suggest GastroMighty follow human behavioral fundamentals applicable to human computer interaction for guidelines on interface, look, and feel design. A few suggestions we have are (this is by no means an exhaustive list): • Action buttons, links, or icons related to a particular task flow should be in close proximity. For example ‘Suggest more Recipes’ should be closer to the list of recipes displayed. • Use highlight colors (in GastroMighty’s case Blue, Red, and Green) for actions one would consider as important and logical. For example, highlight ‘Add to meal plan’ rather than ‘Add comments’ in a recipe page. Also reconsider color palate to ensure adherence to 508 compliance. • Ensure the sides workflow is visually better connected to adding main dishes as they form part of the main meal planning activity. Also ensure the recipe filters are better highlighted as currently they blend with the grey color theme and don’t command attention. We also suggest GastroMighty incorporate some distinct visual cues to help users keep a track of their work process on the website. For example distinguishing the look and feel of home page and create meal plan from finished meal plan and previous meal plans would go a long way in optimizing a user’s experience. 6. Ratings and comments should be optimized and system learning capabilities should be conveyed. From our usability tests, we found that there was lack of awareness among the participants of how certain aspects of the system actually work. Most of these issues were about the machine learning algorithms, commenting, and rating features on the website. For example, the website does not communicate its machine learning capabilities. Liking or disliking a recipe affects what recipe suggestions the system makes for the user. However, none of our participants could infer this relationship between liking/disliking a recipe and recipe suggestions. So, they did not realize that “disliking” a recipe would block it from appearing in future meal planning suggestions. The system does not clearly communicate that when a user likes a recipe, Gastromighty uses this data to suggest similar recipes in the future and gradually learns from these inputs. We also observed that participants could not understand how the rating and commenting feature works. Most of them were unsure if the comments were only visible to them or if they were publicly Usability Testing Report 12
available. Some of them asked if their comments could be printed while printing the recipe. We believe that since there were no other comments on the recipe page during testing, the participants expected comments to work like personal notes for the recipes. One of our participants indicated that they would like to have personal notes for each recipe. During the usability tests, all participants expressed confusion about the rating feature. GastroMighty uses terms like “vote up” and “vote down” to add recipes to favorites or block them from appearing in the suggested recipes section. A user’s favourite recipes are visible to their friends. Participants expected “vote up” and “vote down” feature to work like facebook where they can see that how many people have liked this recipe. One participant also suggested that it would help if the recipes could be sorted according to these ratings. Recommendations We feel that GastroMighty could benefit from informing the users about its learning capabilities. This could be demonstrated through a short guided tour, which tells them how liking/disliking a recipe affects future recommendations. Alternatively, whenever the user rates a recipe, a notification could appear informing them that GastroMighty will remember their choice when suggesting recipes next time. We also suggest that Gastromighty should separate the rating feature from the favoriting feature in the website. Using a “star” icon to favorite a recipe and the thumbs-up/ thumbs-down icon to rate a recipe would help in reducing the confusion in the user’s mind. Additionally, marking the number of likes or dislikes for a recipe would help them understand that rating is a publicly visible feature whereas “star” icon (similar to Gmail) is for their personal use to mark a recipe as favorite. For the commenting feature, we feel that since Gastromighty does not yet have many comments on its recipe pages, information boxes like “0 users have commented on this recipe. Be the first to comment!” could provide a clear indication to the users that their comments are visible to the public. Once they have more comments, it will be more obvious to the users that their comments are public. Usability Testing Report 13
Page 1 and 2: SI 622: Evaluation of System and Se
Page 3 and 4: Executive Summary In this study, we
Page 5 and 6: Methods The goal of our usability t
Page 7 and 8: Recommendations We recommend that G
Page 9 and 10: select options in this field while
Page 11: 5. Interface design should remain m
Page 15 and 16: Conclusion In this study, our team
Page 17 and 18: Appendix A: Consent Form Consent Fo
Page 19 and 20: Task 3 A good friend of yours is vi
Page 21 and 22: Appendix C: Post-Test Questionnaire
Page 23 and 24: Appendix E: Additional Reference Ma
Page 25: Appendix G: User Data Logs and Post

Download Usability Testing Report - Soma Ray

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?