Jobs-to-be-done theory reframes the central product discovery question from "who is our customer" or "what features do people want" to "what underlying job is a customer trying to get done, and what are they currently hiring to do it" — a genuinely valuable reframing that has helped many product teams uncover real customer motivation and unexpected competitive dynamics they'd otherwise have missed. It is not, on its own, a complete product or business strategy, and treating it as one skips over several genuinely important strategic questions the framework was never designed to answer.
What the framework genuinely does well
Asking what job a customer is actually trying to accomplish, rather than starting from a specific product category or feature set, often reveals that customers are "hiring" a surprisingly wide range of different solutions to accomplish the same underlying job — a well-known example describes fast food milkshakes being purchased by commuters specifically for a long, one-handed, not-too-messy breakfast during a boring commute, a job better understood by observing this actual use case than by conventional demographic segmentation of milkshake buyers. This reframing genuinely surfaces real, actionable insight about actual customer motivation that feature-focused or demographic-focused discovery methods can miss.
What the framework doesn't tell you, even once the job is well understood
Understanding the specific job a customer hires your product to do doesn't, on its own, tell you how to build a defensible, differentiated position relative to the other solutions customers are also using to get that same job done — a genuinely separate strategic question requiring frameworks addressing competitive positioning, differentiation, and moat-building that jobs-to-be-done theory doesn't directly provide. Knowing the job also doesn't resolve how to price a solution, since pricing depends on factors like willingness to pay, competitive alternatives' pricing, and unit economics that the underlying job's identification doesn't directly determine.
Why prioritization among multiple genuine jobs remains a separate, unresolved question
A product can plausibly serve several different genuine jobs for different customer segments, and jobs-to-be-done theory doesn't inherently provide a method for prioritizing among these multiple genuine jobs when resources are limited — that prioritization decision still requires separate strategic judgment about market size, competitive intensity, and strategic fit that the framework's core discovery method doesn't directly address on its own.
Why this matters for how the framework should actually be used
A product team that treats "we've identified the job" as equivalent to "we now have a complete product strategy" skips directly from a genuinely valuable discovery insight to strategic decisions the framework was never designed to make on its own — jobs-to-be-done functions best as an input into a broader strategic process, informing decisions about competitive positioning, pricing, and prioritization that still require their own separate frameworks and judgment.
What this means for applying jobs-to-be-done theory effectively
- Use jobs-to-be-done theory specifically for the discovery task it excels at — uncovering genuine underlying customer motivation and identifying unexpected competitive alternatives
- Pair job identification with separate frameworks addressing competitive positioning, pricing strategy, and prioritization among multiple candidate jobs
- Avoid treating "we understand the job" as equivalent to having a complete product strategy, since genuinely important strategic questions remain open even after the job is well understood
- Recognize the framework's value as a discovery lens, distinct from and complementary to the broader strategic decisions a product team still needs to make
Jobs-to-be-done theory earns its influence through a genuinely powerful discovery reframing — the limitation isn't in what the framework does, it's in treating that genuine discovery value as a substitute for the separate strategic work the framework was never built to do.