✦ Problem
✦ Solution
✦ sneak peek
✦ End-to-end product design roadmap

✦ Explanatory User research
2 Main Insights
The need for a unified book keeping platform. Persona 1 says : "Cancelling a class is more than just cancelling. It's a logistics nightmare!"
Entry level trainers needed tools than just service. Persona 2 says: I like to read the reviews of other trainers to see how much clients they are getting and how they do things differently"
The need to track revenue and performance
There was significant demand for revenue tracking and for monitoring the longitudinal progress of trainers' income.
✦ Competitive Analysis
How does 10+ competitor provide payment tracking and analytics

✦ Ideation
Defining the MVP features for payment integration and analytics. Using Moscow method, must haves, could haves and wont haves were prioritized for the MVP. Budget, speed and cleint stakeholder feedback were considered in the navigating ambiguity.

✦ Rapid wireframes and prototypes
In phase 2, the source of payment was also added as an additional feature. However, due to limitations of STIPE API, the feature was taken out in further phases.

✦ Design System
Using existing design system and visual styles to create Brand centric design components and high speed execution.

✦ Final Design

✦ Usability testing
6 Participants, 3 hours and 6 tasks per person

✦ Iterations
The icon of payment source was removed and sorting by selected dates in calender was added

Details of rescheduling is more clear. What ever that is changes is highlighted in red with a tag on top.

Simplified cancellation policy. 7 different options were simplified into just 3.

✦ Learnings
Self Reflection