Outcome-Driven Innovation: The Definitive Guide

Why Most Innovation Still Fails — and One Method Doesn’t

Here is a number that should bother every executive reading this: the failure rate for new products has hovered between 72% and 90% for the past four decades. Billions in R&D spending, thousands of design sprints, mountains of Post-it notes — and the success rate has barely moved.

Now here is a different number: 86%. That is the success rate of products developed using Outcome-Driven Innovation (ODI), based on the published ODI track record across more than 1,000 innovation initiatives since 1991.

The gap between those two numbers is not a marketing claim. It is a structural difference in how innovation problems get framed, measured, and solved. And it is the reason we built our entire practice around this method.

This guide covers everything you need to understand ODI: what it is, why it works, how each of the six steps functions in practice, and what distinguishes it from the half-dozen other frameworks competing for your attention. Whether you are a product manager looking for a better way to prioritize features, or a VP of innovation trying to justify a systematic approach to your board, this is the reference document.

What Is Outcome-Driven Innovation?

Outcome-Driven Innovation is an innovation strategy and process created by Tony Ulwick in the early 1990s. It is built on a single foundational insight: customers do not buy products — they hire them to get a job done. And the metric of success for that job is not satisfaction with the product, but how well the customer achieves the outcomes they care about while executing the job.

ODI takes this insight and turns it into a quantitative, repeatable process. Instead of asking customers what they want (which produces unreliable data), ODI identifies the desired outcomes customers use to measure success when executing a job — then measures which of those outcomes are underserved or overserved in the current market.

The result is a precise map of where opportunity exists, not based on opinion or trend-watching, but on statistically validated customer data.

For a concise introduction, see What Is ODI? Outcome-Driven Innovation Explained.

The Core Principles

ODI rests on several principles that differentiate it from conventional innovation approaches:

1. The unit of analysis is the job, not the product. Markets are defined around the job the customer is trying to get done, not around the product category or technology.

2. Customer needs are measurable. Every desired outcome can be stated in a standard format and quantified through survey research. This eliminates the subjectivity that plagues most “voice of the customer” work.

3. Innovation is predictable. When you know which outcomes are underserved, you can systematically create solutions that address them. The uncertainty is in execution, not in direction.

4. Segmentation follows needs, not demographics. The most actionable segments are groups of customers who share a common set of unmet outcomes — regardless of their age, industry, or geography.

The 6-Step ODI Process

The ODI process follows six sequential steps. Each step produces specific deliverables that feed the next. Skipping steps or reordering them breaks the logic chain.

For a detailed walkthrough of each step with practical tips, see The ODI Process: 6 Steps to Systematic Innovation.

Step 1: Define the Market Around the Job to Be Done

Traditional market definition starts with the product: “We are in the power tools market” or “We compete in the infusion pumps space.” ODI starts differently. It asks: What job is the customer trying to get done?

A job is a fundamental goal the customer is trying to achieve. It is stable over time — the job of “cutting a piece of wood to a desired size and shape” has not changed in centuries, even though the tools have evolved from hand saws to laser cutters.

Defining the market around the job does three things:

• It expands your competitive frame. You are not just competing against products in your category, but against every solution the customer uses to get the job done — including workarounds, manual processes, and doing nothing.
• It stabilizes your strategy. Jobs do not change as fast as technologies or trends. A strategy anchored to a job remains valid for years.
• It reveals non-consumption. When you see the full scope of the job, you often find segments of customers who cannot get the job done at all — the largest opportunities in any market.

A properly defined job follows a specific syntax: [verb] + [object] + [contextual clarifier]. For example: “Maintain optimal body temperature of an infant during transport” or “Secure heavy loads to a truck bed for highway transport.”

Step 2: Discover Customer Needs Through Qualitative Research

Once the job is defined, the next step is uncovering the full set of desired outcomes — the metrics customers use to judge how well the job gets done. This happens through qualitative research: in-depth interviews with job executors, structured around a Job Map.

The Job Map breaks the job into its component steps — typically 8 to 15 process stages that every executor goes through, from defining what needs to be done, to confirming the job was completed successfully. The standard stages are:

1. Define
2. Locate
3. Prepare
4. Confirm
5. Execute
6. Monitor
7. Modify
8. Conclude

For each stage, researchers ask: “What are you trying to achieve? What makes this step difficult? How do you know you did it well?” The answers, when properly translated into outcome statements, yield 100 to 150 desired outcomes for a typical job.

