Team Badger: Usability Report

We tested our Figma prototype (link) on two sets of users during class. As a reminder, how we conducted the usability testing can be seen here (link). Both tests were successful: users navigated through both the onboarding scenario and “return” scenario with minimal guidance. We were successful in providing a smooth onboarding experience and flow – there were only minor flow issues, such as buttons not looking clickable. Overall users felt like the brand/design was quite strong/unique/impactful, saying things such as “wow” or “this is sick.” As such, most of our feedback focused on other elements.

First, users wanted more “delightfulness” from Barry; one user described Barry as “underwhelming.” Since our product is focused on amplifying delight, this is an important issue. To fix this, we wanted more dramatic visual effects or sound effects when prompts were received. Secondly, users wanted more personalized feedback from Barry, which also means that they wanted the tone of his feedback to be more constructive/useful/suitable for them. 

Following their feedback, we will change these features, grouped into the categories stated above, and then ranked by category:

Flow/usability:

  1. SEVERE: The navigation elements look like static labels, not interactive tabs.
    1. Lean into the static labels as “page titles”; change up the flow so that you can only view your stats at the end. Use the tab bar like a browser bar.
  2. SEVERE: There are no clear back/exit paths throughout both the flows. 
    1. Add a back button. Add a modal that confirms exit. 
  3. MODERATE: There is no explicit confirmation when you end a session, making the experience feel too “quick.”
    1. Add more explicit confirmations, especially when ending the experience, possibly adding more modals to confirm.
  4. TRIVIAL: Unclear during the onboarding that you needed to click on Barry to continue.
    1. Add more tooltips to explain how to continue.

Improving Barry’s delightfulness:

  1. SEVERE: Barry is not interesting enough! 
    1. Amplify Barry’s health animations: more dramatic visual change, optional sound effects, and a critical/death state.
    2. Randomize the arms/legs/faces so that Barry has more variations and each time Barry changes, it’s a surprise.
  2. MODERATE: There’s not any repercussions when Barry dies – there are no stakes.
    1. Add a lockout feature that raises the stakes of Barry dying.

Personalizing Barry’s feedback:

  1. SEVERE: Barry can be too mean or harsh.
    1. Add a “tone” personalized tuner for Barry: you can select between nice, neutral, and mean.
  2. MODERATE: Barry’s feedback doesn’t seem very impactful or personalized.
    1. Add more personalized, actionable feedback on prompts rather than standardized/blanket responses from Barry.
    2. Tie Barry’s health criteria to the user’s personal goal set during onboarding (which was not possible during Figma prototype)
    3. Add a widget to the “stats” page that displays AI usage over time.

Optional improvements:

  1. TRIVIAL: The only thing that you can customize about Barry is his name.
    1. Add more accessories and personalizable options for Barry.
Avatar

About the author

Leave a Reply