How to Know What Customers Really Want (Even Before They Do)
The most transformative products often address needs that customers couldn’t have articulated in a survey. Nobody told Steve Jobs they wanted a touchscreen smartphone. Nobody told Stewart Butterfield they wanted a workplace messaging platform. These products succeeded not by building what customers asked for but by understanding what customers fundamentally needed — and delivering a solution they hadn’t imagined.
Discovering what customers truly want, including the needs they haven’t yet found language for, is one of the most challenging and most valuable capabilities a product team can develop.
The Limits of Asking Customers What They Want
The problem with asking customers what they want is that customers can only articulate what they want in terms of what they already know. They describe modifications to existing solutions, improvements to current experiences, and features they’ve seen in other products they use. They can’t describe capabilities they haven’t imagined, experiences they’ve never had, or solutions to problems they’ve normalized to the point of no longer feeling as pain.
This is not a criticism of customers — it’s a feature of human cognition. We evaluate new possibilities against existing mental models. What we can imagine is constrained by what we’ve experienced.
Effective product managers supplement customer requests with methods that reveal the underlying needs behind those requests — and the unarticulated needs that no request has yet expressed.
Methods for Discovering Latent Needs
Observe Behavior, Not Just Stated Preferences
Watching users actually work — in their real environment, using their real tools, accomplishing their actual daily tasks — reveals friction they’ve stopped noticing, workarounds they’ve forgotten they’ve built, and contextual factors they wouldn’t think to mention in an interview.
The workaround is especially revealing. When users have invented their own workarounds to a problem — exporting data to Excel because the product’s reporting is inadequate, using a different tool for a step the product should handle, maintaining a separate tracking document because the product doesn’t support something they need — these workarounds document unmet needs with more precision than any interview question could elicit.
Ask About Experiences, Not Features
Rather than asking “what features would you like?”, ask about experiences: “Tell me about the last time you struggled to accomplish X.” “What was the most frustrating thing about Y last month?” “Walk me through what you did when Z happened.”
Experience-focused questions produce much richer insight than feature-focused ones. They reveal the emotional context of user frustration, the sequence of events that leads to pain, and the impact of problems that users might minimize when asked about them in the abstract.
Follow the Energy
In user research, pay attention to emotional cues: where does the user lean in? Where do they sigh? Where do they laugh? Emotional engagement — including frustration — is the trace evidence of needs that may not yet be articulable.
Users who become animated describing a workflow problem are pointing at a genuine need, even if their articulation of what would fix it is imprecise. Following that energy — probing further into what makes it painful, what a better experience would feel like — often reveals the underlying need with more clarity.
Study the Adjacent Possible
What are users doing just outside your product? What tools are they using immediately before and after? What information do they wish they had when they’re using your product? Understanding the ecosystem in which the product lives reveals the connections and gaps that represent unmet needs.
Analyze Support Tickets and Search Behavior
Support tickets document needs the product isn’t meeting. Search queries within the product document what users are looking for and not finding. Both are rich sources of insight into unmet needs that haven’t yet appeared as feature requests.
Key Takeaways
Discovering what customers truly want requires going beyond what they say they want to understand what they actually need — the functional, emotional, and social jobs they’re trying to accomplish, the friction that stands in their way, and the outcomes that would make them dramatically better served. The methods above are all variations on a single theme: get closer to the actual user experience, in its full context and complexity, with genuine curiosity about what makes it difficult. That’s where the insights that produce transformative products come from.