conducting-user-interviews

Guides planning, execution, and analysis of customer discovery interviews using product leader techniques.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill conducting-user-interviews-alexyedi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conducting-user-interviews
Source: https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3/tree/main/.claude/skills/conducting-user-interviews
Command: npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill conducting-user-interviews-alexyedi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product teams often run user interviews that produce polite validation instead of real insights, asking leading questions, pitching instead of listening, or interviewing too few participants. This Skill coaches users through the full interview lifecycle using proven techniques from 43 product leaders. ## Core Features & Use Cases - Interview Preparation: Helps define learning goals, recruit the right participants, and craft story-based questions that avoid leading or hypothetical framing. - Technique Coaching: Shares principles like collecting stories over opinions, falsifying rather than validating, observing workflows instead of asking, and testing willingness to pay. - Findings Analysis: Assists in synthesizing interview results into actionable product insights, with a reference library of 64 insights from 43 product leaders. - Use Case: A PM preparing discovery interviews for a new feature gets help writing opening questions, avoiding common mistakes like pitching, and planning a 7-14 interview sample size. ## Quick Start Help me prepare a discovery interview plan to validate whether small business owners struggle with invoice tracking.

Frequently Asked Questions about conducting-user-interviews

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare for a user discovery interview?

Start by defining what you want to learn, such as validating a problem or understanding behavior. Recruit participants who have already tried to solve the problem, and write opening questions that ask for stories rather than opinions.

How many user interviews should I conduct?

Aim for 7 to 14 interviews. Fewer than 7 does not provide enough data to identify patterns, while more than 14 typically yields diminishing returns as you stop learning new things.

What questions should I avoid in customer interviews?

Avoid leading questions, hypotheticals like "would you use this", and asking users what features they want built. Focus instead on past behavior, real stories, and the emotions behind their requests.

How do I test willingness to pay during an interview?

Ask the customer to send a $1 invoice or payment link during the conversation. The gap between stated willingness to pay and actually paying is large, so a real transaction tests genuine commitment.

Should I interview non-users of my product?

Yes, non-users often provide the most insightful conversations. Asking why they have not adopted your product reveals perception gaps and barriers to adoption that current users cannot see.