Key Principle
A Job to Be Done is not a task, activity, or need -- it is the process a customer goes through to transform their existing life-situation into a preferred one. Products are not end goals; they are enablers customers "hire" to become a "new me" they have imagined. The engine of all demand is self-betterment: the gap between who a customer is today and who they want to become.
Critically, JTBDs are designed, not discovered. Customers must first imagine a better version of themselves before desire arises. This means marketing, word of mouth, and social exposure can create demand by catalyzing that imagination. Without the "new me" picture forming in the customer's mind, no Job exists and no purchase happens (Chapter 2).
Why This Matters
Most innovation frameworks anchor teams to the current product form -- studying "needs" tells you what customers dislike about today's solution, not what progress they are trying to make. This anchoring is why companies optimize drill bits when customers would happily abandon drilling altogether, and why Kodak shelved the digital camera in 1975 to protect film sales (Chapter 1). JTBD breaks this trap by decoupling innovation from product description entirely: the unit of analysis is the customer's transformation arc, not the product's spec sheet.
The self-betterment lens also explains a puzzle that demographic and satisfaction data cannot: why customers whose needs are already well met continue hunting the market for new solutions. Satisfied customers still switch because self-betterment never terminates -- "Customers are always beautifully, wonderfully dissatisfied, even when they report being happy and business is great" (Chapter 3). If your framework cannot explain why happy customers leave, it cannot predict or create new demand.
Good Examples
Revlon's "Fire and Ice" campaign (1952): Sold transformation, not cosmetics. Provocative self-assessment questions and aspirational imagery helped customers design a new version of themselves; the product was barely mentioned. Charles Revson: "In the factory, we make cosmetics. In the drugstore, we sell hope." Revlon remained profitable for eighty-four years (Chapter 2).
Andreas and Basecamp: A medical tourism business owner assumed his 5-person company had hit its growth ceiling. Only after hearing about Basecamp from a friend did he imagine a "new me" -- a business owner whose company could stay organized as it scaled. His JTBD did not exist until the better version of himself was designed in his mind (Chapter 2).
Weber Grills: Offers education, recipes, party-planning guides, accessories, and a free hotline -- not just grills. "Weber understands that it's not in the business of making and selling grills. It's in the business of making people better grillers." Profitable since 1893 (Chapter 3).
Counterpoints
The chotuKool refrigerator: Godrej partnered with Clayton Christensen to design a "disruptive innovation" for low-income Indians (2006). It failed as "a costly flop" because it answered a competition map drawn by the company, not by the buyer. Industry-defined competition led to a product that ignored how customers actually framed their choices (Chapter 2).
Confusing usage with progress: The author's second business (Vizipres) "made a product that people would use, but not pay for." High engagement does not mean the product connects to self-betterment. Customers will pay for products they rarely use (gym memberships, insurance) if those products enable identity-level progress -- and ignore high-usage products that do not (Chapter 2).
Classifying Jobs into types: Attempting to categorize Jobs as "emotional," "functional," or "social" adds no actionable information -- only unresolvable team debate. "Take it from me, don't waste your time trying to dissect Jobs into different types. It's about as productive as trying to answer, 'How many angels can dance on the head of a pin?'" (Chapter 3).
Key Quotes
"A Job to be Done is the process a consumer goes through whenever she aims to transform her existing life-situation into a preferred one, but cannot because there are constraints that stop her." -- Alan Klement, Chapter 2
"Upgrade your user, not your product. Don't build better cameras -- build better photographers." -- Kathy Sierra, quoted in Chapter 2
"We can't build the products of tomorrow when we limit ourselves to the needs and expectations associated with the products of today. Instead, we should focus on what never changes for customers: their desire for progress." -- Alan Klement, Chapter 2
"A dissatisfied customer does not complain; he just switches." -- W. Edwards Deming, quoted in Chapter 2
Rules of Thumb
- Frame the Job as the customer's desired transformation ("become a better griller"), never as a product function ("buy a grill") or a task ("cook steaks").
- If you cannot describe the "new me" your customer is trying to become, you do not yet understand the Job.
- Treat compensatory behaviors (customers repurposing your product for unintended uses) as demand signals for Jobs no existing product serves directly.
- When growth plateaus, resist adding features to push metrics -- this creates baggage that makes a lean competitor more attractive.
- Test your Job statement with the Decision Tree: Can you visualize the customer acting it out? Then it is a task, not a Job. Does it describe what the customer dislikes? Then it is a complaint. Does it describe a better version of the customer? Then it is a Job.
- Competition is customer-defined and cross-category. Your real competitors are whatever the customer mentally simulates as enabling the same progress -- not the companies in your industry classification.
- Products deliver value even when not actively used. Do not let usage metrics cause you to cut features whose real worth is ambient readiness, security, or optionality.
- Value is context-dependent: "progress defines value, and contrast reveals it." Evaluate your product against alternatives in the same situation, not the same category.
- JTBD is zero-sum at the individual level -- a customer holds one solution per Job at a time. Adoption of a new solution causes abandonment of the old one, not portfolio expansion.
Related References
- The Forces of Progress - the emotional forces that drive JTBD
- The System of Progress - how Jobs evolve in interconnected systems