Jobs to Be Done (JTBD): Understanding customers. Enabling innovation.

Jobs to be Done is a research and strategy framework that reconstructs the progress a customer wants to make with a purchase – rather than asking who they are. At its centre is the specific trigger that pushes someone away from what they did before and towards a new solution.

By asking not what people wish for, but what progress they want to make in a specific situation. The Jobs to be Done method provides a structured interview process that makes the real purchase triggers visible – regardless of demographics or personas.

Customers buy when a product helps them get an important task done better than their current solution. They switch when the pain of the current solution is great enough and an alternative credibly promises to deliver the progress they want. JTBD makes this dynamic open to systematic analysis.

Personas describe demographic characteristics: age, occupation, interests. Useful for targeting – but of no use in explaining purchase decisions. JTBD asks instead: in what situation does someone decide to switch, and what progress do they want to make by doing so? Two people with an identical persona may want to get a completely different job done – and two people with completely different personas can hire a product for the same job. JTBD explains the why. Personas describe the who. Both have their place, but purchase logic follows JTBD, not demographics.

The JTBD framework has four components: (1) The situation – when and why does the need arise? (2) The forces – push (current pain), pull (new solution), anxiety (doubts) and habit. (3) The desired outcome – what progress does the person really want? (4) The switching moment – what triggered the decision? Oberwasser Consulting has developed this framework further into the JTBD Innovation Framework, including the Wheel of Progress canvas.

The best-known example is the McDonald’s milkshake: customers bought it in the morning not because they were hungry, but to make the drive to work more pleasant – something that keeps them busy, does not drip and lasts a long time. The job was not “satisfy hunger”, but “get through a boring drive”. Anyone who understands this develops the right product – not more features, but a better way of getting the job done.

They are not opinion polls. You reconstruct a specific switch: trigger, alternatives, doubts, decision, use and outcome.

Usually 8–12 interviews. No more than 3 a day – and analyse them straight afterwards, not days later. Every day of delay between interview and analysis doubles the effort.

Yes: templates are helpful, but only if they fit the logic of the interview. Otherwise, teams fill in boxes and call it “customer focus”.

The Wheel of Progress (Böhme and Rochel, 2019) maps a buyer’s complete progress cycle on a single canvas and is the standard data-gathering tool in the Wheel of Progress tradition of the JTBD school. It brings together four forces (push, pull, anxiety, habit) and five phases of progress (P1 passive looking to P5 repeated use).

Instead of developing features based on internal assumptions, you use JTBD to identify the specific tasks and progress customers want to achieve. From this you derive requirements based on real customer behaviour – not on opinions voiced in meetings.

Synthetic interviews deliver usable results for quick insights. But if you want to build real empathy and customer understanding, you have to conduct real interviews and analyse them yourself. You have to internalise the customer’s perspective – no AI can do that for you.

When buyers switch even though the product has not got any worse. When a bestseller stops selling. When a new feature does not catch on. When a market entry fails. Whenever the question is not how many people buy, but why they do – or do not.

Jobs to be Done is particularly well suited to mid-sized companies because the method works without large research budgets. With 8–12 structured customer interviews, you can identify robust patterns that feed directly into product, marketing and sales decisions.

Sprint: when a specific decision is stuck. Mastering: when you want to build the capability in-house. E2I: when the insights are there, but the impact is not.

They collect statements instead of situations, confuse jobs with features and fail to translate insights into clear trade-offs and measurable decisions.

The basic logic is quick to grasp. But to use JTBD analyses with enough confidence for product management or business model decisions, you need hands-on experience – either through projects or through structured training such as Mastering JTBD.

Surprisingly little. In JTBD interviews you hardly hear anything about price. A yoga mat start-up priced its new professional range at €155 instead of the previous €130 – without any drop in sales. Expensive extras such as elaborate prints and carrying cases, on the other hand, were no reason to buy at all. When the job is done well, price fades into the background.