Jobs to be Done asks what progress someone is trying to make when they choose a product. The answer includes the circumstances that make the choice necessary, the alternatives available, and the practical, emotional, or social consequences that matter to that person.
The Christensen Institute’s explanation frames products as things people “hire” to help them make progress. This shifts attention beyond a product’s feature list without assuming that customer characteristics are irrelevant.
Follow a real decision through time
Consider an illustrative small-business owner moving from a spreadsheet to invoicing software. The useful question is not simply which features they prefer. Research might examine the late payment that prompted a search, the work involved in chasing it, the options considered, and the concern that clients would find a new payment process inconvenient.
Ask for the sequence of a recent decision. What was happening before the person began looking? What made the existing approach inadequate? Who else was involved? What nearly stopped the change? Semi-structured interviews provide room to follow those details while covering comparable ground across participants.
The timeline helps distinguish an appealing feature from a reason to act. A dashboard might attract attention during a demonstration, while the ability to send a clear reminder was what finally made switching worthwhile.
Describe the progress without prescribing the product
A useful job statement connects a circumstance with the progress sought. In the invoicing example, “When several payments are overdue, I need to follow up without losing track of what each client has already been told” leaves several responses open. “I need an automated reminder feature” has already chosen one.
Do not make the statement so broad that it loses practical value. “Feel in control” may capture an emotional concern, but the research should explain what control means in this situation and how the person recognises it.
Competing alternatives can include other products, manual work, asking someone else, or postponing the task. Those alternatives belong in the research because they shape what the proposed experience must improve upon.
Use the account to compare possible responses
The job can guide concept testing, positioning, and decisions about what to build. A team might compare a reminder workflow with a shared payment-status view, examining which part of the experience each addresses.
JTBD does not itself measure market size or establish how many people share the circumstances. Further sampling and measurement may be needed for that decision. Nor must it replace personas: a persona can preserve relevant differences in behaviour and context, while a job focuses attention on progress in a situation.
Keep the original accounts available alongside the synthesis. The framework is most useful when it helps the team understand why a change became worthwhile, with enough detail to avoid turning a concrete human decision into another abstract statement about needs.