Outcome-Driven Innovation in the DACH Region

Why an American Framework Fits DACH Engineering Culture Better Than Expected

Outcome-Driven Innovation (ODI) was developed in the United States. Tony Ulwick refined the methodology over three decades and hundreds of projects with companies including Johnson & Johnson, Microsoft, and Bosch. The headline number: 86 percent of ODI-guided product launches succeed — five times the industry average.

Those figures are impressive. But for a German engineer, an Austrian product manager, or a Swiss managing director, an American success story is not enough. The real question is: does this work here? In our culture, with our customers, in our markets?

The short answer: yes. Particularly well, in fact.

This article explains why ODI and DACH engineering culture are a natural fit, where the cultural adaptations lie, and what the ODI process looks like when applied to industrial, MedTech, and mechanical engineering companies in Germany, Austria, and Switzerland.

What ODI Is — and What It Is Not

ODI is not a creativity framework. It is not a brainstorming tool. It is not a workshop format. ODI is a complete innovation process that runs from market definition to growth strategy.

A brief clarification on terminology: Jobs to Be Done (JTBD) is the theoretical lens — the insight that customers want to accomplish goals, not acquire products. ODI is the operational methodology built on that lens. You can apply JTBD as a thinking model without ODI. But ODI requires JTBD.

The six steps of the ODI process:

Step 1: Define the Market Around the Job

A market is not “hospital equipment” or “agricultural machinery.” A market is a group of people who share the same job-to-be-done. “Surgeons performing minimally invasive procedures” is a market. “Farmers preparing soil for planting” is a market.

This redefinition changes competitive analysis fundamentally. If your market is “excavators,” you compete with Caterpillar and Komatsu. If your market is “move earth to prepare a foundation,” you also compete with specialist foundation contractors, alternative foundation systems, and digital planning tools that minimize excavation requirements. The competitive set expands — and so does the strategic canvas.

Step 2: Discover Customer Needs as Desired Outcomes

Through qualitative interviews with 10 to 15 job performers, a Job Map is built — a functional decomposition of the job into sequential steps. For each step, desired outcomes are formulated: solution-independent, measurable statements of what the customer wants to achieve.

A typical ODI project produces 100 to 150 outcomes. That volume is not excess — it is necessary. The specificity of the outcome set is precisely why ODI surfaces needs that customer surveys and focus groups never capture. Outcomes like “Minimize the likelihood of missing a relevant subsurface obstacle before excavation begins” never appear in standard VOC programs. But when 240 customers rate that outcome as critically important and poorly served by current solutions, it becomes a quantified strategic opportunity.

Step 3: Quantify Over- and Underserved Needs

In a quantitative survey, 180 to 600 customers rate each outcome on two dimensions:

• Importance: How important is this outcome to you? (1–5 scale)
• Satisfaction: How satisfied are you with current solutions? (1–5 scale)

The opportunity score: Importance + (Importance − Satisfaction).

Scores above 10 on a 20-point scale signal a growth opportunity. Scores above 15 are rare but highly attractive targets — they represent outcomes that customers care deeply about and that no current solution addresses adequately. Scores below 6 signal overservice — the need is already well-met, and further investment there delivers diminishing returns.

Step 4: Discover Hidden Growth Segments

Cluster analysis of the survey data identifies customer segments — not defined by industry, region, or company size, but by patterns of unmet needs. These segments are strategically significant because they describe groups of customers who are willing to pay for better solutions and are not adequately served by existing offerings.

Step 5: Formulate a Growth Strategy

Based on the data, one of five strategies is selected:

• Differentiated: Serve underserved outcomes better than competitors in the main segment.
• Dominant: Serve all outcomes better than anyone — possible in some markets, but rare.
• Disruptive: Strip back overserved outcomes and offer a simpler, lower-cost entry point.
• Discrete: Target a niche segment with highly specific unmet needs.
• Sustaining: Defend an existing position with incremental improvement.

The data makes this choice explicit rather than political. When the opportunity scores are visible, the strategic option that maximizes addressable value becomes apparent.

