Competing Against Luck: JTBD for Founders

Competing Against Luck, by Clayton Christensen and co-authors, argues that customers don't buy products — they hire them to make progress in a specific circumstance. That unit of progress is a "Job to Be Done." Understand the functional, emotional, and social job behind a purchase, and you can innovate on purpose instead of by luck.

Quick Answer: Competing Against Luck reframes innovation around the "Job to Be Done" — the progress a customer hires a product to make in a given situation. Nail the functional, emotional, and social dimensions of that job, and you compete on causality, not correlation.

Most founders build features and hope the market rewards them. Competing Against Luck (Clayton Christensen, Taddy Hall, Karen Dillon, and David S. Duncan, 2016) offers a more reliable path. This guide walks through the book's core theory of Jobs to Be Done and translates each idea into something a founder can act on before writing a line of code.

Why customers "hire" products to make progress in a circumstance

Customers hire products to make progress in a circumstance — they don't buy an object for its own sake. The central move in Competing Against Luck is to stop describing customers by their attributes and start describing the progress they are trying to make when a product enters the picture.

Christensen calls that progress a Job to Be Done. A job is not a task or a feature request. It is the whole story of what a person is struggling to achieve, in a specific situation, including the constraints and anxieties that come with it.

The distinction matters because most companies confuse correlation with causation. They collect mountains of data about who the customer is — age, income, job title, past behavior — and find patterns. But knowing that a 34-year-old buys your product does not tell you why, and it certainly does not tell you what to build next.

A job is the causal mechanism. It answers "why did this person hire this thing, right now, over the alternatives?" When you understand the job, product decisions stop being guesses. This is the shift the Jobs-to-Be-Done framework for founders is built to operationalize.

Two words carry the weight of the whole theory:

• Circumstance. The same person has different jobs at different moments. Context, not the customer profile, defines the job.
• Progress. A job always has direction — a customer moving from where they are toward where they want to be. Progress, not features, is what they are paying for.

Consider how this changes a founder's questions. Instead of asking "what does a small-business owner want in accounting software?" — a question about a profile — you ask "what was this person struggling to make progress on the day they went looking?" The first question invites a wish list. The second surfaces a story with a beginning, a trigger, and a decision, and that story is where the real design constraints live.

The book's provocation is that features are downstream of jobs. A well-specified job tells you what to build, what to leave out, and how to know when you have done it — none of which a demographic segment can tell you.

What Jobs to Be Done means — the core concepts at a glance

Jobs to Be Done is a theory of causation: it explains why customers make the choices they do, so you can predict what would make them switch. Before going deeper, it helps to see the book's vocabulary in one place, because the terms build on each other.

The table below maps the core concepts from Competing Against Luck to what each one means in plain language and why it changes how a founder decides.

Takeaway: these concepts are not independent tips — they compose into one lens. A job arises in a circumstance, carries three dimensions, and is contested by alternatives that include doing nothing at all. Get the lens right and the rest of the book follows.

The three dimensions of a job — functional, emotional, and social

Every Job to Be Done has three dimensions at once: functional, emotional, and social. Competing Against Luck argues that founders who optimize only the functional dimension routinely lose to products that are technically weaker but that satisfy the whole job.

Here is what each dimension captures:

• Functional — the practical task the customer needs accomplished. This is the dimension companies default to, because it is the easiest to measure and spec.
• Emotional — how the customer wants to feel, or to stop feeling. Reassured instead of anxious, confident instead of overwhelmed, in control instead of at the mercy of a process.
• Social — how the customer wants to be perceived by others, and how they want to see themselves. What hiring this product signals about the kind of person they are.

The reason this framing is powerful is that the functional job is often the least differentiated part of a category. Plenty of products can technically do the task. What decides the hire is frequently the emotional and social progress a customer is quietly seeking.

For a founder, this is a warning against feature races. If your entire pitch lives on the functional axis — faster, cheaper, more options — you are competing where differentiation is hardest and margins are thinnest. The emotional and social dimensions are where an underdog can win, because incumbents usually ignore them.

Picture a founder building a tool for freelancers to send invoices. The functional job is obvious: create and send an invoice. But the emotional job might be to feel professional and in control rather than embarrassed about chasing payment, and the social job might be to look established and credible to a new client. A competitor that only sped up invoice creation would miss two-thirds of what the freelancer is actually hiring for.

The practical habit is to write out all three dimensions for your target job before you scope features. If a feature only serves the functional dimension, ask whether an emotional or social improvement would move the hire more — the answer often reroutes the roadmap.

