At a Glance

Industry	Healthcare (Global)
Challenge	Product decisions driven by internal opinions and tribal knowledge rather than validated market data; no standardized customer research methodology; competitive intelligence scattered with no central repository
Approach	Organizational diagnostic followed by customer and market insight infrastructure build: standardized research methodologies, competitive intelligence repository, and integration of insights into planning processes
Key Results	Customer research embedded as a required input to product planning; prioritization decisions grounded in validated data; competitive intelligence centralized with assigned ownership; leadership equipped to reject investments lacking market evidence

Overview

Customer focus is not the same as customer knowledge.

This product management case study describes how a global healthcare company built customer and market insight capability at the organizational level. Product decisions had been based on internal conversations and tribal knowledge rather than validated research. By investing in research infrastructure, standardizing methodologies, and integrating insights into planning processes, the organization enabled evidence-based prioritization, including the discipline to say no to investments that lacked market validation.

The Business Situation: Talking About Customers Without Knowing Them

“We have extensive conversations internally about customers. But when you ask where the data comes from, the answer is often… we’re not sure.”

A global healthcare company prided itself on customer focus. The phrase appeared in mission statements, leadership communications, and performance reviews. Product teams referenced customer needs in every strategy presentation.

When the diagnostic pressed deeper, a different picture emerged. Customer research happened, but sporadically. Some product managers were diligent about conducting interviews and validating assumptions. Others relied on what they had heard from sales, what they remembered from past experiences, or what seemed intuitively obvious. There was no standardized approach. No common methodology. No way to distinguish validated insight from informed speculation.

The Problem: Tribal Knowledge as the Foundation for Strategy

In the absence of systematic customer research, internal conversations filled the gap. Experienced people shared perspectives. Consensus emerged. Decisions were made. The problem was not that experienced people were wrong. Often their intuitions had been built over years of genuine customer interaction. The problem was that no one could distinguish pattern recognition based on evidence from assumption based on familiarity.

“If we discuss it together, it must be right.”

With competitive intelligence, even the opinions were thin. Information about competitors lived in individual heads and scattered files. There was no central repository. No systematic collection process. Customer retention was strong, which created a false sense of security about competitive threats.

The downstream effects were significant. Product strategies were built on assumptions that could not be verified. Prioritization debates devolved into opinion battles where the loudest voice or most senior advocate won. Leadership had no grounds to say no. Without validated data, every proposed investment had roughly equal standing, which meant resources spread too thin and the portfolio filled with work that could not be defended.

The Product Management Training Intervention: Building the Research Infrastructure

The diagnostic made clear this was not a skills gap at the product manager level. Individual product managers knew how to conduct customer research. Many wanted to do more of it. The gap was organizational: no budget allocated for research, no standardized methodologies, no expectation that strategies would be grounded in validated data.

Fixing this required leadership commitment, not just endorsement but actual investment. The build covered three areas:

Research methodology was standardized. Not rigid templates, but consistent approaches that ensured quality and comparability. Customer discovery protocols were defined. Interview frameworks were developed. Techniques for distinguishing stated needs from latent needs were embedded into the planning process.

Competitive intelligence got a home. A central repository was established, not a technology platform but a structured approach to capturing, organizing, and sharing competitive information. Regular competitive reviews were added to the planning cadence, with assigned ownership so the work was undertaken.

Insights were integrated into planning. Customer and market insights became required elements of strategy development. Product strategies had to demonstrate the research that informed them. Prioritization discussions had to reference market data.

Leadership learned to ask different questions. Instead of “what do you think customers want?” the question became “what does your research tell you?” Instead of “why should we invest?” the question became “what is the validated market opportunity?” When leadership changes its questions, product teams adapt their preparation.

The Turning Point: The Discipline to Say No

The most significant outcome was not better research methods. It was better decisions.

When market insights became the foundation for prioritization, some projects that had been building momentum were stopped. The research did not support them. Customer need was not validated. Market opportunity was smaller than assumed. Previously, these projects would have proceeded because the team was committed, because an executive believed in it, because momentum is hard to stop without a principled basis for objection.

Now, leadership had grounds to say no. Not “I don’t like this idea” but “the market evidence does not support this investment.” That shift, from opinion-based rejection to evidence-based rejection, changed the culture of prioritization.

The discipline of saying no begins with the discipline of truly knowing.

Saying no was uncomfortable at first. Some teams felt dismissed. Some relationships were strained. But resources flowed to validated opportunities, and the overall quality of the portfolio improved because the bar for entry had been raised.

Outcomes

• Customer research embedded in the product planning cadence as a required input, not an optional activity
• Prioritization decisions grounded in validated market data rather than advocacy or seniority
• Competitive intelligence repository established with assigned ownership and regular review cadence
• Leadership equipped with the evidence and the expectation to reject investments lacking market validation
• Culture shift from passionate argument wins to evidence wins, sustained by changed leadership questions

The culture shift took longer than the infrastructure build. Old habits persisted. But the foundation was in place, the expectation had been set, and customer insight gradually became embedded in how the organization made product decisions.

What This Story Reveals About Customer Research and Product Management

Many product organizations talk about customers constantly while knowing remarkably little about them. Internal conversations create the illusion of insight. Tribal knowledge fills the gap where validated research should be. The result is strategies built on assumptions, prioritization debates that cannot be resolved, and leadership that cannot say no because there is no basis for rejection.

Changing this requires more than product management training in research techniques. It requires organizational investment in customer and market insight infrastructure: standardized methodologies, competitive intelligence systems, and integration of insights into planning processes at every level.

Most importantly, it requires leadership that asks different questions. Not “what do you think?” but “what does your research show?” When that becomes the standard, teams adapt. And the portfolio gets better, not because people worked harder, but because better information was available when decisions were made.

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