Every requested feature had shipped. Everything was built to spec. A leading UK cement manufacturer had exactly the trucking app it had asked for.
Daily usage was stuck at 30%.
In most companies, the next step is predictable. Someone writes a list of new features. The roadmap grows. The number stays where it is, and now the product costs more.
We did something less exciting. We listened.
What the drivers told us
We spoke with truck drivers over Microsoft Teams, and we let them talk about their frustrations, their routines and the reality of their workday. We expected usability issues. We did not find the main one there.
The app worked fine. Drivers simply had no reason to open it.
That single sentence changed the project. A usability problem asks, "Can people do this?" An adoption problem asks, "Why would they bother?" Those questions need completely different answers.
Usability vs adoption
| Usability | Adoption | |
|---|---|---|
| Core question | Can people complete the task? | Do people choose to return? |
| Common signs of trouble | Errors, confusion, long task times | Low usage, drop-off, workarounds |
| Best research | Usability tests, heuristic reviews | Interviews, field context, behaviour data |
| Typical fix | Simplify the flow | Create a reason to care |
You need both. Poor usability will kill a product that people want. Great usability will not rescue a product that people have no reason to use.
What we changed
We explored ways to make existing tasks feel worth doing. The answer was Star Miles, points that drivers earned for completing tasks and could redeem for products on shopping sites. A leaderboard then turned routine deliveries into friendly competition.
We added motivation, not more functionality. After launch, usage rose from 30% to 90%. You can read the full trucking app case study here.
How to diagnose low adoption
Before you approve a new feature, work through these questions:
- Can users complete the main task without help?
- Do they know the product exists, and what it is for?
- Does it fit the rhythm of their real working day?
- What do they use instead? There is always something.
- What do they gain personally from using it?
Question five is the one that businesses forget. Your reason for wanting people to use a product is rarely their reason for using it.
Usability still matters
I take usability seriously. On a GE programme, Design Thinking, usability testing and heuristic evaluation helped reduce user friction by 30%. The point is not that usability is overrated. The point is that you need the right diagnosis before you choose the treatment.
Questions people ask
Why do users not adopt a product with good usability? They may not see personal value in it, or it may not fit their daily routine. Good usability removes barriers, but it does not create motivation.
How do you measure product adoption? Track how many intended users return and complete the key action. Choose a time period that matches how often the task really happens.
Is your product working fine and going nowhere?
That is one of my favourite problems. Tell me about it at pranjal.productmind@gmail.com or on LinkedIn. I would start by asking to meet your users.