The milkshake study — how a single job reframes an entire market

The milkshake study is the book's most famous illustration of a Job to Be Done, and it shows how one product can be hired for completely different jobs. A fast-food chain wanted to sell more milkshakes and had spent months improving the product along obvious lines — thicker, sweeter, more flavors — based on what customer panels said. Sales did not move.

Researchers took a different approach. Instead of asking what would make the milkshake better in the abstract, they asked: what job are people hiring a milkshake to do? They watched when milkshakes were actually bought.

A large share were sold early in the morning, to solo commuters, taken to go. The job was not "enjoy a treat." It was closer to: make a long, monotonous drive more interesting and hold off hunger until lunch. The milkshake was perfect for it — thick enough to last the whole commute through a straw, filling, one-handed, and not messy.

Seen this way, the milkshake's competitors were not other milkshakes. They were bananas (gone too fast), bagels (dry and crumbly, needed two hands), donuts (messy), and coffee. That is the competitive set the job actually defines. You can explore the full breakdown in the milkshake Jobs-to-Be-Done example.

The twist: in the afternoon, the same product was hired for a different job. Parents bought milkshakes for their kids as a small way to say yes and feel like a good parent — an emotional and social job, with a completely different ideal product. One milkshake, two jobs. Improving "the milkshake" in general would have satisfied neither.

The founder lesson is not about milkshakes at all. It is that customer panels and attribute surveys pointed the company in the wrong direction for months, because they asked people to react to the product rather than describe their struggle. The breakthrough came from watching behavior in context. When your roadmap is stuck, the milkshake study says the answer is probably hiding in the circumstance you haven't observed yet.

The four forces of progress — what drives and blocks a switch

The four forces of progress explain why a customer does or does not switch to something new. Competing Against Luck describes two forces that push a customer toward change and two that hold them back — and a switch only happens when the first pair outweighs the second.

The table below summarizes the four forces qualitatively. Note that anxiety and habit are not obstacles to remove from the customer; they are real, rational feelings your solution has to overcome.

Takeaway: most founders obsess over the pull — making their solution more attractive. But a switch fails just as often because anxiety and habit are underestimated. To win the hire, you must both amplify the push and pull and actively defuse the anxiety and reduce the friction of leaving the old way behind.

This reframes onboarding, pricing, and messaging. A free trial reduces anxiety. A migration tool weakens habit. A vivid articulation of the customer's current frustration sharpens the push. Each lever maps to a specific force.

The forces also explain a frustrating category of "no decision" losses. When a prospect says your product is great and then does nothing, it is rarely because the pull was too weak. More often the anxiety of switching or the gravity of the current habit quietly won. Diagnosing which of the two stalled the deal tells you exactly what to fix — a reassurance, a guarantee, and a lighter migration path solve very different problems than a longer feature list.

Nonconsumption and negative jobs — your real competitors

Your biggest competitor is usually not a rival product — it is nonconsumption. Competing Against Luck stresses that when a customer struggles with a job, their most common response is to do nothing, tolerate the problem, or rig a makeshift workaround. That inaction is what you are really up against.

This matters because founders tend to define their market by named competitors and then position against them. But if most people with the job are currently hiring nothing, the real battle is convincing someone that making progress is worth the effort at all.

Nonconsumption shows up in a few recognizable forms:

• Doing nothing — the customer lives with the frustration because no option feels worth it.
• The workaround — a spreadsheet, a manual process, or duct-taping several tools together.
• The "good enough" substitute — a product built for a different job that is being stretched to cover this one.

There is a related idea worth naming: some jobs are ones people would rather not have at all. These "negative jobs" — things a customer wishes they never had to deal with — often signal the strongest opportunities, because the ideal solution helps them avoid the job entirely, not just perform it more efficiently.

For a founder, spotting nonconsumption is a gift. It means demand exists but is unserved, and you are not fighting a price war with an entrenched incumbent — you are giving people a way to make progress they had given up on.

The catch is that nonconsumption is invisible in the usual data. It leaves no purchase trail, no support tickets, and no competitor to benchmark against. You only find it by asking people about the job directly and listening for the workaround they are embarrassed to admit — the spreadsheet they have quietly maintained for three years, or the reason they stopped trying altogether.

Big hire vs. little hire — why product fit has to be earned repeatedly

A "big hire" is when a customer buys your product; a "little hire" is each time they actually use it to get the job done. Competing Against Luck draws this distinction to explain a painful pattern: you can win the purchase and still lose the customer.

