Jesse Jacoby
A division president I spoke with last spring described a moment of clarity that came too late. He had just finished reviewing his organization’s project portfolio and realized that nine of the fourteen active initiatives on his list had been approved individually, in separate steering committee meetings, over a period of eighteen months. Each one had made sense at the time. Each had a compelling business case. No single approval had felt reckless.
But when he laid them out side by side and mapped which ones were in active deployment simultaneously, the picture was undeniable: four major initiatives were all reaching their peak adoption demands in the same 90-day window. Three of them touched the same 400-person workforce. None of the planning conversations had accounted for the others.
“We didn’t overload the organization,” he told me. “We did it incrementally, over a year and a half, one good decision at a time.”
This is one of the most common and least visible failure modes in enterprise transformation: not a single reckless bet, but the accumulation of individually reasonable decisions that collectively exceed what an organization can absorb. The result looks like change fatigue, poor adoption, and resistant culture. But those are symptoms, not causes. The cause is a portfolio management problem.
Why Initiative Count Doesn’t Tell the Whole Story
The most common heuristic leaders use to assess change load is counting initiatives. If the number feels high, something gets put on hold. If it feels manageable, the team presses forward.
The problem is that raw count ignores the most important dimension: weight. Two initiatives with minimal organizational impact are a different challenge than two initiatives requiring every affected employee to learn a new system, adopt new processes, and shift how they collaborate with adjacent teams. Counting them the same way produces no useful information.
Change weight has at least four meaningful components. The first is stakeholder reach: how many people are affected, and how diverse are those populations? A single initiative that touches one function is fundamentally different from one that touches seven. The second is change magnitude: how much is actually changing? Process adjustments and behavioral overhauls sit at opposite ends of a spectrum, and organizations routinely underestimate how far right they are on that spectrum. The third is timeline intensity: a 24-month rollout with multiple phases absorbs very differently than a compressed six-month implementation. The fourth is the change readiness of the affected group, the least commonly assessed factor and often the most predictive one. A team that has recently been through a successful transformation has developed muscle. A team that has never been asked to change substantially has none.
When you score initiatives on these dimensions rather than simply counting them, the portfolio looks different. And when you map those scores across time, overlapping peaks become visible before they become crises.
The Portfolio View Most Organizations Skip
Managing transformation at the portfolio level requires a discipline that most organizations apply only in theory. The language exists: governance committees, steering councils, transformation management offices. The practice, more often than not, collapses back into initiative-level management the moment day-to-day execution pressure builds.
What a genuine portfolio view requires is a shared visibility into three things simultaneously: the total change load the organization is carrying at any given moment, the absorption capacity available to receive that load, and the sequencing of peak demands relative to each other.
The capacity side of this equation is the most neglected. Absorption capacity is not fixed. It varies by how much change management infrastructure exists, how engaged and available executive sponsors are, how recent and successful the organization’s prior change experience has been, and how deeply change capability has been built into the workforce. An organization with a mature change management function, a strong track record, and an engaged leadership team can absorb significantly more than one operating with ad hoc change support and depleted goodwill from a rough prior implementation.
Understanding your capacity isn’t an imprecise exercise. It can be assessed systematically across those dimensions, scored, and used as a real denominator against which you measure portfolio load. When the load-to-capacity ratio runs hot, the response isn’t always to reduce initiatives. Sometimes it means building capacity first. Sometimes it means staggering timelines. Sometimes it means making explicit the sequencing decisions that were previously implicit and contested.
The Sequencing Decision Nobody Wants to Make
The hardest part of portfolio-level change management isn’t the analysis. It’s the conversation that follows the analysis.
Most transformation portfolios are politically loaded. Each initiative has a sponsor with authority, a business case tied to someone’s annual objectives, and a team of people who have been working on it for months. When the portfolio view reveals that three of those initiatives are competing for the same organizational bandwidth in the same quarter, the response is rarely “let’s move ours.” It’s “everyone else should move theirs.”
Sequencing decisions require someone with the authority and the mandate to make them. In most organizations, that person is either the transformation management office (if one exists and has real authority) or the most senior leader with visibility across the full portfolio. Without explicit ownership of the sequencing function, portfolio overload persists because every individual sponsor is optimizing for their initiative, not for the organization’s overall absorption capacity.
This is why portfolio governance is not a process question. It’s a leadership question. The structures matter, but they only produce outcomes when a leader is willing to tell a peer that their high-priority initiative needs to move by a quarter because the organization cannot absorb four simultaneous peak demands.
The Capacity Foundation
There is a longer-term dimension to this that organizations rarely address directly. Absorption capacity is not just a constraint to manage around. It is a capability to build.
Organizations that invest in internal change management infrastructure, a common methodology, practitioner competency, governance structures, and leadership development, increase their absorption capacity over time. They become capable of carrying more change load without the same level of disruption. They make better sequencing decisions because they have better visibility. They deploy change resources strategically rather than reactively.
The organizations that struggle chronically with transformation are not always overambitious. Often, they are under-built on the capacity side and have never made the investment to change that. The symptom is a portfolio that always seems too full. The diagnosis is a capacity baseline that has never been developed deliberately.
I’ve seen this play out in both directions. A large health system we worked with had a sophisticated IT organization managing a complex portfolio of strategic initiatives, but change expertise was fragmented across functions, methodologies varied by project, and there was no shared way to assess or prioritize incoming demand. We designed and built an internal change management capability from the ground up, tailored to fit how their teams actually operated and what their culture could sustain. That meant custom methodology, a practitioner development model, governance structures with real teeth, and a portfolio-level intake process. Within a year, their capacity to absorb change had measurably increased, not because they were running more initiatives, but because they had the infrastructure to manage them intentionally rather than reactively.
The division president I mentioned at the start eventually built a portfolio-level tracking discipline that showed him and his peers, in a single view, the total change weight the organization was carrying each quarter, mapped against a capacity score his team had assessed. The first time they ran it, two pending approvals were deferred. Not because they were bad ideas, but because the organization could not absorb them without sacrificing the four that were already in flight.
That’s not failure. That’s governance. And organizations that treat it as such get more from their transformations, not less.
