Customer Discovery Interviews: How to Learn What Buyers Actually Need

“That sounds great” is one of the easiest answers to get in a customer interview. It’s also one of the least useful. People are often polite about an idea they won’t buy, especially when the person asking seems attached to it. A better conversation begins with the last time the customer faced the problem. What did they try, and what happened?

Customer discovery interviews are useful when you’re willing to hear something inconvenient. Ask about a real decision the person made recently. Find out what got in the way. Then check whether the story lines up with what people actually do.

Nielsen Norman Group’s guide to user interviews explains an important limit. People may remember an experience imperfectly, and what they say they will do can differ from what happens. That means the interview is a clue to investigate, not permission to redesign the whole business after one conversation.

Decide What You Need to Learn

Go in with a question about a real problem. If people are visiting a service page but rarely asking for a quote, find out what happened in a recent buying decision. Did they understand the offer? What made them keep looking?

Don’t walk in with a proposed fix and ask whether they like it. The purpose of the interview is to learn what you missed before deciding what to build.

Speak to People Who Made the Decision

If you only interview happy customers, you’ll mostly hear why your service worked for them. Speak to someone who considered the offer and chose another way forward. Ask about a recent decision while the details are still fresh.

Friends and colleagues can help you rehearse questions. They usually can’t replace real buyers. They know your intentions and may overlook problems that a stranger would notice immediately.

Ask About the Last Time, Not the Perfect Future

“Would you use a dashboard that did this?” is easy to answer politely. “Tell me about the last time you needed that information” is harder to fake. The second question asks for a real moment instead of an imaginary one.

Listen to what happened next. Did they try another tool? Did somebody else need to approve the work? Ask them to show you the process when that’s possible and appropriate. A live demonstration can reveal details they would never think to mention.

People still forget things, so keep the limits of what you learned in mind. Use an interview to decide what deserves another look, then test your idea against actual behavior.

Listen without supplying the answer

It’s hard to interview somebody about an idea you care about without nudging them toward it. “Would faster reporting make this easier?” tells the person that speed is the problem. “What happened the last time you needed that report?” gives them room to explain it themselves.

They may have been waiting for an approval or trying to work out which numbers to trust. Let them finish the story before offering the feature you were hoping they’d ask for.

The Workaround Is Often the Interesting Part

When someone says a booking process is difficult, ask what they do instead. Do they telephone the business? Do they leave the page and come back later? Those answers may point somewhere other than the form everyone wants to redesign.

Ask them to walk through a recent experience. If they can show what happened without revealing private information, even better. Pay attention to the part where they switch tools or wait for somebody else. That interruption often tells you more than an answer to “What features would you like?”

Write down their explanation in their own words. Don’t interrupt to pitch a solution. You’ll have time to interpret the story afterward.

Pay attention to the words they choose

Customers rarely learn your internal terminology before they start looking for help. If several people describe the same difficulty in plain words that never appear on your service page, read the page again. You might be answering a question they weren’t asking.

Keep the phrases in your notes, then check whether they describe the problem accurately and appear in real searches. Don’t paste an interview quote into a headline just because it sounds more conversational. Use it to improve the explanation wherever people make their decision.

Keep what happened separate from what you think it means

Write down what the person said or did. Save your explanation for a separate note. If somebody visited the pricing page and went back to search, that tells you where they went. It doesn’t tell you why. The options might have been confusing, or they might have wanted to compare another provider first.

This distinction is easy to lose when a team already has a favored solution. Keeping it visible makes the next interview or page test more useful. You can investigate the explanation instead of treating it as something the customer proved.

Find Patterns Without Cherry-Picking the Quotes

After five interviews, it’s tempting to find the sentence that best supports the team’s favorite idea. Try the opposite. Put the observations next to each other, including the awkward ones that don’t fit.

If pricing keeps coming up, find out which part people struggled to understand. Timing may matter just as much to a different buyer. Neither concern tells you what most visitors think if you only spoke with a few existing customers, but both give you something worth checking.

Look at who was interviewed, what situation they were in and whether the same behavior appeared independently. A repeated workaround or a question that stalls a purchase deserves follow-up. So does a genuine disagreement between customers: it may reveal different audiences or circumstances rather than somebody being wrong.

For decisions involving several teams, the same discipline applies. Our guide to collective intelligence explains why gathering independent views before a group discussion can reveal missing evidence.

Find One Assumption Worth Testing

Interview notes become useful when they change a decision. Put the customer’s words beside your interpretation, then ask what evidence could prove you wrong. It’s easy to hear a complaint about pricing and decide the website needs a new design. The real issue could be that people can’t tell which service fits them.

Start with the smallest test that can answer that question. If several people struggle with the same explanation, improve it and see how real visitors respond before replacing the entire site. CMX’s website development services cover implementation when the finding points to a site change.

Use analytics to test what the interviews suggest

If interviewees struggle with a question on your booking form, check what happens on the live page before redesigning it. Analytics may show that visitors often leave at that step, but they won’t tell you whether the wording, the price or a technical error drove them away. Try the form yourself and look at the conversations alongside the numbers.

Search Console can help you investigate phrases people used in interviews, too. Check which pages appear for those searches and what visitors find when they arrive. A few interviews can point you toward a problem; broader data helps you judge how often it occurs. Neither source can answer every question on its own.

Customer Discovery Interview Questions That Reveal What Happened

You do not need to ask all of these. Choose the ones that match the research question.

• What was happening when you first realized you needed help?
• What had you tried before this?
• How did you look for a solution?
• What information mattered most while comparing options?
• What made you hesitate?
• What nearly stopped you from moving forward?
• Who else was involved in the decision?
• What happened after you chose a solution?
• What still feels difficult today?

Be Willing to Dislike the Answer

A good interview may show that the feature your team loves is not the problem customers are trying to solve. That’s useful. It can save a surprising amount of work.

The next step is to check whether the behavior appears beyond the people you interviewed. If it does, make a change you can test. If it doesn’t, keep listening before you commit the business to somebody else’s guess.