Customer Research and Jobs-to-Be-Done Interviews SKILL.md

This is the exact file agents read, including the credit header and licence notice. Save it as customer-research-interviews/SKILL.md.

---
name: customer-research-interviews
description: "Plan and run customer research for product marketing: jobs-to-be-done switch interviews and the buying timeline, the four forces, customer, lost prospect and churn interviews, surveys, review and sales call mining, recruiting, unbiased interview guides, synthesis with evidence and quotes, and insights turned into positioning, messaging, pricing and launch decisions. Use whenever someone asks about customer interviews, jobs to be done, JTBD, voice of customer research, why customers buy, interview questions, review mining or turning research into messaging."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/product-marketing/customer-research-interviews/
  category: marketing
  subcategory: product-marketing
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# Customer Research and Jobs-to-Be-Done Interviews

Good product marketing is built on knowing customers better than competitors do: why they started looking, what they compared, what almost stopped them, what made them choose and what value they actually get. Surveys and analytics show patterns; interviews explain them. Yet many teams interview rarely, ask leading questions, talk only to happy customers and never turn findings into decisions.

This skill plans and runs customer research for product marketing: jobs-to-be-done (JTBD) switch interviews, customer and prospect interviews, surveys, review mining and synthesis into insights that change positioning, messaging, pricing and launches.

## Operating principles
1. **Talk to the right people.** Recent buyers, recent churners and lost prospects reveal more than long-time fans.
2. **Ask about past behaviour, not opinions.** "Tell me about the day you started looking" beats "Would you use feature X?"
3. **Don't lead.** Neutral questions, silence and follow-ups surface the real story.
4. **Synthesise into decisions.** Research that doesn't change something wasn't worth doing.
5. **Keep a steady rhythm.** A few interviews every month beat a big study once a year.

## Research methods
| Method | Best for | Watch out for |
|---|---|---|
| JTBD switch interviews | Why people buy and switch; triggers and anxieties | Need recent buyers (last 90 days) for accurate recall |
| Customer interviews | Value received, use cases, language | Bias towards happy customers |
| Lost prospect interviews | Why you lose | Hard to recruit; offer incentives |
| Churn interviews | Why customers leave | Emotional; keep them short |
| Surveys | Size and frequency of patterns | Can't explain why; question wording bias |
| Review mining (G2, Capterra, app stores, Amazon) | Customer language, praise and complaints | Skewed towards extremes |
| Sales call recordings | Objections, questions, competitor mentions | Seller-led conversations |

## The JTBD timeline
JTBD switch interviews reconstruct the buying journey:
1. **First thought:** when did they first realise the old way wasn't working?
2. **Passive looking:** what did they notice without actively searching?
3. **Event that triggered active looking:** what made it urgent?
4. **Active looking:** what did they compare, and how?
5. **Deciding:** what made them choose, and what almost stopped them?
6. **Consuming:** what happened after they started using it?
Along the way, capture the four forces: push of the current situation, pull of the new solution, anxiety about the new solution and habit of the present.

## When to use, and when not to
Use it before positioning or messaging work, when win rates change, before pricing changes, before launches, when entering new segments and as a continuous monthly practice.

Don't use it for usability testing of the product (product research teams handle that) or for statistical market sizing.

## Inputs to ask for, in one message
1. Research questions and the decisions they inform.
2. Access to recent customers, lost prospects and churned customers.
3. Existing research, reviews and sales call recordings.
4. Budget for incentives and tools (scheduling, recording, transcription).
5. Team members who can interview and synthesise.

## Workflow

### Step 1. Define the decision
"We need to choose which segment to focus messaging on" or "We need to know why we lose to Competitor X."

### Step 2. Choose methods and participants
Usually 8 to 15 interviews per segment or question, mixing recent buyers, lost prospects and churners.

### Step 3. Recruit
Email from a real person, a clear purpose, 30 to 45 minutes, an incentive where appropriate and consent to record.

### Step 4. Interview
Use a discussion guide but follow the story; ask for specifics (dates, people, alternatives, numbers).

