Job executor, job map, and job outcome in Tony Ulwick's taxonomy

The Jobs-to-be-Done (JTBD) theory provides a conceptual framework for understanding consumer and corporate purchasing behavior by positing that individuals do not merely buy products; rather, they "hire" products or services to complete specific tasks, resolve problems, or make progress in their lives ¹². While the theory was popularized in academic and business literature by Harvard Business School professor Clayton Christensen, the operationalization of this theory into a structured, quantitative innovation process was pioneered by Anthony W. Ulwick ¹². Ulwick's methodology, known as Outcome-Driven Innovation (ODI), translates the abstract concepts of JTBD into a rigorous, data-driven framework designed to bring predictability to new product development ³⁴⁵.

At the core of Ulwick's ODI methodology is a highly specific taxonomy that standardizes how organizations identify, categorize, and measure customer needs ⁴. This taxonomy relies on three foundational constructs: the job executor, the job map, and the job outcome. By rigidly defining the market around the job executor and the core functional job, deconstructing the task via a job map, and measuring success through customer-defined job outcomes, the ODI framework structures innovation research as an empirical science rather than a speculative art .

Foundational Principles of Outcome-Driven Innovation

To understand the taxonomy, it is necessary to contextualize Outcome-Driven Innovation against traditional product development methodologies. Historically, organizations have relied on an "ideas-first" approach, where product teams brainstorm concepts and subsequently test them against target demographics to gauge viability ⁸⁶. According to Strategyn, Ulwick's consulting firm, this approach yields an industry-average success rate of approximately 17%, primarily because the evaluation and filtering processes occur too late to prevent the misallocation of research and development resources ¹⁰⁷⁸.

Ulwick developed ODI in 1990 by applying Six Sigma principles to product innovation, suggesting that innovation could be managed with the same predictability as manufacturing processes if the correct inputs were isolated ²⁹. His approach builds upon the premise established by Theodore Levitt, who famously noted that consumers do not want a quarter-inch drill, but rather a quarter-inch hole ¹². ODI systematically shifts the unit of analysis away from the product and the customer's demographic profile, placing it entirely on the underlying process or "job" ².

This perspective introduces a critical distinction between Ulwick's interpretation of JTBD and that of Clayton Christensen. Christensen's "Jobs-As-Progress" model suggests that consumers hire products to make positive emotional or social progress in their lives . Conversely, Ulwick's "Jobs-As-Activities" model assumes users are focused primarily on efficiently executing tasks and activities . Under Ulwick's paradigm, a market is fundamentally defined as a group of people and the core functional job they are attempting to execute ²¹⁵¹⁰.

The Job Executor

A fundamental premise of Outcome-Driven Innovation is that traditional market definitions, which typically rely on product categories, geographic boundaries, or demographic and psychographic customer profiles, are inadequate for predicting innovation success ¹⁵¹⁰¹⁷. Instead, ODI defines the market anchor as the specific individual or group performing the task, defined in the taxonomy as the "job executor" ².

Distinction from Traditional Buyer Personas

In traditional marketing and agile product development, organizations frequently rely on buyer personas - composite profiles based on demographic data (e.g., "males aged 18-35") or behavioral psychographics (e.g., "tech-savvy early adopters") ¹⁷¹¹. The ODI framework argues that these characteristics are correlative rather than causative of buying behavior ¹⁷. Furthermore, focusing on personas often conflates disparate types of customer interactions with the product ⁸²⁰.

The ODI taxonomy explicitly separates the customer into three distinct roles, recognizing that in complex environments (particularly business-to-business or enterprise software markets), the person using the product, the person maintaining it, and the person purchasing it are rarely the same individual ²²⁰.

In consumer-facing (B2C) markets, a single individual often embodies all three roles simultaneously. For instance, a consumer purchasing a toothbrush acts as the buyer, the lifecycle support team (maintaining and disposing of the brush), and the job executor (cleaning teeth) . However, by formally separating these roles, innovation research can systematically capture the distinct needs of each stakeholder without conflating a buyer's financial constraints with an executor's functional requirements ⁸²⁰.

Targeting the wrong role can lead to strategic vulnerability. For example, if a medical device company focuses exclusively on the phlebotomist (the job executor) to improve blood-drawing procedures, they risk disruption from a competitor who develops a solution directly for the patient (the job beneficiary), thereby eliminating the need for the trained executor altogether ²⁰.

Structuring Market Definition

