Key Principle
Outcome-Driven Innovation (ODI) is the 10-step quantitative process that operationalizes Jobs-to-be-Done theory. JTBD provides the theory; ODI provides the structured method that converts customer understanding into measurable, actionable innovation strategy. The 10 high-level steps are: (1) Define the Customer, (2) Define the Job, (3) Uncover Needs, (4) Find Segments of Opportunity, (5) Define Value Proposition, (6) Competitive Analysis, (7) Innovation Strategy, (8) Hidden Growth Opportunities, (9) Market Strategy, (10) Product Strategy. In practice, these expand into 84 codified sub-steps across six phases, each phase's output serving as a hard prerequisite for the next.
Why This Matters
- Without a structured process, companies default to ad hoc qualitative tools and produce unpredictable innovation results. ODI converts subjective customer understanding into measurable targets that can be validated quantitatively. (p. 82)
- Front-loading alignment on customer definition, job definition, and job map in Phase I prevents the downstream misalignment that invalidates later findings. Nearly 18% of the 84 steps occur before any customer research begins. (p. 165)
- The codified steps externalize expert judgment so any trained practitioner can replicate results -- this is what converts a consulting methodology into an organizational capability. (p. 164-165)
- ODI produces both a market strategy and a product roadmap from the same dataset, ensuring market promises align with product capabilities. (pp. 172-174)
Good Examples
Three customer types determine what you learn. For a surgical tool, the core job executor (surgeon) reveals functional desired outcomes like "minimize the likelihood of removing healthy tissue." The lifecycle support team (nurses, OR managers) reveals consumption chain outcomes. The purchase decision maker (hospital administrator) reveals financial outcomes like "reduce the patient's length of stay." Interviewing only one type yields the wrong category of data entirely. (pp. 83-86)
Job scoping prevents disruption. A stove top kettle maker who defines the job as "boil water" scopes too narrowly. The real job is "prepare a hot beverage for consumption." Keurig addressed the entire job on a single platform and displaced the incumbent. The calibration question: "Can and will the company address this job from beginning to end over time?" (pp. 87-88)
Customer-framed jobs open the solution space. A herbicide company defining the job as "kill weeds" constrains solutions to chemicals. Growers frame it as "prevent weeds from impacting crop yields," opening the space to biological controls, crop engineering, and soil management. (p. 88)
Phase pairing prevents organizational misalignment. Phase V (Market Strategy) opens with product strengths -- what to exploit now. Phase VI (Product Strategy) opens with product weaknesses -- what to fix or build next. This mirror structure prevents marketing from selling what engineering has not built. (pp. 172-174)
Counterpoints
- The 84-step process demands significant organizational commitment and cross-functional coordination. Companies lacking executive sponsorship or research infrastructure may find the full process impractical, even if the theory is sound.
- The claimed 86% success rate comes from Strategyn's own engagements; independent replication data across diverse organizational contexts is not provided in the source material.
- The strict phase-gating (each phase's output is prerequisite to the next) trades speed for rigor. In fast-moving markets, teams may need to compress or parallelize phases at the cost of some analytical confidence.
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. The core functional job is the stable, long-term focal point around which all other needs are defined and around which value creation should be centered." (p. 86)
"A product that does not have to be installed, set up, stored, transported, and so on, is far more valuable than one that does." (p. 85)
"The goal in this phase of the engagement is to gain the project team's agreement on (i) the project plan and scope, (ii) who the customer is, (iii) the definition of the job-to-be-done, and (iv) the preliminary job map." (p. 165)
"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)
Rules of Thumb
- Always start with customer definition. Different customer types (executor, lifecycle support, buyer) hold structurally different insight categories. Choosing the wrong type does not give worse data -- it gives the wrong kind of data.
- Frame jobs from the customer's perspective, not the company's. Company-centric framing invisibly constrains the solution space.
- Separate the job statement from desired outcomes. Compound statements ("accurately, safely, and quickly cut wood") prevent quantitative analysis. The job is the task; speed, accuracy, and safety are separate measurable outcomes.
- Never skip Phase I alignment. Teams that jump to customer research without agreeing on scope, customer, job definition, and job map produce findings that cannot be acted on.
- Capture variance drivers qualitatively before designing segmentation. Understanding why some customers struggle more than others is the qualitative precursor to valid quantitative segments.
- Use both lenses in product strategy. Underserved outcomes are value creation opportunities; overserved outcomes are cost reduction opportunities. Pursuing only one leads to over-engineering or commoditization.
- Build the customer acquisition tool. Without a mechanism to classify real prospects into outcome-based segments, segmentation remains a research artifact that sales teams cannot use.
Related References
- Desired Outcome Statements -- The syntax and structure of the outcome statements that ODI Steps 2-3 produce.
- The Opportunity Algorithm & Opportunity Landscape -- The quantitative scoring method used in ODI Steps 4-6 to prioritize underserved outcomes.
- Implementation Playbook -- Tactical guidance for executing ODI phases within an organization.