/christensen-jobs

name: christensen-jobs
description: "Knowledge base from \"Competing Against Luck: The Story of Innovation and Customer Choice\" by Clayton M. Christensen, Taddy Hall, Karen Dillon & David S. Duncan. Use when applying Jobs Theory / Jobs to Be Done for innovation, customer research, product strategy, the Forces of Progress, the job spec, purpose brands, integrating around a job, or referencing its concepts."
allowed-tools:
  - Read
  - Grep
argument-hint: [topic, framework name, or chapter number]

Competing Against Luck

**Author**: Clayton M. Christensen with Taddy Hall, Karen Dillon & David S. Duncan | **Pages**: ~256 | **Chapters**: 10 (+ Introduction) | **Generated**: 2026-06-08

How to Use This Skill

• **Without arguments** — load core frameworks for reference
• **With a topic** — ask about `forces of progress`, `nonconsumption`, `job spec`, `the three fallacies`; I find and read the relevant chapter
• **With chapter** — ask for `ch05`; I load that specific chapter
• **Browse** — ask "what chapters do you have?" to see the full index

When you ask about a topic not in Core Frameworks below, I read the relevant chapter file before answering.

---

Core Frameworks & Mental Models

**The central question** — *"What job did you hire that product to do?"* Customers don't buy products; they **hire** them to make progress, and **fire** them when something does the job better.

**The Job to Be Done (the definition)** — *A job is the progress that a person is trying to make in a particular circumstance.* Three load-bearing words:

• **Progress** — movement toward a goal/aspiration. A job is never just a function; it's a verb-driven struggle, not a product category or a customer attribute.
• **Circumstance** — the job is defined by the *situation*, not by customer demographics, product attributes, technology, or trends. "I'm a 40-year-old male" doesn't cause a purchase; "I have a long, boring morning commute and one free hand" does. **The circumstance is the fundamental unit of innovation work** — not the customer.
• **Functional + Social + Emotional dimensions** — every job has all three; the social and emotional are often heavier than the functional. Miss them and you miss the job.

**Jobs are stable; solutions churn.** The job ("get me from A to B reliably") barely changes over decades; the products hired to do it (horse → car → Uber) change constantly. Innovate against the job, not the current solution.

**The Milk Shake Dilemma** — When you study the *product* (improve the shake), you optimize the wrong thing. When you study the *job* (the morning shake is hired to make a boring commute survivable with one hand; the afternoon shake is a different job — a dad placating a kid), you see what to build and what you really compete with. Same product, two different jobs.

**Competing against nonconsumption / "competing with nothing"** — your real competition is often not a rival product but the customer doing nothing, or a clumsy workaround. The biggest growth lives where people are currently *not* solving the job at all.

**Causality, not correlation** — Big Data shows *what* correlates; Jobs Theory supplies the *causal mechanism* of why people buy. Data describes; the job explains and predicts. Most data measures attributes of customers and products — neither of which causes a purchase.

**Big Hire / Little Hire** — the **Big Hire** is the purchase (money changes hands); the **Little Hire** is every time the customer actually *uses* the product to get the job done. A product can be Big-Hired and never Little-Hired (bought, never used) — that's a job not actually being done.

**The Forces of Progress** (the switch happens only when push + pull > habit + anxiety):

• **Push** of the situation — the frustration/struggle with the current state.
• **Pull** of the new solution — the attraction of the new idea.
• *(opposing)* **Habits of the present** — inertia; "it's good enough."
• *(opposing)* **Anxiety of the new** — anxiety of choosing + anxiety of using.

To win a switch you must amplify push+pull **and** actively dismantle habit and anxiety — most innovators ignore the two opposing forces entirely.

**The Job Spec → the Résumé** — write the job as a spec: the functional/social/emotional dimensions, the trade-offs the customer will make, the obstacles to remove, the competing set ("the job's résumé of candidates"). Then design the product as a *résumé* that perfectly matches the spec — including the **experiences** of purchase and use that the job requires.

**Experiences, not features, command premium prices and loyalty.** Competitors can copy features; the right set of experiences wrapped around the job is what's hard to copy and what earns a **purpose brand** — a brand the customer mentally equates with the job ("milk for my Oreos," "I'll just Uber there"). A purpose brand is the highest-leverage asset in innovation.

**Integrate around the job, not the function.** *Processes* — how you integrate to get the customer's job done — are the durable competitive advantage, because they're invisible and hard to copy (Mayo Clinic, Amazon). Org charts are built around functions and products; the job cuts across them.

**The Three Fallacies of Innovation Data** — why good companies lose sight of the job: 1. **Fallacy of Active vs. Passive Data** — once a product ships, "operations" data (active, abundant, easy) crowds out the rich, passive, context-laden data of the original job. The map replaces the territory. 2. **Fallacy of Surface Growth** — chasing growth by selling more *products* to existing customers (line extensions, adjacencies) pulls focus off the core job and dissolves the company's purpose-brand clarity. 3. **Fallacy of Conforming Data** — managers unconsciously bend data to fit the model they already believe; data has no voice of its own.

**The Jobs-Focused Organization** — make the job, not the function, the organizing principle. Like **commander's intent**, a clearly und