MyGuitare

Redesigning guitar e-learning platform

Project description

Myguitare is a guitar learning platform for French speaking middle age adults, who are looking for practical lessons to reignite their passion for the instrument.

Problem

MyGuitare’s redesign was very much overdue. New features were built on top of temporary structures, and was chaotic. Their online guitar courses grew for their pedagogy and unique approach to teaching guitar online, but their outdated platform was a hindrance to their growth, deterring less tolerant users when faced with frustrating experiences.

Solution

To help users achieve their guitar dreams, and accelerate business growth, we set foot to redesign the platform for better learning experience.

Role

As the design lead, I was responsible for the success of the platform redesign, from ideation to delivery. Beyond hands-on design work, I played a major role in mediating communication with client teams, facilitated internal team discussions.

Team

Yuki Nishida, Design lead

Charlotte Chen, Product Designer

Leo Chazalon, Product Manager

Natalia Tarasova, UI/UX Designer

Abdellah Rholem, Branding

Nick Lighter, Project Coordinator

Table of Contents

Who is this really for?

01 - RESEARCH

Establishing scope

02 - DEFINE

To the sketch board

03 - DESIGN

Handing over our vision

04 - DELIVER

Evaluating designs

05 - OUTCOME

Learning outcomes

06 - REFLECTION

Who is this really for?

01 - RESEARCH

We began with understanding the context of the problem. Before we interviewed anyone, we outlined the objectives for our research.

  1. User needs: Who are the users? What are their needs, and their existing pain points?
  2. Business needs: What is the core offering of online learning? What is MyGuitare’s unique value proposition and their competitive edge?
  3. Competitor analysis: What is the competitive landscape and how can MyGuitare standout?

We conducted 9 contextual interviews, 3 client discovery sessions, and 5 competitor platform audits.

Understanding user needs

We outlined three guiding questions for users...

  1. Who are the users?
  2. What are their needs?
  3. What pain points do they have?

We scheduled remote unstructured interviews with regular and power users to an open-ended conversation to probe for insights. As we approached our 9th user interview, we began to identify pattern in their response and gained confidence in moving on with our data.

Based on our findings, we created a target user to identify primary users and their needs. This target user would be referred to as Sébastien, which served as a reference for making design decisions and aligning internal discussions.

MyGuitare's primary persona
"What would Sébastien do?"

Top pain points were:

Understanding business needs

MyGuitare helps guitarists reach their goals. We interviewed our client team to find out their strengths and weaknesses of their offering to ensure their strengths are reflected on the platform.

"How can the platform make use of the strengths, and limit the weaknesses?"

This surfaced critical features for a successful platform:

Competitor analysis

We audited 5 competitor platforms to learn from industry standards, and identify unique advantage we may be able to achieve for users like Sébastien. Our insights are summarized below.

Establishing scope

02 - DEFINE

Our scope sets realistic expectations for all stakeholders and avoids planning for failure. We surfaced constraints and limitations early in the project to bring up for discussions and plan ahead. With our research synthesized, all stakeholders agreed on the following scope for our first deliverable. We believed that if we get the fundamental features right, the rest will follow.

Project scope

  1. Redesign the information architecture (IA)
    Both, client team and users, indicated a disconnect between user's expectation and the platform IA.
  2. Redesign fundamental user flows
    We prioritized our efforts on the fundamental userflows (onboarding, course navigation, resuming a lesson) and backlogged luxurious features to later iterations.
  3. Establish a design system
    A design system that aligns with their new brand identity. It served to create alignment among designers and maintain consistency across designs.

To the sketch board

03 - DESIGN

Charlotte, Leo, and I began by drafting the IA, which then informed the userflows. For each flow, we iterated on wireframes, only then we moved on to created interactive prototypes.

Information Architecture

We reorganized the information architecture based on a common pain point that it takes "too many clicks to get to where I want to go".

IA before with flat hierarchy and dead ends.
updated IA, all flows leading to the core activity of the platform, lesson videos.

The original platform had a flat hierarchy which made navigation heavily reliant on the main menu. We stripped out unused legacy features and merged relevant pages. i The update puts more emphasis towards the core activity of watching lesson videos and practicing, ensuring all pages on the platform is a means towards watching videos rather than dead-ends that leads to procrastination or loss of concentration.

Redesigning 3 fundamental userflows

  1. Onboarding
  2. Course navigation
  3. Resuming a lesson

I took the lead in distilling each userflow down to its essence, and sketched wireframes to accommodate the actions. The goal was to optimize between minimizing the number of steps without over crowding any single page with too many options.

Because userflows are fundamental in the platform, each interactions that accommodates the flows were designed to be one of the most prominent in each screen.

1. Onboarding

Onboarding is many user's first impression so it's important. Our team focused on creating an engaging and streamlined experience to find the right course for users, who are eager to look for a course and start practicing.

With much discussion among all stakeholders, we decided to onboard new users with a short quiz to suggest personalized course recommendations based on guitar experience and music preferences. This is designed to show new users only what is necessary and streamline the steps to finding a suitable course and begin practicing.

2. Course navigation

