Skip to content

borghei/Claude-Skills / project-management/discovery/jtbd-workshop

jtbd-workshop

Verified

Plans and runs a 2, 4 or 8-hour Jobs-To-Be-Done workshop: switch interviews, forces of progress, scored outcome statements. Use when you need to know why customers switch, or to ground strategy in jobs before writing PRDs.

assets/switch_interview_script.md

View on GitHub
# Switch Interview Script

**Method:** Bob Moesta's switch interview
**Length:** 60-90 minutes
**Recording:** Required (with explicit consent)
**Participants:** 1 interviewer + 1 customer (+ optional silent observer for note-taking)

---

## Pre-Interview Checklist

- [ ] Recording software tested
- [ ] Consent confirmed in writing (per `discovery/customer-interview-script/`)
- [ ] Note-taking doc open with four-anchor timeline ready
- [ ] Customer has switched TO or FROM the product in last 90 days

---

## Opening (5 min)

```text
"Thanks for taking the time today. I want to walk through your decision to
[start using / stop using / consider switching from] [product] step by step.

I'll be asking a lot of questions about WHEN things happened -- not just
WHAT happened -- because I'm trying to understand the timeline of how
your thinking changed.

A few ground rules:
- There are no wrong answers. I'm trying to learn how you actually thought
  about this, not what you should have thought.
- I'd like to record this. The recording stays internal, is deleted in 90
  days, and the transcript will be redacted. Is that okay?
- We have [60/90] minutes. If anything is uncomfortable, just say so.

Ready? Let's start at the beginning."
```

---

## Anchor 1: First Thought (10-15 min)

**Goal:** Identify the PUSH from the current situation.

**Opening prompt:**

> "Take me back to the FIRST TIME you thought you needed something
> different than what you were using. When was that?"

**Probing questions:**

- "What was happening that day? What were you working on?"
- "What were you using before?"
- "What specifically made you think 'there must be a better way'?"
- "Who else was involved? Did anyone else notice?"
- "What did you do right after that first thought?"

**Listening for:**

- Specific moments of frustration with the current state
- Failed tasks, errors, missed deadlines tied to the current solution
- Comments from peers, bosses, or auditors that triggered the realization
- Emotional markers ("I was furious", "I was embarrassed")

---

## Anchor 2: Passive Looking (10-15 min)

**Goal:** Identify what kept the job *latent* and what re-triggered it.

**Opening prompt:**

> "Between that first thought and when you started actively researching
> alternatives, what happened? Walk me through that period."

**Probing questions:**

- "Did you mention it to anyone?"
- "Did anything happen that made you think about it again?"
- "How long was that period -- weeks, months, longer?"
- "Did you do any casual research -- Google, reading articles, asking colleagues?"
- "What was keeping you from acting on it?"

**Listening for:**

- The latency between push and active research (often months in B2B)
- Re-triggering events (a second failure, a colleague's recommendation, a vendor email)
- The competing priorities that kept the job dormant
- The internal politics of bringing up the change

---

## Anchor 3: Active Looking (15-20 min)

**Goal:** Identify the PULL of alternatives and the moment urgency crossed threshold.

**Opening prompt:**

> "When did you start actively comparing options? Tell me about that
> shift -- what changed?"

**Probing questions:**

- "What was the trigger that moved you from thinking to doing?"
- "What did you do first -- Google, ask a colleague, read reviews, demo?"
- "What options were on your shortlist? How did each one come on your radar?"
- "Who was involved in the search -- you alone, or a team?"
- "What were the must-haves you were looking for?"
- "What were the deal-breakers?"

**Listening for:**

- The specific event that made the search urgent (an incident, a deadline, a budget cycle)
- Named alternatives -- including ones that weren't your product
- The criteria they used (functional, social, emotional)
- Who else was involved and their role

---

## Anchor 4: Deciding (15-20 min)

**Goal:** Identify ANXIETY and HABIT forces that almost stopped the switch.

**Opening prompt:**

> "Walk me through the conversation -- or moment -- where you decided.
> Who was involved? What was said?"

**Probing questions:**

- "What was the single biggest factor in the decision?"
- "What almost made you choose differently?"
- "What were you worried about?"
- "What was hard about leaving the old way?"
- "What had to be true for you to commit?"
- "Did anyone push back? Why?"
- "How long did the decision take -- days, weeks?"

**Listening for:**

- Specific worries about the new solution (implementation risk, data migration, training, cost)
- The emotional ties to the old way (sunk cost, comfort, fear of looking foolish)
- The deciding voice (was it you? your boss? the team?)
- The "almost" -- what almost killed the deal?

---

## Anchor 5: First Use (10-15 min)

**Goal:** Identify ANXIETY that persisted after purchase and HABIT residue.

**Opening prompt:**

> "Walk me through the first time you actually used [the new solution].
> What was that like?"

**Probing questions:**

- "What surprised you -- good or bad?"
- "What was harder than you expected?"
- "What was easier than you expected?"
- "Did you go back to the old way for anything? What?"
- "How long did it take to feel comfortable?"
- "Did you have any moments of regret? When?"

**Listening for:**

- Onboarding friction -- where did the new solution stumble?
- Surprises that revealed unstated expectations
- Persistent dual-running (using both the new and old way) -- this is habit residue
- Moments where the new solution proved itself

---

## Closing (5 min)

```text
"That was incredibly helpful. A few last questions:

- Is there anything I should have asked but didn't?
- Looking back, what one thing would you have wanted to know before you
  started this whole process?
- If a colleague were in your position today, what would you tell them?
- Can I follow up if I have a clarifying question?

Thanks so much for your time."
```

---

## Post-Interview Debrief (within 30 min)

Within 30 minutes of the interview, write down:

### Timeline summary

- First Thought (when, what, why):
- Passive Looking (how long, what re-triggered):
- Active Looking (when started, alternatives considered):
- Deciding (when, who, what almost stopped it):
- First Use (surprises, regrets, dual-running):

### Forces of progress map

| Force | What you heard |
|-------|----------------|
| Push (current state pain) | [...] |
| Pull (new solution attraction) | [...] |
| Anxiety (switching worry) | [...] |
| Habit (status quo tie) | [...] |

### Top 3 quotes (with timestamps)

1. [timestamp + quote]
2. [timestamp + quote]
3. [timestamp + quote]

### Three biggest surprises

1. [...]
2. [...]
3. [...]

### Hand-off

- [ ] Transcript uploaded to research repo
- [ ] One-page summary written for workshop pre-read
- [ ] Snippets extracted for the workshop snippet wall
- [ ] Follow-up email sent (thank-you + incentive)
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