Project Overview

As a student at General Assembly, my team and I were tasked with integrating new features into an existing mobile application. Paired with 3 other designers, we were assigned ClassPass, a mobile fitness booking application. The entire project was done over the span of 2 weeks, however, it was segmented into a research phase, design phase and prototyping phase over that time frame.

As we collected data it became apparent that ClassPass users wished there was more within the application. Furthermore, ClassPass was looking to increase class bookings among existing members to create a stronger community. As a result, we decided to focus the scope of our project on figuring out which features to integrate, how to integrate them and how to successfully deliver a product that solved ClassPasses needs.

Screen and Conquer

For our research we needed to garner unbiased interview feedback, so we created a screener survey that we distributed across various social media channels. Out of the 20+ replies we received, we narrowed down the results to 5 top candidates and scheduled times to meet with them for an interview.

Part of the challenge of interviewing was that our users were very busy people with limited time to meet with us. Furthermore, with only 2 weeks to complete this project we were strapped for time ourselves. We offered to meet our interviewees at convenient locations throughout New York City, regardless of time of day, in an effort to mitigate and solve this problem. As a result, we were able to conduct more authentic interviews because we were capturing audio in a setting that was more comfortable for the user.

User Interview Process — Screener (left), Interview (middle), User Insights(right)

Key Insights

Post-it notes, sharpie markers and a whiteboard wall. What do all three of these things have in common? They’re all part of a process called affinity mapping.

Following UX protocol, we aggregated our data onto post-it notes, grouped them into similar ideologies and categorized them according to conceptual models. As a result, we were given key insights into user behavior, as well as their needs, goals and pain points.

Among our discoveries, some essentials included:

  1. Users want to workout consistently
  2. Users enjoy working out with their friends
  3. Users enjoy meeting new people in classes
  4. Users need a more convenient way to communicate with other ClassPass users.

Additionally, we crafted a primary persona that encapsulated all of our insights into one pseudo-individual, so that when we moved into our design phase we could reference their needs, goals and pain points for a customized solution.

While our prompt addressed a specific problem it wanted us to solve, we knew that a deeper problem had to exist, and that if that problem was solved, it would inherently increase class bookings all on its own. According to our data, it was clear that users felt strongly about working out with their friends, and that there was minimal social interaction within the ClassPass application. As a result, we concentrated our efforts on solving for the following problem statement.

How might we provide a sense of community and increase class bookings by improving social interaction within the ClassPass application?


With our problem statement clearly outlined we ran a design studio to brainstorm and conceptualize any and all ideas to solve this problem. Each of us sat down around a table, sharpies in hand, and sketched out what we believed to be a good solution to the problem. We then entered a cycle of critiquing each other’s designs, iterating on those designs and sketching new designs, until we agreed on a multitude of features that could possibly be explored.

In consideration of time restraints, we mapped out and prioritized which features were essential to the Minimum Viable Product(MVP). If we had decided to add every feature we thought of, not only would we run out of time, but we would be in a state of featuritis, which would be very difficult to climb out of.

Our Design Studio and Feature Prioritization taught us that we needed to:

  1. Redesign the home page into a feed page with easy access to updates, friends and notifications
  2. Add the ability to view what classes your friends are taking and if they are looking for a workout partner
  3. Implementing a group feature where people with similar workout interests can meet new people
  4. Implement an easier way to invite your friends to class
  5. Make it easier to add new friends

After deciding which features to implement, we mapped out ideal paths for users and created mid fidelity wireframes to bring into InVision for testing.

feed screen (left), friend’s list (middle), class booking page (right)

Usability Testing 1

We created 3 scenarios with specific tasks for each new feature we implemented and conducted 5 usability tests with active ClassPass users.

Mid fidelity Usability Test

We found that — even with the friends list easily accessible — users indirectly completed the tasks — meaning they deviated from the task or had trouble completing the task, but ultimately succeeded in completing the task. We had designed a new icon indicating when someone was looking for a workout partner. Unfortunately, that icon made little sense to ClassPass users. Only 40% finished that task and 0% of users finished it directly. That being said, 100% of users joined a recommended class, with 80% of those being on the direct path.

Usability Test 2

We went back to the drawing board and iterated on our original designs. We completely removed our workout partner icon and turned the big profile icon into smaller profile icons in place of ratings. We also upgraded our prototype to high fidelity (hi-fi) by adding color, photographs and removed lorem ipsum for real world text content.

Our second round of usability testing was far more successful.

High Fidelity Usability Test

Two things happened in our second round. The first being that we had a 100% direct success rate in joining a class where someone was looking for a buddy.

What changed?

As stated, we removed the workout partner icon and added a new section on the feed page called ‘looking for a buddy’. As a result, when a user opens the app it shows all their friends who are looking for workout partners right on their feed page.

While we had monumental success in one area, adding a friend actually declined by 20%.We attributed this to the fact that we lowered the contrast on the button, which appeared to get ‘lost’ on the page.

Next Steps

After several rounds of testing and iteration it is evident that the features integrated into the ClassPass application by our design team have been met with promising results. If we were to have more time on this project our next steps are as followed:

  1. Conduct another Usability Test on most recent iterations
  2. Track members to see if social integration increases class bookings.
  3. Find a way to re-integrate home page ads into ClassPass application that doesn’t interfere with new feed feature.

Source link


Please enter your comment!
Please enter your name here