The big hire is the moment of commitment — the signup, the purchase, the download. It is what most metrics celebrate. But the big hire only matters if it is followed by little hires.

The little hires are the repeated, ordinary moments when the customer reaches for your product instead of the alternative to make real progress. This is where the job is either done or not. Every little hire that goes well strengthens the relationship; every one that disappoints invites a "fire."

This is why so many products with strong early sales quietly stall. They won the big hire through marketing or novelty but never delivered the progress in daily use. The gap between "bought it" and "keeps using it" is the gap between the two hires.

For founders, the lesson is blunt: activation and retention are not separate from the job — they are the job, tested repeatedly. A demo that dazzles but a workflow that frustrates will win big hires and lose little ones, and churn will follow no matter how good the top of the funnel looks.

It also reframes what "product-market fit" means. Fit is not a milestone you cross once at launch; it is the accumulated evidence of little hires going well, over and over. A product earns the right to grow by making the job easier to complete each time, not by adding surface area. When you treat every little hire as the real test, roadmap priorities reorder themselves around the moments where customers actually experience progress or fail to.

How founders apply Jobs to Be Done to validate an idea

Founders apply Jobs to Be Done by investigating the story of a real switch, not by asking customers what features they want. The framework turns validation from opinion-gathering into causal detective work, which is exactly what an early-stage founder needs before committing resources.

A practical sequence looks like this:

1. Find people who recently switched to any solution for the job — including a workaround. Recent switchers remember the causal story; hypothetical customers invent one.
2. Reconstruct the timeline of their struggle: the first thought, the trigger event, the moment they decided to look, and the moment they hired something.
3. Map the four forces in their story — what pushed and pulled them, and what anxiety or habit almost stopped them.
4. Identify the true competitive set, including nonconsumption, so you know what you actually have to beat.

The interviews are where this lives or dies, and the questions are deliberately backward-looking rather than aspirational. A structured set of Jobs-to-Be-Done interview questions helps you surface the timeline and the forces instead of collecting wish lists.

This is also where a validation platform earns its keep. At Edmired, the point is to help founders test whether a real, hireable job exists before building — capturing the switch stories, forces, and nonconsumption signals in one place rather than scattered notes. JTBD gives you the questions; a disciplined process makes sure you actually act on the answers. For the wider method this fits into, see the complete guide to customer research for founders.

Key Takeaways

• A Job to Be Done is progress, not a product — customers hire solutions to move forward in a circumstance, so define your market by the job, not by demographics or features.
• Every job has functional, emotional, and social dimensions — winning only on the functional axis leaves the differentiation that decides most hires on the table.
• The milkshake study proves one product serves many jobs — the same item was hired for a commute and for parenting, and each job implied a different ideal product and competitive set.
• The four forces of progress govern every switch — amplify push and pull, but actively defuse the customer's anxiety and habit, or the switch never happens.
• Nonconsumption is usually your largest competitor — most people with a job do nothing or improvise, which means unserved demand, not an incumbent, is the real target.
• Big hires without little hires become churn — winning the purchase means nothing if the product fails to deliver the job in repeated daily use.
• Validate by studying real switches — reconstruct the timeline and forces behind an actual hire instead of asking customers to predict what they want.

Frequently Asked Questions

What is the main idea of Competing Against Luck?

The main idea is that customers hire products to make progress in a specific circumstance — a "Job to Be Done." By understanding the functional, emotional, and social job behind a purchase, companies can innovate predictably rather than relying on luck or correlation-based guesswork.

Who wrote Competing Against Luck?

Competing Against Luck was written by Harvard Business School professor Clayton Christensen with co-authors Taddy Hall, Karen Dillon, and David S. Duncan. Published in 2016, it builds on Christensen's earlier disruption work and formalizes the Jobs-to-Be-Done theory of innovation and customer behavior.

What is the milkshake example in Jobs to Be Done?

The milkshake example shows a fast-food chain discovering that morning commuters hired milkshakes to make a boring drive more interesting and stave off hunger — competing with bananas and bagels, not other milkshakes. The same product was later hired for a different, parenting-related job.

What are the four forces of progress?

The four forces are the push of the situation and the pull of the new solution, which drive change, plus the anxiety of the new choice and the habit of the present, which block it. A customer only switches when the driving forces outweigh the blocking ones.

How is Jobs to Be Done different from customer personas?

Personas describe who a customer is — their traits and demographics — while Jobs to Be Done describes what progress a customer is trying to make in a circumstance. JTBD focuses on causation rather than correlation, which makes it far more predictive of actual buying and switching behavior.