Identifying the job executor provides the anchor for all subsequent innovation research. In the ODI methodology, the intersection of the job executor and the core functional job forms the definitive boundary of the "market" ²¹⁰. For example, rather than defining a market around a product class like "circular saws," ODI defines it around the user and the task: "tradesmen (job executor) cutting wood in a straight line (core functional job)" ¹⁰.

This solution-agnostic definition ensures that research efforts remain focused on the underlying objective, which is stable over time, rather than on transient product features or technologies ²¹⁰. While the technology to listen to music has evolved from vinyl records to cassettes, compact discs, MP3 files, and streaming services, the job executor's core functional job - "listening to music on the go" - has remained entirely constant ².

The Universal Job Map

Once the job executor and the core functional job are established, the ODI taxonomy dictates that the job must be deconstructed into discrete, manageable steps. This is achieved through the "job map," a visual and conceptual framework introduced by Tony Ulwick and Lance Bettencourt in the Harvard Business Review ¹³²³.

A critical distinction in the ODI framework is that a job map is not a customer journey map or a process flow diagram ². Customer journey maps typically document the user's experiential interaction with a specific company, product, or service (e.g., navigating a website, unboxing a device, contacting customer support) ²¹⁰. In contrast, a job map is entirely solution-agnostic. It describes what the customer is attempting to achieve at each stage of a task, regardless of the tools, products, or manual workarounds they currently employ ¹².

The Eight Chronological Job Steps

Through the analysis of hundreds of core functional jobs across diverse industries, Ulwick identified that virtually all jobs share a universal structure comprising eight fundamental process steps ¹³. The average job consists of between 10 and 20 specific sub-steps that fit within these eight macro categories ². This structure provides researchers with a systematic template for qualitative data collection, ensuring that no phase of the customer's objective is overlooked.

Identifying Innovation Opportunities Across the Map

In practice, organizations utilize the job map during the qualitative phase of innovation research. Through ethnographic observation and customer interviews, researchers document how job executors attempt to achieve each step ²⁶²⁷. By establishing this context, companies can identify where customers utilize inefficient workarounds, experience friction, or employ disjointed tools to move from one step to the next.

According to Ulwick, a highly effective and stable innovation strategy is to design a comprehensive platform or offering that gets the entire job - spanning all eight steps from definition to conclusion - done within a single solution . This eliminates the need for the customer to piece together disparate products, thereby creating a dominant market position.

The Job Outcome

While the job map outlines what the customer is trying to do, the "job outcome" defines how the customer measures success when executing those steps . In the ODI taxonomy, a customer "need" is strictly defined as a desired outcome statement. This conceptualization addresses a persistent problem in traditional Voice of the Customer (VOC) research, where organizations often conflate abstract benefits, product features, technical specifications, and vague preferences with actual customer needs ⁴¹⁴.

Anatomy of a Desired Outcome Statement

In Ulwick's methodology, desired outcomes are highly structured, measurable, and solution-independent performance metrics ¹⁰²⁹. They act as the definitive instructions for innovation, allowing companies to evaluate concepts long before the physical product development phase begins ²⁹. For any given core functional job, there are typically between 50 and 150 desired outcomes distributed across the various steps of the job map ²²⁹.

To eliminate ambiguity, outcome statements are formulated using a rigid syntactic structure. They consistently express the desire to improve performance along specific dimensions, such as speed, predictability, efficiency, output, throughput, or waste reduction ²⁹. For example, rather than a customer asking for "a sharper scalpel" (a solution), a surgeon's desired outcome when executing a procedure might be expressed as: "Minimize the time it takes to locate blood vessels" or "Minimize the likelihood of damaging blood vessels" ¹⁵.

Because these outcomes are stripped of any reference to current technologies or specific solutions, they remain stable over time ²¹⁰. While the technology to locate blood vessels may evolve from manual palpation to ultrasound to augmented reality overlays, the underlying metric of success - minimizing time and minimizing error - remains perfectly constant ².

The Opportunity Algorithm and Need Prioritization

The capture of 50 to 150 outcome statements presents a severe data prioritization challenge for product teams. To resolve this, ODI employs quantitative research to measure the relative importance of each outcome and the degree to which current solutions satisfy it ²⁸¹⁵. Surveying a statistically valid sample of job executors (typically between 180 and 600 respondents) yields data that is processed through Ulwick's proprietary "Opportunity Algorithm" ¹⁵³¹.

