A product can have exactly what users asked for and still fail them.
I have seen this happen. A team does the research, identifies the right features, runs the usability tests, and gets confirmation that yes, these are the things people need. And then the product still underperforms. Users drop off. Adoption is slower than expected. The team wonders what went wrong.
What went wrong, most of the time, is that they confused utility with usefulness.
The equation that changed how I think about products
There is a simple way I started framing this for product teams, and it has stuck with me ever since:
Useful = Utility + Usability
Utility means the features are the right ones. The product does what users need it to do. Usability means those features are easy and pleasant to use. Both have to be true. A product that scores on utility but fails on usability is not actually useful, even if it technically has everything.
I started using this framing during a project where user testing confirmed that the product had all the right features. People wanted those features. But when it came time to actually use them, things got painful. The filters were buried. The navigation created friction at every step. Users could not find what they needed, so they stopped trying.
The features were right. The experience was not. And that gap is what made the product feel broken.
What design-led products get right
The companies that have built products people genuinely love tend to understand this intuitively. Think about Airbnb, Notion, or early Apple. The design is not decoration layered on top of the product. It is part of how the product delivers value. The user experience shapes what gets built and in what order, not the other way around.
That is what it means to be design-led. A few traits tend to show up consistently in products like these:
The user experience shapes the roadmap, not the reverse. The interface creates a competitive edge that is hard to replicate. The product is easy to understand from the start, which means design also supports growth. And the design itself is part of what the product is, not just how it looks.
Most products are not built this way. Most products are built around the features first, with the user experience treated as a finishing step. And that sequencing is exactly where usefulness breaks down.
Usability is not just "make it pretty"
When I work with teams on usability, I often use a heuristic framework from information architect Abby Covert. The pillars she lays out map closely to what I see in practice: a product needs to be findable, credible, accessible, desirable, and valuable. Each one of those is a real, specific thing that can be assessed and improved.
- Findable: can people locate what they need without friction?
- Credible: does the product feel reliable and accurate?
- Accessible: can people of different abilities and contexts actually use it?
- Desirable: does the product create a sense of trust and appeal that keeps people coming back?
- Valuable: does it deliver something worth the time and cost, for both the user and the business?
When a product is struggling, running it against these pillars usually surfaces where the breakdown is. It is rarely about the features themselves. More often, it is about how those features show up for the person trying to use them.
The next step is not more features
One of the most common mistakes I see when a product is underperforming is the instinct to add. Add a new capability. Build another module. Expand the feature set. The assumption is that if the product is not working, it must be missing something.
But more often, the product is not missing features. It is missing usability. The existing features need refinement, not company.
Before adding anything new, it is worth asking: are the things we already built actually usable? Can people find them? Do they understand what they are for? Is the path to using them clear?
If the answer to any of those is no, adding more features just creates more places for the experience to break down.
What this means for your product
If your product is not performing the way you expected, and you know the underlying features are right because you did the research, usability is probably where to look next.
Run the product against those five pillars. Sit with a real user and watch them try to accomplish something. Do not guide them. Just watch. You will learn more in twenty minutes of observation than in a week of analytics review.
The goal is not a product that has everything. The goal is a product that works.
Useful equals utility plus usability. Both sides of that equation have to hold.
