JTBD looks easy on a slide and almost always falls apart in practice: teams write job statements that are really feature descriptions, skip the switch-trigger entirely, and end up using JTBD as a brainstorm warmup instead of a decision filter. These prompts give you 12 rigorous applications — switch-trigger interview design, defensible job statements, functional/emotional/social decomposition, and using JTBD to actually cut features from a backlog. Pair with the feature prioritization prompts once you have a job locked in.
Best for
- Pre-MVP customer discovery
- Re-positioning existing products
- Sharpening landing-page copy
- Feature prioritization
- Sales-call structure
1. JTBD interview question bank
Generate 15 JTBD interview questions for a {product} customer who just signed up / churned / referred. Cover: trigger, evaluation, decision moment, expected outcome, the alternative they almost picked.2. Job-statement writer
Below: interview notes. Write 3 candidate job statements using "When {situation}, I want to {motivation}, so I can {expected outcome}". Pick the most defensible one. Justify the others as wrong.
{paste notes}3. Switch-trigger analysis
My customer just switched from {alternative} to my product. Walk me through the JTBD switch interview: first thought (passive), trigger event (active), evaluation (active), decision (purchase), early usage. Output the questions in order.4. Alternatives map (not just competitors)
For job statement {paste}, list the real alternatives: direct competitors, indirect tools, manual workarounds, "doing nothing", hiring help. For each: when they win, when they lose.5. Functional-vs-emotional-vs-social job map
Below is my JTBD. Break into functional, emotional, and social dimensions. For each, give 2 specific cues from interviews that signal that dimension.
{paste}6. JTBD → positioning
For job {paste}, write a positioning that names the situation, the desired progress, and the unique way we deliver it. Then 3 variants. Avoid generic "best in class" framing.7. JTBD → feature filter
Below: 15 features in my backlog. Below: the primary job to be done. Score each feature on "advances the JTBD" / "tangential" / "different job entirely". Cut anything that scores below "advances".
{paste}8. JTBD-misalignment detection
Below: my current landing page + a customer interview where they describe their job. Find every place my page is solving a DIFFERENT job than the customer's. Suggest fixes.
{paste}9. JTBD for B2B (buyer-job vs user-job)
For my B2B product, separate the buyer-job (why a company purchases) from the user-job (why an individual uses). Inputs: {paste}. Output: both jobs, where they conflict, and how to address both in messaging.10. Job-segments map
I think my product serves 1 job but the customer base is heterogeneous. Below: customer descriptions. Identify whether there are 2-3 distinct jobs being served and how to either focus or segment messaging.
{paste}11. Job-Story drafter
Convert this JTBD into 5 specific job stories. Format: "When {situation + emotional context}, I want to {motivation}, so I can {outcome + meta-outcome}". Each story should suggest 1 specific feature.
{paste JTBD}12. JTBD interview transcript analyzer
Below: a 60-min JTBD interview transcript. Extract: trigger, alternatives considered, decision criteria, the moment of "I have to find something", and the expected outcome. Output as a structured 1-page summary.
{paste}Common mistakes
- Job statements that read like feature descriptions (“user can filter…”) instead of progress
- No alternatives map — pretending “doing nothing” and “manual workaround” aren’t real competitors
- Mixing buyer-job and user-job for B2B and producing messaging that satisfies neither
- Skipping the switch-trigger event — JTBD without context is fortune-cookie copy
- Using JTBD as a brainstorm warmup instead of a feature-cut filter
- One job statement for a heterogeneous customer base instead of segmenting into 2-3 jobs