The Opportunity Algorithm mathematically quantifies unmet needs to identify where the greatest potential for innovation lies ¹⁵. Respondents rate both the importance of an outcome and their current satisfaction with it on a scale (frequently 1-10 or 1-5, depending on the implementation) ¹⁵³¹. The formula explicitly gives twice as much weight to importance as to satisfaction to highlight outcomes that are highly valued but poorly served by the market:

Opportunity Score = Importance + max(Importance - Satisfaction, 0) ¹⁵³²

By plotting these scores on an opportunity landscape, organizations can categorize outcomes into distinct strategic zones. Outcomes with high importance and low satisfaction yield the highest scores; these are deemed "underserved" and represent optimal targets for breakthrough innovation or premium pricing strategies ¹⁵¹⁰³¹. Conversely, outcomes with low importance and high satisfaction are "overserved," indicating areas where companies might reduce costs or introduce disruptive, lower-tier solutions without significantly harming the core user experience ¹⁰¹⁵³¹.

Structuring Innovation Research Using the Taxonomy

The integration of the job executor, the job map, and the job outcome forms the operational backbone of Outcome-Driven Innovation. By combining qualitative exploration with rigorous quantitative validation, the taxonomy structures the innovation research lifecycle into a predictable, multi-phase sequence ². Research conducted by Strategyn claims that adhering to this structured methodology yields an 86% success rate in new product development, significantly higher than the industry average ⁴¹⁰.

Qualitative Phase and Need Capture

The research process begins by explicitly defining the market boundary: the intersection of the job executor and the core functional job ¹⁵¹⁰. Once established, researchers conduct qualitative interviews and observational studies to construct the universal job map ¹³²⁶.

During this qualitative phase, the objective is not to solicit product ideas, brainstorm features, or test prototypes ⁶¹⁴. Instead, researchers probe the customer's intent at each step of the job map to uncover their desired outcomes. If a customer suggests a specific product feature (e.g., "I need a bluetooth connection"), the ODI researcher must trace that solution back to the underlying performance metric it addresses (e.g., "Minimize the time it takes to transfer data to a secondary device") ¹⁴. This discipline ensures that the resulting master list of 50 to 150 outcomes represents a complete, mutually exclusive, and collectively exhaustive catalog of customer needs that accurately reflects the executor's evaluation criteria ²⁸.

Quantitative Phase and Outcome-Based Segmentation

Following the qualitative capture of outcomes, the research shifts to a quantitative validation phase. The master list of outcomes is administered via survey to the representative sample of job executors ²³¹.

A critical insight of the ODI framework is that markets are rarely homogeneous; average scores across an entire market often obscure deep pockets of opportunity ⁴. Consequently, ODI structures its market research around "outcome-based segmentation" ⁴. Rather than clustering customers by demographic traits, behavioral patterns, or industry verticals, statistical analysis (such as cluster analysis) is applied to group respondents based exclusively on their shared unmet needs ⁴¹⁵.

A foundational application of this research structure occurred with the Cordis Corporation in 1992 ²⁹. By applying ODI to the angioplasty balloon market, Cordis identified a unique segment of cardiologists whose specific outcomes regarding maneuverability and predictability were vastly underserved by existing medical devices. By designing products specifically to hit those unmet metrics, Cordis increased its market share from 1% to over 20%, multiplying the company's stock value ²⁹.

Similarly, outcome-based segmentation in the power tool market revealed that approximately 30% of tradesmen struggled significantly more than others with making finish cuts, yielding 14 highly unmet outcomes . Because these individuals faced specific physical complexities (e.g., cutting crown molding angles in tight corners), their desired outcomes differed drastically from the rest of the market. Traditional demographic segmentation would have failed to isolate this group, but structuring research around job outcomes made the segment visible and actionable for product development, directly leading to the creation of a highly successful Bosch circular saw .

Integration with Agile and Software Development

While originally developed for physical goods and medical devices, the ODI taxonomy has been heavily adapted to structure research in modern software development and Agile methodologies ³³³⁴³⁵. Traditional Agile development relies heavily on "User Stories," which often articulate features rather than fundamental needs. To address this, software teams utilize "Outcome-Driven Development" (ODD), bridging the gap between high-level JTBD strategy and sprint-level execution ³³¹⁶.

