Jobs to Be Done: The Framework That Fixes Bad Products

Clayton Christensen introduced Jobs to Be Done at Harvard in the early 2000s. The idea sounds simple: people don't buy products, they hire them to do a job. A guy buying a milkshake at 7am isn't craving dairy. He's hiring the milkshake to make his boring commute bearable and keep him full until lunch.

That one insight changed how smart companies build products. Instead of asking "what features should we add?" you ask "what job is the customer trying to get done?" It flips the whole conversation. You stop obsessing over competitors and start obsessing over the moment your customer reaches for a solution.

We used JTBD with a client who ran a pet grooming SaaS. They kept adding features — breed databases, grooming tutorials, inventory tracking. Usage was flat. When we interviewed their customers using JTBD questions, the real job emerged: groomers wanted to fill empty appointment slots. That was it. The whole product strategy shifted to booking and reminders. Revenue doubled in four months.

Why this matters to you

Most products fail because they solve problems the builder imagined, not problems the customer actually has. JTBD forces you to get out of your own head. It's not about demographics or personas. It's about the specific moment someone decides they need something and the progress they're trying to make in their life.

When you understand the job, you stop wasting time on features that look impressive in demos but don't move the needle. You build less, but everything you build matters.

More in Frameworks