Logistics · Case Study · Adoption and engagement
How I turned a feature-complete app that drivers ignored into one they chose to open — by solving for motivation, not functionality.
Overview
When adoption is low, the instinct is to build more. This project is a clear example of how I handle it: find out why people aren't using the product before spending more budget on it, then fix the real cause.
A trucking app had every feature the business had asked for, built exactly to spec. Daily usage was stuck at 30%.
The obvious next step was a longer feature list: more cost, more complexity, and the same adoption number.
I went to the drivers and listened. The app worked fine. They simply had no reason to open it.
After launch, daily usage rose from 30% to 90%. The business got the adoption it needed.
Challenge
Every requested feature had shipped. The app was built exactly to specification. Yet 70% of the people it was built for were not using it on a given day, and nobody could say why.
Insight
Rather than guess, I connected with truck drivers over Microsoft Teams and let them talk about their frustrations, their routines and the reality of their workday. I expected usability issues. That wasn't the main problem.
The problem wasn't functionality. It was motivation. The app worked fine — drivers simply had no reason to open it.
A usability problem asks, "Can people do this?" An adoption problem asks, "Why would they bother?" Naming the right problem is what changed the project.
Approach
Instead of expanding the feature set, I explored ways to make the tasks drivers already completed every day feel worth doing: points, recognition and rewards tied directly to those actions.
Spoke directly with drivers to separate a usability problem from an adoption problem.
Redefined the brief from "add features" to "give drivers a reason to care about the ones we built".
Introduced Star Miles, points earned for completing tasks and redeemable for products on shopping sites.
Added a leaderboard that turned routine deliveries into friendly competition among drivers.
The full driver experience: home dashboard, driving stats, live deliveries, and the pre-trip safety check that feeds the Star Miles system.
Results
After launch, daily app usage jumped from 30% to 90%. The business got the adoption it had been paying for, and drivers got an experience that motivated them to open the app every day.
How I work
The trucking app is one example of a habit I apply to every product that isn't delivering. If you lead a team, a product or a budget, this is what you can expect from me.
Low usage can mean many things. I find the actual cause by talking to the people who aren't using the product, then fix that.
More features rarely fix a product people have no reason to open. I look for what motivates the behaviour you need.
Recognition, reward and a sense of progress change behaviour. I build them into everyday work without adding friction.
Success is measured in what people do, such as daily usage, not in how the product looks, so leadership can see the return.
This applies when a product is live but unused, when employees or partners won't adopt a tool you paid for, or when the next feature request looks like an expensive guess. If any of that sounds familiar, write to me at pranjal.productmind@gmail.com.
Go deeper on the thinking: Usability vs adoption · Ethical persuasive design · Emotional design