Competing Against Luck — Clayton Christensen
Core Thesis
Customers don’t buy products — they “hire” them to do a job. Understanding the Job to Be Done (JTBD) — the progress a customer is trying to make in a specific circumstance — is the key to innovation that isn’t luck.
Key Principlesflashcards
What is a “Job to Be Done” and how is it different from a customer need? ? A JTBD is the progress a person is trying to make in a particular circumstance. It includes functional, emotional, and social dimensions.
- “Need”: I need a drill → focuses on the product
- “JTBD”: I need a hole in my wall so I can hang a family photo that makes my home feel warm → focuses on the progress The circumstance matters as much as the need. The same person has different jobs in different contexts.
What is the “milkshake story” and what does it teach? ? McDonald’s wanted to sell more milkshakes. Demographics and product attributes didn’t help. When they studied the JTBD: 40% of milkshakes were bought before 8am, by solo commuters, to:
- Make a boring commute more interesting
- Keep them full until lunch
- Be consumable with one hand while driving The competition wasn’t other milkshakes — it was bananas, bagels, boredom. Understanding the JOB, not the product category, reveals true competitors and true innovation opportunities.
What are the “forces of progress” in a JTBD switch? ? Four forces determine whether someone “hires” a new solution: Push FOR change:
- Dissatisfaction with current solution
- Attraction of new solution Push AGAINST change:
- Anxiety about the new solution (“what if it doesn’t work?“)
- Habit of the current solution (“I know how this works”) Innovation must strengthen forces 1+2 AND reduce forces 3+4. Most companies only focus on making the new thing attractive (force 2) and ignore the other three.
What is the difference between “active” and “passive” job data? ? Active data: what customers SAY they want (surveys, interviews, feature requests). Often misleading. Passive data: what customers actually DO — workarounds, compensating behaviors, complaints. Much more revealing. Watch for: what are people cobbling together from multiple tools? What do they complain about? What do they hire a crappy solution for because nothing better exists? That’s where unmet jobs live.
How do you integrate JTBD into organizational decision-making? ? Make the job the unit of analysis, not the customer segment or product feature:
- Product roadmap: organized by jobs, not features
- Metrics: “how well are we fulfilling the job?” not just NPS
- Competitive analysis: who else could be hired for this job? (often not who you think)
- Team structure: teams own jobs, not product surfaces When everyone shares the same understanding of the job, alignment happens naturally.
Situations
- product-strategy, customer-insight, roadmap-planning, prioritization, innovation, stakeholder-communication, market-analysis