Step 6: Generate Ideas and Develop Concepts

Only at this stage are ideas generated — with precise targets. Each concept is evaluated against how many underserved outcomes it addresses and how significantly it improves the aggregate opportunity score. This replaces subjective innovation scoring with a data-based evaluation criterion, removing the internal politics that typically dominate concept selection.

Why ODI Works Particularly Well in the DACH Region

The Engineering Mindset as Structural Advantage

DACH engineers think in specifications, tolerances, and measurable quantities. ODI delivers exactly that — from the customer’s perspective. Desired outcomes are, in effect, customer specifications: measurable, prioritizable requirements.

An outcome like “Minimize the likelihood that the cut surface becomes uneven when processing materials of varying thickness” is immediately comprehensible to an engineer. It can be translated directly into a technical requirement. It comes not from a product management meeting but from 240 customers who rated it as a top priority. That is a different kind of input — one that engineering teams find far easier to trust and act on than qualitative customer stories.

In workshops with DACH engineers, I see the same moment again and again. When they see the quantified opportunity scores for the first time, their eyes light up. Finally, they have clear, data-backed requirements — instead of vague product management briefings that blend customer wishes with internal assumptions. ODI speaks the language engineers already understand.

Long Product Cycles Demand Precision

Mechanical engineering companies like Palfinger, Liebherr, and Pöttinger develop products with lifecycles of 5 to 15 years. A wrong strategic decision — the wrong features, the wrong market segment — propagates for a decade. In these markets, quantified customer data is not optional. It is a risk management mechanism for investments that cannot be easily reversed.

An ODI project typically costs a fraction of the development investment for a new product. If it prevents a company from committing ten million euros to a product direction that addresses already-served needs, it has paid for itself many times over before a single part is manufactured.

Quality Standards and Appetite for Evidence

“German Engineering” is a quality signal because it means something was designed to rigorous specifications. That same rigor extends to decision-making. DACH executives are skeptical of gut decisions and marketing narratives. They want evidence. ODI produces evidence — not opinions, not impressions, but statistically defensible opportunity scores derived from representative customer samples.

This cultural preference for systematic evidence over subjective judgment makes DACH organizations more receptive to ODI’s quantitative output than many other markets.

Long-Term Relationships and Their Blind Spots

The DACH Mittelstand maintains customer relationships that span decades. Key account managers know their customers personally. This relationship capital is genuine — but it creates a specific kind of blind spot. Organizations believe they know their customers because they have been visiting them for fifteen years.

ODI uses these relationships as a starting point but goes systematically deeper. Qualitative interviews work particularly well when real trust exists between the manufacturer and the user. And the quantitative results regularly surprise even the most experienced account teams: needs they ranked as critical turn out to be already well-served; outcomes they had never discussed with customers carry the highest opportunity scores. For a full account of how these ODI case studies played out in practice, the dedicated article provides concrete before-and-after comparisons.

Cultural Adaptations for the DACH Market

Language and Terminology

ODI-specific terms — “Desired Outcome,” “Opportunity Score,” “Job Map” — have no established German equivalents. In practice, we use the English terms paired with German explanations. DACH professionals operating in international business contexts are accustomed to English technical vocabulary. What matters is that the concept is clear, not that the label is in German.

For the formulation of outcomes, we work in the language the customer uses to describe their job. If a machine operator says “Umrüstzeit” (changeover time), the outcome is formulated in German. The syntax rules apply regardless of language.

GDPR and Data Protection

The quantitative survey phase must be conducted in compliance with GDPR. This requires attention to consent, data storage, and anonymization — but it is not an obstacle. DACH companies are experienced with data protection requirements, and standard survey platforms used for ODI projects can be configured for full compliance.

Decision Culture and Consensus

Many DACH companies make decisions through consensus-oriented processes — more so than US firms. This can slow an ODI project at the strategy formulation stage. But it can also strengthen outcomes. When quantitative data is on the table, it changes the nature of the consensus discussion. “We have different views” becomes “The data shows that outcome #47 has a score of 14.3.” That makes consensus easier to reach, because the discussion shifts from subjective preference to shared evidence.