This is where most companies underinvest. They interview 5 customers and call it research. ODI typically requires 15 to 30 qualitative interviews to reach saturation — the point where new interviews stop producing new outcomes.

For deep guidance on writing outcome statements, see How to Write Outcome Statements That Drive Product Decisions and Customer Desired Outcomes: The Building Blocks of ODI.

Step 3: Quantify Over- and Underserved Needs

This is where ODI diverges most sharply from qualitative-only methods. Once you have your 50–150 outcome statements, you survey a statistically significant sample of job executors (typically 180-600 respondents) and ask two questions for each outcome:

1. How important is this outcome? (1-5 scale)
2. How well is this outcome currently satisfied? (1-5 scale)

The responses feed into the Opportunity Algorithm, which calculates an opportunity score for each outcome:

Opportunity Score = Importance + max(Importance - Satisfaction, 0)

An outcome with high importance and low satisfaction scores high — it represents an underserved need. An outcome with high importance and high satisfaction is appropriately served. An outcome with low importance and high satisfaction is overserved — a signal that the market may be ripe for a low-cost disruptive play.

For the full mathematical treatment, see The Opportunity Algorithm: Finding Underserved Customer Needs.

Step 4: Discover Hidden Growth Opportunities

The quantified outcomes are plotted on the Opportunity Landscape — a two-dimensional chart with importance on the y-axis and satisfaction on the x-axis. This visual immediately reveals:

• Underserved outcomes (upper left): High importance, low satisfaction. These are the opportunities for differentiated innovation.
• Appropriately served outcomes (diagonal): Importance roughly equals satisfaction. These are table stakes — you must satisfy them but they will not differentiate you.
• Overserved outcomes (lower right): Low importance, high satisfaction. These suggest cost-reduction or simplification opportunities.

The Opportunity Landscape is not just a pretty chart. It is a strategic decision tool. Clusters of underserved outcomes define opportunity spaces. Clusters of overserved outcomes point toward disruptive strategies. Mixed patterns suggest platform plays.

Outcome-based segmentation happens here as well. Not all customers share the same pattern of unmet needs. By running latent class analysis or k-means clustering on the survey data, you can identify segments of customers with systematically different opportunity profiles — and then target the segment where your capabilities give you the best chance of winning.

Step 5: Formulate a Growth Strategy

With the Opportunity Landscape and segments mapped, the strategic options become concrete:

• Differentiated strategy: Target a segment with 10+ underserved outcomes and create a solution that addresses them. This is the classic ODI play — it is how Bosch redesigned its circular saw line, how a medical device company we worked with redefined wound closure, and how several of our DACH clients have found high-growth niches in mature markets.

• Dominant strategy: Address underserved outcomes across multiple segments. This is harder and more expensive, but creates market leaders.

• Disruptive strategy: Target the overserved segment with a simpler, cheaper solution that strips out the features they do not value. This is the Christensen-style disruption, but with quantitative backing.

• Discrete strategy: Focus on a narrow cluster of related underserved outcomes and solve them perfectly. This creates premium niches.

• Sustaining strategy: Incrementally improve appropriately served outcomes. Lower risk, lower reward.

The strategy choice is not arbitrary — it follows directly from the data. This is why ODI produces higher success rates: by the time you decide what to build, you already know which unmet needs are large enough to justify the investment.

Step 6: Generate Ideas and Create Concepts

Only now — after five steps of rigorous analysis — does ODI turn to ideation. And even here, the process is structured differently from a typical brainstorm.

Instead of open-ended ideation (“How might we improve the customer experience?”), ODI provides specific outcome targets: “Generate concepts that minimize the time it takes to verify that the load is secured to specification” or “Generate concepts that minimize the likelihood that the adhesive fails under vibration.”

These are specific, measurable design targets. Engineers and designers know exactly what success looks like. Concepts can be evaluated against the outcome targets before a single prototype is built — reducing the cycle time and cost of concept development by 50-70%.

Outcome Statements: The Currency of ODI

The entire ODI process depends on the quality of outcome statements. A well-written outcome statement is specific, measurable, and free of solution references. It follows a strict format:

Direction of improvement + Performance metric + Object of control

Examples:

• Minimize the time it takes to identify the correct drill bit for the material
• Minimize the likelihood that the suture creates tissue damage during insertion
• Minimize the amount of material wasted when cutting to specification

Notice what these statements do NOT include: any reference to a product, feature, or technology. They are pure expressions of what the customer wants to achieve. This is critical because it decouples the need from the solution — allowing you to explore solution spaces that competitors have not considered.

