Jobs to be done interview questions that improve hooks and offers
On this pagetap to expand

Most “JTBD interviews” are really polite podcasts. The host nods. The guest performs competence. Nobody says the embarrassing sentence that would have stopped the scroll.

Good JTBD work is ruder—in the best way. It chases progress, anxiety, and tradeoffs until you have language your creative team can steal without guilt.

Last reviewed: April 2026. Get consent to record and quote; anonymize when you ship learnings outside the org.

The spine: four moves you are hiring the interview to make

  1. Situate — What was happening the week they cared?
  2. Expose the workaround — What did they actually do instead of your category?
  3. Price the tradeoff — What did that workaround cost—in time, money, reputation, sleep?
  4. Define “good enough proof” — What would have to be true for them to switch without feeling stupid?

If your questions do not touch all four, your hooks will sound like category copy.

Question bank (copy, adapt, delete ruthlessly)

Situation and hire

  • “Walk me through the last time this broke badly enough that you did something about it—Monday to Monday.”
  • “If I followed you that week, what would I see on your calendar and inbox?”
  • “When did you first realize the old way was not going to scale?”

Workarounds (gold for hooks)

  • “What did you try before you started seriously looking for a product?”
  • “What almost worked—and why did you abandon it?”
  • “What tool or habit do you still use alongside anything new—and why?”

Stakes (gold for offers)

  • “What were you afraid would happen if you did nothing for another quarter?”
  • “Who else had to sign off—and what would have made them say no?”
  • “What would have embarrassed you in a leadership meeting if it surfaced?”

Proof bar (gold for paid social credibility)

  • “What evidence would you need in the first scroll to believe a claim?”
  • “What makes you assume an ad is lying?”
  • “Tell me about a time a vendor promise burned you—what words did they use?”

Live mini-script (composite)

Bad: “How important is efficiency to you?”
Good: “Last month, when exactly did ‘efficiency’ stop being a buzzword and start being an emergency—who was waiting on you?”

The second question produces a scene. Scenes become hooks.

Turn answers into ad fuel the same day

Tag each note:

  • Scene (camera could film it)
  • Quote (permission path)
  • Objection (first three seconds)
  • Proof artifact (demo, number, peer, policy)

Then force three hooks and one offer angle per interview before you sleep.

Pinnacle AdForge connects this kind of research to messaging and hooks so the chain does not break—ICP and avatar research, mass desire extraction, hook development. Start free when you are ready to run it as a system.

JTBD vs feature tourism (the conference call test)

If your notes read like a release checklist (“they want integrations”), you interviewed the roadmap, not the job. Jobs sound like verbs under pressure: “get the board deck out without another all-nighter.” Rewind questions until you hear calendar, boss, budget, shame, workaround.

Five “rude kindness” follow-ups that unlock scenes

  1. “What did you try right before you paid—honestly, even the embarrassing spreadsheet?”
  2. “Who was waiting on you while it was broken?”
  3. “What would have counted as ‘good enough’ that you still rejected—and why?”
  4. “When did you almost churn—and what specific sentence in support fixed it?”
  5. “If this disappeared tomorrow, what would you hire instead?”

Silence is data. Nodding is not.

B2B committee hint (one question)

“Who else had to say yes—and what proof did they need that differed from yours?” That answer becomes two ads more often than you expect: practitioner pain vs economic buyer fear.

JTBD stories are gold for hooks—and dangerous if you composite carelessly. Label internal docs composite when you blend voices; never ship a quote that implies a real person said words they did not. Your brand’s trust curve is smoother than any single CPA win.

After five interviews: pattern or noise?

Look for same workaround with different nouns. If five buyers “MacGyver” the problem the same way, you have a category default to attack in cold open. If every story is a snowflake, your segment definition is still too wide—tighten motion (new buyer vs switcher vs rescue).

Offer angles that fall out of jobs (not out of slides)

When someone describes what they almost bought instead, you have a substitute map—great for risk-reversal tests (“why teams pick us over spreadsheets,” said without trashing humans who love spreadsheets). When they describe the refund moment, you have a trust gap—great for proof-first hooks.

The “one-roommate” rule for note-taking

If your notes would confuse your roommate who does not work in software, rewrite them. JTBD gold is human-simple: who, waiting, deadline, shame, workaround. Jargon is a tax you pay at edit time—with interest.

Lightning debrief (five minutes, same day)

Answer three bullets before you close the laptop: scene, tradeoff, proof artifact. If you cannot, you did not finish the interview—you held a friendly chat.

Key takeaways

  • JTBD for ads = scenes + workarounds + proof, not personas in nicer fonts.
  • Rude kindness beats polite interviews.
  • Three hooks same day or you are still researching for sport.

People also ask

What is jobs to be done in marketing?

JTBD explains what progress a buyer is trying to make in a situation, not only demographics or personas. For ads, it should change hooks and offers because it names struggle, tradeoffs, and the old way that failed.

What questions should I ask in a JTBD interview?

Ask about the last time the situation boiled over, what they tried before, what almost worked, what they were afraid to lose, and what would count as proof the new way works. Avoid leading questions that train the customer to compliment your category.

How long should a JTBD interview be?

Thirty to forty five focused minutes beats ninety wandering minutes—tight time forces concrete stories.

How do JTBD interviews improve ad hooks?

Hooks need scenes and stakes; JTBD pulls the moment the buyer hired a workaround and why it hurt. That language is often paste-ready for first-frame copy after light editing.

Should I record JTBD interviews?

Yes when participants consent—verbatim lines protect you from misremembering emotion words that sell.

FAQ

How many JTBD interviews do I need before writing ads?

Patterns usually emerge after five to eight similar buyers in the same segment—not after one heroic call.

What is the biggest JTBD interviewing mistake?

Pitching your product instead of excavating the last purchase journey and the emotions inside it.

How does Pinnacle AdForge use JTBD-style inputs?

AdForge is built so research and avatar work feed messaging and hooks in one workspace instead of dying in a doc. Pair interviews with synthesis and pillars when you graduate from notes.

How do I try Pinnacle AdForge after JTBD interviews?

Signup, paste anonymized quotes and situation summaries, and route outputs into hook and offer work in the same project. Compare time-to-first testable hook versus your old handoff.


JTBD is a lens, not a license to skip ethics—honor consent, anonymize when needed, and never fabricate quotes in live ads.