Managing the Products You Already Have

At a Glance

Overview

The Business Situation: Great at Launching, Lost After Launch

“We were great at launching. We had no idea how to manage what happened after.”

A global technology company had built an impressive product launch capability. The development process was well-defined with clear stage gates. Cross-functional teams assembled reliably. Launch checklists ensured sales was enabled, marketing was prepared, and operations was ready.

Products got to market. Then they disappeared.

Once a product was in market, attention shifted to the next initiative. The question “how is the product we launched six months ago actually doing?” was rarely asked, and almost never answered with data. Leadership estimated that fewer than 30% of new products were meeting original revenue expectations, but that was a guess, because the data to know for certain did not exist.

The Problem: Accountability That Ends at Launch

The diagnostic revealed a pattern leadership had sensed but never fully examined. The root cause was structural: accountability ended at launch. Product managers were measured on getting products to market. What happened after was someone else’s problem, or no one’s.

• Performance data was not tracked systematically. Products launched with business case projections: revenue targets, margin expectations, customer acquisition goals. But there was no process for tracking whether those projections were being met. Data lived in individual spreadsheets, not shared systems.
• Win-loss analysis did not happen. When deals were won, sales celebrated. When deals were lost, sales moved on. No one captured why customers chose the product or why they chose competitors. The feedback loop that should have connected market response to product decisions simply did not exist.
• Zombie products accumulated silently. Products that should have been retired years ago continued consuming engineering time, support resources, and leadership attention. Not successful enough to deserve investment. Not failing visibly enough to force a decision. They persisted by default.

Zombie products are not a resource allocation problem. They are an accountability problem. When no one is responsible for post-launch performance, no one has grounds to make a retirement decision.

The Product Management Training Intervention: Extending Accountability Beyond Launch

Building post-launch discipline required changes across multiple dimensions. No single intervention would fix a structural accountability gap.

• Performance metrics were institutionalized. A standard framework for post-launch metrics was established: revenue realization versus projection, customer acquisition and retention, usage patterns, support volume, NPS trajectory, margin performance. Product managers identified the metrics that mattered for their specific product and tracked them consistently in shared systems, not individual spreadsheets.
• Review cadences were established. Quarterly post-launch reviews became part of the planning rhythm. For the first year after launch, every new product was reviewed against business case projections. The question was explicit: is this product performing as expected? The reviews were not punitive. A product not meeting projections was not a failure. It was information requiring a response.
• Win-loss analysis was institutionalized. A systematic process captured why customers chose the product or chose competitors. This data flowed to product teams on a regular cadence, informing roadmap priorities, positioning adjustments, and pricing decisions.
• Lifecycle decisions were formalized. Every product in the portfolio was categorized: grow, maintain, harvest, or sunset. The categorization drove resource allocation. Zombie products were finally visible, named, and many were moved to sunset, freeing significant resources.
• Accountability was extended. Product managers became responsible for post-launch performance, not just launch execution. The incentive shifted from getting it launched to making it successful. That shift changed how product managers thought about business cases, positioning, and the decisions they made during development.

The Turning Point: Seeing What Was Always There

The first round of post-launch reviews was uncomfortable. Products everyone assumed were successful turned out to be underperforming against their business cases. Products that had been largely ignored were revealed as quiet successes deserving more investment.

The gap between projection and reality was larger than anyone had admitted. But now it was visible, which meant it could be addressed. Over time, a feedback loop developed. Product managers who knew they would be accountable for post-launch performance created more realistic business cases during the planning phase. Forecast accuracy improved. The gap between projection and reality narrowed on subsequent launches.

When you change what product managers are measured on, you change what they optimize for from the beginning.

Outcomes

• Product performance visibility established across the full portfolio for the first time
• Underperforming products identified and addressed through reinvestment, repositioning, or retirement
• Zombie products moved to sunset, freeing engineering, support, and leadership resources
• Product manager accountability extended through the full lifecycle, not just to launch
• Business case forecast accuracy improved on subsequent product launches
• Win-loss data flowing regularly to product teams to inform roadmap and positioning decisions

The organization developed a capability it had not previously had: managing the products already in the portfolio with the same discipline applied to products in development. The products already in market, often a larger source of untapped value than anything in the development pipeline, finally received the management attention they required.

What This Story Reveals About Post-Launch Product Management

Most product management training and consulting attention goes to the front end of the product lifecycle: discovery, strategy, roadmapping, and launch. These are critical capabilities. But they only explain part of why product portfolios underperform.

The other part is what happens after launch. When accountability ends at launch, performance is never measured against projection, zombie products accumulate by default, win-loss intelligence never reaches product teams, and lifecycle decisions are never made explicitly. Resources stay committed to products that have stopped earning them.

Building post-launch discipline requires metrics systems, review cadences, lifecycle decision frameworks, and, most importantly, extending accountability beyond launch. Product managers measured on market success rather than launch completion make different decisions about what to build, how to position it, and what to commit in the business case.

The products you already have are often a larger source of untapped value than the products you are planning to build. But capturing that value requires managing them actively, and management requires visibility, accountability, and decision discipline through the full product lifecycle, not just through launch day.

Related Case Studies

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

Ready to Build Post-Launch Discipline 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