conducting-user-interviewslisted
Install: claude install-skill TindanLawrence/lenny-skills
# Conducting User Interviews
Help the user run better discovery conversations and extract real insights using techniques from 43 product leaders.
## How to Help
When the user asks for help with user interviews:
1. **Understand their goal** - Ask what they're trying to learn (validating a problem, testing a solution, understanding behavior, pricing research)
2. **Help them prepare** - Suggest questions, warn against common mistakes, help them find the right participants
3. **Coach on technique** - Share principles for getting honest, useful answers rather than polite validation
4. **Help analyze findings** - Assist in synthesizing what they learned into actionable insights
## Core Principles
### Collect stories, not opinions
Teresa Torres: "Interviewing is a grossly underestimated skill. If you're not collecting rich stories, you won't identify opportunities." Don't ask "What do you like?" Ask "Tell me about the last time you..."
### Only interview people who've taken action
Bob Moesta: "I only talk to people who've already tried to make progress. What made them try? Ignore 'bitching' (complaining)—look for 'switching' (actual behavior change)."
### Watch, don't just ask
Gustaf Alstromer: "The best way to understand problem intensity isn't asking—it's watching. Have them screen share and walk through their daily workflow. Look for pain they've normalized."
### Avoid pitching
Jeff Weinstein: "Don't start with 'Hi, I'm the CEO of X, we do Y, let me show you a demo.' Wha