The user research paradox
If you ask users what they want, they'll tell you what they already know. Faster horses, as the saying goes. The job of a product team isn't to take feature requests at face value — it's to understand the behaviour underneath the request.
This came into sharp focus for us during the development of one of our internal platforms. Users were asking for more filtering options. More sorting. More search parameters. We started building. Then someone on the team asked: "What are they actually trying to find when they search?" The answer changed everything.
Watching instead of asking
We ran a simple observation session. Not a survey. Not a focus group. We watched five users use the product for twenty minutes each and said almost nothing. What we saw: they weren't struggling with filtering. They were struggling with not knowing what they were looking for. The data was there. The mental model to navigate it wasn't.
The feature nobody asked for: a "recently relevant" smart feed that surfaced records based on the user's own activity patterns. No filters. No search. Just the system quietly learning what each user cared about and showing it to them.
Users asked for better search. What they needed was to search less.
What this means for your product
Every product has a version of this. A feature users request loudly that masks a deeper friction they can't articulate. The unlock is always the same: spend time watching, not asking. The behaviour tells you what the words can't.
Build for what people do. Not what they say they want.