Build a sequenced Jobs-to-be-Done product strategy
Product Strategy
0 uses
Updated 4/17/2026
Description
You have 40 JTBD interview snippets and no idea which job to build around first. This converts raw switch-interview data into a ranked job map, picks the first job to win on, and plans the adjacent jobs you will add in the following year without diluting the wedge.
Example Usage
You are a JTBD strategist helping me sequence jobs for {{product_name}}. I have {{interview_count}} switch interviews. Our current product focus: {{current_focus}}.
## Step 1 — Extract the jobs
For each interview, extract:
- Triggering event (what changed for the customer)
- Job statement: "When [situation], I want to [motivation], so I can [outcome]"
- Current solution they switched from/to
- Forces (push of the situation, pull of the new, anxiety of switching, habit of old)
## Step 2 — Cluster into core jobs
Group raw statements into 5-8 core jobs. For each core job:
- Frequency (how many interviews)
- Intensity (how painful is the old solution)
- Budget (what they pay for current solution)
- Switching resistance (anxiety + habit score)
## Step 3 — Pick the wedge
The wedge job is the one where: intensity is high, switching resistance is low, budget is real. Score each job on a 3x3 grid:
- High intensity × high budget = priority
- High switching resistance = defer
- Low frequency = niche, evaluate separately
## Step 4 — Adjacent jobs (months 6-18)
Once we win the wedge, which jobs naturally extend from the same customer? Use the "job overlap score" — how often does a wedge-job customer also have each candidate adjacent job in their interview?
## Output
1. Ranked job table
2. The wedge job with rationale
3. 2 adjacent jobs for months 6-12, 1 for months 12-18
4. The one job I should explicitly NOT pursue and whyCustomize This Prompt
Customize Variables0/6
Was this helpful?
Read the full guide
In-depth article with examples, pitfalls, and expert sources