---
title: Transformation Requires Portfolio Discipline
description: Map the work against where the value is, and be willing to stop what does not survive the test.
---

[Skip to content](https://www.fountainheadltd.com/insights/transformation-requires-portfolio-discipline#main-content)

[![](https://www.fountainheadltd.com/hs-fs/hubfs/TFAL%20Logo%20v3-3.jpg?width=541&height=800&name=TFAL%20Logo%20v3-3.jpg)Homepage](https://www.fountainheadltd.com/)

- [How I Work](https://www.fountainheadltd.com/approach)
- [Results](https://www.fountainheadltd.com/results)
- [Insights](https://www.fountainheadltd.com/insights)
- [About](https://www.fountainheadltd.com/aboutus)
- [Contact](https://www.fountainheadltd.com/contact-us)

[Schedule an Intro Call](https://calendly.com/vinay-tfal/intro)

- [How I Work](https://www.fountainheadltd.com/approach)
- [Results](https://www.fountainheadltd.com/results)
- [Insights](https://www.fountainheadltd.com/insights)
- [About](https://www.fountainheadltd.com/aboutus)
- [Contact](https://www.fountainheadltd.com/contact-us)

[Schedule an Intro Call](https://calendly.com/vinay-tfal/intro)

Portfolio Discipline Value Creation

# Transformation Requires Portfolio Discipline

![Vinay Agrawal](https://www.fountainheadltd.com/hs-fs/hubfs/2023-08-23%20Vinay%20L%20AI%20white2.png?width=48&height=48&name=2023-08-23%20Vinay%20L%20AI%20white2.png)

 Vinay Agrawal

June 4, 2026

Every transformation program I've seen has a version of "but we've always done it that way" buried somewhere in the portfolio. The irony is that phrase is usually what the transformation was supposed to eliminate — and nobody noticed it was still running the show.

The most expensive assumption in any transformation program usually includes some version of "but we've always done it that way."

I've seen it in manufacturing. We were redesigning the package sizes for an entire product portfolio — 30 production lines across 4 sites. While working with the business planning team on line assignments, we kept hitting a roadblock: lines were dedicated to a single size, and there wasn't enough regional demand for each size to keep every line fully utilized. Some lines were sitting idle 30% of the time. The obvious fix was to run multiple sizes on the same line. The obstacle: converting between sizes took 2–3 days, which made flexibility economically unviable. So we asked why — traced it to three specific part families — and redesigned them to be quick-change. Conversion time dropped from days to hours. Lines that had been idle were now flexible. When we mapped the full network, 20% of total capacity was excess. A site consolidation that wasn't in the original plan became not just possible but straightforward.

The question that unlocked it wasn't "how do we deliver the new packages faster." It was "why are these lines sitting idle" — which nobody had asked because the answer had always been assumed.

I've seen the same pattern in digital. An Auto Finance executive team had a full book of work underway — roadmaps, platforms, active development. When we mapped all of it against a newly created Customer Lifecycle Management Model — Assess (am I ready for my next car?), Shop (which car, what can I afford?), Buy (the transaction itself), and Service (not just the loan but the life of the vehicle) — the picture was uncomfortable. To be fair, most auto finance companies at the time were oriented the same way: heavily invested in competing at the point of purchase, the Buy moment. It made sense historically. That's where the transaction happened.

But the opportunity we saw was different. If you could be genuinely helpful to a customer during Assess and Shop — before they'd made any decisions — you'd earn share of mind long before a financing decision was needed. You'd be the obvious choice at Buy not because you competed hardest at the transaction, but because you'd already been useful when it mattered. The lifecycle map made that opportunity visible — and made equally visible how little of the existing investment was pointed at it. There were also duplicate efforts running in parallel within the existing portfolio that nobody had line of sight to. The business hadn't made a bad decision. It had inherited a definition of itself and never pressure-tested it against where customers actually needed it to show up.

The lifecycle map forced a choice: keep investing in what was already crowded, or redirect toward what was actually underserved. That's a stopping decision as much as a building decision.

The discipline is the same whether you're allocating capacity across a manufacturing network, redesigning equipment changeover for flexible production, or deciding which parts of the customer experience in a tech or service business are actually worth investing in: map what you're doing against where the value actually is. And be willing to stop — or never start — the work that doesn't survive that test.

The organizations that create the most value in a transformation aren't the ones with the longest and most ambitious roadmaps. They're the ones with the courage to challenge long-held beliefs and keep the roadmap short and focused.

*This is part of a series on value creation in PE-backed businesses. Earlier pieces: [AI Transformation Doesn't Start With AI](https://www.fountainheadltd.com/insights/ai-transformation-doesnt-start-with-ai) and [Complexity Is a Margin Problem](https://www.fountainheadltd.com/insights/complexity-is-a-margin-problem).*

## Share this post

<https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.fountainheadltd.com%2Finsights%2Ftransformation-requires-portfolio-discipline><https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.fountainheadltd.com%2Finsights%2Ftransformation-requires-portfolio-discipline><https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fwww.fountainheadltd.com%2Finsights%2Ftransformation-requires-portfolio-discipline><https://pinterest.com/pin/create/button/?url=https%3A%2F%2Fwww.fountainheadltd.com%2Finsights%2Ftransformation-requires-portfolio-discipline>[mailto:https%3A%2F%2Fwww.fountainheadltd.com%2Finsights%2Ftransformation-requires-portfolio-discipline](mailto:https%3A%2F%2Fwww.fountainheadltd.com%2Finsights%2Ftransformation-requires-portfolio-discipline)

## Keep reading

### [Operating Model Value Creation May the Force Be With You](https://www.fountainheadltd.com/insights/may-the-force-be-with-you)

### [Operating Model Value Creation Who Owns the Constraint?](https://www.fountainheadltd.com/insights/who-owns-the-constraint)

# The Fountainhead Advisors LLC

- [How I Work](https://www.fountainheadltd.com/approach)
- [Results](https://www.fountainheadltd.com/results)
- [Insights](https://www.fountainheadltd.com/insights)
- [About](https://www.fountainheadltd.com/aboutus)
- [Contact](https://www.fountainheadltd.com/contact-us)

<https://www.linkedin.com/in/vinay-agrawal/>

---

Operating partner and transformation executive. People, process and technology, not financial engineering.

© 2026 The Fountainhead Advisors LLC · Dallas–Fort Worth · [Vinay@FountainheadLtd.com](mailto:Vinay@FountainheadLtd.com)

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Vinay Agrawal",
    "url" : "https://www.fountainheadltd.com/insights/author/vinay-agrawal"
  },
  "dateModified" : "2026-10-31T16:19:06.256Z",
  "datePublished" : "2026-06-04T14:00:00.000Z",
  "headline" : "Transformation Requires Portfolio Discipline",
  "mainEntityOfPage" : {
    "@id" : "https://www.fountainheadltd.com/insights/transformation-requires-portfolio-discipline",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://www.fountainheadltd.com/hubfs/TFAL%20Logo%20v3-3.jpg"
    },
    "name" : "The Fountainhead Advisors LLC"
  }
}
```