At a Glance

Industry	Industrial Manufacturing (Global)
Challenge	Engineering-led culture pushing technology to market without customer validation; roadmaps disconnected from strategy; U.S. and Germany teams with competing priorities
Approach	Six-month applied product management training and coaching program focused on market-first strategy and roadmapping
Key Results	3 of 4 product teams secured customer validation and budget commitments before development; 1 weak investment halted before a dollar was spent; roadmaps reconnected to strategic intent; organizational constraints surfaced and resolved at the executive level

Overview

This product management case study describes how a global industrial manufacturing company broke a deeply ingrained habit: building products based on what the technology could do rather than what customers were trying to accomplish. Through a six-month applied learning engagement with Sequent Learning Networks, product teams were required to validate customer demand before committing to development. Three teams came back with customer confirmation and budget commitments. One team recommended stopping an initiative entirely. The result was not just better roadmaps. It was better product investment decisions, grounded in market evidence instead of engineering instinct.

The Business Situation

“We are very engineering-led. The instinct is to push technology to market without doing the market work first.”

The company had built its reputation on engineering excellence. Its products served demanding industrial applications where precision and reliability were non-negotiable. The technology was sophisticated and the talent was deep. But market share had eroded by approximately 0.5% over two years, and gross margins were under pressure.

Product roadmaps looked robust on the surface: detailed timelines, organized feature lists, allocated resources. But they reflected what the technology could deliver, not what customers were willing to buy. Roadmaps had become project schedules masquerading as strategy.

The Problem: Roadmaps Without Strategy

The technology push vs. market pull tension is one of the most common failure patterns in product management. Organizations with deep engineering capability default to a simple question: what can we build next? But that question, answered in isolation, produces plans that are internally coherent and externally irrelevant.

This organization also operated across the United States and Germany, with product leaders in each geography holding different views on priorities with limited shared context. What leadership described as an execution problem was, in reality, a strategy problem: no shared understanding of where to compete, which customers to serve, or what winning would require.

Roadmaps were full. Direction was absent.

The Product Management Training Intervention: Strategy Before Roadmaps

Sequent Learning Networks was engaged to help the organization rebuild its product strategy and roadmapping discipline. The six-month program enforced a fundamental sequencing change: no roadmap could be created until the strategy work was complete.

Before defining products or features, each team was required to complete a structured market analysis:

• Customer segments and specific application requirements
• Industry and market dynamics affecting the category
• Competitive positioning, alternatives, and switching costs
• Current business performance, margin realities, and portfolio fit
• Strategic rationale for investment priority

The guiding question changed from “What can our technology do?” to “What are customers trying to accomplish, and where does that align with our strategic priorities?” For this organization, that meant understanding how similar technologies delivered different value across distinct industrial applications, and which of those applications were worth pursuing.

The Turning Point: Customers Heard, Customers Confirmed

Three of the four teams developed product strategies strong enough to take to key customers. This was a significant moment, because no one had ever thought to involve customers in the process before. Engineers and salespeople had long assumed customers knew exactly what they wanted. What the teams discovered was that customers often knew what they wanted, but not necessarily what they needed.

Sequent’s facilitator accompanied two of the teams on customer visits, with approval from both the client and the customers’ account managers. The conversations were direct, structured, and illuminating. Customers confirmed the relevance of the proposed solutions and indicated they would allocate budget for the new offerings once available. One customer told Sequent that the visit had deepened the relationship and increased their sense of commitment to the vendor as a partner. Being invited into the conversation changed the dynamic.

The fourth team reached a different conclusion. Their market analysis revealed that the assumed opportunity was smaller and more constrained than leadership had believed. Rather than pushing forward, the team presented its findings and recommended reallocating resources to higher-priority initiatives. This was not viewed as failure. It was viewed as disciplined product management.

What Else Surfaced

Strong product strategy work does not just find market opportunities. It exposes organizational constraints that strategy-free roadmapping keeps hidden. In this engagement, the work surfaced:

• Resource contention across product lines that had never been named or resolved
• Unclear decision ownership between U.S. and German product leaders
• Political dynamics that had been managed around rather than addressed
• Execution dependencies outside the control of the product teams

Leadership was forced to confront tradeoffs it had been working around for years. One senior leader ultimately exited the organization. The CEO stepped in to clarify priorities and direct key initiatives. The product management training did not instantly accelerate growth. It clarified what growth would actually require, which is a more valuable and more honest outcome.

Outcomes

• Three product strategies validated by customers before development investment was committed
• Budget commitments secured from customers prior to major resource allocation
• One weak investment halted entirely after market analysis revealed insufficient opportunity
• Roadmaps converted from feature delivery plans into strategic investment narratives grounded in market evidence
• Organizational and resource constraints surfaced and resolved at the executive level

Teams regained time and focus by stopping work that did not deserve to continue. That is one of the least celebrated but most valuable outcomes of rigorous product strategy work.

What This Story Reveals About Product Strategy and Roadmapping

Roadmaps are not strategies. They are outputs of strategy. In engineering-led organizations, it is natural to start with capability: what can we build next? But without market validation, that approach produces plans that are internally coherent and externally irrelevant.

The discipline of product strategy means doing the market work first. Understanding customers. Validating demand. Assessing competitive alternatives before committing development resources. The strongest product roadmap is the one connected to strategic intent, informed by real customer conversations, and pruned by honest analysis of where the market actually is.

Technology push is not inherently wrong. But unvalidated technology push is how good engineering organizations build products nobody buys.

Related Case Studies

• Business Case Discipline That Stops Bad Investments: How a Professional Services Firm Reduced Project Failure Rates
• Building the Infrastructure That Makes Everything Else Work: Product Management at a Global Financial Services Firm

Ready to Build Market-Driven Product Strategy in Your Organization?

Sequent Learning Networks works with product organizations at mid-to-large companies to build the strategy and roadmapping discipline that connects product decisions to market reality and business performance.

• Schedule a Conversation with Sequent Learning Networks
• Explore Product Management Training Programs
• Learn About Product Management Capability Assessments