My Stats

Role

Design Owner

Team

Project Manager

Fitness Scientist SME

Club Liaison

Timeline

August - December 2021

5 months

Outcome

Shipped to over 20,000 fitness clubs

jump to designs

Overview

My Stats - a web app that tracks exercisers' workout performance over time, is one of my larger, more impactful projects at Peloton.

It records exercisers’ workouts, progress over time, key metrics (e.g., speed, heart rate, etc), and key moments

Problem

Previously, after an exerciser ends their workout they see some high-level metrics like duration, distance, and average speed.

After the session is over, that data is lost - exercisers have no insights into the change in their performance.

While our equipment could capture workout data AND store it to surface to the user in the future, it wasn’t supported by the software.

How can we create a way for exercisers to view their daily & past workout metrics so that they can analyze and improve their performance?

Research

Our club liaison connected us to multiple partner gyms. The admins and front desk workers provided us with excellent feedback over the phone.

We learned more about exercisers and their mental model/needs.

Mental model

How did I do in that workout?

What did I accomplish today/yesterday/last week?

Has my performance improved since X?

User needs

Granular view of workout metrics during and after a workout

Insight into performance for all workouts in a given time frame

Insight into a change in performance over a long period of time

Ideation

After identifying and validating requirements from the users and marketing stakeholders, my PM and I prioritized features.

I then iterated on user flows and designs, sharing them regularly with stakeholders to gather feedback and with the engineering team to measure technical feasibility.

Today’s accomplishments

An overview of all the workout the exerciser completed today, with aggregated metrics.

Timeline

A complete history of a person's workout sessions with all the relevant metrics.

Personal bests

Workouts with the exerciser’s highest performance metrics.

Badges

Collectible rewards that represent milestone achievements.

After prioritizing features with my PM, I rapidly iterated on low-fidelity designs and worked my way up to higher fidelity after solidifying the structure of the product.

I regularly held critique sessions with my larger design team also.

Usability testing

Accessibility was a large concern

The exerciser will use the product right after a workout - they’re tired and are likely to have less energy/focus
Vision-impaired users are likely to work out with their glasses off

So when designing high-fidelity comps, I frequently tested with exercisers for accessibility as we didn’t have an established design library to pull components from at the moment.

Final designs

I finalized the P0 design specs & handed them off to Engineering.

Since portions of this project are still under NDA, I cannot include post-launch design specs.

In my user flows, I also annotated entry/exit points into the product, as My Stats lives in the larger Peloton Commercial NextGen OS.

I also wrote engineering tickets that added design context and intended interactions/behaviors, and corner/edge cases.

After the hand-off, I attended DesignOps meetings to support my designs and answer questions from Engineering.

Conclusion

My Stats was one of my more impactful and personally-rewarding projects at Peloton. One of the biggest challenges was catering to the needs of an exerciser - a user with unique needs and accessibility risks.

I successfully mitigated those concerns by carefully measuring the risks with continuous user testing and iterating on my designs.