Figuring out how to organize all the proposed features into the existing app was a challenge. I considered three options:
- A single tab that housed all of Well's features
- Integrating the features into different parts of the existing Profile tab
- Creating a standalone app (like Nike Training and FitBit do)
I reviewed these with the MBA candidate team, weighing each against Well’s value proposition and users’ needs. We decided that fracturing the Peloton experience (3) or nesting Well too deep in the app (2) could make everyday use frustrating, and make it hard for users to connect the dots between executing their plan and the encouragement they receive in turn.
One cohesive tab (1) offered the most accessible, efficient, and cohesive experience. And, a top tab bar for sub-navigation hierarchically under the bottom tab bar is a pattern that Peloton already employed. I assumed this pattern is, while unconventional, vetted and working well for Peloton users.
I decided the Well tab would replace the existing Featured tab, assuming the latter was not often used. I then planned a few usability testing tasks to assess if the navigation posed issues to new users. That testing showed the double tabs caused minor confusion, but nothing that impeded workflow completion.
Here’s a few more routes I’d pursue to inform this decision if I was working on this product with Peloton’s UX team:
- Confirming the Featured tab isn’t often used, and testing how discoverable its new in-app location is
- Longitudinal A/B (or A/B/C) testing and qualitative feedback on the options above. I’d love to do this with new and veteran users.
- Live user activity monitoring of navigation issues for both Well and existing tabs