Enterprise platforms, such as the digital workspace tool MURAL, integrate the job map directly into their product development life cycle. During the planning phase, MURAL maps out persona scenarios and combines them with Tony Ulwick's job map ³⁵. They then map specific desired outcomes to each step of the flow. Instead of traditional User Stories, they generate "Job Stories" that include context from the job map without requiring developers to interpret the entire strategic framework ³⁵. This provides designers and engineers with a highly specific design challenge (e.g., minimizing the time it takes to authenticate a new external collaborator) with the confidence that the feature ties directly into a validated, unmet customer need ³⁵.

This integration ensures that Agile teams do not become mere "ticket factories" highly efficient at building the wrong features, but rather outcome-focused engines that connect every technical decision to measurable customer value ³³¹⁷. Microsoft similarly utilized this framework to refine its Software Assurance program; rather than simply pushing continuous software updates, the company reoriented the program to address the core jobs IT administrators were attempting to achieve, leading to higher engagement and perceived value ³⁴.

Academic Critiques and Practitioner Limitations

While Outcome-Driven Innovation presents a highly structured approach to product strategy, the taxonomy and its associated methodologies have drawn significant critique from academic circles, behavioral economists, and market research practitioners ¹⁴¹⁸¹⁹. Analyzing these critiques provides a nuanced understanding of the framework's limitations and the boundaries of its applicability.

Methodological Rigidity and Implementation Complexity

A primary criticism leveled against the ODI taxonomy involves its implementation complexity and the rigid structure of its qualitative and quantitative phases ¹⁸⁴⁰. Generating, parsing, and validating 100 to 150 discrete outcome statements requires substantial financial resources, time, and specialized consulting expertise ¹⁴¹⁸.

From a data collection standpoint, administering surveys that ask respondents to rate the importance and satisfaction of over 100 outcomes represents a severe cognitive burden ¹⁴. Critics note that a survey requiring product-to-product comparisons across 100 outcomes could demand that a single respondent answer 300 to 400 separate questions ¹⁴. Market researchers argue this volume inevitably induces respondent fatigue, potentially leading to lower data integrity as respondents simply check boxes arbitrarily to finish the survey and collect their incentive ¹⁴.

Furthermore, practitioners point out that managing 100 raw needs is overwhelming for product development teams. Traditional Voice of the Customer (VOC) best practices recommend utilizing ethnographic research and affinity diagrams to group needs into a more manageable hierarchy of 15 to 25 core themes ¹⁴. ODI rejects this thematic grouping, insisting that all outcomes be evaluated and scored independently, which critics argue tests the limits of generally accepted good research practices ¹⁴.

The Marginalization of Emotional and Social Jobs

The ODI taxonomy heavily prioritizes the functional aspects of product consumption. While the framework formally acknowledges the existence of "emotional jobs" (how the executor wants to feel) and "social jobs" (how they want to be perceived by others), critics argue that the methodology structurally marginalizes these subjective elements by focusing so intensely on quantifiable performance metrics ⁶²⁰.

This divergence is most apparent when comparing Ulwick's framework to Clayton Christensen's later iterations of JTBD theory. Christensen's model emphasizes the broader context of consumer motivation. In his famous "Milkshake Marketing" case study with McDonald's, Christensen's team discovered that commuters hired milkshakes not just for the functional job of satisfying morning hunger, but for the emotional job of alleviating the boredom of a long drive ²¹. The "progress" the consumer sought was heavily psychological . Critics argue that ODI's intense focus on functional steps (Define, Locate, Prepare) may fail to capture these visceral, emotional drivers that dictate consumer behavior, particularly in lifestyle, entertainment, or luxury markets ⁴³.

Validity of the Opportunity Algorithm

The mathematical foundation of the Opportunity Algorithm has also faced scrutiny within the product innovation management discipline. Evaluators such as Jeffrey Pinegar and Gerry Katz have argued in the Journal of Product Innovation Management that the foundational formula - subtracting satisfaction from importance - is "technically and intellectually flawed" ¹⁴³².

The critique asserts that importance and performance (satisfaction) are entirely separate psychometric constructs, and combining them in a linear equation is analytically unsound ³². Pinegar likens the equation to "subtracting apples from broccoli," suggesting that while the resulting heuristic might be a practically useful tool for highlighting underserved needs in corporate settings, it lacks rigorous statistical or psychometric validity ³². Despite these critiques, proponents argue that the algorithm effectively focuses enterprise resources on areas where high market demand intersects with poor existing solutions, fulfilling its intended strategic purpose ³².