HomeFrameworksDesign & UX › Jobs to Be Done (JTBD)
// framework

Jobs to Be Done (JTBD)

Clayton Christensen & Anthony Ulwick

A framework that asks what task a customer hires your product to do — transforming how you design, name, and describe products by anchoring every decision to the buyer's actual motivation, not their demographic.

// description

The Jobs to Be Done framework focuses on the underlying task (or "job") that a customer is trying to accomplish when they "hire" a product or service. Rather than segmenting customers by demographics, JTBD segments by the situation and desired outcome. A customer doesn't buy a drill because they want a drill; they buy it because they want a hole in the wall. Understanding the job reframes competition: a milkshake competes not just with other milkshakes but with anything that fills the job of "make my morning commute less boring."

// history

The framework draws on two parallel lines of work. Clayton Christensen (Harvard Business School) popularised the milkshake example in his books and lectures, emphasising the demand-side perspective. Anthony Ulwick developed the Outcome-Driven Innovation (ODI) methodology, providing a structured process for identifying underserved jobs and outcomes.

// example

A KDP author publishing recipe books segments her audience by job rather than demographic. One job: "I need to impress dinner guests without spending all day cooking." Another: "I want to teach my teenager basic cooking skills." A third: "I need weeknight meals I can make with pantry staples after a long day." Each job implies a different book with a different title, subtitle, cover, and keyword strategy. By designing for the job rather than a vague "people who like cooking" audience, each book's listing speaks directly to the buyer's specific situation, dramatically improving click-through and conversion compared to generic recipe books.

// katharyne's take

This framework completely changed how I write KDP book descriptions and Etsy listings. Ask yourself: what job is my customer hiring this product to do? Not "what is this product?" but "what problem does it solve at a specific moment in someone's life?" A gratitude journal isn't hired because someone wants to fill in daily prompts — it's hired because someone wants to feel less overwhelmed and more grateful at the end of a difficult season. Write your listing from inside that hiring moment, and you'll speak directly to the buyer's actual motivation rather than describing features that every competitor also has.

// creative uses
// quick actions
// prompt ideas
Apply Jobs to Be Done analysis to my [KDP book / Etsy product / digital course]: [describe the product briefly]. Identify 3-5 distinct jobs a customer might "hire" this product to do — be specific about the situation, the desired progress, and the emotional component for each job. Then rewrite my current listing title and first sentence of description for the most underserved job you identify.
I'm researching a new niche for [KDP / Etsy / a digital product]. Help me use JTBD to find underserved jobs in the [describe category — e.g. planner, journal, coloring book, prompt pack] market. What questions should I be asking in Amazon reviews, Reddit threads, and Etsy reviews to surface job statements? Give me the exact search strings and questions to look for.
Rewrite the product description for my [describe your product] using Jobs to Be Done language. Instead of describing features, describe the specific situation the buyer is in when they need this, the job they're trying to accomplish, and the progress or transformation they'll feel after using it. My current description reads: [paste current description].
See also: Kano Model · Value Proposition Canvas · Persona Development
← Hick's Law Kano Model →