Background
Lenus is a platform for online fitness coaching. It offers products for both coaches and their clients. The core of the platform is planning and tracking of two major aspects of lifestyle change: fitness activities and nutrition.
In 2021 Lenus launched a workout tracker. As a client you use it to see the workout plan created by your coach. When you go to the gym, you mark what exercises you did, what weights you used, and how you felt about it.
The need and the task
An update to the business strategy brought new requirements to the workout tracker. Our team was tasked with designing and developing a new kind of workout tracker, the one where you don't have a workout planned by your coach but instead you select the exercises yourself.
This project was driven by the need to expand the business and to explore a new business model. It was a completely new branch of Lenus product offering, and we did not explore what needs our current coaches might have with regards to this product.
💡 Process: defining product foundations → concept development, prototyping and user testing → UI design → beta test launch
Definining product foundations
Together with my product trio we started with clarifying and defining the product foundations: business case, goals and opportunities, assumptions and hypotheses. We did the scoping for the first release.
It was decided to launch the new tracker as a separate product, do an extensive beta testing, and eventually merge it with the current workout tracker.
A visual mapping starting from the business goal and down to specific features
Concept development, prototyping and user testing
There were two main drivers of concept development.
One was the analysis of the current workout tracker: its flow, feature set, layout and UI. For the sake of speed, we aimed at changing as little as possible while accomodating the new features.
The other was extensive competitor analysis.
Narrowing down on the feature set and the user flow
A part of an extensive competitor analysis
Iterating on the user flow of the new workout tracker
Specs
Defining detailed feature logic
UI design
We built the product in a few weeks. During that time I worked closely with developers to clarify and adjust the requirements as well as do minor iterations.
In order to decide on some of the UI patterns (such as how to delete a set of an exercise) I did a few variations and quick user testing.
Some of many UI variations
Beta test launch
The new tracker was launched to about 60 fitness coaches and their clients in the beta test mode.
We prepared to learn from this beta by:
- Formulating product hypotheses that can be proven or disproven. We defined specific features looking at the use of which (qualitatively and quantitatively) we could work with those hypotheses.
- Preparing the product for quantitative data collection.
- Preparing objectives and protocol for qualitative research.
A part of user research documentation
Outcomes
- A functional product in beta testing that is completely ready for the team to learn from, qualitatively and quantitatively.
- A detailed learning plan to the most out of this beta.