I once spent three months building a feature that nobody used. Three months of development time, design resources, and testing. When I finally asked customers why they weren’t using it, the answer was almost embarrassingly simple.
“We didn’t ask for this,” one customer said. “We asked for something that would help us export reports faster. This doesn’t do that.”
I had assumed I knew what they wanted. I had looked at usage data, drawn conclusions, and built something I thought solved a problem. But I never actually asked them what problem they were trying to solve. I never sat down and had a real conversation about their frustrations, their workarounds, and the gap between what they had and what they needed.
That mistake cost me three months. But it taught me something invaluable: customers rarely tell you what they want unless you ask the right questions. And most of us are terrible at asking.
We ask leading questions that confirm our assumptions. We ask vague questions that produce vague answers. We ask about features when we should be asking about problems. We survey customers with multiple-choice options that force their complex needs into neat little boxes that don’t fit.
The result is that we build things nobody wants, write copy that doesn’t resonate, and create products that miss the mark. Then we wonder why.
The solution isn’t more data. It’s better questions. The kind that reveal what customers actually want—not what they say they want, not what we hope they want, but what they genuinely need and would pay for.
Here are seven questions that do exactly that.
Why These Questions Work
Before we dive in, let’s talk about what makes a question useful.
They’re open-ended. Yes/no questions produce binary answers that tell you almost nothing. Open-ended questions invite customers to tell stories, share frustrations, and reveal the context behind their needs.
They focus on behavior, not hypotheticals. “Would you buy this?” is useless. People are terrible at predicting their own future behavior. “What did you do the last time you faced this problem?” produces real, actionable information.
They dig into emotion. Logic makes people think. Emotion makes people act. The best questions uncover not just what customers do, but how they feel about it—the frustration, the anxiety, the relief they’re seeking.
They avoid leading. The moment you signal what answer you want, you’ve contaminated the data. Good questions are neutral, curious, and genuinely open to any response.
They’re simple. If a customer has to work to understand the question, they’ll give you a shallow answer. Simple questions produce rich responses.
Keep these principles in mind as we explore each question.
Question 1: “What’s the hardest part of [your situation]?”
This is the single most valuable question in customer research. It’s simple, open-ended, and immediately surfaces the friction points that matter most.
The key is to be specific about the situation. Don’t ask “What’s the hardest part of your job?” Ask “What’s the hardest part of managing your team’s schedules?” or “What’s the hardest part of planning meals for your family?”
Here’s why this question works. People are wired to notice problems. We complain about the hard parts of our day all the time. But we rarely feel heard. When you ask this question, you’re giving someone permission to tell you exactly what’s frustrating them.
The answers will surprise you. A software company asked this question to users of their project management tool. They expected complaints about missing features. Instead, they heard about a completely different problem: users couldn’t get their teams actually to adopt the tool. The hardest part wasn’t the software—it was the change management.
That insight shifted their entire product roadmap. They stopped building features and started building onboarding resources, training materials, and adoption guides. Churn dropped significantly.
How to use it: Ask this question in customer interviews, surveys, and even casual conversations. Listen for patterns. When multiple customers name the same hard part, you’ve found a problem worth solving.
Question 2: “Walk me through the last time you dealt with [problem].”
Hypothetical questions are unreliable. People imagine they’ll behave one way, then behave completely differently in reality. The solution is to ask about actual past behavior.
“Walk me through the last time you…” is a narrative prompt. It invites the customer to tell a story. Stories are rich with detail—what they did, what they felt, what worked, what didn’t, what they wished had been different.
A meal kit company used this question to understand why customers were canceling. They expected to hear about price or food quality. Instead, they heard detailed stories about the stress of cooking after a long day. Customers weren’t canceling because they didn’t like the food. They were canceling because the cognitive load of deciding what to cook, even with pre-portioned ingredients, felt overwhelming at 6 p.m. after an exhausting workday.
The company responded by creating “no-decision” meal options—complete dinners that required no choices and minimal preparation. Retention improved.
How to use it: Ask this question during customer interviews. Let them talk without interrupting. Take notes on the specific steps, emotions, and workarounds they describe. These details are gold.
Question 3: “What have you already tried to solve this?”
This question reveals the competitive landscape from the customer’s perspective. It shows you what alternatives they’ve considered, what they’ve invested in, and why those solutions didn’t work.
The answers often reveal that your biggest competitor isn’t another company. It’s inertia. It’s a spreadsheet. It’s doing nothing. It’s a workaround that’s good enough.
A productivity app asked this question and discovered that most of their target customers used paper planners. Not because they preferred paper, but because digital tools felt too complicated. The app’s onboarding was designed for people who were already tech-savvy—the customers they wanted to reach needed something simpler.
They simplified setup, added templates for common planning styles, and created a “paper-to-digital” guide. Downloads tripled.
How to use it: Ask this question to understand what you’re really competing against. Then position your solution against that reality, not against an imaginary competitor.
Question 4: “What would change if this problem disappeared tomorrow?”
This question uncovers the deeper outcome the customer is seeking. It moves beyond the surface problem to the emotional payoff.
Someone might say they want to save time. But the real answer might be: “I’d be less stressed when I get home. I’d actually enjoy my evenings instead of dreading the pile of chores.”
Someone might say they want to save money. But the real answer might be: “I’d feel in control. I wouldn’t lie awake worrying about bills.”
These deeper motivations are what drive purchasing decisions. Features solve problems. Outcomes sell products.
A financial planning service asked this question. The surface answer was “I’d save more money.” But the deeper answer, which emerged after gentle probing, was “I wouldn’t fight with my spouse about money anymore.” The service shifted its marketing from “grow your savings” to “end money arguments for good.” Conversions increased.
How to use it: Ask this question and then follow up. “Tell me more about that.” “What would that feel like?” “Why does that matter to you?” Keep digging until you reach the emotional core.
Question 5: “What almost stopped you from buying?”
This question is pure gold for conversion optimization. It reveals the objections, hesitations, and fears that nearly kept you from buying.
The answers might be about price. They might be about trust. They might be about timing. They might be about a confusing feature or a missing guarantee.
One e-commerce brand asked this question and discovered that shipping costs were a major hesitation point. Customers would fill their carts, see the shipping fee, and abandon. The brand started offering free shipping over a certain threshold. Cart abandonment dropped by 22 percent.
Another brand found that customers hesitated because they didn’t know what happened after purchase. How long would delivery take? Could they return it? What if they had questions? The brand added a simple “What happens next” section to every product page. Returns dropped, and satisfaction scores improved.
How to use it: Ask this question in post-purchase surveys, in follow-up emails, or in customer interviews. Then address the most common objections directly in your marketing.
Question 6: “What would make this perfect for you?”
This question is dangerous if used poorly. It invites feature requests, and customers will happily list a hundred things they’d like. But used well, it reveals the gap between your current offering and the customer’s ideal.
The key is to follow up on every answer. “Why would that make it better?” “What would that allow you to do?” “What problem would that solve?”
A SaaS company asked this question and got a common answer: “I wish it integrated with my CRM.” When they dug deeper, they discovered the real need wasn’t a specific integration. It was a fear of losing data. Customers worried that switching to this new tool meant abandoning all the history they’d built up elsewhere. The company built an import tool that preserved that history. The CRM integration turned out to be unnecessary.
How to use it: Ask this question, then dig into every response. Look for the underlying need behind the stated request. Feature requests are symptoms. The real need is the disease.
Question 7: “Who else has this problem?”
This question does two things. First, it reveals whether the customer sees the problem as widespread or niche. Second, it gives you warm introductions to other potential customers.
When someone says, “My whole team has this problem,” that’s valuable information. It suggests the problem is systemic and your potential market is large.
When someone says, “You know, my sister-in-law complains about the same thing,” that’s a warm lead. Ask if they’d be willing to make an introduction.
A B2B startup used this question to grow rapidly. They asked every customer who else might benefit from the service. Those introductions converted at a much higher rate than cold outreach. The referral loop became their primary growth channel.
How to use it: Ask this question at the end of customer interviews or onboarding calls. Offer to provide value to the person they mention—a free trial, a helpful resource, an introduction—to make the referral easier.
How to Actually Ask These Questions
Knowing the questions is only half the battle. How you ask them matters just as much.
Ask in the right context. Post-purchase surveys, customer interviews, and casual conversations all have their place. Choose the context based on the depth of answer you need.
Be genuinely curious. Customers can tell when you’re going through the motions. If you’re not genuinely interested in their answers, they won’t give you their best insights.
Listen more than you talk. The best interviewers speak maybe 20 percent of the time. Let the customer carry the conversation.
Follow up with “Why?” and “Tell me more.” The first answer is rarely the most valuable. The gold is in the follow-up.
Take notes and look for patterns. One customer’s comment is an anecdote. Ten customers saying the same thing is a trend. Trends drive strategy.
Close the loop. If you ask customers for their insights, tell them what you learned and what you’re doing about it. This builds trust and encourages future participation.
The Real Secret
The real secret to understanding what customers want isn’t a magic question. It’s the willingness actually to listen.
Most businesses don’t. They survey customers, collect data, and then do what they were going to do anyway. They ask for feedback and then ignore it. They assume they already know what customers want, so they don’t ask.
The seven questions in this article are powerful because they force you to engage with reality. They surface what customers actually think, feel, and need—not what you assume, not what you hope, not what your competitors are doing.
But they only work if you’re willing to hear the answers. Even the uncomfortable ones. Especially the uncomfortable ones.
The feature nobody used? The one that cost me three months? If I had asked these questions before building, I would have saved all that time. I would have known exactly what problem my customers wanted solved. I would have built something they actually wanted.
Don’t make the same mistake. Ask the questions. Listen to the answers. Then build what people actually need.
