Why Portfolio Connectivity Is Your Biggest Enabler or Your Biggest Risk
Decisions create value only when supply and demand move dynamically and in concert.
Afew months ago, I was with a team at a global pharmaceutical company reviewing a product portfolio that, on paper, looked relatively stable.
Early demand signals were coming through; for instance, one showed a clear rise in prescriptions for a newly launched oncology therapy after updated clinical guidance. At the same time, a mature respiratory drug was declining faster than expected in some regions as generics gained traction. Elsewhere, a supply constraint was evident, with limited availability of a key API starting to impact production.
None of this was unusual. What stood out was how disconnected all these signals were.
The pharma company sees this often, just in different forms. And it’s not alone – more than half of my conversations with supply chain and operations leaders over the last three months have been about the same underlying challenge: when you have visibility, how do you then connect demand signals, supply constraints, and portfolio decisions in a way that actually drives coordinated action? And how do you do it quickly enough for it to matter?
That’s the pattern I keep seeing: SKU-level connectivity, across the portfolio, is either your biggest enabler or your biggest source of risk. If underlying connectivity is weak, the system does not move with the signal. Over time, this stops being a planning issue and becomes a structural one.
PLM No Longer Reflects Reality
A big part of this problem is that product lifecycle management (PLM) systems still presume that there is a certain level of order: concept to launch, launch to growth, growth to exit. In reality, lifecycle behavior is jagged, asynchronous, and constantly interrupted, with new information that does not respect any predefined stage or move in phases.
Signals may be reported at the portfolio level, but they enter the organization at the lowest level of granularity. In retail, it is a unit sale by SKU, by store, at a specific moment. In pharma, it may be a new patient response or a batch deviation. In energy, it may be an unexpected fluctuation at an asset, a well, or a node in the network.
These are examples of reality deviating from the plan and not in any sort of sequenced way. But most PLM systems are still designed as if this isn’t the case.
If an SKU is overperforming in one region while supply is locked somewhere else, commercial, supply, and allocation decisions need to move dynamically and in concert, otherwise the response fragments. One team updates the forecast. Another raises a constraint. A third discusses reallocation in the next cadence. By the time the system reacts, the moment has passed.
Decisions create value only when they move together. If demand and supply are static and sit in different systems, different teams, and different rhythms, you can see and analyze what is happening, but decisions can’t move and, therefore, neither can the system.
How to Make This a Reality
Companies like NVIDIA show what addressing this nuance looks like in practice.
Signals are acted on beyond the company itself, shaping capacity, memory, and packaging decisions across partners before constraints fully hit. That’s the difference: not awareness of the signal per se, but coordinated movement early enough to shape the ideal outcome.
The imperative for leaders is to build explicit connectivity between demand and supply at the level where decisions are made and executed. That often starts with simplifying each side independently: creating a coherent view of demand, a coherent view of supply, and then reconnecting them into a system that can coordinate action.
One pharmaceutical company in our community enabled this through parameter management. Demand thresholds were set around prescription uplift and clinical guidance changes, while supply parameters defined API constraints, batch sizes, and prioritization rules across the portfolio. When a signal hits at the local level, those connections become pathways for action. Inventory shifts, demand redirects, and capacity is reallocated, all at the same time.
Connectivity is not the outcome. Movement is. And that movement must hold across time and levels of aggregation because decisions don’t live in one view. The business still has to be sliced by function, horizon, region, and level of detail. Connectivity is what keeps those views aligned without freezing the system.
Connectivity Is About Control
In this context, connectivity isn’t about integration for its own sake. It’s about control.
That is the shift many teams underestimate. We still manage portfolios as static collections moving through defined stages, when, in reality, they’re dynamic systems that need constant correction.
The practical starting point is simple. Ask:
- Are signals captured at the level where they occur, or lost through aggregation?
- Do they propagate across demand and supply, or stall inside functional silos?
- When they hit, do decisions move together, or in sequence?
Portfolio discipline is no longer about balance. It’s about how quickly you can move weight.