Load history feature that reduced complaints from personal trainers
Context
During a phase of platform improvements (mapping workflows, analyzing competitors, and gathering feedback), we identified a critical gap: neither trainers nor students were able to view the load history in the exercises.
As a solution, we created a load history visualization feature with two view options and time filters, accessible to both students and trainers.
The Challenge
Problem
User:
Trainers: Impossible to track student progress without external spreadsheets or manual notes
Students: No visibility into their own progress within the platform
Both: Constant frustration: the platform was supposed to handle workout management, but left a huge gap precisely in load tracking
Business:
Constant support feedback complaining about this gap
Risk of churn among active trainers
Solution
We created a load history visualization feature with two view options and time filters.
Progress Chart: Users can quickly and intuitively see their progress curve visually.
Detailed Table: For those who prefer numbers: dates + load used in each workout, all organized.
Interval Selector: The user chooses the period that makes sense for their analysis.
Process
Mapping of accumulated feedback from support
Competitor analysis during the platform improvement phase
Tested layout of chart vs. table
Defined that the user could switch between both (not just choose one)
Time selector as the main filter
Tests
Testing Round 1: Developers tested technical issues (3 devs)
Testing Round 2: I + CPO validated visuals and usability before deployment
Results and Impacts
Support complaints on this topic dropped to zero
Trainers stopped using external tools for this purpose
The feature became an essential part of the tracking workflow
My Role
I was the sole designer throughout the entire process:
- Research (feedback and competitor analysis)
- Wireframes
- Final UI
- Testing (together with the CPO)
- Reporting directly to the CPO and working side by side with 3 developers.
Learning: At the time, I was a junior designer and focused heavily on “delivering the solution.” Even thought it worked and quickly solved a real pain point, today I would run usability tests before development and validate hypotheses with more real users.
