Customer development, the simple version: how to talk to users without lying to yourself

Most founders ask leading questions, get polite answers, and ship the wrong thing. Customer development is the discipline of talking to users in a way that actually teaches you something. It is not surveys, not focus groups, not pitching them on what you wish were true. It is a small set of habits that make a thirty-minute conversation worth more than three months of guessing. This lesson is the basics version.

The core problem is almost embarrassing once you see it: people are nice. If you ask them whether they would use your product, they will say yes, especially if you look excited. The yes feels like data. It is not. It is friendliness. The whole point of customer development is to ask differently, so the truth has somewhere to come out.

// 01Why founders ask leading questions and don’t realize it

A leading question is one that hints at the answer the asker wants to hear. Most leading questions feel completely innocent. The cost is that the answers are completely useless.

• Asking about the future: "Would you use a tool that does X?" The honest answer is "I have no idea, I am not in that situation right now." The polite answer is "yes, sounds great." Future-tense questions get the polite answer.
• Pitching, then asking: "We are building a tool that solves Y. Do you think that is a real problem?" Your enthusiasm is the question; their compliment is the answer. Nothing was learned.
• Asking for advice instead of stories: "What features should we build?" Customers are not product managers; their guesses about what they would want are weaker than their stories about what they have actually done.

// 02The Mom Test, in five rules

Rob Fitzpatrick’s book The Mom Test is the reference for this; the title comes from the idea that even your mother, who would never want to discourage you, can give you useful information if you ask the right kind of question. The rules condense to five.

• Talk about their life, not your idea: You learn nothing by describing your product. You learn a lot by listening to how they currently spend their time on the problem you think you are solving.
• Ask about specifics in the past, not generics in the future: "Walk me through the last time you needed to do X" beats "How often do you do X?" by an order of magnitude.
• Talk less, listen more: A useful interview has the customer talking 80% of the time. If you find yourself explaining things, the conversation has already gone wrong.
• Listen for what they have already paid for or done: Time, money, and effort already spent are the strongest signal of how real a problem is. Words alone are cheap.
• Look for emotion: Frustration, embarrassment, urgency, relief: these are the markers of a real problem. Calm acknowledgment that "yes, that is annoying" usually is not.

// 03Problem interviews vs solution interviews

Two different conversations, run for two different purposes, often confused.

• Problem interview: Used to figure out whether a problem is real, how often it occurs, who has it, and what people are doing about it now. The product is barely mentioned. The customer does most of the talking. Run these first.
• Solution interview: Used to figure out whether your specific solution makes sense to a person who has the problem. You show a sketch, a prototype, or a description, and watch their reaction. Useful only after you know the problem is real.

The most common mistake is doing solution interviews before problem interviews. You find out people like your idea before you have evidence that the problem is worth solving. That is exactly the order in which products fail expensively.

// 04Who to talk to and how to find them

You do not need a research firm. You need access to ten people who fit the customer description you wrote in lesson 2. Here are the ways founders actually find them, in rough order of effectiveness.

• People you already know: A friend of a friend who fits. The fastest way to start. The trade is that they may try harder to be encouraging; ask the questions in past tense to compensate.
• Communities they already participate in: Subreddits, Slack groups, Discord servers, niche forums. Be present long enough to be a member, not a recruiter, then ask politely.
• A short note on a platform they use: A LinkedIn message, a thoughtful X reply, an email to a writer whose work matches your topic. A specific, short note works far better than a templated request.
• Cold outreach with a sharp hook: "I am researching how freelance designers handle late invoices and would like to learn from you for 15 minutes" beats "I am building a product, would love your thoughts." Shorter and more honest is better.

Aim for ten conversations before you draw any conclusions. With three people, the noise is too high. By ten, the patterns start to repeat enough that you can trust them. By twenty, you are usually wasting time you should be spending on the next thing.

// 05What to do with what you learn

Notes from interviews are only useful if you do something with them. The most common failure mode is taking thirty pages of notes and never going back to them.

• Write down the verbatims: Quotes, in the customer’s own words. These are the most valuable artifact. They become headlines, onboarding copy, support replies, and the basis for everything that comes next.
• Tag the patterns: After five conversations, look for words and phrases that came up more than once. Five repeated phrases will tell you more than the same number of survey responses ever could.
• Notice what surprised you: A surprise is a small explosion of new information. If a customer described the problem in a way you had not considered, that is the most valuable sentence in the interview. Write it where you will see it again.
• Update the customer description: You wrote a paragraph about who your customer is. After ten interviews, rewrite it. The new version will be more specific, more accurate, and more useful than what you started with.

// 06Five things to carry forward

• 01: People are polite. Polite answers are not data. The whole job of customer development is to ask in a way that makes the truth easier to share than the polite answer.
• 02: Stop asking about the future. Ask about the past. "Walk me through the last time" is the most valuable phrase in customer research.
• 03: Run problem interviews before solution interviews. Verifying that a problem is real comes before checking that your solution looks good.
• 04: Ten conversations is the sweet spot. Three is too few; twenty is procrastination. Find the patterns, then act on them.
• 05: Verbatims, surprises, repeated phrases. Those are what you mine from interviews. They become the words on your homepage and the features that actually matter.

At this point you have a customer in mind, an approach to growth, a sense of how product and growth work together, and a way to learn directly from the people you are trying to serve. The next lesson takes everything in the series so far and turns it into a starter playbook: how to actually go from idea to your first ten paying customers.