We sat down with members of our product and engineering teams, Dave, Benoit, and Minxin to talk more about why it was important to design our latest heart rate feature with a user-centered mindset.
Why was this feature so important to put into motion?
Dave: As we’ve grown, we’ve observed an increase in the percentage of users who take workouts with heart rate monitors. It offers a very individualized metric, that is catered to their fitness level. While output is a core metric in the Peloton experience (and helps connect riders on the leaderboard), heart rate zone training is a great way for users to tailor their training to themselves.
Benoit: We’re not just streaming cycling classes but building experiences around them. When our instructors teach new techniques that become popular, we think it’s important to build them into our application so they become part of the experience! In a lot of ways, it’s what makes Peloton so special.
We know that this feature was a major request from riders. Is there extra excitement around creating a feature that’s highly anticipated by the community?
Minxin: Absolutely! We knew that the user experience would be elevated by heart rate zone training, and being able to develop the feature based on user feedback is inspiring!
Benoit: Every feature we build or change we really do with our users in mind but there’s always an extra bit of excitement when it’s something they’ve been waiting for!
Dave: I personally enjoy following along with user feedback after the launch (either through the Facebook rider page or from our support team,) to see how our riders are using the feature. There is a lot to learn based on initial excitement, and it helps to further improve the feature down the line.
How was this feature built with our members in mind?
Dave: This feature was a direct response to feedback from our users, and the traction that our heart rate zone training classes had. During the design and development process, we tested a number of different prototypes on users and people around the office, in the end settling on the simple solution that is now available.
Minxin: To keep the user experience in mind, we considered two aspects: the default framework that provides the user with guidance and the other is the customized framework where the user can achieve their desired heart rate zone training experience.
What was the collaboration process like for this feature?
Benoit: There is a lot of information we want to show our users when they’re taking a class and even with our amazing display, it’s hard to add new things without it starting to look like a dashboard. During this process, we worked very closely with the design team to make sure we show the information users want to see without cluttering the user interface.
Dave: At Peloton, we believe that ideas and feedback can come from all directions and departments. In this particular project, we worked closely with instructors to understand the philosophy of heart rate training, designers to figure out how to add it to the interface, and developers on the best way to execute.
How can riders anticipate this feature evolving over time?
Dave: Overall, heart rate zones is still a fairly basic feature. We stuck to the simple route so that we could deliver this without a complete overhaul of our in-class screen. Over time we think the heart rate feature will become deeply embedded into the experience, specifically as it relates to a user’s workout history. I also think there are opportunities to improve the display of heart rate zones in class, to help users better measure their rate of recovery and their overall heart rate stats for a specific class.
Learn more on our heart rate zone feature here