Business Case Discipline That Stops Bad Investments

At a Glance

Overview

This product management case study describes how a global professional services organization reduced project failure rates by building business case discipline across its product and technology investment process. Through an applied learning engagement with Sequent Learning Networks, cross-functional teams evaluated real investment opportunities using a structured, evidence-based methodology. Two proposed investments were rejected before a single euro was spent on development. Two were approved and delivered strong financial results. The most important outcome was not better spreadsheets. It was better decisions.

A Familiar Situation

“Every possible investment went through the CFO spreadsheet, and the spreadsheet always said yes.”

A global professional services organization was experiencing product and technology project failure rates exceeding 50%. The company had a formal investment approval process. Spreadsheets were reviewed. Assumptions were questioned. The process looked rigorous.

But the outcome was always the same. Every proposed investment got approved. The pipeline never slowed, even as failure rates climbed.

The problem was not the process. It was how teams had learned to use it.

The Real Problem: Business Cases as Justification Documents

Teams had mastered the art of reverse-engineering approval. They started with the conclusion, then worked backward to fabricate numbers that supported it. Customer validation was assumed, not verified. Market sizing relied on optimistic projections. Competitive analysis was thin. As one leader put it directly: “People fake the numbers without validation.”

The business case process had become a compliance exercise, not a decision discipline. This is a common product management failure mode: when investment approval becomes the goal, analysis becomes theater.

The Product Management Training Intervention

After a new CEO joined the organization, Sequent Learning Networks was engaged to reset how product and technology investments were evaluated. Four cross-functional teams were formed, each assigned a real investment decision ranging from €1M to €3M. No hypothetical cases. No training simulations. Real money, real stakes.

Teams completed a two-day workshop introducing a 12-section business case framework covering:

• Customer context and validated need
• Competitive landscape and alternatives
• Value proposition and pricing rationale
• Financial scenarios, sensitivity analysis, and risk
• Operational and delivery implications

The workshop was only the starting point. Over the following weeks, teams conducted real customer discovery, gathered competitive intelligence, and built financial models grounded in evidence, not hope. Weekly coaching sessions replaced guesswork with scrutiny. Assumptions had to be documented and defended. When teams drifted back toward spreadsheet-driven optimism, they were stopped and redirected.

The Turning Point: Saying No

Midway through the program, two teams concluded that their investments could not be justified. Their first instinct was to stop and return to their day jobs. Instead, they were encouraged to complete the analysis and present a no-go recommendation to senior leadership.

This was culturally uncomfortable. Delivering bad news up the chain was not the norm. But those no-go decisions became the most powerful learning moments of the entire program, and the clearest demonstration that the product management training had taken hold.

When business case discipline works, approval rates go down, not up. High approval rates usually signal a broken system.

Outcomes

All four teams presented to the executive team. Here is what happened:

• Two investments were rejected, avoiding an estimated €4–10M in likely losses
• Two investments were approved and moved to development
• One launched early, with fewer resources than planned
• One launched later but exceeded revenue forecasts by approximately 20%
• €1.9M in incremental annual revenue generated by the end of Year 2
• Company EBITDA increased by approximately 1.5 percentage points

The two teams that recommended no-go were recognized and rewarded by senior leadership, a signal that changed the culture of how investment decisions were framed going forward.

What This Story Reveals About Product Management Training

The goal of product management training is not to help organizations approve more investments. It is to help them make better ones. In this case, better meant saying no to two investments that would have failed, and saying yes to two that delivered real returns.

Failure rates drop not because execution improves, but because fewer bad bets get funded. The real question every product organization should be asking is not “how do we get more projects approved?” but “how do we make better investment decisions?” Because sometimes the best decision is no.

This kind of discipline requires more than a methodology. It requires an organizational commitment to evidence over advocacy, and leadership willing to reward the teams that surface problems before they become failures.

Related Case Studies

• From Technology Push to Market Pull: How a Global Industrial Company Transformed Product Strategy and Roadmapping
• Building the Infrastructure That Makes Everything Else Work: Product Management at a Global Financial Services Firm

Ready to Build Business Case Discipline in Your Organization?

Sequent Learning Networks works with product organizations at mid-to-large companies to build the investment decision discipline that separates strong product portfolios from crowded, underperforming ones.

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