Users tell you what hurts, not what is missing
The largest product opportunities do not arrive as customer requests. They come from watching what users work around and never think to mention.
Customers describe friction accurately. Ask what frustrates them about your product and you get a precise, usable list. That list is the smallest part of the opportunity.
People report pain they have noticed. They do not report the workflow they abandoned two years ago, the spreadsheet they maintain beside your product, or the thing they never attempted because it did not occur to them that software could do it.
Why requests undercount
A request requires the user to hold three things at once: awareness that a problem exists, a belief that it is solvable, and a sense that you are the one to solve it. Drop any of the three and the need stays unspoken.
The third is the one product teams forget. Users file requests inside the boundary of what they think you do. A customer who considers you a reporting tool will never ask you for a workflow feature, no matter how much time the missing workflow costs them.
What observation catches
Three signals I look for, none of which arrive through a feedback form:
Workarounds. Someone exporting to CSV every Monday, transforming in Excel, and re-uploading. That loop is a feature specification written in user behaviour. They rarely mention it, because they solved it and stopped considering it a problem.
Abandonment points. Where sessions end without completing anything. The user did not file a complaint, they left. Funnel data shows the where; watching sessions shows the why.
Adjacent tool usage. What sits open in the next tab while someone uses your product. The gap between your product and that tab is often the highest-value thing you could build.
Method
Watch people work in their environment rather than in a call where they demonstrate for you. Look at what they do before opening your product and after closing it. Ask about the last time they tried to accomplish the goal and gave up.
None of this replaces the request list. Requests keep existing users from leaving. Observation is where the growth is, because the need nobody articulated is also the need no competitor has built for.
Related reading
- Product managementVolume is not evidenceThe most confident voice in a product review steers decisions it should not. Quiet team members often hold better information, and that is a product risk rather than a culture complaint.
- Product managementThe hard part of product management is the backlog you rejectEvery roadmap becomes a prioritisation problem where sales, design, engineering, and leadership all have defensible asks. Scoring frameworks help by forcing better arguments, not by producing answers.
- Product managementNine things to settle before you build an AI productProduct managers who approach AI products like traditional software ship disappointing results. Three assumptions stop holding, and the differences are worth settling before design starts.