Clayton Christensen used to tell a story about a fast food company that wanted to sell more milkshakes. They interviewed customers about flavour preferences, sweetness levels, and cup size. Nothing they changed moved sales. Then a researcher tried a different approach: he stood in a car park and watched people buy milkshakes. He asked one question — "what were you trying to do when you decided to get a milkshake this morning?"
The answer: most morning milkshake buyers had a long, boring commute ahead of them. They wanted something that would keep them occupied and not leave them hungry before lunch. The milkshake did that better than a banana (too fast), a bagel (too messy), or a coffee (too small). The product they were competing with wasn't other milkshakes — it was boredom and hunger.
That story is the essence of Jobs-to-be-Done. People don't buy products. They hire them to do a job in their life.
In JTBD terminology, a "job" is the progress a person is trying to make in a particular circumstance. It's not a task ("I need to send a file"). It's not a goal ("I want to be more productive"). It's the specific progress a specific person is trying to make in a specific situation — with all the context, constraints, and emotions that surround that moment.
The job has three components: a situation (the trigger that creates the need), a motivation (what the person is trying to achieve), and an outcome (the definition of success from their perspective). All three matter. A product that nails motivation but ignores situation will be used at the wrong moments. A product that nails situation but ignores outcome will get hired and quickly fired.
Writing formal JTBD statements forces clarity about what job your product is actually being hired to do — and reveals gaps between what you think the job is and what users actually experience.
Notice how each statement reveals something a feature list never would: the emotional stakes, the context of competing forces, and the definition of success from the user's perspective. None of these would surface in a survey asking "what features do you want?"
Every job has three dimensions, and products that only address the functional one leave real value on the table.
Slack didn't grow because it was better than email at sending messages (functional). It grew because it made teams feel more connected and alive (emotional) and made individuals feel like they were part of a real-time conversation rather than an inbox queue (social). Features that address only the functional job are easily commoditised. Products that address all three dimensions are much harder to replace.
The best JTBD research focuses on the moment of hiring — the decision to start using a product — and the moment of firing — the decision to stop. Both moments are rich with signal.
For the hiring interview, ask: "Think back to the last time you decided to use [product]. What was going on? What were you trying to accomplish? What else did you try first?" For the firing interview: "When did you stop using [product]? What were you doing right before you decided to switch? What did the alternative do differently?"
The answers will almost always surprise you. Users will describe situations, frustrations, and motivations that your team never anticipated. That's the point. JTBD research is not validation research — it's discovery research. You're not testing your assumptions; you're replacing them with evidence.
Once you've identified the primary jobs your product is hired to do, use them as a filter for every significant product decision. For any proposed feature, ask: which specific job does this help users make progress on? If the answer is "none of our primary jobs," that's a strong signal to deprioritise — even if the feature sounds appealing.
JTBD also reveals where you're over-serving. If users have a job that's already being done well enough, adding more features to that area provides diminishing returns — and potentially adds complexity that makes the product harder to use for users with different jobs. The jobs lens shows you where to invest and where to stop.