Jobs To Be Done

Jobs To Be Done (JTBD) is the lens I reach for when a team is drowning in feature requests and demographic personas and still cannot explain why people actually use the product. The core idea was popularized by Clayton Christensen and developed in parallel by Tony Ulwick (Outcome-Driven Innovation): customers don't buy products; they "hire" them to do a job. Your product is competing not with the obvious rivals but with every other way a customer might get that job done, including doing nothing at all.

#The milkshake, briefly

Christensen's famous example: a chain could not sell more milkshakes by tweaking flavors. Reframed by job, the data showed morning commuters "hiring" the shake to make a dull drive less boring and to stay full until lunch. Its real competitors were bananas, bagels, and boredom. Demographics were useless, and the job explained everything. That is the whole method: stop describing who the customer is and start understanding what progress they're trying to make.

#The shape of a job statement

A well-formed job is solution-agnostic and built around progress:

When [situation], I want to [motivation], so I can [expected outcome].

For example: "When I'm watching a game with friends and the odds shift, I want to place a bet in seconds, so I can act before the moment passes." No app, no feature, no demographic, and that is deliberate, so the solution space stays wide open. It also exposes the three layers of a job: functional (place the bet fast), emotional (don't look slow in front of friends), and social (be the one who called it). Most products over-serve the functional and ignore the other two, which is exactly where loyalty actually lives.

#JTBD vs personas, the contrast I care about

This is where the framework is best known, and where I hold a strong view.

Here is my take: personas tell you who is in the room, and jobs tell you why they came. They are complementary, but when forced to choose, the job is the more durable foundation for strategy, because a persona built on demographics will happily predict the wrong thing (the milkshake buyers spanned every demographic). I use jobs for "what business are we even in", and personas and journeys to ground day-to-day design. Personas drift into theater. JTBD drifts into an abstract framework debate that never touches a real decision. Watch for both.

#How I actually use it

• To find the real competitor. What does the customer do today to get this job done? Usually it is not who you think. Often it is a spreadsheet, a text to a friend, or nothing.
• To frame opportunities in an Opportunity Solution Tree. Unmet jobs and under-served outcomes are exactly the opportunity branches.
• To write outcome-based product goals instead of feature lists, feeding Strategic Impact.
• As the thing to listen for in a customer interview. Ask about the last time they did the job, not whether they would like your feature.

#How AI is changing it

AI is good at the first pass of job discovery. Feed it a thousand reviews and support tickets and it will cluster the recurring "I was trying to…" patterns into candidate jobs faster than any analyst, which accelerates surfacing the functional job. But the emotional and social layers, and the judgment to tell a real, fundable job from a plausible-sounding cluster, stay human work. A model will confidently name a "job" that is really an artifact of how people phrase their complaints. Use it to widen the net, not to make the call. See AI in Discovery and Research.

#Continue Reading

• User Personas and Journey Mapping for the complementary lens, and where personas earn their keep.
• The Opportunity Solution Tree for where unmet jobs become opportunity branches.
• Voice of the Customer for the competency JTBD sharpens.
• Outcomes Over Outputs for the kindred idea: progress over features.
• Product Sense and Judgment for the judgment that turns a job into the right bet.