Skip to content

borghei/Claude-Skills / project-management/discovery/customer-interview-script

customer-interview-script

Verified

Writes and times a customer interview script that collects past-behavior stories, not opinions. Use when preparing a discovery, solution-validation, journey, churn or win-loss interview, or when interviews keep producing compliments.

assets/question_bank.md

View on GitHub
# Question Bank by Interview Type

Ready-to-use questions, organized by interview type. All questions follow Fitzpatrick's Mom Test rules (past behavior, no compliments, no hypotheticals) and Torres' story-first principle.

---

## Problem Discovery

**Purpose:** Validate that a pain exists, understand who has it, measure how acute it is.

### Opening story prompts

- "Tell me about the last time you tried to [job-to-be-done]."
- "Walk me through the last time [job] happened in your week."
- "When was the most recent time you ran into [problem area]?"

### Probing the pain

- "What is the most frustrating part of [job] today?"
- "What workarounds have you built to deal with [problem]?"
- "What does it cost you when [problem] happens -- in time, money, or stress?"
- "How often does this come up -- once a week, once a month, once a quarter?"
- "Who else on your team deals with this?"

### Behavioral evidence probes

- "What tools do you currently use for this? How much do they cost?"
- "Have you ever tried to solve this with a custom-built solution? Tell me about that."
- "Has this ever caused a meeting, a Slack thread, or a project to be created?"
- "Have you ever complained about this to a manager or a vendor?"

### Closing the problem discovery

- "If you could wave a magic wand and fix one thing about [job], what would it be -- and why that specifically?"
- "Who else should I talk to about this?"

---

## Solution Validation

**Purpose:** Test whether a prototype, mock, or concept resonates with the underlying job. Avoid asking "do you like it" -- ask about past behavior that would predict adoption.

### Opening (without prompting)

- "Before I show you anything, walk me through how you [do the job] today."
- "What tools do you currently use? Where do they break down?"

### Showing the prototype

- "I'm going to show you something. Tell me what you see -- what do you think this is?"
- "If you were trying to [job], where would you click first?"
- "Walk me through what you would do next."
- "What's confusing? What's surprising?"

### Validating fit

- "Where in your week would you actually use this?"
- "Who else on your team would touch this?"
- "What is missing that would prevent you from using it?"
- "What would you have to stop doing in order to start using this?"

### Probing for the real signal

- "What would have to be true for you to start using this tomorrow?"
  -> Then probe their answer for past behavior evidence
- "Is there a similar tool you've tried before? What happened?"

### Anti-pattern to avoid

Do not ask "Would you use this?" or "Would you pay for this?" -- both produce false positives.

---

## Journey Mapping

**Purpose:** Understand the end-to-end flow of how a customer accomplishes a job today, including handoffs, waiting, and workarounds.

### Setting up the journey

- "I want to understand the full process from start to finish. Walk me through the last time you did [end-to-end job], from the moment it started to the moment it ended."

### Probing each step

For each step the participant describes:

- "What triggered that step?"
- "What tool were you in?"
- "How long did it take?"
- "Who else was involved? What did they do?"
- "What did you wait for? How long did you wait?"
- "What did you have to look up or remember?"

### Pain probes within the journey

- "Where did you get stuck?"
- "What part felt slowest or most frustrating?"
- "Was there a step where you almost gave up?"
- "What workarounds did you use to get past obstacles?"

### Mapping handoffs

- "When you handed off to [other person/team], how did that work?"
- "What did you have to send them?"
- "What format -- email, ticket, Slack, document?"
- "What did they send back? How long did it take?"

### Closing the journey

- "If you redrew this whole process from scratch, what would be the biggest change?"
- "Are there steps you skip when you're under time pressure? Why those?"

---

## Churn (Why Did You Leave?)

**Purpose:** Understand why a customer canceled, downgraded, or stopped using the product.

### Setting up the conversation

- "Thank you for being honest with me today. I'm not here to win you back -- I just want to understand what happened."

### The original promise

- "When you first signed up, what were you trying to accomplish?"
- "What problem were you hoping to solve?"
- "Who else was involved in the decision to sign up?"

### The decline

- "When did you start feeling like it was not working?"
- "What was the moment you realized you were going to leave?"
- "Walk me through that day -- what happened?"
- "Did anyone else on your team feel the same way? Different?"

### The replacement

- "What did you do before [our product]?"
- "What are you doing now -- did you replace it with something else?"
- "How is the new thing different? Better? Worse?"

### The counterfactual

- "If we had done one thing differently, what would have changed your mind?"
- "Was there a single feature missing, or was it a larger issue?"

### Closing

- "Anything else you'd want a product team to know if they were trying to keep customers like you?"

---

## Win-Loss (Why Did You Choose Us / Them?)

**Purpose:** Understand the decision criteria, the alternatives considered, and the final tipping point.

### The trigger

- "What made you start looking for a tool in this category?"
- "What was happening in your business at the time?"
- "Who initiated the search -- you or someone else?"

### The shortlist

- "What other tools did you evaluate?"
- "How did you find them?"
- "Who was on the evaluation team?"

### The criteria

- "What were the must-haves?"
- "What were the nice-to-haves?"
- "What did you NOT care about even though vendors talked about it a lot?"

### The decision

- "Walk me through the conversation where you made the final decision."
- "What was the single biggest factor?"
- "What almost made you choose differently?"
- "Was anyone on the team pushing for a different choice? Why?"

### The aftermath (if won)

- "After you implemented, what surprised you -- good or bad?"
- "What did you discover that was not part of the original evaluation?"

### The aftermath (if lost)

- "Now that you've been using [competitor] for [time], what do you think -- right call?"
- "What do you wish we had said or shown in the sales process?"

---

## Universal Probes (Use Across All Types)

### Pulling for stories

- "Tell me about the last time..."
- "Walk me through what happened."
- "Give me a specific example."
- "When was the most recent time?"

### Probing depth

- "Why was that important?"
- "What did you do next?"
- "Who else was involved?"
- "What did that feel like?"

### Testing contradictions

- "Earlier you said [X]. Later you mentioned [Y]. Help me understand how those fit together."

### Testing counterfactuals

- "If [workaround] disappeared tomorrow, what would you do?"
- "What would have to be true for you to [behavior change]?"

### Closing every interview

- "Is there anything I should have asked but didn't?"
- "Who else should I talk to about this?"

---

## Questions to NEVER Ask

| Bad question | Why | Replace with |
|--------------|-----|--------------|
| "Would you use a product that...?" | Hypothetical -> polite lies | "Tell me about the last time you needed..." |
| "Do you like X?" | Compliment-seeking | "Walk me through how you used X last week" |
| "How often do you...?" | Generic -> averaged guess | "When was the last time? And before that?" |
| "What features do you want?" | Solution-mode -> participant becomes PM | "What is the hardest part of [job]?" |
| "Don't you agree that...?" | Leading | Remove framing, ask open-ended |
| "If you had X, would you Y?" | Double-hypothetical | "Tell me what you do today" |
| "Why don't you just...?" | Implies they're wrong | "Walk me through what you tried" |
| "Would you pay for this?" | False positive engine | "What do you currently spend on solving this?" |
| "Is this a problem for you?" | Yes/no -> no story | "Tell me about the last time [problem] happened" |
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall