On this page
Large enterprise organizations are introducing AI tools, replacing core systems and changing operating models while their teams continue to serve customers. These efforts often need the same managers and specialists to redesign processes, test systems and train colleagues. Approving each program separately makes it easy to miss how much work the organization is asking those people to absorb.
The consequence is more than a crowded calendar. A team that cannot keep up may continue using an old process after a new system launches, or meet a transformation deadline by allowing service quality to deteriorate. Leaders then have to decide whether the problem calls for better support, a different schedule or a change in priorities. Treating each of these as employee resistance obscures that decision.
Recent research makes this distinction particularly relevant. In its November 2026 workforce-risk announcement, Gartner reported that 68% of surveyed CHROs said more than 10% of their organization's leaders were misaligned on business strategy or transformation. It also highlighted the cumulative effect of continuous change on employees. The management response needs to address both: the demands leaders approve and the practical support people need to meet them.
Leadership agreement has to reach operating decisions
A leadership team can agree on a transformation's purpose while disagreeing about what takes priority during implementation. The disagreement becomes visible when managers must release experienced staff for testing, accept lower output during training or retire a process that still supports a functional target.
A shared presentation does little to resolve these choices. If a sponsor asks for rapid adoption while a functional leader insists on unchanged output with unchanged staffing, the local manager has to reconcile the conflict. People may support the transformation and still conclude that following the existing process is the safest way to meet their targets.
Leadership alignment therefore needs a more demanding test than agreement with the business case. Sponsors and operating leaders need a common understanding of the temporary disruption they will accept, the work they will defer and the measures that will change during the transition. Where they disagree, the executive team needs to settle the tradeoff before passing it down.
Some commitments cannot move. Regulatory deadlines and customer obligations constrain the choices available. Making those constraints explicit gives leaders a basis for deciding which discretionary work must wait.
The relevant workload is the team's combined workload
Project plans usually describe the resources needed to deliver a change. They need a corresponding account of the effort required to adopt it.
Those are different demands. A system team may have enough developers to meet its launch date while the finance team lacks time to validate migrated data or rehearse the close. Adding delivery resources does not necessarily resolve the adoption problem.
A useful portfolio review therefore looks across programs at the teams whose work will change. For the next few months, leaders need to see when those teams face testing, training, process redesign and periods of parallel running. Operational peaks belong in the same discussion. An annual planning cycle or seasonal increase in customer demand can make an otherwise reasonable rollout date impractical.
This need not become a precise numerical score for change capacity. Estimates will be imperfect. The purpose is to expose specific conflicts early enough to make a choice. If several programs require the same specialists in the same month, their sponsors need to agree on sequencing or fund credible cover. Leaving each program to negotiate separately invites repeated escalation and unreliable commitments.
One finance team, three programs, four months
An illustrative example of the view a portfolio review needs: the adoption work each program asks of the same team, set against that team's own operating peak.
| Demand on the finance team | Month 1 | Month 2 | Month 3 | Month 4 |
|---|---|---|---|---|
| ERP replacement | Validate migrated data | Rehearse the close | Parallel running | Parallel running |
| AI forecasting tool | Testing | Training | ||
| Operating model change | Process redesign | New roles start | ||
| Business as usual | Month-end | Month-end | Quarter-end close | Month-end |
| Changes landing at once | 1 | 2 | 3 + peak | 2 |
What the review decides: each program's plan looks reasonable on its own. Month 3 is where the sponsors need to agree a new sequence or fund credible cover.
For further reading on this subject see Accuracy vs Precision: Rethinking Resource Capacity Planning.
Different problems require different support
Coordination does not remove the need for good change management. It makes that work more useful by distinguishing a shortage of time from a shortage of knowledge, confidence or clarity.
BCG's Personalizing Change Management at Scale, published in November 2026, argues that employee groups need different forms of support according to their roles and circumstances. That is a useful starting point. A manager explaining changed responsibilities faces a different task from a specialist learning a new system.
The distinction also limits what personalization can achieve. More relevant training addresses a skills gap. It does not create time to attend the training. Clearer communications explain a decision, but cannot reconcile two executives giving incompatible instructions.
Employee feedback needs to inform the diagnosis before leaders choose a response. Reports of duplicate data entry point toward unfinished process or system work. Confusion about responsibilities calls for an operating decision. Difficulty completing unfamiliar tasks suggests a need for practice and accessible support. Labeling these concerns as resistance groups together problems that require different remedies.
Match the response to the problem behind the complaint
Why it matters: tailored training only fixes the last row. Calling all four "resistance" sends every problem to the change team.
For further reading on this subject see How to overcome resistance to change in enterprise organizations.
Completion includes withdrawing the old work
Long transformations create a particular burden when organizations introduce new requirements without removing the old ones. Parallel reporting or duplicate approvals may be justified during a transition. Without an agreed end, they become continuing operating costs.
Sponsors need to make retirement of old processes part of the transformation plan, with conditions that operating leaders can verify. Successful adoption then includes the removal of work, rather than only the introduction of a new tool or procedure.
The next portfolio review can begin with the teams facing the heaviest combination of changes. Their managers need to explain which demands conflict and what prevents the old work from ending. Executives can then change the sequence or provide the support required. That produces a more credible transformation plan because the people expected to adopt it have a workable way to do so.







