Customers Don't Buy Products—They Hire Them: Jobs to Be Done for Strategic Thinking
For Senior Product Managers and Product Leaders navigating the age of AI, LLMs, and Agentic Products
Among the frameworks that have genuinely influenced the practice of product management over the past three decades, Jobs To Be Done (JTBD) occupies a distinctive position: it is simultaneously one of the most theoretically rigorous and one of the most practically transformative tools available to product strategists. Yet it is also among the most frequently misapplied. Organizations that adopt JTBD as a user research interview technique—a more narrative-rich alternative to traditional requirements gathering—capture only the most superficial layer of the framework’s strategic value. The deeper contribution of JTBD is not methodological; it is ontological. It reframes the fundamental unit of strategic analysis in product development from “what features does the customer want?” to “what progress is the customer trying to make in their life or work, and what is the current situation preventing them from achieving it?”—a reframing that has profound implications for how product leaders think about competition, differentiation, and the conditions under which customers switch.
The intellectual history of JTBD is instructive for understanding its strategic depth. Tony Ulwick conceptualized the core framework in 1990, applying Six Sigma’s outcome-measurement logic to the innovation process and formalizing it as Outcome-Driven Innovation (ODI) in 1999 (Strategyn, 2024). Clayton Christensen, introduced to the framework by Ulwick, elaborated and popularized it in The Innovator’s Solution (2003), developing the “milkshake example” that became one of the most cited illustrations in product management literature. Bob Moesta and Chris Spiek subsequently developed the “Forces of Progress” model and the “Switch Interview” methodology, focusing on the precise moment at which customers switch from one solution to another and the psychological forces that govern that transition. Alan Klement’s “jobs-as-progress” theory extended the framework into its most expansive formulation: that a “job” is not merely a task to be completed but a form of progress toward an improved version of the customer’s situation—an aspiration that encompasses functional, emotional, and social dimensions simultaneously (Klement, as cited in GoPractice, 2024).
This essay develops the strategic application of JTBD across three dimensions: the tripartite structure of functional, emotional, and social jobs and its implications for product design and positioning; the outcome-driven thinking methodology and how it reframes competitive analysis; and the switching trigger dynamics that determine when and why customers adopt new solutions—with particular attention to the AI era’s implications for each.
Functional, Emotional, and Social Jobs: The Full Architecture of Customer Motivation
The simplest formulation of JTBD—customers hire products to get jobs done—is accurate but dangerously incomplete if it is taken to mean only functional jobs. Every customer situation that motivates a product search contains at minimum three distinct job dimensions: a functional job (the concrete task the customer needs to accomplish), an emotional job (the internal feeling the customer wants to achieve or avoid in the process), and a social job (the way the customer wants to be perceived by others in the context of the task). Neglecting the emotional and social dimensions—as is common in product teams with an engineering-dominant culture—produces products that are technically capable but psychologically or socially misaligned with what the customer is actually trying to achieve (GoPractice, 2024; UXCrush, 2026).
The functional job is the dimension that product teams most readily attend to, because it is the most directly observable and the most naturally connected to the language of product requirements. A business professional who “hires” a presentation software product has a functional job: producing a visually coherent slide deck within a limited time. A team that uses a project management tool has a functional job: coordinating work across individuals with different responsibilities, time zones, and priorities. Defining the functional job precisely—and, crucially, at the right level of abstraction—is the first step in JTBD analysis. Ulwick’s ODI framework is particularly rigorous on this point, insisting that the job should be defined independently of any specific solution, at a level of abstraction that captures the underlying progress the customer is seeking rather than the specific workflow step they currently perform (Ulwick, as cited in Strategyn, 2024).
The emotional job captures what the customer wants to feel—or to avoid feeling—in the course of getting the functional job done. The professional using presentation software does not merely want to produce slides; they want to feel confident that the output reflects well on their capabilities, to avoid the anxiety of discovering a formatting problem at the last moment, and to feel that the time invested was proportionate to the output quality achieved. These emotional dimensions are not peripheral to the product experience; they are central to it. Products that address the functional job well but fail to manage the emotional dimensions—creating anxiety, frustration, or a sense of inadequacy in the course of use—will generate functional satisfaction and emotional dissatisfaction simultaneously, a combination that produces weak retention and poor word-of-mouth despite adequate feature coverage.
The social job captures the dimension that is perhaps most consistently underweighted: what the customer wants others to think about them in the context of the task. The team adopting a new collaboration tool does not merely want to coordinate work more effectively; they also want to signal organizational sophistication, to be seen as technologically current by peers and superiors, and to demonstrate the kind of systematic thinking about team performance that reflects well on the team leader’s judgment. Slack’s early adoption dynamics were driven significantly by social job considerations—teams that adopted Slack were signaling a particular organizational culture and identity, one associated with technical modernity and startup-adjacent practices, that was as motivationally significant for some early adopters as the functional communication improvements the product delivered (Intercom, 2024).
In the context of AI-native product development, the social job dimension has acquired particular strategic importance. The adoption of AI-powered tools in organizational contexts is not governed only by functional performance—how well the AI performs the task—but significantly by the social and identity dimensions of being known as an AI-forward organization, team, or individual. Product leaders building AI tools for knowledge workers should attend carefully to both the functional and social job dimensions: the AI capability must be demonstrably effective at the functional task, but it must also be designed and positioned in a way that allows users to adopt it without compromising the social and professional identity dimensions that govern self-presentation in organizational contexts (Gocious, 2026).
Outcome-Driven Thinking: Reframing the Competitive Arena
The most transformative strategic contribution of Ulwick’s ODI framework is the concept of outcome-driven innovation: the practice of identifying the specific, measurable outcomes that customers are trying to achieve in getting a job done, and using those outcomes—rather than product features or customer-stated preferences—as the primary unit of competitive analysis and product investment decision-making.
In Ulwick’s formulation, a customer outcome is a metric that the customer uses to evaluate how well the job is getting done: “minimize the time required to X,” “increase the likelihood of Y,” “reduce the number of errors in Z.” These outcomes are stable—they do not change when new solutions emerge, because they are properties of the job rather than properties of any specific solution—and they are measurable, because the customer can reliably assess the degree to which a solution moves the outcome in the desired direction. The strategic implication is that competitive analysis, conducted through the outcome lens, reveals the landscape of over-served and under-served outcomes across the existing competitive set—showing not which competitor has the most features, but which specific outcomes the existing solutions address well and which they address poorly.
This outcome-based competitive map has two strategically valuable applications. The first is differentiation: products that identify a cluster of under-served outcomes in a target customer’s job space and build their differentiation around addressing those outcomes will achieve a competitive position that is grounded in genuine customer value rather than feature parity or marketing narrative. The second is disruption detection: organizations that monitor the outcome-satisfaction landscape systematically can identify the early signatures of disruptive competitive entry—specifically, the entrance of competitors who are addressing previously under-served outcomes in ways that the incumbent’s architecture makes difficult to match.
Spotify’s product strategy illustrates outcome-driven thinking applied with unusual consistency. The functional job Spotify addresses—access to music in the right moment—contains a well-characterized set of customer outcomes, including reducing the time required to discover music the listener will enjoy, increasing the likelihood that the music selection matches the listener’s current context and mood, and minimizing the cognitive load of active playlist management. Spotify’s product investments—Discover Weekly, Daily Mix, algorithmic playlist generation, and context-aware recommendations—are coherent expressions of a strategy to lead on the specific outcomes of discovery, context-fit, and effortlessness within the music listening job space (Railsware, 2024). The product has not attempted to lead on all dimensions of the music listening job simultaneously; it has concentrated its competitive differentiation on the outcomes where it has the structural advantage—behavioral data depth and algorithmic personalization capability—that competitors without equivalent data assets cannot easily replicate.
Switching Triggers: The Strategic Anatomy of Customer Change
Perhaps the most directly actionable contribution of the JTBD framework for product strategy is the “Forces of Progress” model developed by Bob Moesta, which provides a structural account of the forces that govern the customer’s decision to switch from an existing solution to a new one. Understanding these forces is essential for product leaders for two reasons: it reveals the conditions under which customers will be most receptive to adopting a new product, and it reveals the incumbent’s structural defenses against competitive displacement.
In Moesta’s formulation, four forces shape the switching decision: (1) the push of the current situation—the degree to which the customer’s dissatisfaction with the existing solution has accumulated to the point of motivating a change; (2) the pull of the new solution—the degree to which the new product’s value proposition creates an attractive vision of the improved situation it enables; (3) the anxiety of switching—the degree to which the customer anticipates difficulty, disruption, or risk in the transition; and (4) the habit of the present—the degree to which the existing solution has become embedded in the customer’s behavioral routine, creating inertia that must be overcome even when the functional case for switching is compelling (Moesta, as cited in Business of Software, 2024).
The strategic implication is that adoption is not determined by the pull of the new solution alone—a fact that is frequently underweighted in product launch strategies that focus primarily on value proposition articulation. The push of the current situation must be sufficient to create the behavioral energy required to overcome switching anxiety and habit inertia. Products that have compelling pull but insufficient push—that are clearly superior to existing alternatives but address a problem that customers have not yet experienced as acutely enough to motivate change—will achieve lower adoption velocity than their functional quality would predict. Products that have strong push—that are entering a market where significant accumulated dissatisfaction with existing solutions creates a receptive customer base—can achieve high adoption velocity even with a value proposition that is only modestly superior to the incumbent.
For product leaders, the practical implication is that switching trigger analysis should be conducted alongside ICP development and problem selection. The question is not only “who experiences this problem most acutely?” but “who is most likely to be actively searching for a new solution right now—and what is the specific accumulated push event that has created their current motivation?” Bob Moesta’s recommended methodology—interviewing customers who have recently switched (rather than habitual users of an established product) to understand the precise sequence of push, pull, anxiety, and habit forces that governed their decision—generates the most actionable insight for this analysis (Business of Software, 2024).
In the AI era, switching trigger dynamics have taken on particular complexity. The rapid improvement of AI capabilities has created a distinctive switching dynamic in markets where AI-powered solutions are displacing incumbents: the accumulated dissatisfaction with incumbent solutions is substantial (owing to the increasingly visible gap between what AI-powered alternatives can deliver and what legacy solutions provide), creating strong push; but the anxiety of switching is also high (owing to concerns about data privacy, workflow disruption, organizational change management, and the risk of dependent on a product category that is evolving rapidly). Product leaders who understand this specific push-anxiety dynamic are better positioned to design adoption pathways—trial environments, gradual migration, outcome-guarantee pricing—that reduce switching anxiety sufficiently to allow the push energy to produce adoptions rather than deferral decisions.
JTBD as a Strategic Lens for the AI Era
The most consequential application of JTBD thinking in the current AI landscape concerns a structural question that the framework is uniquely equipped to illuminate: when AI capabilities automate or enhance the performance of the functional job, what happens to the emotional and social jobs—and are those residual dimensions sufficient to sustain customer motivation for a distinctively human-augmented product experience?
The evidence suggests that the functional job automation enabled by AI is proceeding faster than the emotional and social job implications are being worked through. Products that automate significant portions of the functional job—AI-powered content generation, AI-assisted coding, AI-driven data analysis—face the strategic question of whether the emotional and social jobs that previously required human engagement and judgment are preserved, diminished, or transformed by the automation. A knowledge worker whose functional job is to produce written communications, and for whom that functional job is also a primary mechanism for establishing professional identity and demonstrating intellectual contribution (social job), will relate to an AI writing assistant very differently than a knowledge worker for whom the writing is a means to an end rather than a professional identity signal.
Product leaders who apply JTBD thinking rigorously to their AI product concepts—asking not only “what functional job does this AI capability address?” but “what happens to the emotional and social jobs when AI automates the functional core?”—will be better positioned to design AI products that enhance rather than erode the full architecture of customer motivation. The products that achieve durable adoption in the AI era are likely to be those that enhance human agency and identity in the performance of the emotional and social jobs, while reducing the friction and effort associated with the functional job—an integration of human and AI contribution that is more strategically sophisticated than either pure automation or pure augmentation.
References
Business of Software. (2024). Bob Moesta: Understanding your customer jobs-to-be-done. https://businessofsoftware.org/talks/understanding-your-customer-jtbd/
Christensen, C. M., & Raynor, M. E. (2003). The innovator’s solution: Creating and sustaining successful growth. Harvard Business School Press.
Gocious. (2026). AI in product management guide for 2026 for product leaders. https://gocious.com/blog/ai-in-product-management-guide-for-2026-for-product-leaders
GoPractice. (2024). Jobs to be done theory and frameworks explained: Christensen, Moesta & Ulwick. https://gopractice.io/product/jobs-to-be-done-the-theory-and-the-frameworks/
HowToes. (2025). Jobs-to-be-done: Complete guide to understanding customer needs for breakthrough innovation. https://howtoes.blog/2025/07/01/jobs-to-be-done-complete-guide-to-understanding-customer-needs-for-breakthrough-innovation/
Intercom. (2024). Intercom on jobs-to-be-done. Intercom Books. https://www.intercom.com/resources/books/intercom-jobs-to-be-done
Medium – Strategy Dynamics. (2024). What it takes to switch: Using jobs to be done as a framework. https://medium.com/strategy-dynamics/what-it-takes-to-switch-ded91b1caccb
ProductPlan. (2024). Jobs-to-be-done framework. https://www.productplan.com/glossary/jobs-to-be-done-framework
Railsware. (2024). Jobs to be done examples: Spotify, Duolingo, Uber cases. https://railsware.com/blog/jobs-to-be-done-examples/
Strategyn. (2024). Jobs to be done (JTBD): The original framework by Tony Ulwick. https://strategyn.com/jobs-to-be-done/
Ulwick, A. W. (2005). What customers want: Using outcome-driven innovation to create breakthrough products and services. McGraw-Hill.
UXCrush. (2026). Jobs-to-be-done framework: A UX practitioner’s guide. https://uxcrush.com/jobs-to-be-done-framework