Customer interviews for product validation in a B2B setting are structured conversations with target buyers, users, and economic decision-makers designed to validate or invalidate product hypotheses before significant engineering investment — minimizing the risk of building something that doesn't solve a real business problem.
According to Lenny Rachitsky on Lenny's Podcast, the biggest mistake PMs make in customer interviews is asking users what they want instead of understanding what they're trying to accomplish. Features are solutions — your job is to understand the problem so deeply that the right solution becomes obvious.
According to Gibson Biddle on Lenny's Podcast, the best customer research at Netflix was never about asking users to design features — it was about understanding the emotional states that led to behavior: boredom, anticipation, the desire to share. Understanding the emotion, not the feature request, led to the best product decisions.
According to Chandra Janakiraman on Lenny's Podcast, in B2B settings the person who uses the product every day is often not the person who buys it — which means you need to interview both to understand the full adoption and retention picture.
Why B2B Customer Interviews Are Different from B2C
B2B validation interviews are more complex because:
- Multiple stakeholders: You need to interview the champion user AND the economic buyer AND the admin separately
- Professional context: Users are measuring product success by business outcomes, not personal delight
- Permission to interview: You need to navigate scheduling, NDA requirements, and competitive sensitivity
- Advocacy vs truth: Happy customers overstate how much they use the product; churned customers are the most honest
Problem Interview: A customer interview focused exclusively on understanding the problem, the existing workarounds, and the emotional cost of the pain — without mentioning your solution — to avoid confirmation bias.
The 5 Types of B2B Product Validation Interviews
Type 1: Problem Discovery Interviews
Goal: Validate that the problem is real, frequent, and painful. Who: Target customer who fits the ICP but hasn't used your product yet. Key questions: "Walk me through the last time you had to deal with [problem area]." "What do you currently do to address it?" "What's most frustrating about that approach?"
Type 2: Prototype/Concept Validation Interviews
Goal: Test a specific solution concept before building it. Who: Mix of existing customers and prospects. Key questions: "I'm going to show you a concept — tell me what you think it does." "Where would this fit in your current workflow?" "What would prevent you from using this?"
Type 3: Onboarding Friction Interviews
Goal: Identify where new customers struggle to reach the aha moment. Who: Users who signed up in the last 30 days, with and without successful activation. Key questions: "Can you walk me through your first experience with the product?" "What was the first moment you felt like it was working for you?" "What almost made you give up?"
Type 4: Retention and Expansion Interviews
Goal: Understand what drives customers to stay and expand. Who: Long-term customers (>12 months) who have expanded usage. Key questions: "What would need to change for you to reduce usage?" "What has been the most valuable thing the product has done for your team?" "What's missing that you wish we had?"
Type 5: Churn Interviews
Goal: Understand the real reasons customers left. Who: Customers who cancelled in the last 30-60 days. Key questions: "What triggered the decision to cancel?" "What would have needed to change for you to stay?" "What are you doing instead?"
Best Practices for B2B Interview Execution
Recruitment
- Interview 5-8 users per segment per question — beyond 8, diminishing returns on new insights
- Recruit churned customers through CS and sales — they are underrepresented in most research programs
- Avoid recruiting only your happiest customers — they'll validate your assumptions, not challenge them
Question Design
- Open with "Tell me about a recent time when..." — behavioral questions elicit stories, not opinions
- Never mention your feature idea until the final 10 minutes — protect against confirmation bias
- Use the "5 Whys" technique: ask "why?" to every answer at least twice to get to root cause
- Avoid leading questions: "Would you use this?" → "How would you currently handle [workflow]?"
Note-Taking and Synthesis
- Record with permission (transcription tools: Otter.ai, Grain)
- Write synthesis notes within 24 hours — memory decays quickly
- Use affinity mapping to cluster insights across interviews into themes
- Report insights as behavioral patterns, not feature requests: "Users spend 45 minutes/week on X" not "Users want a button to automate X"
Common Pitfalls to Avoid
- Interviewing only power users: They've adapted to your product's limitations; they'll miss the friction that kills new users
- Asking hypothetical questions: "Would you buy this for $99?" is not predictive — behavior in hypothetical scenarios differs from real behavior
- Over-indexing on the last interview: One memorable interview with a strong opinion can distort synthesis — weight patterns across interviews, not individual quotes
Success Metrics for B2B Customer Interview Programs
- 80% of major product decisions have supporting customer interview evidence
- Prototype validation interviews reduce major post-launch pivots
- Onboarding friction interview findings are implemented within one sprint cycle
- Churn interview insights are reviewed in monthly product retrospectives
For more on customer research, visit PM interview prep and daily PM challenges.
Learn more about continuous discovery habits at Lenny's Newsletter.
Frequently Asked Questions
How many customer interviews do you need for B2B product validation?
Interview 5-8 customers per distinct segment per research question. Beyond 8, you hear the same patterns repeatedly with diminishing new insight. Breadth across segments matters more than depth within one segment.
What is the difference between a problem interview and a solution interview?
A problem interview focuses exclusively on understanding the customer's pain, workflow, and existing solutions — without mentioning your product. A solution interview presents a concept or prototype and tests whether it fits the customer's workflow and mental model.
How do you recruit B2B customers for product interviews?
Use CS to identify willing customers across segments. Recruit churned customers via CS or sales contacts. For prospects, use LinkedIn outreach with a specific value exchange (brief, research-only call). Avoid recruiting only happy customers.
How do you avoid confirmation bias in customer interviews?
Never mention your feature idea until the final 10 minutes. Start with open behavioral questions about current workflow. Let the customer describe the problem in their own words before you reveal any solution concept.
How do you turn customer interview insights into product decisions?
Cluster findings into behavioral patterns using affinity mapping. Translate patterns into problem statements: 'Users currently spend X time on Y because Z.' Present to the team as insights, not feature requests, to keep the solution space open.