A typical ODI project generates 100 to 150 outcome statements. Each one is a potential innovation target. The quantitative survey determines which ones matter most and which ones are currently underserved.

For the complete guide to writing outcome statements, including 10+ examples and common mistakes to avoid, see How to Write Outcome Statements That Drive Product Decisions.

The Opportunity Algorithm in Detail

The Opportunity Algorithm is the mathematical engine of ODI. It converts subjective customer data into an objective scoring system.

The formula: Opportunity Score = Importance + max(Importance - Satisfaction, 0)

Why this specific formula? Because it captures two dynamics simultaneously:

1. Importance alone is necessary but insufficient. A highly important outcome that is also highly satisfied is not an opportunity — the market has already addressed it.

2. The gap between importance and satisfaction reveals unmet need. But only when satisfaction is below importance. When satisfaction exceeds importance, the gap is zero — you cannot score negative on opportunity.

The maximum possible score is 20 (importance = 10 on a rescaled basis, satisfaction = 0). In practice, scores above 15 are rare and indicate major market failures. Scores between 10 and 15 are attractive opportunities. Scores below 10 are typically appropriately served.

When plotted across all 50–150 outcomes, the pattern tells you whether the market is:

• Underserved overall (many high scores): room for a premium, feature-rich solution
• Overserved overall (many low scores): ripe for disruption with a simpler offering
• Mixed (scores scattered): opportunity for segment-specific strategies

For worked examples with real numbers, see The Opportunity Algorithm: Finding Underserved Customer Needs.

ODI and Jobs to Be Done: The Relationship

ODI is sometimes confused with Jobs to Be Done (JTBD) theory. The relationship is simpler than the internet makes it:

JTBD is the theory. ODI is the practice.

Jobs to Be Done, as articulated by Clayton Christensen and refined by Tony Ulwick, provides the theoretical foundation: customers hire products to get jobs done, and understanding those jobs is the key to innovation. But JTBD theory alone does not tell you how to identify jobs, how to measure needs, or how to determine which needs to target.

ODI takes JTBD theory and operationalizes it into a repeatable, quantitative process. It defines specific methods for:

• Identifying and scoping jobs
• Mapping the job into process steps
• Capturing desired outcomes in a standardized format
• Measuring opportunity through survey research
• Segmenting markets based on unmet needs
• Formulating strategy based on opportunity patterns

You can practice JTBD without ODI — many consultants do, relying on qualitative interviews and intuition. But you cannot practice ODI without JTBD, because the job is the fundamental unit of analysis.

For more on how JTBD theory informs the entire approach, see our Jobs to Be Done pillar guide.

Why ODI Achieves an 86% Success Rate

The 86% success rate is not magic. It is the predictable result of doing several things that most innovation processes skip:

1. It eliminates the biggest source of failure: working on the wrong problem. Most products fail not because of bad engineering but because they solve a problem customers do not care about, or one that is already well-solved. ODI’s quantitative measurement ensures you only invest in outcomes that are both important and underserved.

2. It uses the customer’s frame of reference, not the company’s. Internal stakeholders argue about features. Customers think in outcomes. ODI translates between these two worlds, ensuring that what gets built maps directly to what customers value.

3. It produces statistically valid data, not anecdotes. A product manager who visited three customers and “heard a clear theme” is not doing research — they are confirming their existing bias. ODI surveys 180-600 customers and applies rigorous statistical analysis to the results.

4. It separates need-finding from idea-generation. Most processes conflate these two activities. “The customer said they want a bigger handle” is not a need — it is a solution. By disciplining the process to capture outcomes (not solutions), ODI ensures you explore the full solution space before committing.

5. It provides a shared language across functions. When R&D, marketing, and product management all look at the same Opportunity Landscape, debates become productive. Instead of arguing about whose customer anecdote is more representative, teams can point to specific scores and make evidence-based decisions.

ODI vs. Other Innovation Approaches

ODI vs. Design Thinking

Design Thinking excels at building empathy and generating creative solutions. It fails at prioritization and measurement. A design sprint will produce 50 ideas — but no rigorous way to determine which ones address the highest-value opportunities. ODI provides the quantitative backbone that Design Thinking lacks.

For a detailed comparison, see ODI vs. Design Thinking: Complementary or Competing?.

ODI vs. Stage-Gate

