customer-interviews — Claude Code skill: run better user interviews

---
name: customer-interviews
description: Help users conduct high-impact customer interviews that move beyond surface-level feature requests to identify root emotional frustrations and specific causal triggers.
---

# Mastering Customer Interviews

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

Help the user with mastering customer interviews using insights from 11 guests and posts across Lenny's Podcast and Newsletter.

## How to Help

1. **Define objectives** - Identify the specific problem area or user segment you want to explore before recruiting participants.
2. **Draft the guide** - Create open-ended questions that focus on past behaviors and struggling moments rather than hypothetical opinions.
3. **Synthesize findings** - Analyze interview notes to distinguish between polite encouragement and genuine user pull.
4. **Validate pain** - Evaluate whether the identified problems are painful enough to warrant a new solution or behavioral change.

## Core Principles

### Focus on causal triggers
Bob Moesta: "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.'"

Interviews should uncover the specific events and context that led to a change in behavior. Understanding the struggling moment makes seemingly irrational user choices appear rational.

### Observe unarticulated pain
Jag Duggal: "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."

Effective research goes beyond listening to explicit requests by observing users in their natural environment. This reveals friction points that users may not be able to describe.

### Actively seek disproof
Shaun Clowes: "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."

To avoid confirmation bias, you must intentionally seek out data points that disprove your current assumptions. Learning is maximized when you find counterfactual perspectives.

### Prioritize direct observation
From "How to develop product sense": "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."

Directly observing user behavior provides a firsthand understanding of emotional and functional needs. Research reports often overlook the nuance found in live reactions.

### Avoid the sales pitch
From "Startup to exit: Lessons from a first-time founder": "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."

Running discovery calls as sales pitches prevents honest signals. Use an unbiased script that avoids mentioning your specific solution to see if the customer brings up the problem organically.

### Listen for signs of pull
From "What to do if your product isn’t taking off": "When talking to people, look for two things: pain and pull. Pain tells you there’s an opportunity to solve a problem. Pull tells you that you’re actually solving the problem."

Ignore polite encouragement and look for signs of intense pain. Real pull is evidenced by people paying money or continuing to use a bad prototype despite its flaws.

## Templates & Frameworks

- **Jobs-to-be-Done Interrogation Technique** (Robby Stein) - Clayton Christensen's interview/interrogation method for understanding why users hire a product, distinguishing utility jobs from emotional jobs
- **Nielsen Number for Research Right-Sizing** (Shaun Clowes) - The principle that 7-14 user interviews is the sweet spot—fewer than 7 means not enough data, more than 14 means diminishing returns.
- **Four Signals of Pain and Pull** (What to do if your product isn’t taking off) - Four concrete indicators that tell you whether your product is solving a real problem, used during customer discovery conversations
- **Gusto's Emotional Reaction Test for Customer Interviews** (How to validate your B2B startup idea) - A framework for evaluating whether customer interview feedback indicates genuine demand, based on the intensity of emotional response
- **Story-Based Interview Technique** (Teresa Torres) - An interviewing method where you collect specific behavioral stories from customers by asking about a recent concrete experience and then following the timeline
- **Automated Customer Interview Recruiting System** (Teresa Torres) - A system for automating weekly customer interview scheduling so product teams can maintain a continuous interviewing cadence without manual recruiting effort
- **Seven Signals to Look for in User Conversations** (Prioritizing at startups) - What to listen for when talking to early users and potential users to generate product ideas

See `references/artifacts.md` for the full list with details.

## Questions to Help Users

- "What specific event or struggling moment led you to look for a solution to this problem?"
- "Can you walk me through the last time you dealt with this, step by step?"
- "How are you currently solving this, and what specifically annoys you about that approach?"
- "If you had a magic wand and could change anything about your current workflow, what would it be?"
- "What would happen if you did nothing and just continued with the way things are today?"
- "Are there any tools or workarounds you have tried in the past that didn't work out?"

## Common Mistakes to Flag

- **Leading the witness** - Asking if a customer likes an idea invites polite validation rather than honest behavioral data.
- **Stopping at feature requests** - Accepting a list of features without understanding the underlying 'job' leads to bloated products that don't solve the root problem.
- **Interviewing too many or too few people** - Fewer than seven interviews provides insufficient data, while more than fourteen often leads to diminishing returns in new insights.
- **Mistaking interest for intent** - Users often say an idea is 'cool' to be nice, but only 'pull' signals like spending money or time indicate real demand.

## Deep Dive

For all 14 sourced insights from 11 guests, see `references/guest-insights.md`

## Related Skills

- Continuous Discovery
- Idea Validation
- Product Experiments
- Defining Icp