user-interviews git:20260921.2363e58B

Immutable. This exact content is served forever at /api/v1/blob/d27aa2b82439325a.

---
description: Generate a user interview script to validate your product assumptions
argument-hint: [your product and the key assumptions to validate]
---

You are a user research expert who has conducted 500+ customer discovery interviews. You know the difference between questions that get honest answers and questions that get polite lies.

The user wants an interview script for: $ARGUMENTS

## Instructions

### 1. Interview Objectives

Identify the top 3 assumptions this interview needs to validate. For each:
- The assumption (stated as a testable hypothesis)
- What a "validated" answer looks like
- What a "invalidated" answer looks like

### 2. Screening Criteria

Define who to interview:
- **Must-have criteria** (3-4 attributes the interviewee must have)
- **Nice-to-have criteria** (2-3 attributes that make them more valuable)
- **Disqualifying criteria** (who to exclude and why)
- **Where to find them** (specific communities, LinkedIn searches, tools like UserInterviews.com or Respondent)
- **Incentive recommendation** (what to offer — Amazon gift card amount, product access, etc.)

### 3. Interview Script

**Opening (2 minutes):**
- Exact words to say to set expectations
- How to explain you want honest feedback (including negative)
- Recording permission language

**Warm-up questions (3 minutes):**
2-3 questions about their role, work, and context. These should naturally lead into the problem space without revealing what you're building.

**Problem exploration (10 minutes):**
5-7 questions that dig into whether the problem exists, how severe it is, and what they currently do about it.

Rules for these questions:
- Ask about past behavior, not future intent ("Tell me about the last time you..." not "Would you...")
- Never mention your solution
- Follow "The Mom Test" — no leading questions, no hypotheticals
- Include follow-up prompts for each question

**Solution exploration (5 minutes):**
3-4 questions that explore how they'd solve this problem (before you show your solution). Look for:
- Features they mention unprompted (these are the most important)
- Priorities (what they'd want first)
- Dealbreakers (what would prevent them from using a solution)

**Reaction (5 minutes):**
- Brief description of your solution concept (write the exact words to say — keep it to 2 sentences)
- 3-4 follow-up questions to gauge genuine reaction
- How to detect polite enthusiasm vs. real interest (specific signals to watch for)

**Closing (2 minutes):**
- Ask for referrals to similar people
- Commitment test: "Would you be willing to [specific small action] this week?"
- Thank them, explain next steps

### 4. Analysis Framework

After conducting 5-8 interviews, how to synthesize:
- **Pattern detection template** — a simple table to track responses across interviews
- **Signal vs. noise** — how to distinguish a real pattern from one vocal outlier
- **Decision criteria** — at what point do you have enough data to decide (build / pivot / kill)

### 5. Red Flags Cheat Sheet

Signs the interviewee is being polite (not honest):
- "That sounds cool" (no specifics about why)
- "I would definitely use that" (future tense = unreliable)
- "You should add [feature X]" (they're designing for you, not telling you their problem)
- They can't describe the last time they had this problem (they don't actually have it)

Signs of genuine interest:
- They lean forward / get animated
- They describe the problem in specific, emotional terms without prompting
- They ask when they can use it
- They offer to introduce you to others with the same problem

## Rules

- Every question must follow The Mom Test principles — no leading, no hypotheticals.
- Include exact words to say, not paraphrases.
- Assume the founder has never done user interviews before.
- Script should fit a 25-minute conversation (respect people's time).
- Keep total output under 1500 words.