Jobs to Be Done: Why Your Customers "Hire" Your Product (and What That Changes)
Customers don't want your product — they hire it to get a job done, and fire it when something does the job better. Here's how Jobs to Be Done reframes discovery, prioritization, and messaging.
Your customers don't want your product. They never have. They have a job to get done, and your product is just the thing they've "hired" to do it — and the moment something does the job better, they'll fire you without a second thought. That's the uncomfortable core of Jobs to Be Done (JTBD), and it changes how you build.
"Hire" and "Fire"
The framing comes from Clayton Christensen's milkshake study and Tony Ulwick's work: people don't buy products, they hire them to make progress in a specific situation. Nobody wants a quarter-inch drill; they want a quarter-inch hole — and really, the shelf that hole lets them hang. When you see your product as one of many candidates competing to do a job, the competitive set explodes: your rival isn't just the obvious competitor, it's the spreadsheet, the status quo, and "doing nothing."
The Three Dimensions of Every Job
A job is never purely functional. There are three layers:
- Functional — the practical task ("file my taxes accurately").
- Emotional — how the person wants to feel ("not anxious I'll get audited").
- Social — how they want to be seen ("someone who has their finances together").
Miss the emotional and social layers and you build a technically-correct product nobody loves. Most feature requests describe the functional job; the interview is where you find the other two.
Why It Beats Personas and Features
Personas describe who the customer is; jobs describe what they're trying to accomplish — and the job is both more stable and more actionable. As JTBD practitioners put it, jobs remain stable while solutions change: "send money to my family abroad" is a job that has outlived cash, wire transfers, and three generations of apps. Anchor strategy to the job and you get a foundation that doesn't move every time the tech does. It also sharpens everything downstream — discovery gets grounded, prioritisation gets clearer, and messaging writes itself, because you're speaking to intent instead of features.
Keep reading
Stakeholder Management in the Age of AI: Why Everyone Now Has an Opinion About Your Roadmap
In 2026, every stakeholder has an AI assistant generating roadmap ideas. The PM's information advantage is gone — unless you build a different kind of advantage: specific customer evidence that no AI can replicate.
Is Your AI PM Tool EU AI Act Compliant? A Framework for Product Managers
Every AI tool in your stack now has to answer this question. Here is the 4-step framework we used to answer it honestly for Specky, and how to run it on your own stack in under an hour.
Customer Journey Mapping for Product Managers: Stop Guessing, Start Seeing
Most customer journey maps end up as beautiful wall art that nobody opens after the workshop. Here's how to build one that actually drives product decisions.