Course navigation include steps users take to progress through a course from one lesson to the next. Although this flow could be a simple click of a button, the challenge were to implement MyGuitare's pedagogy which requires users to meet two conditions before moving on to the next lesson. The two conditions are:

Our solution aims to provide just enough information to educate new users of the two conditions without being intrusive to recurring users.

To accommodate for such requirement, we disabled the ability for users to move on to the next lesson, when it is unavailable. This eliminated dead ends for users and simplified the steps of navigating through a course. Hovering over a disabled button reveals a tooltip to assists users in gaining clarity of the system. 

3. Resuming a lesson

Having established the core activity as watching lesson videos, we needed to design the shortest path to pick up where users left off in a previous session.

As a solution, we introduced a dashboard menu with shortcuts to the previous lesson as the most prominent feature, eliminating the need to shuffle through all courses available. Since users often need to wait for the next lesson to become available, a quick route to the previous lesson would greatly reduce the number of clicks needed.

Some design considerations were...

How many "Previous lessons" should be displayed on the dashboard?

Two, we decided. Based on our data from average courses owned per account and interviewing users, majority of users juggle between one to three lessons at a time.

What other information would be useful on the dashboard?

Referring to the list of critical features for success in the research phase, we decided to include previous lessons, announcements, user statistics, and community posts.

Establishing a Design system

With multiple designers working simultaneously on the project, a robust and flexible design system was necessary in maintaining consistency. I took the lead in establishing the design system, communicating rules and expectations to the team, and monitoring the component library.

MyGuitare's design system

We organized our component library using the atomic design system, categorizing atoms, molecules, and organisms. This system proved beneficial when designers can build new molecules using a collection of existing atoms, and new organisms with existing molecules.

Atomic design system, Button (atom), Modal (molecule), Section (organism)

HANDING OVER OUR VISION

04 - final deliverable

Our handoff were challenging. We had to deliver design assets to client's development team across time zones, language barriers, and with different collaborative expectations.

We prefer the hot potato process, a handoff process with frequent communications to unblock any issues, compared to a traditional waterfall process. Unfortunately, our team and the client's development team had different expectations. However, luckily, both parties were transparent and resolved any development issues in a timely manner.

Course navigation

Educating users of conditions to access the next lesson, completing a lesson, and toggling lesson status.

Onboarding quiz

Personalized recommendations of relevant guitar courses to assist users get started.

Instructor chat

Access to all chats with instructors on any lesson, all in one place.

Support

Newly categorized support FAQs based on historical support tickets.

Payment flow

Selecting a portion of a course to purchase (module), VIP access add-on, payment methods, and purchase confirmation.

Evaluating designs

05 - Outcome

Once the platform was launched, we spent some time reflecting on our process and asked ourselves the tough question, how effective was the redesign? i But what should we measure? The possible answers were so vast we felt slightly lost. In such uncertainty, what got us out of the mud were to refer back to the goal of the redesign. What did we aim to achieve? how did we perform? We knew that any metrics that would help answer those questions were useful metrics to track.

Understanding that MyGuitare has a large enough user base to extrapolate meaningful insights, we set up google analytics as the base line to track overall performance of the platform i. Below are key metrics and indicators we will be paying close attention to evaluate each aspects of the redesign i.

  1. Evaluating information architecture
    Good IA helps users understand where they are, where they were, what’s around, and what to expect. High bounce rates, Low unique pageviews, high volume of search queries, are a few indicators of poor IA.
  2. Evaluating fundamental user flows
    Onboarding: Low new user course registration, high quiz page drop-off rates, low recommended course visits.
    Course navigation: Recurring user's average session duration, user survey, usability testing.
    Resuming a lesson: Fewer visits to "my courses" page, few navigation from dashboard to a previous lesson,
  3. Evaluating design system
    Although the purpose of a design system is not just for users, we can collect user's opinion from surveys and interviews.

*Metrics are being collected and analyzed. Stay tuned!


Learning outcomes

06 - Reflection

MyGuitare platform redesign was a large project to tackle. Defining core activities of the platform helped prioritize features to be developed, backlogged, or removed. Our solution gained all stakeholder buy-ins and we are confident in releasing to the public. My team looks forward to tracking the outcome of our redesign.

Below are some thoughts and insights I have developed during this project:

Half of the design skills is about connecting with people

It is evident that connecting with users is necessary to get the job done. However, connecting with your client, colleagues, and other stakeholders become as important to produce great work.

It is hard to distill design into its essence

It is really easy to get lost in the complex dependencies of each feature but distilling it into its essence requires deep understanding and engagement from designers. I believe this is what separates great designers from good designers.

Ask for relevant feedback from the right people

It is easy to present your designs to non-designers and ask the holy question, "what do you think?" expecting nods of approval. Most times, the feedback is not helpful, and it isn't their fault. I learnt that I was asking the wrong people. The last thing I want is the CFO giving me his/her opinion on typography, when you needed their approval on budget extensions. i

Future iterations

We created a list of backlogged features that were out of scope for this project. Two major features that are certainly on the priority list are based on insights from the competitive analysis.


Fun facts:

Thank you for reading 👏

You are awesome for scrolling all the way through! I would love to get in touch with you, so please reach out via email!