At a Glance

Industry	Financial Services (Global)
Challenge	Product managers existed across 80+ roles but had no product-level financial data, inconsistent metrics, 20+ overlapping job titles, and no portfolio governance
Approach	Organizational diagnostic followed by infrastructure build: proxy product P&L, metrics standardization, role rationalization, and portfolio review cadence
Key Results	Product-level financial visibility established; NPS and retention metrics standardized across products; 20+ job titles rationalized to a consistent role structure; quarterly portfolio reviews instituted; zombie products identified and sunset; foundation built for competency development

Overview

This product management case study describes how a financial services firm built the foundational infrastructure required for product management to function as an operating discipline. The organization had product managers across multiple business units, but metrics existed only at the business line level, roles were inconsistently defined, and portfolio governance was absent. By establishing product-level financial visibility, standardizing metrics, clarifying roles, and institutionalizing portfolio reviews, the organization enabled product managers to manage their products as businesses for the first time.

The Business Situation

“We were general managers without financial statements.”

This financial services firm had product managers. Dozens of them, spread across multiple business units and product lines. The org charts showed a product management function. The job postings used product management language.

But when leaders tried to answer basic questions, the answers did not exist. Which products are performing well? Where is the portfolio underinvested? What should we stop funding? Product management was a job title, not an operating discipline.

The organization was not ignoring performance. New customer acquisition was monitored carefully, particularly for B2B treasury services lines where landing a new corporate client represented significant lifetime value. NPS was collected. Client retention was reviewed quarterly. But all of it lived at the business line level. Product managers could see how Treasury Services was performing. They could not see how their product within Treasury Services was performing.

The Problem: No Infrastructure to Support the Discipline

The product P&L gap was structural. Financial systems had been built around business lines, customer segments, and channels. Products cut across those structures, and the systems had never been configured to track performance at the product level.

“We had NPS, but every group measured it differently, on different intervals. You couldn’t compare across products. It was data without insight.”

Compounding this, more than 20 different job titles existed across 80 or more people with product responsibilities. The same work carried different names depending on the business unit. Career paths were unclear. Expectations were inconsistent. New hires had no model for what good looked like.

There was no mechanism for looking across the portfolio and making trade-off decisions. No cross-product visibility. No investment criteria. No governance.

This is one of the most common product management failure patterns: organizations invest in hiring product managers without building the organizational infrastructure that makes product management possible.

The Product Management Consulting Intervention: Infrastructure First

Sequent Learning Networks conducted a comprehensive organizational diagnostic and concluded that this was not a skills gap. Individual product managers knew how to do the work. The gap was organizational: there was no infrastructure to support product management as a discipline.

The intervention built the foundation across four dimensions:

1. Product-level financial visibility. Rebuilding core financial systems was not feasible in the near term. But directional visibility was achievable. Working with finance partners, the team developed proxy metrics and allocation methodologies that gave product managers approximate product-level financials. Revenue was attributed using product logic. Costs were assigned using activity-based estimates. The numbers were not audit-ready. They were decision-ready.
2. Metrics standardization. The organization did not need every product measured identically. But it needed comparable methodologies and consistent intervals. NPS measurement was rationalized: same calculation method, same cadence, same survey approach across product lines. Retention metrics were disaggregated to the product level where data structures allowed.
3. Role clarity. Working with HR and business unit leaders, the organization defined what product managers were responsible for, and what they were not. The 20-plus titles were mapped to a simplified structure with clear distinctions between levels and expectations. Career paths were documented. Competency requirements were specified.
4. Portfolio governance. A quarterly portfolio review cadence was established with clear criteria for investment decisions. Products were categorized by strategic role: grow, maintain, harvest, or sunset. Resource allocation conversations now had a framework.

The Turning Point: Knowing What You Have

The changes were not dramatic in any single dimension. Infrastructure work rarely produces a single headline metric. But the cumulative effect was significant.

Product managers could see their product’s financial performance, approximately and directionally, but visibly. They could compare their NPS trends to other products and know the comparison was valid. They could explain their role without inventing their own definition.

Leaders could answer questions they could not answer before: which products are profitable, where should we invest next quarter, what should we stop doing.

“We finally know what we have.”

Outcomes

• Product-level financial visibility established using proxy allocation methodologies developed with finance partners
• NPS and retention metrics standardized for cross-product comparison, eliminating the data-without-insight problem
• Role definitions rationalized from 20+ titles to a consistent structure with clear levels and career paths
• Quarterly portfolio review cadence institutionalized with investment criteria for grow, maintain, harvest, and sunset decisions
• Zombie products identified and moved to sunset, freeing resources for higher-priority work

The infrastructure build also revealed the next challenge: product managers who now had data but needed to develop the analytical skills to use it. Role clarity existed, but competency development was still needed. That became the next phase of the engagement.

But the infrastructure had to come first. You cannot develop business case skills without access to business data. You cannot build roadmapping discipline without portfolio context. You cannot manage product performance without product-level visibility.

What This Story Reveals About Product Management Capability

Product management capability is not just about skills. It is about infrastructure.

Organizations often try to improve product management through training alone, teaching methodologies, frameworks, and best practices. But training assumes the infrastructure exists to apply what is learned. When data is not available at the product level, when roles are not clearly defined, and when portfolio governance does not exist, even well-trained product managers cannot perform effectively.

The sequence matters: infrastructure first, then capability development. Product-level financial visibility, even if approximate. Metrics that are consistent enough to compare. Role definitions that set clear expectations. Portfolio governance that enables trade-off decisions.

Many organizations discover they have been trying to build product management capability on a foundation that does not exist. The infrastructure is not glamorous work. But without it, product management remains a job title rather than an operating discipline.

Related Case Studies

• Business Case Discipline That Stops Bad Investments: How a Professional Services Firm Reduced Project Failure Rates
• From Technology Push to Market Pull: How a Global Industrial Company Transformed Product Strategy

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