Team 1: Usability Test Report – A Higher Common Sense

Usability Test Report

Team 1: Grace Zhangs, Alix Cui, Godsfavour Simon

1. 1. Users thought it would be confusing to be given the series of onboarding questions without having context about what they were for and how the responses would be used. We will add an extra screen initially that gives an overview of the app’s mission statement and what the questions hope to achieve in terms of fine-tuning the user experience for each use case.

Add vs save buttons in post-interaction flow (adding friends and statements)

1. 1. The buttons to add friends and add statements in the post-interaction flow vs the buttons to save those inputs were confusing to users. We will change this interface to make it more intuitive for users by adjusting the button placements and sizes.

1. One potential use case that users thought we may have missed was the case of someone who is lonely and doesn’t really have friends or wants to meet and hang out with more people. This was notably mentioned in the notification question, where a low number of notifications could either indicate someone who is extremely responsive, or someone who just has no one reaching out to them or talking to them. We will add more questions and clarification to the questions themselves.

“Data Access” wording in permissions is unclear. In addition, on the screen where we ask the user to add friends, we might want to allow for an automatic option such as syncing contacts. If the user prefers not to sync contacts, they can still manually add contacts, but we should design a more complex form for that

1. 1. Next to the data access question, we will have an info icon that links to our data privacy policy. Or, we will give an explicit link to read our privacy policy.
  2. We will implement an alert for syncing contacts when the users first get onto the screen. We will also design out a more complex form so users can have equivalent information when manually adding friends

Clarify the differences between reflections and notes. Should we merge these together in some way? How can we make the design intuitive for the user so they understand the difference between reflections and notes?

1. 1. We are going to merge reflections and notes. When going through the note-taking flow, initially the user will be able to choose from a select few templates for adding a note. One of these templates will be a reflection. This reflection template will come with predefined questions, feelings surveys, etc.

How can we better the navigation across questions in the onboarding questionnaire e.g. back and skip

1. 1. After comparative research with other apps that have skip and back buttons in a form, we will place the back button as a back error in the top left of the screen and the skip button in the top right of the screen

1. 1. The different statements presented in the question seemed to not be immediately related and the disparity in their general topic area/purpose could lead to confusion with users. We will group the potential responses by general topic, and also include some positive statements as well to offset the predominantly negative ones.

1. There was some confusion whether adding a note about a friend means that the person may see it/it may be sent to the person. We will clarify the purpose of adding notes on people by for example adding a title to the add notes page saying “Something to remember about April”. This will hopefully make it clear that notes are only for users to see, not other people.

How can we better identify social media apps in the onboarding questionnaire

1. We could potentially use app icons instead of titles to break up the text and make it more visually stimulating