Discovery & Research 4 guests | 11 insights

Mastering Customer Interviews

Uncover deep user pain and behavioral triggers to build products people actually need.

The Guide

5 key steps synthesized from 4 experts.

Recruit and schedule a high volume of participants

Aim for a high density of feedback by conducting 30 to 75 interviews in a short window. Use specialized scheduling tools to reduce friction and maintain a continuous interviewing cadence.

Featured guest perspectives

"We did a lot of interviews with CFOs, heads of procurement, heads of finance (I think the exact number is around 75), and over the span of two to three weeks. It really helped refine that idea. We had like 110 pages of notes or something in those two or three-ish weeks. Turns out the response rate is pretty good on LinkedIn when you just want advice."

— Lenny Rachitsky

"Talk to many (ideally 100+) people from this segment. Identify a major pain point that you can solve. . . If you go after something that isn’t a major pain point for people, your product will struggle."

— Lenny Rachitsky

Design a behavior-focused interview guide

Draft an unbiased script using open-ended questions that avoid mentioning your solution. Focus on the 'magic wand' question to move beyond features and uncover critical unmet needs.

Featured guest perspectives

"However, we realized our first several “interviews” were actually sales pitches (e.g. “here’s this cool new thing, what do you think?”). Far too biased to get any real signal."

— Lenny Rachitsky

Reconstruct the user timeline

Deep dive into the customer's history to identify the specific context and triggers for their actions. Focus on the 'struggling moment' to understand why they might switch from a current solution.

Featured guest perspectives

"And so the real heart of the method of Jobs to Be Done is understanding the causation of what pushes people to say, 'Today's the day I got to do something different.'"

— Bob Moesta

"Pick the people you talk to carefully. Figuring out the target audience for your product is very much part of this search, so be careful getting discouraged by talking to the wrong group of people."

— Lenny Rachitsky

Observe and record raw reactions

Watch users interact with their current tools or your prototype without intervening. Record and re-listen to calls to internalize exact quotes and catch subtle emotional signals.

Featured guest perspectives

"Don’t just read reports from researchers on your team; instead attend user research sessions to get firsthand exposure to user experiences and reactions. What’s important is to pay attention to micro details and ask yourself why people react to your product the way they do."

— Lenny Rachitsky

"Talk to many (ideally 100+) people from this segment. Identify a major pain point that you can solve. . . If you go after something that isn’t a major pain point for people, your product will struggle."

— Lenny Rachitsky

"Don’t ask users if something is working—watch them do it. That will give you a much better sense of their pain points."

— Lenny Rachitsky

Synthesize patterns and seek counterfactuals

Interview between 7 and 14 people per segment to find the sweet spot where learning is maximized. Look specifically for data that disproves your assumptions or reveals segment-specific friction.

Featured guest perspectives

"Avoid availability or confirmation bias. Most of the time people go talk to the people they always talk to and they learn nothing particularly new. They don't synthesize the results that they got from that conversation. They don't seek out the counterfactual, they don't seek out the proof that they're wrong."

— Shaun Clowes

Get this guide as an AI skill for Claude Code

Install This Skill

Add this skill to Claude Code, Cursor, or any AI coding assistant that supports Agent Skills.

Quick Install (Recommended)

Install this skill directly using npx:

npx skills add RefoundAI/lenny-skills --skill customer-interviews

Or install all 76 skills:

npx skills add RefoundAI/lenny-skills

View on GitHub →

Manual Installation

Download the skill

Download Skill (.zip)

Add to your project

Create a folder in your project root and add the skill file:

.claude/skills/customer-interviews/SKILL.md

Start using it

Claude will automatically detect and use the skill when relevant. You can also invoke it directly:

Help me with mastering customer interviews

Guest Perspectives

Deep dive into what 3 podcast guests shared about mastering customer interviews.

Bob Moesta 1 quote

Listen to episode →

"And so the real heart of the method of Jobs to Be Done is understanding the causation of what pushes people to say, 'Today's the day I got to do something different.'"

Tactical:

Deep dive into the 'struggling moment' to identify the specific context that makes seemingly irrational behavior rational.
Reconstruct the timeline of events leading up to a purchase to find the true 'push' from the previous solution.
Identify the 'four forces' during interviews: the push of the situation, the pull of the new solution, the anxiety of change, and the habit of the present.

View all skills from Bob Moesta →

Jag Duggal 1 quote

Listen to episode →

"You make sure that you focus on customer discovery before you start building. You make sure that that discovery is focused not simply on asking the customer, but on innovating on their behalf."

Tactical:

Conduct thorough customer discovery before any engineering resources are committed.
Observe users in their natural environment to find pain points they might not explicitly notice.
Borrow research techniques from various industries to find new ways to innovate on the customer's behalf.

View all skills from Jag Duggal →

Shaun Clowes 1 quote

Listen to episode →

"Avoid availability or confirmation bias. Most of the time people go talk to the people they always talk to and they learn nothing particularly new. They don't synthesize the results that they got from that conversation. They don't seek out the counterfactual, they don't seek out the proof that they're wrong."

Tactical:

Interview between 7 and 14 people to find the sweet spot where learning is maximized before hitting diminishing returns.
Actively seek out counterfactuals and proof that your hypothesis is wrong during synthesis.
Compare actual product usage data against what customers tell you in conversations to find discrepancies.

View all skills from Shaun Clowes →