AO-07 Jobs to be done (JTBD)
Frames demand around the progress a customer is trying to make in a circumstance, producing a job statement that shows which jobs are poorly served.
What it does
Frames demand around the progress a customer is trying to make in a circumstance, not buyer demographics. Artefact: a job statement; read which jobs are poorly served.
When to use it
Use when a user asks why customers choose or leave a product, and demographic segments do not explain it.
When it does not fit
Jobs conflict; the source does not address this.
Result format
The result is a set of job statements, each framed as the progress a customer is trying to make in a stated circumstance and not as a buyer demographic. It names the jobs that are poorly served.
Requirements on the material
| Property | Requirement type | Requirement |
|---|---|---|
| Content type | Always applies | requires=text |
| Unit of analysis | Always applies | requires=topic |
| Appraises source credibility | Applies in some cases | no |
Not restricted on: Structure, Variable types, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.
| Minimum material | Accounts of customer circumstances and of the job each customer was serving. The source does not say how to identify jobs systematically. |
|---|---|
| Additional sources needed | none |
| Not for (rules) | none |
| Not for (text) | Wrong choice when jobs conflict, which the source does not address. |
Choosing and ordering
| Kind of technique | Primary technique, runs in step 5.3 |
|---|---|
| Phase tag | analyse |
| Other phase tags | frame |
| Kind of finding | gap; pattern |
| Question answered | why; what |
| Strongest statement it supports | describe |
| Needs as input |
|
| Makes as output |
|
| Must exist first | None |
| Loop target | return to gather |
Library checks by stakes
Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: judgement dependent.
| Stakes | Check | Person involved | Counts as a different method |
|---|---|---|---|
| exploratory | assumption and limitation statement | none | no |
| decision-informing | assumption and limitation statement | none | no |
| decision-informing | source-span citation | none | no |
| decision-informing | human review sample | needed; left out below high stakes | no |
| high-stakes | assumption and limitation statement | none | no |
| high-stakes | source-span citation | none | no |
| high-stakes | human review sample | needed | no |
| high-stakes | independent review | needed | no |
| high-stakes | expert review | needed | no |
Failure modes and limits
| Model suitability | human judgement required |
|---|---|
| Typical model failure | Restates demographic segments as jobs, or writes a product feature as the job. |
| Error sources | input data; source selection; coder or rater judgement |
| Certainty limits | Certainty drops because evidence for the technique is anecdotal, and when job statements come from few accounts (imprecision). |
Related techniques
- pairs with AO-06 Personas: a persona describes who the customer is, and the job describes the progress sought
- pairs with AO-05 Customer journey mapping: stages show where the job is poorly served
Evidence and tag basis
Practice. One detailed example in a magazine article; evidence is anecdotal (inference). (Harvard Business Review, Know your customers' jobs to be done)
Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.