Customer Interviews That Find Real Problems in 2026
- What good customer interviews actually mean
- The common mistake teams make
- The Mom Test rules in practice
- How to practice this as a daily habit
Customer interviews are a cornerstone of product development, but many teams still struggle to extract actionable insights from these conversations. Often, they focus on what users say rather than what they actually do. The Mom Test by Rob Fitzpatrick, published in 2013, highlights this disconnect and introduces a framework that can fundamentally change how we approach customer interviews. In 2026, as we strive for deeper understanding of our users, it's crucial to apply these principles to discover real problems rather than just seeking validation for our ideas.
What Good Customer Interviews Actually Mean
At their core, customer interviews should be about uncovering truths—what users actually do, the specific challenges they encounter, and the measures they take to address those challenges. When done correctly, the output is not validation but valuable signal. This signal can sometimes lead to difficult conclusions, such as the need to abandon an idea. However, this is a hallmark of effective interviews.
Unfortunately, many interviews masquerade as sales pitches. Questions like "Would you use a product that does X?" or "Do you think this would be valuable?" typically yield polite, affirmative responses that do not correlate with actual behavior. In contrast, the Mom Test approach emphasizes inquiry about past actions. Questions that probe users’ historical behavior elicit honest answers, as they cannot fabricate their past actions.
A compelling example illustrates this point. A founder testing a B2B fintech concept conducted two rounds of interviews. The first round relied on traditional framing, resulting in 18 out of 20 interviews responding positively—an encouraging but ultimately misleading outcome. The second round, however, focused on past behavior. By asking questions like, "Walk me through how you handled this last quarter," and "What was the worst part?" the team learned that while users had a real problem, they had developed workable solutions and were not compelled to switch to the new product. This critical insight saved the team from investing four additional months in a product that lacked sufficient demand.
The Common Mistake Teams Make
Many teams fall into the trap of asking leading questions, erroneously labeling them as research. Questions like "Do you think bulk export would be useful?" may elicit enthusiastic agreement, but they don’t drive towards the truth. As a result, teams feel validated, only to watch their products fail at launch.
Another prevalent mistake is pitching during the interview. Interviewers often become excited about their ideas, inadvertently selling instead of probing. This dynamic leads interviewees to agree out of politeness, transforming the session into a confirmation theater.
Additionally, teams often lean on hypothetical questions about the future rather than focusing on factual past behavior. Asking, "Would you pay for this?" invites speculation; however, "Have you paid for anything to solve this problem before?" anchors the conversation in reality. People are generally poor predictors of their own behavior, while their past actions offer reliable insights.
Lastly, failing to push for specifics can derail the interview process. General answers like "we're trying to grow" do little to inform product direction. In contrast, specific responses such as "we lost two enterprise deals last quarter due to a six-week security review" provide actionable insights. It is the interviewer’s responsibility to dig deeper until they arrive at concrete information.
The Mom Test Rules in Practice
To conduct effective interviews, adhere to three fundamental rules:
-
Ask About Specific Past Behavior, Not Future Intent. Shift from "Would you use this?" to "Have you tried that?" Replace "Do you think this is a problem?" with "What was the last time this came up?" This transition from future hypotheticals to past realities elicits more honest responses. The question "Walk me through the last time you tried to solve X" is particularly effective.
-
Ignore Opinions About Your Product; Hunt for Problems and Behavior. Even if interviewees express positive opinions about your product, redirect the conversation to their actual experiences. Instead of focusing on what they think about your idea, ask about their past needs and solutions. Opinions often cloud the truth, while behavioral data provides clear signals.
-
Get Specific by Asking "Tell Me More" Three Times. Initial answers may be surface-level. To uncover deeper insights, follow up with three additional questions: "What happened next?" and "How did you feel about that?" This practice helps you reach the core of the user's experience, allowing you to gather more useful data.
For broader insights on how to integrate these interviews into your discovery process, check out resources on product discovery basics and research synthesis tips.
How to Practice This as a Daily Habit
Customer interviews should not be relegated to occasional projects; they need to become a regular practice for teams committed to delivering products that genuinely resonate with users. Aim for one customer conversation per week. This doesn’t have to be a formal research project; even a 30-minute chat can yield significant insights.
By consistently applying the Mom Test rules, you can build a library of knowledge about your customers. Take notes during each interview and write up your takeaways within 24 hours while the information is still fresh. Over time, the cumulative effect of fifty structured conversations will provide a depth of understanding that far surpasses sporadic research projects.
Adopt a micro-learning principle: focus on improving one aspect of your interviewing skills each week. For instance, concentrate on asking three follow-up questions to elicit specifics. The next week, work on avoiding the urge to pitch your product. Gradually, you'll build the interviewing muscle necessary to uncover meaningful insights.
What Good Looks Like
You’ll know your interviews are effective when your assumptions begin to shift productively. Here are some specific indicators:
- You consistently leave interviews with new insights rather than mere validation. Sometimes, interviews will challenge ideas you were excited about, but that’s beneficial—better to discover a flaw now than after launching.
- You start hearing repeated phrases from various users, such as "we waste hours on this" or "this part is the worst." These insights signal areas where you should focus your efforts and may even inform your marketing language down the line.
- The conversational dynamic shifts; interviews become about the users’ experiences rather than your product. Users appreciate discussing their challenges, and both parties end up enjoying the process.
As your understanding deepens, your product roadmap will naturally evolve. Features that initially seemed promising may get replaced by solutions to the most pressing user problems, leading to a sharper, more relevant product.
The One-Sentence Version
Customer interviews that work ask about specific past behavior, not opinions about the future—what people did is signal, what they say they would do is noise.
If you want to master the art of customer interviews without overwhelming your schedule, take the Omie Skill Assessment. You'll receive tailored lessons designed to help you excel based on your unique role and goals.