Library
Jobs to be Done: Theory to Practice · 6 of 12
Jobs to be Done: Theory to Practice
Entrepreneurship HIGH

Implementation Playbook

Jobs to be Done: Theory to Practice Tony Ulwick
odi implementation process practitioner organizational-change

Implementation Playbook

Key Principle

ODI converts JTBD theory into a codified, repeatable process — 84 steps across 6 phases — so that innovation success depends on disciplined execution rather than individual intuition. Each phase produces outputs that are hard prerequisites for the next; skipping or misaligning any phase corrupts everything downstream.

Why This Matters

Most innovation failures trace not to bad ideas but to misalignment: teams who never agreed on who the customer is, what job they are trying to get done, or what counts as a "need." The implementation playbook front-loads consensus (Phase I dedicates 15 of 84 steps to alignment alone) and chains qualitative rigor into quantitative validation, then into dual market-and-product strategy. Without this structure, JTBD remains a theory exercise that never reaches execution.

Good Examples (Practical Steps)

1. Start with alignment, not research. Run a 2-day Phase I workshop to resolve six foundational disagreements: who the customer is, what the market is, the job definition, the job map, what a "need" means, and the shared needs list (pp. 178-180). Until these are settled, research produces conflicting interpretations.

2. Define three customer types before gathering any data. Interview the core job executor (functional outcomes), the product lifecycle support team (consumption chain outcomes), and the purchase decision maker (financial outcomes). Each type holds a structurally different category of insight (pp. 83-85).

3. Scope the job correctly. Ask "What are you ultimately trying to get done?" — never "What job did you hire this product to do?" The product-centric question systematically narrows the job to current capabilities (p. 87). Calibrate breadth: "Can and will the company address this job from beginning to end over time?" (p. 88).

4. Use the Universal Job Map as a completeness check. Map the job across 8 steps (Define, Locate, Prepare, Confirm, Execute, Monitor, Modify, Conclude) before capturing outcomes. Teams systematically overlook Confirm, Monitor, and Conclude phases (pp. 92-93).

5. Write 50-150 desired outcome statements per job. Use the rigid four-part formula: direction of improvement + performance metric + object of control + contextual clarifier. Inconsistent phrasing distorts survey data and corrupts opportunity scores (p. 94).

6. Chain phases without shortcuts. Phase II (qualitative needs) feeds Phase III (quantitative survey), which feeds Phase IV (segmentation and opportunity discovery), which feeds Phases V-VI (market strategy and product strategy). The survey instrument includes willingness-to-pay questions alongside outcome questions, gathering pricing data simultaneously (p. 169).

7. Build the Customer Acquisition Tool (Step 71). Convert Phase IV complexity factors into a diagnostic that sales teams use to classify real prospects into outcome-based segments. Without this bridge, segmentation stays a research artifact (p. 172).

Counterpoints (Execution Pitfalls)

  • Skipping Phase I alignment is the most common failure mode. Teams eager to "get to the data" produce research that each function interprets differently, wasting the entire investment.
  • Scoping the job too narrowly by anchoring to the current product. The Keurig case: stove-top kettle makers defined the job as "boil water" when the real job was "prepare a hot beverage for consumption" (p. 87).
  • Using company-centric framing. A herbicide company defining the job as "kill weeds" constrains solutions to chemicals; growers frame it as "prevent weeds from impacting crop yields," opening biological, genetic, and agronomic solution spaces (p. 88).
  • Bundling outcomes into compound statements. "Accurately, safely and quickly cut a piece of wood in a straight line" cannot be quantified — each modifier must be a separate measurable outcome (p. 89).
  • Treating ODI as a one-time project rather than building internal capability. Without a dedicated practitioner per business unit, JTBD reverts to buzzword status (p. 176).
  • Producing only a marketing plan OR a product roadmap. ODI produces both from the same dataset; the strength/weakness mirror between Phases V and VI prevents marketing from selling what engineering hasn't built (pp. 172-174).

Key Quotes

  • "While Jobs-to-be-Done is the theory, Outcome-Driven Innovation is the process that puts it into practice." (p. 81)
  • "Making the core functional job the unit of analysis is the cornerstone of successful innovation." (p. 86)
  • "A job map does not show what the customer is doing (a solution view); rather, it describes what the customer is trying to get done (a needs view)." (p. 91)
  • "Desired outcomes don't change over time — only the solutions that address them do." (p. 95)
  • "The goal in this phase of the engagement is to create the qualitative market research deliverable. It should contain a complete set of needs built around the Jobs-to-be-Done Needs Framework." (p. 167)
  • "Most of them didn't want to be dependent on a third-party consulting firm over the long term for their ongoing success. Instead, they wanted to... make Jobs Theory and ODI part of their DNA and organizational fabric." (p. 162)
  • "Because the job map and customer outcomes are stable over time, these qualitative insights are an indispensable, long-term guide to success at innovation." (p. 180)
  • "We find that Six Sigma certified practitioners with qualitative and quantitative market research experience are often the best at understanding and applying ODI within the organization." (p. 177)

Rules of Thumb

  1. Alignment before research. Never run customer interviews until the team agrees on customer type, job definition, and job map.
  2. Customer framing, not company framing. State the job the way the customer describes it, not the way your product category implies it.
  3. Separate, never bundle. Each desired outcome must be an independent, measurable statement — compound statements destroy quantitative validity.
  4. 50-150 outcomes is the target. Fewer means you missed job steps; more means you are capturing solution-level detail.
  5. Qualitative feeds quantitative feeds strategy. Never skip a phase; each output is a prerequisite for the next.
  6. Build internal practitioners, not consulting dependency. The best candidates combine Six Sigma discipline with market research experience.
  7. Both lenses, always. Underserved outcomes reveal value creation; overserved outcomes reveal cost reduction. Pursue both or risk over-engineering or commoditization.

Related References