Zwift has a plethora of on-demand content to engage with. The metrics showed that users who engaged with two key content types stayed longer on the platform than users that did not. The main goal of these programs was to put the planning aspect of user behavior into their pockets. This body of work unlocked two key content types for users to engage with at any time (workouts & routes) and plan their training accordingly. It began with allowing users to browse all of Zwift’s Worlds, Routes, and Segments and see their personal best times on any given segment. The next phase of evolution was allowing users to browse the entire workout catalog featured on Zwift. Route exploring and workout discovery was phase 1 & 2 in a larger plan to unlock users to browse, discover and queue routes or workouts from the Zwift Companion app.
My role
Lead Product Designer
Team
Cross-functional product team. Including:
- Project Manager
- Engineering Manager
- iOS Engineer
- Android Engineer
- QA Tester
- QA Automation Engineer
Problem / Challenges:
A large hurdle that the teams had to overcome was that these content types did not exist independently of the main Zwift game service. Separate micro-services had to be built to accommodate unique features outside of the main Zwift game. It started with an information architecture exercise to organize world and routes as well as workout collections and individual workouts.
Route Explorer:
Workout Discovery:
Scaling designs to incorporate the Queue:
