Managing multiple changes simultaneously is not an edge case in enterprise transformation. It is the norm. Most large organisations are running ten, twenty, or more concurrent change initiatives at any point in time. The assumptions that change practitioners rely on to manage this complexity have largely been inherited from single-initiative change management and applied wholesale to the portfolio context. Many of them are wrong.

This matters because wrong assumptions about managing multiple changes lead to specific, predictable, and expensive failures: adoption rates that fall short of targets, employee fatigue that accumulates into resistance, and programme sequencing decisions that look reasonable in isolation but create unnecessary risk in aggregate. Gartner’s research on change adoption found that only 32% of business leaders report achieving healthy change adoption by employees. The gap between change investment and change outcomes is real and persistent.

Working through seven assumptions that are widespread in change management practice, and what the evidence actually shows, offers a clearer picture of where portfolio-level management typically breaks down.

Assumption 1: If each programme is managed well, the portfolio will be managed well

This is the foundational assumption of most enterprise change management: that quality at the programme level aggregates into quality at the portfolio level. It is comforting because it is consistent with how resourcing models work: staff each programme with capable change managers, and the organisation’s change burden is handled.

The evidence suggests otherwise. A programme can have excellent communication, well-designed training, rigorous stakeholder engagement, and still fail to achieve target adoption if it lands in a quarter when the relevant employee group is simultaneously absorbing two other significant changes. The failure is not programme-level. It is portfolio-level. And it is invisible to a resourcing model that assigns one change manager per programme.

The assumption treats change capacity as infinite. Smartsheet’s 2025 Project and Portfolio Management Priorities Report found that 92% of PPM professionals struggle to adapt to workplace changes, and 71% say constant workplace shifts make it difficult to stay productive. Employee capacity to absorb change is finite and varies by group and by history. Portfolio management of change requires treating it as such.

Assumption 2: Change saturation is visible

Most change managers who have worked in large organisations have seen change saturation: the glazed look when a new initiative is announced, the rising resistance that seems disproportionate to the scale of the change, the help desk calls that stay high long after go-live. The assumption is that saturation is detectable when it occurs, and that practitioners will notice it in time to respond.

The problem is that saturation often builds slowly, through the accumulation of changes none of which individually seems overwhelming. By the time the symptoms are visible, the capacity depletion has already occurred and the immediate change is already in trouble.

Managing multiple changes effectively requires measuring cumulative load before saturation becomes visible. This means tracking what is landing on specific employee groups across the full portfolio, quantifying the aggregate impact, and identifying when load is approaching or exceeding historical absorption capacity. This cannot be done by observing individual programmes in isolation. It requires portfolio-level data.

Assumption 3: Communications from different programmes can be managed separately

In organisations running multiple concurrent programmes, each programme typically has its own communications plan, its own channels, and its own messaging cadence. The assumption is that employees can contextualise each communication separately and engage with it on its own terms.

In practice, employees receive communications from multiple change initiatives, often in the same week or the same day. The communications compete for attention. Employees develop filters, often unconsciously, that route change communications directly to low-priority status. The most sophisticated change communication strategy for any individual programme has to work within this noise environment.

Effective management of multiple changes requires cross-programme communication coordination: understanding what employees in specific groups are receiving from all programmes simultaneously, and designing communications that acknowledge the full change context rather than pretending each change exists in isolation. An employee who has received three change communications this week does not need a fourth that opens with “we are excited to announce.” They need a communication that is specific, brief, and gives them exactly what they need to act.

Assumption 4: Training is the primary adoption lever

The allocation of change budget in most programmes is disproportionately weighted toward training design and delivery. This reflects an implicit assumption that knowledge is the primary barrier to adoption: if employees understand the new system or process, they will use it.

Knowledge is necessary but not sufficient. The research on adoption failure consistently finds that employees who have completed training and understand the new way of working often do not adopt it. The barriers are motivational, structural, and environmental, not informational. They include:

• Performance frameworks that still measure old behaviours
• Line managers who are themselves uncertain about the change and cannot credibly reinforce it
• Peer norms that make the old way of working the default
• Practical friction in the new process that makes old habits easier

When managing multiple changes, this assumption is compounded because training resources are frequently the binding constraint. Programmes compete for training developer time, LMS bandwidth, and employee training hours. If training is over-weighted as an adoption lever, the resource allocation is wrong in two ways: too much investment in content development, and not enough in manager enablement, environment redesign, and performance alignment.

Assumption 5: Resistance means the change is wrong

When a change encounters significant resistance, the instinctive response is to investigate what is wrong with the change: Is the design flawed? Is the business case unclear? Are sponsors not visible enough? These are legitimate questions. But in a portfolio context, resistance is frequently not a signal about the specific change. It is a signal about cumulative load.

A team that has been through three restructures and two major system implementations in 18 months may resist a relatively modest change with intensity that is disproportionate to the change’s actual impact on their work. The resistance is real and needs to be addressed, but diagnosing it as a problem specific to the current programme leads to misguided responses: more communication, more engagement sessions, more executive visibility. What the team may actually need is a genuine pause in change load, or meaningful acknowledgement of the cumulative burden they have been carrying.

This distinction matters for how change managers advise programme sponsors. When resistance patterns look inconsistent with the scale of the change, the right question is: what is the change history for this group, and what is the current portfolio load they are carrying?

Assumption 6: The sponsor of each programme is the right governance mechanism

In single-programme change management, executive sponsorship is consistently identified as one of the strongest predictors of change success. The programme sponsor provides visibility, resources, decision-making authority, and legitimacy for the change effort.

In a portfolio context, individual programme sponsorship is necessary but not sufficient. Each programme has a sponsor who is rationally motivated to advocate for their programme’s priority. The result is a governance dynamic where each sponsor argues for their programme to go first, receive the most resource, and face the fewest constraints on timeline. Without a portfolio governance mechanism that can make cross-programme trade-offs, these competing claims default to whoever has the most political capital. This is not portfolio management; it is portfolio politics.

Effective management of multiple changes requires a governance structure that sits above the individual programme sponsor level and has the authority to make sequencing and resource allocation decisions that may disadvantage individual programmes in service of better portfolio outcomes. This structure is often a change portfolio board or a change steering committee with cross-programme scope.

Assumption 7: Progress reporting from multiple programmes gives a complete picture

Most organisations aggregate progress reporting from individual programmes into a portfolio status report: traffic lights, milestone tracking, issue logs. This gives a picture of delivery status. What it does not give is a picture of adoption status across the portfolio, cumulative change load by employee group, or the interaction effects between programmes.

A portfolio where every programme is green from a delivery perspective can still be in serious trouble from a change management perspective, if multiple programmes are delivering simultaneously to the same groups, if adoption rates across programmes are uniformly low, or if change fatigue signals are accumulating in the engagement data.

The Change Compass is designed specifically to provide the portfolio-level view that standard project reporting cannot: cumulative impact by business unit and role group, adoption trend lines across multiple initiatives, and early warning signals when load or adoption patterns indicate portfolio risk. The shift from delivery reporting to adoption intelligence is the most significant operational change in how effective change portfolio management differs from traditional programme reporting.

What managing multiple changes well actually looks like

Effective management of multiple changes is defined less by any single practice and more by a shift in orientation: from programme-centric to portfolio-centric. It asks different questions.

Not “is this programme on track?” but “what is the cumulative change load on the groups this programme targets, and how does this programme’s go-live affect their absorption capacity?”

Not “why is this group resistant?” but “what is the change history and current portfolio load for this group, and is the resistance a programme signal or a portfolio signal?”

Not “how do we communicate this change effectively?” but “how does our communication for this programme fit into the total communications these employees are receiving from all sources this month?”

These questions require portfolio visibility. They cannot be answered with programme-level data. And the answers they generate drive meaningfully better decisions about sequencing, timing, resourcing, and intervention design.

Building that portfolio visibility, through consistent impact methodology, aggregated data across programmes, and regular portfolio governance, is the single most valuable investment that enterprise change functions can make in improving their outcomes from managing multiple changes.

Frequently asked questions

Why is managing multiple changes harder than managing individual changes?

Managing multiple simultaneous changes introduces portfolio-level problems that do not exist at the programme level: change collision (multiple demands landing simultaneously on the same groups), change saturation (cumulative load depleting absorption capacity over time), and cross-programme communication noise. Each of these requires portfolio-level management, not just better single-programme execution.

What is change collision?

Change collision occurs when two or more initiatives simultaneously require significant behavioural or process changes from the same employee group, without coordination of timing or support. The demands compete for attention, reinforce each other’s resistance, and result in lower adoption for both initiatives than would have been achieved if they had been sequenced or staggered.

How do you measure the change load on an employee group?

Change load is measured by aggregating the impact assessments from all active initiatives affecting a specific employee group. This requires a consistent impact taxonomy across programmes so that impact severity can be summed and compared meaningfully. High-load groups are those where the cumulative impact score exceeds historical absorption benchmarks for similar periods of change.

What is the right governance structure for managing multiple changes?

Effective governance requires a cross-programme body, typically a change portfolio board or steering committee, with authority to make sequencing and resource allocation decisions across the portfolio. Individual programme sponsors should sit below this level for portfolio decisions. The portfolio body needs consistent data on cumulative load, adoption status, and portfolio risks to make informed decisions.

How should I prioritise changes in a portfolio?

Prioritisation should be based on three factors: strategic importance (which changes are most critical to the organisation’s strategy), adoption readiness (which employee groups have the capacity and readiness to absorb which changes at this time), and interaction effects (which sequencing minimises collision between high-impact initiatives). Data from a portfolio management platform enables all three factors to be assessed systematically rather than through negotiation alone.

What tools help with managing multiple changes?

Portfolio change management platforms such as The Change Compass aggregate impact data across programmes, visualise cumulative load by business unit and role group, and enable the portfolio governance conversations that managing multiple changes well requires. Without this kind of tooling, portfolio management at scale defaults to manual aggregation and informal coordination, neither of which is reliable at the complexity levels most large organisations face.

References

• Gartner. Gartner HR Research Finds Just 32% of Business Leaders Report Achieving Healthy Change Adoption by Employees (2025). https://www.gartner.com/en/newsroom/press-releases/2025-07-08-gartner-hr-research-finds-just-32-percent-of-business-leaders-report-achieving-healthy-change-adoption-by-employees
• Smartsheet. 2025 Project and Portfolio Management Priorities Report: Teams Are Fatigued, and Executives Need to Pay Attention. https://www.smartsheet.com/content-center/inside-smartsheet/research/2025-ppm-priorities-report-key-takeaways
• WTW. Future-Proofing Work: Key Drivers and Strategies for Work Transformation (2024). https://www.wtwco.com/en-us/insights/2024/09/future-proofing-work-key-drivers-and-strategies-for-work-transformation
• Prosci. The Correlation Between Change Management and Project Success. https://www.prosci.com/blog/the-correlation-between-change-management-and-project-success
• OCM Solution. 2025-2026 Organizational Change Management Trends Report. https://www.ocmsolution.com/organizational-change-management-ocm-trends-report/