Industry Applications in the DACH Region

Agricultural Machinery

An Austrian agricultural equipment manufacturer wanted to develop its next generation of tillage products. The conventional approach would have been competitive benchmarking, technical capability assessment, and sales feedback collection.

The ODI approach: analyze the job “prepare soil for optimal seeding conditions.” The Job Map encompassed 11 steps, from field assessment through soil preparation to quality confirmation of the prepared seedbed. 127 desired outcomes were identified.

A quantitative study with 240 farmers produced a counterintuitive result. The most underserved outcomes did not relate to processing speed — already well-served — or working depth — also adequate. They clustered around automatic adaptation to variable soil conditions within a single field, and around documentation of processing parameters for regulatory compliance.

The company developed a sensor-based system that automatically adjusts machine settings to changing soil conditions and logs the data for compliance reporting. This product would never have been a development priority based on competitive analysis or sales feedback alone. It addressed the most critical unmet needs in the market — needs that had never been explicitly voiced in customer conversations.

Crane and Lifting Equipment

A crane and lifting systems manufacturer — operating in the same space as Palfinger and Liebherr — investigated the job “safely position loads at a construction site.” The study identified a customer segment massively underserved not on lifting capacity — already well-served — but on planning and coordination of lifting operations.

Instead of developing the next crane with greater tonnage, the company invested in a digital planning platform that simulates lifting operations, calculates safety clearances, and automates compliance documentation. The data redirected R&D investment from a well-served area to a genuinely underserved one.

MedTech

A Swiss medical technology company investigated the job “heal a chronic wound.” The study showed that the most underserved area was not the wound dressing itself — technically already highly developed — but the assessment of healing progress and the communication between treating professionals. The most valuable innovation opportunity was in information management, not material science.

ODI and the Stage-Gate Process

Most DACH companies use a Stage-Gate process for product development. ODI does not replace this process — it provides the inputs for the early gates. For detail on how innovation management in large enterprises can be structured around this integration, the dedicated article addresses the organizational dynamics that determine whether early-gate data actually shapes development decisions.

Gate 0 (Idea generation): ODI provides target coordinates: which outcomes are underserved? Which segments are addressable?

Gate 1 (Concept evaluation): Concepts are scored on how many underserved outcomes they address. This replaces subjective evaluation matrices with data-based scoring.

Gate 2 (Business case): The segment data from ODI provides the foundation for market size estimation and willingness-to-pay analysis.

Gate 3+ (Development and launch): The ODI data remains relevant as a benchmark: is the product in development still addressing the identified outcomes, or has the focus drifted?

ODI does not replace your development process. It makes it better. When you enter Gate 1 knowing which 15 outcomes carry the highest opportunity scores, every subsequent gate review can be anchored to those outcomes. That reduces scope creep and politically motivated feature additions more effectively than any governance process alone.

Addressing the Common Objections

“It Takes Too Long. We Need Results Quickly.”

A full ODI project takes three to six months. That is long compared to a brainstorming workshop. It is short compared to an 18-month product development cycle that ends in a market failure. The question is not “how fast can we pick a direction?” but “how certain can we be that the direction is correct?”

“We Cannot Engage Our Customers That Intensively.”

The qualitative phase requires 10 to 15 interviews of 60 to 90 minutes each. The quantitative phase requires a 20- to 30-minute online survey. In practice, customers are willing to invest this time — because the questions concern their actual work, not the standard satisfaction checkboxes they routinely ignore. Several customers have reported that the qualitative interviews gave them new clarity about their own jobs.

“We Already Know Our Customers Well Enough.”

This is the most common and most dangerous objection. In every ODI project we have conducted — without exception — the results contained surprises. Needs that teams assumed were critical turned out to be already well-served. Outcomes that no one had on their radar carried the highest opportunity scores. Relationship-based customer knowledge is valuable. Systematic customer knowledge is strategically superior.

Frequently Asked Questions