Definition
Jobs to Be Done (JTBD)
Jobs to Be Done is a framework for understanding why customers adopt a product: people "hire" products to make progress on a specific job in a given circumstance. It shifts focus from customer demographics and product features to the underlying goal — the job — revealing the real competition and the true criteria by which customers judge success.
Key takeaways
- Jobs to Be Done holds that customers "hire" products to make progress on a specific job in a given circumstance.
- It shifts focus from demographics and features to the underlying goal — the job — which is what actually predicts adoption.
- A good job statement is solution-agnostic and spans functional, emotional, and social dimensions, revealing non-obvious competitors.
- It anchors product decisions to a durable customer goal rather than to technology fashions or fleeting feature requests.
The core insight, popularized by Clayton Christensen, is captured in the line: people don't want a quarter-inch drill, they want a quarter-inch hole — and really, they want to hang a picture. Customers don't buy products; they hire them to make progress in a particular situation. Understanding that job, not the customer's age or industry, is what predicts adoption.
A well-formed job statement is solution-agnostic and stable over time. Functional, emotional, and social dimensions all matter: the milkshake bought to make a boring commute less dull is doing an emotional job, not just a nutritional one. Framing this way reveals non-obvious competitors — the milkshake competes with bananas and bagels, not other milkshakes.
JTBD reframes the entire product conversation. Features are evaluated by how well they help the customer make progress on the job, not by novelty. It guides what to build, what to ignore, and how to position, because it anchors decisions to a durable customer goal rather than to fashions in technology or fleeting feature requests.
Planoda's roadmaps can be structured around jobs rather than features, so initiatives trace explicitly to the customer progress they're meant to enable.
Related terms
- Product-Market FitProduct-market fit is the point at which a product satisfies a strong market demand — the right product serving the right market so well that growth begins to pull rather than push. It is the milestone before which a startup should focus on finding fit, and after which it should focus on scaling, often felt as demand outrunning the team's ability to keep up.
- User StoryA user story is a short, plain-language description of a feature told from the user's perspective, classically in the form 'As a [role], I want [capability], so that [benefit].' It captures who needs something and why, deliberately leaving the how to the team. Stories keep work framed around user value rather than technical tasks.
- North Star MetricA North Star metric is the single measure that best captures the core value a product delivers to customers — and that, when it grows, reliably pulls revenue and retention up with it. It aligns an entire company on one number, cutting through competing departmental metrics so every team can see how its work moves the thing that matters most.
- PRD (Product Requirements Document)A PRD (product requirements document) defines what a product or feature should do and why, before it is built. It captures the problem, the target users, the goals and success metrics, the scope, and the requirements — giving design, engineering, and stakeholders one shared reference so everyone builds toward the same outcome rather than their own interpretation.
- RoadmapA roadmap is a high-level, time-oriented view of what a team or product plans to build and roughly when. It communicates direction and sequencing across initiatives and projects, aligning stakeholders on priorities. Unlike a backlog of granular tasks, a roadmap operates at the altitude of themes, outcomes, and quarters rather than individual issues.