Jobs to Be Done (JTBD)

Jobs to Be Done is a framework that describes customer behavior in terms of the progress a person is trying to make in a particular circumstance, rather than in terms of demographics or product features. Associated with Clayton Christensen, Tony Ulwick, and Bob Moesta among others, its central proposition is that people do not buy products, they hire them to accomplish a job, and they fire them when something does better.

The framing changes how competition is understood. If the job is to have something quick and filling during a morning commute, a breakfast product competes with a coffee shop, a banana, and skipping breakfast entirely, not only with other products in the same category. Similarly, a project management tool may lose more often to a spreadsheet and a group chat than to a rival product, because the job customers are hiring for is narrower than the category assumes. Defining the competitive set by job rather than by category regularly reveals that the real alternative is a non-obvious substitute or simply doing nothing.

Jobs have functional, emotional, and social dimensions, and purchase decisions are frequently driven by the latter two even when the stated reasons are functional. A buyer choosing an established vendor over a better-performing challenger may be hiring the vendor to avoid being blamed if the project fails, which is an emotional and social job that no feature comparison captures. Recognizing these dimensions explains a great deal of otherwise irrational-looking behavior in both consumer and business markets.

The research approach that supports it focuses on the switch: interviewing people who recently changed from one solution to another and reconstructing the sequence that led to the decision. The line of questioning traces first thought, passive looking, active looking, the triggering event, the deciding moment, and the anxieties and habits that resisted the change. This produces a timeline of forces, the push of the current situation, the pull of the new option, the anxiety about switching, and the attachment to the existing habit, which maps directly onto what marketing and product need to address.

Its main practical limitation is imprecision in application. The framework has several competing formulations, and job statements are easy to write badly, either so abstract that they guide nothing or so specific that they simply restate a feature. It also tends to describe demand better than it prescribes solutions, and it is weaker for products where the job is genuinely obvious and the differentiation lies elsewhere, such as in price, distribution, or brand.

The framework also has a practical application in pricing and packaging that is often overlooked. If customers hire a product for a specific job, then the value they place on it is anchored to what accomplishing that job is worth, not to the cost of building the product or to competitors' prices in the nominal category. Understanding the job therefore informs both what to charge and how to package: bundling that matches how the job is performed sells more readily than bundling organized around internal product boundaries. This is also why the same product can support very different prices in different segments, since the same functional capability serves jobs of very different value depending on the customer's situation.

Used well, it is most valuable at the point where positioning and product direction are being set. In practice, switch interviews conducted through user research supply the raw material, the resulting job definitions inform prioritization within product research, and the language customers use to describe the job becomes the basis for propositions tested by a CRO service programme, since copy written in the customer's own account of their problem consistently outperforms copy written from the product's perspective.