What this prompt does
This prompt casts the AI as a senior product researcher trained in Jobs-to-be-Done and makes it write an interview script tight enough to run verbatim, with no leading or yes/no questions. You provide the [product], [segment], [research_goal], and [length]. It returns a timed script: a warm-up, the context of purchase, the JTBD core covering hired, fired, and struggling moments, a grounded feature wish list, a closing and referral ask, plus two to three neutral follow-up probes under each main question.
The structure works because it engineers against the fastest way to ruin interview data: a leading question. By demanding open, situational questions and banning yes/no framing, the prompt keeps the responses about why people actually hire the product. [length] drives the time budget for each section, [research_goal] keeps every question mapped to what the research must answer, and [segment] ensures the language fits the people you are actually talking to. The hired/fired prompts in the core section carry most of the signal.
When to use it
- You are about to interview users and want a script you can read verbatim.
- You keep accidentally asking leading or yes/no questions and skewing the data.
- You need a timed structure that fits a fixed interview length.
- You want the JTBD hired/fired/struggling framing rather than feature-opinion questions.
- You need neutral follow-up probes ready so you do not improvise leading ones.
- You want every question tied back to a specific research goal.
Example output
You get a full interview script with timings: a rapport-building warm-up, a context-of-purchase section on the trigger and first thought, a fifteen-minute JTBD core on hired/fired/struggling moments, a situational feature wish list, a closing and referral ask, and two to three neutral follow-up probes under each main question — the whole thing mapped to your research goal and budgeted to the stated length.
Pro tips
- State
[research_goal]sharply, since every question maps back to it; a vague goal yields a script that wanders. - Match
[segment]to the people you will actually interview so the language and examples land. - Use
[length]to set realistic expectations; a 30-minute budget forces you to cut, and the timings show where. - Lean on the hired/fired prompts in the core section — they carry most of the signal about why people switch.
- Resist editing the probes into leading questions; their neutrality is the whole point of the script and the easiest thing to break under time pressure.
- Keep the warm-up genuinely about rapport rather than rushing into the JTBD core, since a relaxed respondent gives far richer struggling-moment answers.
- Run a pilot interview, then tighten any section that consistently runs over its time budget so the real sessions stay inside the stated length.
