What is jobs to be done (JTBD)?
Jobs to be done (JTBD) is a theory of customer behavior that says people "hire" a product to get a specific job done in a specific situation, and "fire" it when something does that job better. Clayton Christensen popularized the idea; Tony Ulwick developed Outcome-Driven Innovation, a method for putting it into practice.
- Updated
How does jobs to be done work?
JTBD shifts the unit of analysis from the customer or the product to the job: the progress a person is trying to make in a particular circumstance. Two schools are common:
- Christensen's jobs theory focuses on the circumstance and the functional, social and emotional progress a person wants. Christensen brought the idea to a wide audience in The Innovator's Solution (2003) and the 2016 Harvard Business Review article "Know Your Customers' Jobs to Be Done", written with Taddy Hall, Karen Dillon and David S. Duncan.
- Ulwick's Outcome-Driven Innovation (ODI) treats the job as a process, breaks it into steps and attaches measurable desired outcomes to each step, such as "minimize the time it takes to reconcile totals". Ulwick, founder of Strategyn, developed ODI in the early 1990s and presented the underlying theory to Christensen.
Jobs to be done example
Christensen's best-known example is a fast-food chain trying to sell more milkshakes. Many were bought early in the morning by commuters who wanted something filling that lasted a long, boring drive. They were hiring the milkshake for the commute, so its competition was bagels and bananas, not other milkshakes.
A B2B version: a finance lead does not want "a reporting tool". The job is "close the month with numbers I can defend to the CFO". Exports, spreadsheets and a colleague who double-checks are all competing to be hired for it.
Jobs to be done vs personas
| Jobs to be done | Personas | |
|---|---|---|
| Describes | The progress someone wants in a situation | A type of person |
| Explains behavior by | Circumstance and desired outcome | Demographics, role and attitudes |
| Competition | Anything hired for the same job, including workarounds | Usually products in the same category |
They work together: a persona says who, a job says what they are trying to achieve and when.
Common mistakes with JTBD
- Writing the solution into the job. "Export a report" is a task in your product; "prove the numbers are right" is the job.
- Ignoring the circumstance. The same person hires different products in different situations.
- Skipping the evidence. Jobs should come from what customers did and said in interviews, not from a workshop.
- Only listing functional jobs. Social and emotional dimensions, such as looking competent to a manager, often decide which product gets hired.
How does Praxiom AI help with jobs to be done?
Praxiom AI does not run a formal JTBD or ODI study. It helps with the evidence: it synthesizes interviews into insights with source quotes, including user behaviors and pain points, which are the raw material for writing job and outcome statements. See interview synthesis.
Frequently asked questions
Who invented jobs to be done?
Tony Ulwick developed Outcome-Driven Innovation, the practical method built on the jobs idea, starting in the early 1990s and shared it with Clayton Christensen. Christensen popularized the jobs-to-be-done framing in The Innovator's Solution (2003) and later writing.
What is a job statement?
A short description of the progress a customer wants, free of any solution. In ODI it is written as a verb, an object and a context, such as "close the month accurately". Desired outcomes are written as measurable statements, such as "minimize the time it takes to reconcile totals".
What is the difference between JTBD and user stories?
A user story describes a piece of product functionality for a user. A job describes the progress the user wants regardless of your product. Jobs help decide which user stories are worth writing.
Is jobs to be done still relevant?
Yes. It remains one of the most common ways product teams frame customer needs, especially when the real competition is a workaround rather than another product.
Sources
Run your product discovery on autopilot.
Bring your interviews, tickets and surveys. Get scored insights, a PRD and tickets.