Top 9 'Echo-Chamber-Breaking' Customer Discovery Questions to try for startups before writing a single line of code - Goh Ling Yong
You’ve got it. The next billion-dollar idea. It’s brilliant, it’s innovative, and it’s going to change the world. You can already see the sleek interface, the glowing press releases, and the hockey-stick growth chart. There’s just one tiny, nagging problem: what if nobody else cares?
This is the silent fear that haunts every startup founder. We spend months, sometimes years, passionately building a product in isolation, convinced we’re crafting the perfect solution. But we’re doing it inside an echo chamber, a place where our own assumptions are the only voices we hear. We talk to friends who tell us our idea is "cool," and we mistake politeness for purchase intent. The result is a beautiful, functional product launched to the sound of crickets—a solution in search of a problem.
The cure for this all-too-common ailment is radical, early-stage customer discovery. I’m not talking about focus groups or surveys that ask leading questions like, "Would you use an app that did X?" I’m talking about having real, honest conversations that dig into your potential customers' actual problems, workflows, and frustrations. As my colleague Goh Ling Yong often says, the most valuable insights for your business aren't found in a spreadsheet; they're found in the stories of your customers. The goal is to break out of the echo chamber before you write a single line of code.
Here are the nine 'echo-chamber-breaking' questions that will help you uncover the truth and build something people actually want.
1. "Can you tell me about the last time you dealt with [the problem area]?"
This is the golden key that unlocks customer discovery. Instead of asking a hypothetical question about the future, you are grounding the conversation in a real, specific, past experience. People are terrible at predicting their future behavior but are fantastic storytellers about things that have already happened.
This question immediately shifts the dynamic. You're no longer a salesperson pitching an idea; you're a therapist or a journalist, genuinely curious about their life and their struggles. It forces them to give you concrete details—names, dates, emotions, and specific actions. This is where you find the unvarnished truth about the problem you think you're solving.
What to listen for: Listen for emotion. Do they sound frustrated, angry, or resigned when they recount the story? If they struggle to even remember the last time they faced this problem, or if they describe it with a shrug, it’s a massive red flag. A problem worth solving is a problem that’s memorable.
2. "What have you already tried to do about it?"
This is arguably the most important question in the entire customer discovery process. It’s the ultimate validation test for whether a problem is a real, burning pain or just a minor annoyance. If the problem is painful enough, people will have already tried to solve it. They’ve cobbled together a solution, even if it's a messy one.
Their answer reveals two crucial things: first, that the problem is real enough to warrant action, and second, who your real competitors are. Your competition isn't just other startups; it's a combination of spreadsheets, Google Docs, a part-time intern, or just plain old manual grunt work.
Example in action: If you're building a tool to automate social media scheduling for small businesses, and a potential customer says, "Oh, I haven't really done anything about it, I just post when I remember," the pain isn't acute enough. But if they say, "Ugh, it's a nightmare. I have a massive spreadsheet with dates, another Google Doc with captions, and I pay a freelancer for three hours a week just to get the images formatted," you've found a real, quantifiable pain point.
3. "What was the hardest part about that process?"
People often describe a problem in broad strokes, but the value of your product lies in solving the most specific, frustrating details. This question helps you drill down past the surface-level complaint to find the core of the frustration. Is the hard part that it takes too much time? That it's too complicated? That it requires collaborating with difficult people?
The answer to this question helps you define your unique value proposition. You might think the problem with expense reporting is filling out the forms, but after asking this question, you might discover the hardest part is actually finding the receipts in the first place. That single insight could completely change your product's focus from a "better form" to a "magic receipt finder."
Tip: Don't be afraid to ask follow-up questions like "Why was that hard?" or "What made that part so frustrating?" Keep digging until you get to the root emotion or bottleneck. The gold is usually buried a few layers deep.
4. "If you had a magic wand, what would your ideal solution look like?"
This question is a powerful way to understand a user's desired outcome without leading them toward your specific solution. By framing it as a "magic wand," you give them permission to think beyond the constraints of existing technology and describe their perfect world.
This isn't about getting feature requests. In fact, you should largely ignore specific feature requests ("I want a blue button that does X"). Instead, you're listening for the outcome they describe. Do they say, "I would never have to think about this again"? Or, "All the information I need would just appear on one screen"?
What you're listening for: Listen for the verbs and the feelings they use. "It would automatically sync...", "I would feel confident that...", "It would eliminate the need to talk to Bob from accounting." These are the core desires your product should tap into. This question uncovers the "job to be done" from the customer's perspective.
5. "Walk me through your current workflow for this."
This is a more active version of "What are you currently doing?" Instead of just getting a summary, you're asking them to be your guide and show you, step-by-step, how they handle the task right now. This is where you'll discover all the little hacks, workarounds, and inefficiencies they might not even think to mention.
As they walk you through their process, you’ll see where they get stuck, which steps take the longest, and what "unofficial" tools they use (like sticky notes, personal notebooks, or a specific browser extension). These are all opportunities for your product to add value.
Pro-Tip: If possible, do this over a screen share. Ask them to literally show you the spreadsheet, the software, or the chain of emails they use. You will see things they would never think to tell you. This firsthand observation is priceless and will give you a deeper empathy for their situation than a simple description ever could.
6. "What are the consequences if you get this wrong or don't solve it?"
This question helps you quantify the pain and determine if you're building a "vitamin" (a nice-to-have) or a "painkiller" (a must-have). If the consequences of inaction are minimal, people will be less motivated to seek out, pay for, and adopt a new solution.
The answer will help you understand the true cost of the problem. Is it a financial cost (e.g., "We could face a fine of up to $10,000")? A time cost (e.g., "I have to stay late for three nights at the end of every quarter")? Or an emotional cost (e.g., "I constantly worry that I've forgotten something critical")?
How to frame your marketing: The answers to this question are pure gold for your future marketing copy. When you understand the deep-seated fears and negative consequences associated with the problem, you can speak directly to them on your landing page and in your sales pitches, positioning your product as the ultimate painkiller.
7. "Who else on your team is involved in this process?"
For any B2B startup, this question is non-negotiable. You rarely sell to a single individual; you sell to an organization. Understanding the entire ecosystem around the problem is crucial for both product development and your go-to-market strategy.
This question helps you map the stakeholders. Who provides the inputs for this task? Who has to approve the outcome? Who has to clean up the mess if it goes wrong? You’ll start to uncover the difference between the end-user (the person who feels the pain most acutely) and the economic buyer (the person who signs the check). Your product needs to satisfy both.
Example: You might be building a tool for graphic designers (the users), but their manager (the buyer) is the one who cares most about tracking project hours and budget. Your discovery process must include conversations with both personas to build a solution that gets adopted and paid for.
8. "Have you ever allocated a budget to solve this? What would you expect to pay?"
Talking about money can be awkward, but it's one of the most effective ways to break through the echo chamber of polite encouragement. People will happily tell you your idea is "great," but their wallets tell the real story. Asking if they've ever spent money on the problem before is a strong indicator of their willingness to pay.
If they say "zero," it's a cause for concern. If they say, "We hired a consultant for $5,000 to build a custom spreadsheet," you know there's a real budget and a high perceived value for a solution.
A softer approach: Instead of asking directly "What would you pay?", you can frame it as, "What do other tools you use for your business typically cost?" This anchors the conversation and gives you a sense of their existing software budget and price sensitivity. If they're used to paying $10/month for tools, a $200/month product will be a tough sell, no matter how good it is.
9. "Based on our chat, what do you think I'm missing?"
This is a fantastic question to end the interview with. It shows humility, respects their expertise, and turns the interview into a collaborative session. It gives them the floor to correct your assumptions and bring up crucial points you didn't even know to ask about.
Often, the most valuable insight of the entire conversation comes from the answer to this final question. They might say something like, "You're focused on the time-saving aspect, but for us, the real issue is compliance," or "You haven't asked about how this integrates with Salesforce, which is everything to us."
Why it works: This question breaks the final wall of the echo chamber—your own internal biases about what's important. It invites the customer to be your co-founder for a moment, guiding you toward the truth you need to hear, not just the one you want to hear. This is the kind of insight that Goh Ling Yong and other seasoned builders know is critical for avoiding major strategic mistakes down the line.
The Truth Will Set Your Startup Free
Conducting customer discovery isn't about seeking validation for your brilliant idea. It's about a relentless search for the truth. The goal isn't to hear, "Yes, I would buy that." The goal is to deeply understand a customer's world—their pains, their workflows, their fears, and their desired outcomes.
These nine questions are not a rigid script, but a framework for genuine curiosity. They are designed to make you listen more than you talk. They will feel uncomfortable at first, and sometimes the answers will be brutal. You may learn that the problem you're obsessed with is a minor inconvenience for everyone else. That's not failure; that's a gift. That's a discovery that saves you years of wasted effort.
So before you register that domain name, before you design that logo, and certainly before you write a single line of code, get out of the building. Talk to people. And ask them the right questions.
What are your favorite "echo-chamber-breaking" questions? Share your go-to customer discovery gems in the comments below!
About the Author
Goh Ling Yong is a content creator and digital strategist sharing insights across various topics. Connect and follow for more content:
Stay updated with the latest posts and insights by following on your favorite platform!