How to run a customer interview that gets past “would you use it?”
A nine-step guide to discovery interviews that ask about past behaviour, so you get facts you can use instead of polite yes answers.

People are polite. Ask “would you use it?” and they will say yes. That yes costs them nothing and tells you nothing. This guide is for product managers who run discovery interviews. At the end you will have an interview plan, a set of questions about past behaviour, and a way to tell real signals from polite noise.
- Ask about what people did, not what they think or what they might do.
- Talk to people who had the problem recently.
- Do not pitch your idea.
- Keep facts and opinions apart in your notes.
- Write it up within 24 hours.
Why a polite yes is useless
Opinions about the future are cheap. A person can say they would use your product, or pay for it, and nothing changes in their week. Past behaviour is different. It already happened, and it left traces: time spent, money spent, a workaround built.
This is the idea behind Rob Fitzpatrick’s book The Mom Test. Ask about the past and the person has nothing to be polite about. They just tell you what happened. The nine steps below put that idea into practice.

Set a learning goal
Write down the three things you need to learn from this round of interviews. Three, not ten. Every question you ask should help answer one of them. If a question serves none of the three, cut it.
This list is the core of your interview plan. If you want help turning it into questions, PikoPM’s Interview guide is there for that.
Recruit people who had the problem recently
Recent matters. Someone who dealt with the problem last week can tell you what happened. Someone who met it two years ago will give you a tidy summary and some guesses. Pick people for what they have done, not for how friendly they are.
Open with why you are talking to them
Say plainly why you asked for their time: you are trying to understand how they handle a certain part of their work. Say you are learning, not selling. This sets the tone. They know what kind of answers help, and they know they are not being tested.
Ask about the last time it happened
Your main question is a simple one: “Tell me about the last time you …” and then the situation. It asks for a story, and a story has details. “Is this a problem for you?” gets an opinion. “Tell me about the last time” gets an event.
Dig into what they did, what it cost, what they tried and what they paid
Once you have the story, follow it. Four things are worth chasing:
What they did. Step by step, in order.
What it cost them. Time, money, stress, delays.
What they have tried. Tools, habits, other people.
What they paid. Real money, not hypothetical money.
Keep asking “and then what?” until the story runs out.

Do not pitch your idea
The moment you describe your idea, the person starts reacting to it. They will be kind. They will say it sounds useful. You will leave happy and no wiser. Keep the idea to yourself until the interview is over, and if they ask, say you would rather hear about their experience first.
Separate facts from opinions in your notes
Draw two columns. Facts go on the left: what they did, what it cost, what they paid. Opinions go on the right: what they feel, what they think they would do. Later, give the left column the most weight. The right column can still be useful, but it is the weaker evidence.
End by asking for an introduction or a next step
Close by asking for something: an introduction to someone else who has the same problem, or a follow-up conversation. It is a small test. People who care about the problem will say yes. People who were only being nice will go vague.
Write it up within 24 hours
Memory fades fast and tidies itself. Write up the interview within 24 hours, while you still remember the odd details. Keep the two columns. Then check the notes against the three things you set out to learn.
Swap the questions
Most bad questions have a better version that asks about the present or the past. Three swaps to keep next to your plan:
| Instead of | Ask |
|---|---|
| “Would you use X?” | “How do you handle this today?” |
| “How much would you pay?” | “What do you spend on this now?” |
| “Is this a problem for you?” | “When did this last happen?” |
Real signals and polite noise
After a few interviews you need to decide what counts. Two things are real. One: they already spend time or money on the problem. Two: they built a workaround. A person who made a spreadsheet to get around a gap has told you more than a person who said “great idea”.
A worked example
This example is illustrative. It is not a real interview. Say you are interviewing a finance manager about expense reports.
“Would an app that reads receipts automatically help?”
“Yes, definitely.”
You learn nothing. It is a compliment about your idea.
“Walk me through last month’s expense close.”
She spent two days chasing missing receipts from 14 people. She keeps a shared spreadsheet to track them. She tried a reminder bot, and everyone muted it.
Now look at what the good answer holds. She spends two days on it each close. She built a workaround, the spreadsheet. She tried a fix, the bot, and it failed. All of these are signals.
It also changes the problem. The real pain is chasing people, not reading receipts. The app in the bad question would have solved the wrong thing, and she would have said yes to it anyway.
Before your next interview
- I wrote down the three things I need to learn.
- The person had this problem recently.
- I have an opening that says why we are talking.
- My main question starts with “Tell me about the last time”.
- I have follow-ups on what they did, what it cost, what they tried and what they paid.
- I will not pitch my idea.
- My notes have two columns: facts and opinions.
- I will ask for an introduction or a next step.
- I have set aside time to write it up within 24 hours.


