My goal for this project is to design a website/platform where people of all backgrounds and ages have the ability to learn how to play an instrument at any level without any cost, can view pre-recorded lessons with instrument-learning basics, can schedule live lessons with a teacher they can match with, and have unlimited access to a high quality, large database of sheet music for any instrument.
Heuristic Evaluation:
Pilot Usability Testing:
Heuristic Being Tested | Usability problem | Task scenario |
---|---|---|
User control and freedom | Cannot remove instrument category when searching for music lessons, confusion | Finding a clarinet teacher, then changing to flute teacher |
Consistency and standards | An element that appears to be a button but is not a button | Find the FAQs page and phone number from the top navigation |
Recognition rather than recall | Important links under nested menu | Find the "About" page under the nested menu |
Contextual Inquiry and Interview:
My two personas were Diego Jacinto and Nidhi Singh.
Learn more about them, their scenarios, and their journeys here.
The design features I would like to include are:
The purpose of low-fidelity prototyping is to lay-out the features I proposed and researched on previously. I can see how a user interacts with my design, considering how I initially think my design should be. With low-fi prototyping and testing, I can figure out big issues in my design before I start the high-fidelity prototypes.
I asked my friend to go through his journey of the low-fidelity wireframes. The journeys he took are in pink.
Onboarding
Sheet music database
Teacher search
Scheduling a lesson
Academy
I gave my tester the designs and asked him to logically go through the prototype according to what he wanted to do with the website. He talked aloud and suggested things to add or change, but overall did not have any difficulty going through the low-fidelity prototype. I found that directly hand-drawing the wireframes and flow was a lot more difficult than making them in Figma. In the past, for my UX projects, I would create my low-fidelity screens with Figma. However, I think that drawing them by hand makes me think about the journey harder, which is a benefit. Next time, I think I would make them a bit more detailed. When my tester went through the prototype, he found that there were a couple features that were missing or lacking something. From the notes I took of his journey, I will make quite a few changes to my design. First, in the onboarding, I will add an option to indicate what instrument the user is using if they are looking for sheet music. For the sheet music page, I will add more features when viewing it. I will also make the calendar for scheduling the lessons more detailed, perhaps with a legend. Lastly, for the pre-recorded lessons database, I will separate the courses by difficulty level so that the user can find what they are looking for faster.