Stage-Gate is a project management framework. It tells you how to manage the development process, but it does not tell you what to develop. ODI slots into the front end of Stage-Gate — specifically the “Discovery” and “Scoping” stages — providing the customer insight that Stage-Gate assumes someone else has generated.

ODI vs. Lean Startup

Lean Startup says “build, measure, learn” — launch a minimum viable product and iterate based on feedback. This works when the cost of iteration is low (software, consumer apps). It is expensive and dangerous in capital-intensive industries like medical devices, industrial equipment, or automotive, where a wrong iteration can cost millions. ODI front-loads the learning, reducing the number of iterations needed.

ODI vs. Voice of the Customer (VOC)

Traditional VOC captures what customers say they want, which is often a solution, not a need. “I want a faster drill” is a solution statement. “Minimize the time it takes to create a hole of the required depth” is an outcome statement. ODI captures outcomes, not solutions — and the difference determines whether your next product wins or fails.

Real-World Impact: Enterprise Examples

We have applied ODI across industries in the DACH region. While confidentiality prevents full disclosure, here are representative examples:

Medical device manufacturer: A B2B medical device company had been iterating on features for three product generations with declining market share. ODI research revealed that 14 of their 22 most-invested features addressed outcomes that were already overserved. Meanwhile, 11 outcomes related to post-procedural workflow were severely underserved. The redesigned product — which stripped features from the overserved category and invested in workflow integration — captured 8 points of market share in 18 months.

Industrial equipment company: A manufacturer of construction equipment used ODI to redefine their approach to operator safety. Traditional competitor analysis had them adding more sensors and warnings. ODI research revealed that operators’ core unmet needs were about situational awareness — being able to anticipate problems before they required a warning. This shifted the product roadmap from reactive safety systems to predictive visibility tools, resulting in a premium-priced product line that achieved 140% of its revenue target.

Agricultural machinery manufacturer: An established player was losing ground to lower-cost competitors. ODI revealed the market was bifurcated: one segment was overserved (willing to pay less for fewer features), while another was severely underserved on precision outcomes. Instead of one product for all, they launched a stripped-down model for the overserved segment and a premium precision line for the underserved segment — growing total revenue 23% without cannibalizing margins.

For more detailed case studies, see ODI Case Studies: How Enterprise Companies Innovate Systematically.

Implementing ODI in Your Organization

If you are considering ODI for your organization, here is what a realistic implementation looks like:

Timeline

A full ODI engagement typically runs 12 to 16 weeks:

• Weeks 1-2: Job definition and research design
• Weeks 3-6: Qualitative interviews and outcome statement development
• Weeks 7-9: Quantitative survey fielding and analysis
• Weeks 10-12: Opportunity Landscape development and segmentation
• Weeks 13-16: Strategy formulation and concept development

Investment

ODI is not cheap. A full project requires significant investment in research — qualitative interviews, survey design, statistical analysis. But compare that cost to the cost of launching a product that fails: millions in development, tooling, launch, and the opportunity cost of a 2-3 year development cycle spent on the wrong thing.

Skills Required

Running ODI internally requires skills in:

• Qualitative interviewing (specifically, the discipline to capture outcomes, not solutions)
• Survey design and statistical analysis
• Strategic thinking (connecting opportunity scores to business strategy)
• Facilitation (presenting data to cross-functional teams and driving decisions)

Most organizations partner with an experienced ODI firm for their first two to three projects, then gradually build internal capability. This is the model we use with our DACH clients.

For a practical guide tailored to product managers, see ODI for Product Managers: A Practical Implementation Guide.

Common Objections and Honest Answers

Getting Started with ODI

If you are ready to move beyond innovation theater and start building products that win, here is where to begin:

1. Educate your team. Read through our cluster articles: start with What Is ODI?, then The ODI Process, then Outcome Statements.

2. Pick your first job. Choose a market where you have deep domain expertise but declining differentiation. This gives you the best learning environment with the highest potential payoff.

3. Talk to us. As experienced ODI practitioners, we can guide your first ODI project, train your team, and build the internal capability for subsequent projects.

Further Reading

• What Is ODI? Outcome-Driven Innovation Explained
• The ODI Process: 6 Steps to Systematic Innovation
• How to Write Outcome Statements That Drive Product Decisions
• The Opportunity Algorithm: Finding Underserved Customer Needs
• ODI vs. Design Thinking: Complementary or Competing?
• ODI Case Studies: How Enterprise Companies Innovate Systematically
• ODI for Product Managers: A Practical Implementation Guide
• Customer Desired Outcomes: The Building Blocks of ODI