Musico 3/4 — Usability Testing

Performing usability testing helps us modify the interface in a way that will affect the teachers’ efficiency for the best

 

MY ROLE

Planning, writing the script, building mockups, performing tests online or in-person.

PLATFORM

Desktop for online users (mainly overseas), Mobile for local users.

FREQUENCY

At the end of each iteration, usually every 4 weeks.

Overview

Managing and conducting user testing before launching any product update or new feature. 

I use in-person interviews with users and non-users in order to test major usability changes, and conduct quick tests on “Usability Hub” with non-users to test information architecture, copy, etc.

Structure

  1. Setting test goals.

  2. Writing a script, often containing 2 major tasks.

  3. Preparing mockups.

  4. Schedule meetings with relevant users (ex: teachers that have complained about something and I would like to get feedback from on the given solution) - each meeting is 20-30 minutes long.

  5. Recording all sessions - video, audio, and screen recording.

  6. Summarise all tests + find patterns.

  7. Modify designs according to the detected problems.

  8. Repeating the process with different users.

Test case

While working on Musico’s lesson library improvements, we had a vision of curating all pre-made lessons made by Musico’s content team under endless categories, Netflix style. 

We thought that teachers would be love having access to so many pre-made lessons and will spend more time on the platform to browse the content.

On the first two tests, I realized that although the teachers are thrilled about having all the content inside Musico, having too many options confused them: they were browsing for these lessons during the actual lesson with the student, and not in their free time.

This feedback led us to add categories such as “Classical Music”, “Pop/Rock”, “Beginners”, “Disney”, etc, instead of endless carousels.