Customer Discovery Questions That Find Real Pain

Most customer discovery questions fail before the customer even answers. They fail because they ask for opinions, and opinions about a founder's idea are almost always kind. The questions that work share one trait: they dig into what the person has already done, spent, or suffered. Pain that actually exists leaves a trail of behavior behind it.

Here is a working set of questions organized by what each one is designed to uncover, plus the signals that tell you whether you found real pain or a polite shrug.

Questions that surface the problem

Start wide and stay away from your solution entirely.

• "Walk me through the last time you dealt with [the problem area]. What happened?"
• "What is the most annoying part of your week in this area?"
• "When did this last go badly wrong? What did that cost you?"

You are listening for stories with specifics: dates, names, numbers, consequences. "Last Tuesday our launch slipped two days because of this" is pain. "Yeah, it can be frustrating sometimes" is filler.

Follow the emotion

When someone's tone shifts, when they sigh or laugh bitterly or speed up, pull the thread:

• "You rolled your eyes just now. What is behind that?"
• "That sounds frustrating. How often does it happen?"

Emotion is a flag marking buried pain. Interviewers who stick rigidly to a script drive past these moments; the best material in most interviews is unscripted.

Questions that measure whether the pain matters

A problem can be real and still not be worth solving. These questions separate irritations from priorities.

• "What have you tried to fix this?"
• "What tools, spreadsheets, or workarounds do you use today?"
• "Have you looked for a better way? What did you find?"
• "How much time or money does this eat in a normal month?"

The absence of any attempt to solve the problem is not neutral. It is strong evidence that the pain, however real it sounds in conversation, sits below the threshold where people act.

Questions that reveal the buying reality

Even genuine, prioritized pain does not guarantee a purchase. Someone has to have budget and authority.

• "What do you already pay for in this area?"
• "Last time your team bought a tool, how did that decision get made?"
• "Who else feels this problem? Who would own fixing it?"

These questions do double duty. They test willingness to pay with historical facts instead of hypotheticals, and they map the path a future sale would travel.

Questions to delete from your script

Each of these invites answers that sound like validation and prove nothing:

• "Would you use a product that solved this?"
• "How much would you pay for something like that?"
• "Do you think this is a good idea?"
• "Wouldn't it be easier if you could do this automatically?"

The pattern behind all four: they ask the customer to predict their future behavior or judge your idea. Prediction is guessing and judgment is flattery. If your script leans on these, the fix is not one better question, it is the approach in The Mom Test, with concrete rewrites in our good and bad Mom Test question examples.

Reading the answers

Collecting answers is half the job. Scoring them honestly is the other half. After each conversation, sort what you heard into three buckets:

1. Facts. Things that happened, with specifics. These count.
2. Commitments. Intros made, meetings booked, pilots agreed. These count double.
3. Opinions and compliments. Everything else. These count for zero, no matter how enthusiastic.

Three interviews with bucket one full beat thirty interviews of warm encouragement. If you keep ending calls with empty fact buckets, the problem is usually the questions, or the habit of pitching mid-interview, which we cover in how to avoid pitching in customer interviews.

Putting it together

A discovery interview built from these questions has a simple arc. Open with their world, chase the specifics, measure the workarounds and spending, then close with a small commitment. Your idea never needs to appear.

The uncomfortable truth is that questions like these can kill your idea in a week. That is what they are for. Ideas that survive contact with real pain are the ones worth building, and finding out early is the entire point of validating before you build.