### Step 5. Capture
Record and transcribe with consent; note key quotes, triggers, alternatives, forces and outcomes.

### Step 6. Synthesise
Tag transcripts, cluster themes, count how often each appears and pull representative quotes.

### Step 7. Turn insights into decisions
For each insight: what it means, what we'll change, who owns it.

### Step 8. Share
A short readout with quotes and clips; a searchable repository for future work.

## Interview guide (JTBD switch, 40 minutes)
```
1. Context: role, team, what they were using before (5 min)
2. First thought: when did you first feel the old way wasn't working? (5 min)
3. Trigger: what happened that made you start looking seriously? (5 min)
4. Looking: what options did you consider? How did you compare them? (10 min)
5. Deciding: what made you choose? What nearly stopped you? Who else was involved? (10 min)
6. Using: what changed after you started? What surprised you? (5 min)
```

## Questions to avoid
| Avoid | Ask instead |
|---|---|
| "Would you pay for X?" | "Tell me about the last time you paid for something to solve this." |
| "Do you like our product?" | "What were you trying to get done when you signed up?" |
| "Was price an issue?" | "How did the decision get approved?" |
| "Would this feature help?" | "Walk me through how you handle that today." |

## Synthesis template
```
| Insight | Evidence (count, segments) | Representative quote | Implication | Decision | Owner |
```

## Continuous research rhythm
- Two to four interviews a month with recent buyers, alternating with lost prospects or churners.
- A shared repository with tags (segment, trigger, competitor, objection).
- A quarterly synthesis that feeds positioning, messaging and roadmap reviews.

## Consent and ethics
Ask for consent to record, explain how notes will be used, anonymise quotes unless participants agree to be named, store recordings securely and delete them according to your data policy. Never use research calls to sell.

Thank every participant and, where possible, tell them what changed because of their input.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Can't recruit lost prospects | Offer higher incentives; use a third party; mine sales notes |
| B2B buyers with little time | Shorter calls; schedule through sales relationships |
| Consumer products | More interviews, shorter sessions, plus surveys for scale |
| Founder-led research | Train interviewers to avoid selling during calls |
| Conflicting findings | Segment participants; the conflict often reveals two segments |

## Handoffs to related skills
- Positioning from insights: `positioning`
- Messaging with customer language: `messaging-framework`
- ICP and personas: `ideal-customer-profile`
- Win-loss programme: `win-loss-analysis`
- Pricing research: `pricing-packaging`
- Case studies from interviews: `case-studies-customer-proof`

## Worked example
A payroll software company believed customers chose it for price. Twelve switch interviews with customers who bought in the last 90 days showed the trigger was usually a payroll error that upset staff, and the deciding factor was confidence that payroll would be right every month, backed by automatic tax updates and a named support contact. Price came up only as a reassurance. Messaging shifted from "affordable payroll" to "payroll your team can trust, every month", the sales deck added error-prevention proof and the homepage tested the new message against the old, raising qualified sign-ups.

## Output format
```
# Customer research readout: <question>, <date>
## Decision this informs
## Participants (who, how many, segments)
## Key insights with evidence and quotes
## Buying journey and forces
## Decisions and owners
## Repository links
```

## Common mistakes
- Interviewing only happy customers.
- Asking hypothetical questions.
- Selling during interviews.
- Long reports nobody reads.
- Research with no decision attached.

## Questions to ask before you research
- What decision will this research inform?
- Who has the most recent, relevant experience?
- How will insights be shared and acted on?

## Self-check before you answer
- Is the research tied to a decision?
- Are participants a mix of buyers, lost prospects and churners?
- Are questions about past behaviour, not opinions?
- Are insights turned into decisions with owners?

## Further reading
- Bob Moesta, Demand-Side Sales 101 (2020)
- Rob Fitzpatrick, The Mom Test (2013)
- Clayton Christensen et al., Competing Against Luck (2016)

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/product-marketing/customer-research-interviews/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.