The best customer research uncovers problems, not feature requests.
I’m a big believer in talking to customers. Some of the most useful marketing strategies I’ve developed started with conversations rather than dashboards, and I’ve written before about how much context gets lost when companies rely too heavily on data without understanding the people behind it. There's an important distinction between listening to customers and asking customers to tell you what to do.
Those are very different things.
Ask customers what they want and they’ll usually give you an answer. They may ask for a new feature, lower pricing, a different service model, more reporting, another integration, or some capability they saw a competitor offer. Those answers can certainly be useful, but they can also send a company in the wrong direction if they’re accepted too literally.
Customers are experts in their problems and experiences. They aren’t necessarily experts in designing your product, positioning your company, or developing your marketing strategy.
I’ve found the better conversation usually begins one step earlier. Instead of asking what someone wants, try to understand what they’re trying to accomplish. What problem are they dealing with? Why does it matter? What are they doing today? What frustrates them about the current approach? What have they already tried? What happens if they do nothing? How did they decide this problem was important enough to solve?
Those questions tend to produce much richer answers because they get beneath the requested solution.
A customer might tell a software company that they need another dashboard. If you take the request at face value, the product team builds another dashboard. But when you dig deeper, you may discover the customer isn’t really asking for more data. Their manager keeps asking questions they can’t answer quickly, so they’re spending hours every week pulling information together manually. The real problem is access to a specific insight, not the absence of another screen filled with charts.
That distinction matters.
Once you understand the underlying problem, there may be several ways to solve it. A new dashboard might still be the right answer. So might an automated report, an alert, better integration with another system, or simply making information that already exists easier to find. The customer's original request becomes one possible solution rather than the definition of the problem.
The same principle applies to marketing research.
If I ask a customer what message would make them buy a product, I’m asking them to become a copywriter. If I ask what they were worried about before buying, what alternatives they considered, what almost stopped them, and what ultimately made them comfortable moving forward, I’m learning how the buying decision actually happened.
That’s far more useful.
I’ve conducted customer research where the language customers used to describe a problem was noticeably different from the language the company used internally. Leadership had spent years thinking about the business in terms of products, features, and industry terminology. Customers talked about the same company in terms of wasted time, missed revenue, employee frustration, risk, or simply making their jobs easier.
Neither side was necessarily wrong. They were looking at the same value from different perspectives.
The customer's version is usually the one I want Marketing to understand.
This is one reason I prefer customer interviews to rely heavily on open-ended questions. I want people to tell the story in their own words rather than choose from the answers we’ve already decided are important. How did you first hear about the company? What was happening in the business at the time? Why did you decide to look for a solution? What alternatives did you consider? What surprised you after becoming a customer? What would you miss if the product or service disappeared tomorrow?
You start seeing patterns after enough conversations.
Several customers may describe the same frustration using nearly identical language. Buyers may consistently mention a benefit that barely appears in the company’s messaging. You may discover that something leadership considers a major differentiator rarely comes up at all. Sometimes customers value an aspect of the experience that the company has treated as relatively unimportant.
Those discoveries are hard to get from a question like, “What features would you like us to add?”
This also matters when companies are repositioning themselves. Leadership often has a clear idea of what it wants the company to become, but customers can tell you what credibility the business already owns. What do they believe you’re particularly good at? Why did they choose you instead of someone else? What do they tell colleagues about you? Where do they think you fit in the market?
That doesn’t mean customers get to decide the strategy. It means you understand the starting point before trying to move somewhere else.
The same goes for dissatisfied customers and lost prospects. In some ways, those conversations can be even more valuable because they expose friction that happy customers have already overcome. Why didn’t someone buy? What made the alternative more attractive? What was confusing? At what point did they begin losing confidence? If a customer left, what changed in the relationship?
You don’t have to agree with every answer.
That’s another important part of customer research. Individual customers can be wrong about what the company should do. Their requests can conflict with each other. A feature that matters enormously to one customer may be irrelevant to ninety percent of the market. A large customer may ask for something that pulls the product away from the audience the company wants to serve.
Research becomes useful when you look for patterns, context, and underlying needs rather than treating every comment as an instruction.
I think companies sometimes struggle with this because customer-centricity can be interpreted too literally. Listening to customers doesn’t mean handing them the strategy. Henry Ford is often credited with the line about customers asking for faster horses, although there’s little evidence he said it. The quote survives because the idea behind it is useful: people are usually much better at describing their frustration with the current situation than imagining a solution that doesn’t exist yet.
That’s where good product and marketing teams earn their keep.
The customer explains the problem, and we figure out what to do with what we learned.
For marketers, those conversations can influence far more than messaging. They can reveal new segments, expose weaknesses in the sales process, identify competitive threats, explain churn, uncover expansion opportunities, challenge assumptions about the ideal customer, and sometimes point toward entirely new products or services.
But you only get that value when the conversation is designed to discover rather than confirm.
That means resisting questions that quietly steer customers toward the answer you want. It means being willing to hear that the thing you’re most excited about isn’t particularly important to them. It means listening closely when customers describe the problem differently than you do and following the conversation when it moves somewhere unexpected.
Some of the best insights I’ve gotten from customer interviews came from questions I hadn’t planned to ask. Someone said something surprising, I followed up, and suddenly the conversation exposed an issue that hadn’t appeared anywhere in the original research plan.
That’s the value of talking to people.
Customer research shouldn’t be a referendum where buyers vote on your next strategy. It should help you understand the world from their side of the table well enough to make better decisions from yours.
So, talk to customers. Talk to the ones who love you, the ones who left, and the ones who considered you and chose someone else. Listen carefully to what they want but spend even more time understanding why they want it.
The request may point you toward an answer. The problem behind it is where the real insight usually lives.
