Bike-Taxi Drivers A.K.A. Captains who use Rapido Captain app to make money by getting rides, finding their way, and handling their schedule.
It is particularly challenging to design solutions for this user base as a lot of captains can’t even read or write and are new to technology. Google refers to such users as the Next Billion Users.
Captains offered performance-based incentives (e.g., bonuses) will be more likely to finish accepted rides to lift their performance score.
Rapido internally tracks the performance of captains through DAPR (Drop to Accept Ping Ratio) which is based on the number of rides they are accepting and how many of those they are actually finishing. This is calculated by:
City-wise diversification of HP (High Performing) and LP (Low Performing) drivers throughout India
drivers finish less than 4 rides out of every 20 rides they accept
The lack of performance tracking within the app disconnects drivers from its impact and limits their motivation to optimize their performance
Design a transparent and informative performance tracking system for drivers so they can easily understand and optimize their performance
To validate the need of this intervention, I realized that its best to conduct a quick experiment first with captains using CT events which don’t require dev efforts.
To communicate about the ride cancellation and risks involved
Reduce the number of cancellations
Using full screen and half-interstitial banner pop-ups & giving them warning messages, creating awareness abot high cancellation
Before solutioning, we visualized the whole system to set clear expectations of the change we wanted to see
We explored some ideas to find the best ways to that fit our context for the representation of performance of drivers
Performance board highlighting number of cancellations in the last 20 rides.
Progress bar to show where they stand among other drivers with a touch of gamification
Personalized tips and nudges to empower them
I started looking at how other players in the industry had setup their performance tracking system
Based on the problem statement and benchmark I was able to come up with the important components that would go on the performance page.
I tested mid fidelity designs with drivers to understand what resonates with them the most and learned:
Based on the insights from the usability test and prior research, I was able to come up with final high fidelity visual design.
Based on the insights from the usability test and prior research, I was able to come up with final high fidelity visual design.