When two organisations merge, the deal team models one balance sheet, one synergy target, and one integration timeline. What the frontline actually inherits is two of everything: two sets of in-flight projects, two rollout calendars, two waves of system replacements, and two lists of “priority” initiatives that were already stretching people thin before anyone signed. The change that goes wrong after a deal is rarely a single badly run project. It is the collision of two change portfolios that nobody was holding in a combined view until integration was already underway.
This matters right now because dealmaking has not slowed. Companies spend trillions of dollars on acquisitions every year, and those integrations land on workforces across North America, Europe and Asia Pacific alike, all of them asked to keep the business running while they absorb someone else’s operating model. The pattern is global, and no market is exempt: PwC’s M&A outlook for Australia, for instance, describes resilient deal activity and rising inbound acquisition, the same dynamic playing out in dozens of other markets. Wherever the deal is signed, the strategy work gets the attention. The change work, done well, is what determines whether the synergies survive contact with the workforce.
This article is about a specific failure mode in change management for mergers and acquisitions: the doubling of change load across two organisations, and the practices that stop it from doubling the risk. It is not a generic post-merger integration overview, and it is not about restructuring and redundancy. It is about combining two live change portfolios so the value in the deal is not quietly eroded by disruption in the first year.
The failure nobody owns: Two change portfolios, one frontline
The headline statistic on mergers is grim and durable. Harvard Business Review’s New M&A Playbook put the failure rate at between 70 and 90 per cent, a range that has held across decades of research even as deal structuring has become more sophisticated. The reasons are less about price than most executives assume. McKinsey’s work on organisational culture in mergers finds that organisational issues, cultural differences and clashing operating models account on average for almost half of the shortfall between what a merger promised and what it delivered.
Sit with that. Half the value gap is people and organisation, not finance. And yet the accountability for that half is usually the most diffuse in the whole deal. The strategy team owns the thesis. The finance team owns synergies. Legal owns the close. But the question of what happens when both organisations’ change agendas land on the same people, in the same weeks, has no clear owner until the integration management office is stood up, which is often too late to prevent the first wave of disruption.
Why the deal model misses it
Diligence is built to find risk in the target: contracts, liabilities, customer concentration, systems. It is not built to find the interaction risk between the two organisations’ change workloads. A target might look perfectly healthy on its own, with a manageable set of initiatives and a workforce that is coping. The acquirer might look the same. The risk only becomes visible when you overlay the two calendars and see that the acquirer’s finance system migration hits the same quarter as the target’s restructure, on teams that are about to be merged and re-badged.
This is the same class of problem covered in our guide to change conflict detection, but with a sharper edge. In a single organisation, initiative clashes are hard enough to spot. In a merger, you are trying to detect clashes across two organisations that have never shared a planning system, a taxonomy, or a governance forum, and that may still be legally prohibited from sharing detailed operational data before close.
The doubling-the-risk trap
Here is the trap that gives this article its title. Leaders instinctively assume that combining two organisations combines two change agendas additively: portfolio A plus portfolio B. In practice the risk is not additive, it is multiplicative, because the two portfolios compound on a workforce whose capacity to absorb change is already under strain.
The evidence on that strain is stark. Gartner research reported in Harvard Business Review found that the proportion of employees willing to support enterprise change fell from 74 per cent in 2016 to just 43 per cent in 2022, while the average worker went from experiencing two major planned changes a year to ten. Change fatigue at those levels cuts an employee’s intent to stay by as much as 42 per cent and their performance by as much as 27 per cent. Now drop a merger on top of a workforce already at those numbers, and add a second organisation’s worth of change on top of that. The two portfolios do not just add up. They tip people over a threshold where adoption stalls, attrition rises, and the operational performance the deal was supposed to improve goes backwards.
Map the change landscape of both organisations before day one
You cannot manage a combined change load you have never measured. The first discipline of good change management for mergers and acquisitions is to build a shared, honest picture of what change is already live in both organisations, and when it peaks, before the two calendars collide.
Build a combined change portfolio view
The practical task is to construct a single view that lists every material initiative in both organisations, mapped to the business areas, functions and frontline teams each one touches. This is deliberately broader than the deal’s own integration workstreams. It has to include the “business as usual” change that will keep running regardless of the merger: the system upgrade the target had already committed to, the operating model refresh the acquirer started last year, the regulatory change both are subject to.
Getting this view is harder in a merger than in a single organisation because the two sides start with different taxonomies and, often, no dedicated tooling at all. A shared method for describing initiatives, impacts and affected populations is what makes the two portfolios comparable. Our buyer’s guide to change portfolio management tools walks through what separates a genuine portfolio view from a project tracker, which matters here because a merger is exactly the moment a spreadsheet stops coping.
A workable combined view captures, for every initiative:
The functions and frontline teams affected, in both organisations
The go-live or peak-activity window
The size and nature of the behaviour change required
Which initiative “owns” a team’s attention in any given month
Whether the initiative continues, pauses, merges or stops as a result of the deal
Find the peak work volume periods that will collide
The single most useful output of the combined view is a timeline of peak work volume periods across both organisations. Change does not land evenly. It clusters around go-lives, end-of-financial-year, peak trading, regulatory deadlines and reporting cycles. When you overlay both organisations’ peaks, you will almost always find months where two or three heavy initiatives are scheduled to hit the same soon-to-be-merged team at once.
Those collision points are where the risk doubles, and they are also where you have the most leverage. Resequencing one initiative by six weeks, or holding a non-urgent rollout until after a peak trading period, costs almost nothing compared to the productivity and attrition cost of pushing a fatigued team past its limit. This is the merger-specific application of measuring change saturation: you are looking for the weeks where combined saturation crosses the threshold, and treating those as hard planning constraints rather than problems to be discovered after the fact. Pair that with a proper change readiness assessment of the acquired teams, measured with data rather than sentiment, and you have an evidence base for sequencing that a steering committee can actually act on.
Engage the acquired organisation’s leaders, not just its executives
Most integration communication plans are built around executives. The chief executive of the acquired business is retained or farewelled, the top team is confirmed, and a cascade is assumed. The assumption is where it breaks. The people who determine whether change actually lands are the senior and middle managers of the acquired organisation, and they are routinely under-engaged during the exact period when their influence matters most.
Middle managers are the load-bearing layer of any integration. They translate the deal narrative into what it means for a specific team, they hold the relationships that keep good people from leaving, and they absorb the ambiguity that would otherwise flow straight to the frontline. In a merger they are also the most exposed: uncertain about their own roles, asked to reassure teams they cannot yet give answers to, and often the last to be briefed. Engaging them properly is not a courtesy, it is risk management.
Doing it well means treating the acquired organisation’s managers as partners in the integration rather than recipients of it. In practice that means:
Briefing senior and middle managers before, not after, their teams hear news that affects them
Giving managers the context and language to answer the questions they will be asked, including permission to say “we don’t know yet”
Involving acquired-side managers in the design of changes that affect their teams, not just the delivery
Naming which managers own which parts of the integration on their side, so accountability is not all on the acquirer
Protecting a portion of their time, because a manager cannot lead their team through change while also running the business at full capacity and sitting on integration workstreams
The organisations that get this right treat retention of the acquired middle layer as a leading indicator. If capable managers on the target side start leaving in the first six months, the deal is in trouble regardless of what the synergy tracker says.
Build the integration playbook before day one, not after
The strongest predictor of a controlled integration is that the playbook existed before close. Both Bain and Deloitte are emphatic on this point: integration planning should start during diligence, and day one should be treated as a readiness milestone reached through structured preparation, not a starting gun. As Bain frames it in its ten steps to successful M&A integration, day one is not the day you transform the company, it is the day you prove control. The best day one is uneventful: nothing breaks, no customer is surprised, and the organisation feels leadership is in command.
Reaching that requires a structured integration playbook owned by a body with authority and representation from both sides. Bain’s model of a dedicated integration management office, running to a weekly rhythm with a value tree, a KPI pack, an issue log and a risk heat map, is the mechanism. For the change dimension specifically, the equivalent is an integration committee with functional representatives from both organisations, so that every material function, HR, technology, operations, finance, customer, has a named owner on each side who is accountable for the change in their area.
A change-focused integration playbook, ready well before day one, should include:
The combined portfolio and saturation view, with collision points flagged and a resequencing plan for the worst of them
A day-one readiness checklist per function, defining what “in control” means in concrete, testable terms
A 30, 60 and 90 day plan that tracks adoption and disruption, not just task completion
A decision log and escalation path, so cross-organisation clashes are resolved at the committee rather than fought out on the frontline
A clear scope of what continues, pauses, merges or stops on day one, agreed by both sides in advance
Owned communication and feedback rhythms (covered in the next section) built into the calendar from the start
The committee structure matters as much as the document. A playbook written entirely by the acquirer, imposed on the target, recreates the cultural clash that McKinsey identifies as a leading cause of failure. Functional representatives from both sides give the plan legitimacy and surface the operational realities that an outside acquirer simply cannot see.
Keep the feedback loop open: Town halls, briefings, and honest updates
A playbook built before day one is a hypothesis. What makes it survive contact with reality is a proactive feedback mechanism that runs continuously through the integration, so that the plan adjusts to what is actually happening rather than what was assumed months earlier.
The instinct in a merger is to control information tightly and communicate in set-piece announcements. That instinct is understandable and, past the legal necessities of the close, actively harmful. In an information vacuum people assume the worst, and the best people, the ones with options, leave first. The antidote is a predictable, two-way rhythm of engagement that treats employees as adults who can handle uncertainty better than silence.
That rhythm should be designed, not improvised, and it should run on a known cadence so people know when the next update is coming even if the answer is “no change yet”. A practical feedback and engagement structure looks like:
Regular all-hands town halls on a fixed schedule, mixing genuine updates with unscripted question time, and repeated across time zones so distributed and remote teams in every region are not an afterthought
Functional briefing sessions run by the integration committee representatives, translating the enterprise message into what it means for each team
Manager cascades with supporting material, so the acquired organisation’s managers can brief their own people first-hand
Lightweight pulse checks that measure sentiment, confidence and perceived workload frequently enough to catch problems while they are still small
A visible feedback loop, where the organisation shows what it heard and what it changed in response, because feedback that disappears trains people to stop giving it
The purpose of all of this is not communication for its own sake. It is early warning. A middle manager voicing frustration in a briefing, or a pulse check showing confidence dropping in one integrated business unit, is a signal to act before disruption shows up in operational metrics. Minimising disruption is a function of how fast you notice and respond, and that speed depends entirely on keeping the feedback channel open and trusted.
Track cultural change through behaviours, not values statements
Culture is the part of integration that executives say matters most and measure least. McKinsey found that 95 per cent of executives describe cultural fit as critical to integration success, while a quarter cite the lack of cultural cohesion as the primary reason integration efforts fail. The gap between how important culture is and how rigorously it is managed is where a great many deals quietly come apart.
The reason culture is so often mismanaged in mergers is that it gets treated as an abstraction, a matter of values posters and all-hands slogans, rather than as observable behaviour. You cannot track “we value collaboration”. You can track whether decisions that used to require three approvals now require one, whether cross-organisation teams are actually meeting, or whether the acquired organisation’s people are still being cc’d out of decisions six months in.
The discipline is to define the small number of behaviours and ways of working that the combined organisation genuinely needs, and then measure whether they are showing up. Focus on the vital few, not an exhaustive culture map. A workable approach to assessing and tracking cultural change:
Name the top behaviours the integrated organisation depends on, ideally five or fewer, stated as concrete actions rather than values
Baseline them early, in both organisations, so you know where each side is starting from and where the real gaps are
Track them at intervals, using a mix of pulse data, observable indicators and manager assessment, on the same cadence as the rest of the integration
Feed the results back into the integration committee, so culture is a standing agenda item with an owner, not a survey that gets filed
Act on the outliers, where one business unit or function is clearly diverging, before divergence hardens into a permanent us-and-them split
Behaviour-based cultural tracking also gives you an honest read on whether the engagement, feedback and playbook work described above is landing. If the target behaviours are not shifting, no amount of positive town-hall sentiment means the integration is working.
How digital change tools support the combined view
Everything above depends on holding two organisations’ change activity in a single, current picture, and keeping it visible to the people making sequencing and engagement decisions. That is difficult to sustain in spreadsheets, and it is precisely difficult at the moment a merger creates the most complexity. A digital change management platform such as Change Compass is built to hold a combined portfolio view, surface saturation and collision points across business units, and give an integration committee a shared, data-based source of truth rather than two competing versions of reality. The tooling does not replace the disciplines in this article, but it makes them practical to run at merger scale and speed.
Where the risk actually compounds
The through-line of change management for mergers and acquisitions is that the danger is not in either organisation’s change agenda on its own. It is in the combination: two portfolios landing on shared teams, at overlapping peaks, on a workforce whose tolerance for change is already low. Deals fail on that compounding far more often than they fail on price.
The organisations that beat the odds do the unglamorous work early. They build a combined view of both change landscapes before day one. They engage the acquired organisation’s senior and middle managers as partners, not audiences. They stand up an integration committee with representation from both sides and a playbook ready before close. They keep a proactive feedback loop running through the whole integration. And they track culture as behaviour, not sentiment. None of it is exotic. All of it is easier to skip than to do, which is exactly why so few do it, and why the ones who do capture the value everyone else leaves on the table. Start with the combined view. You cannot align two portfolios you have never seen side by side.
Frequently asked questions
What is change management in mergers and acquisitions?
Change management for mergers and acquisitions is the practice of guiding people, behaviours and change workload through the integration of two organisations so the deal’s value is realised rather than eroded by disruption. It focuses on combining two live change portfolios, engaging both organisations’ leaders, and managing the cumulative load on shared teams, which is distinct from the strategy and financial work of the deal itself.
Why do most mergers and acquisitions fail?
Research summarised by Harvard Business Review puts the M&A failure rate at 70 to 90 per cent, and McKinsey attributes almost half of the gap between expected and realised value to organisational issues such as culture, operating-model clashes and poor integration. Price and diligence matter, but the people and change dimension is where most deals underdeliver.
When should change management start in an M&A deal?
It should start during diligence, well before legal close. Integration specialists including Bain and Deloitte treat day one as a readiness milestone reached through structured pre-close preparation, not a starting point. Building the combined change portfolio view and the integration playbook before day one is the strongest predictor of a controlled integration.
How do you manage change fatigue during a merger?
Map the peak work volume periods across both organisations, identify where initiatives collide on shared teams, and resequence or pause non-urgent changes at those collision points. Because employee willingness to support change has fallen sharply and the average worker already faces around ten major changes a year, treating combined saturation thresholds as hard planning constraints is essential to keeping teams functioning.
How do you measure cultural integration after a merger?
Define the small number of behaviours and ways of working the combined organisation needs, baseline them in both organisations early, and track them at regular intervals using pulse data, observable indicators and manager assessment. Measuring specific behaviours rather than abstract values gives an honest read on whether the two cultures are genuinely converging.
References
Christensen, C. et al., The Big Idea: The New M&A Playbook, Harvard Business Review, 2011 (seminal source for the 70-90% failure range, still widely cited)
From late 2025, several of the world’s largest banks quietly cut their junior analyst intake by up to two-thirds while accelerating AI across their operations. In the UK, the major professional services firms pared back graduate hiring, and across the US economy, postings for entry-level roles fell by around 35% between early 2023 and mid-2025, a decline CNBC reports is driven in large part by AI. The people most exposed were not the seasoned experts. They were the juniors doing the drafting, the data cleaning, and the first-pass analysis.
Change management is not immune to this pattern, and pretending otherwise helps no one. A large share of what change practitioners do day to day, drafting communications, building training content, assembling stakeholder lists, summarising feedback, is exactly the kind of structured, language-heavy work that generative AI now does in seconds. The uncomfortable question for the profession is not whether AI will change the job. It is which practitioners remain valuable once the routine layer is automated, and what they need to become. This article sets out the specific capabilities that will define the future of change management in the AI era, and why the practitioners who develop them will be the ones organisations still fight to keep.
The work AI is genuinely absorbing
Let us be honest about where the automation is real rather than hypothetical. The bulk of comms and training production, the volume work that has historically filled a change practitioner’s week, is now well within the capability of general-purpose AI tools.
Ask a competent model to draft a go-live email, a manager talking-points pack, a set of FAQs, a quick-reference guide, or a first-cut training module outline, and it will produce something serviceable almost instantly. It will match a tone, respect a word limit, and generate five variations on request. For the mechanical, high-volume end of change communications and enablement, the productivity gain is not marginal. It is the difference between a day of work and a coffee break.
This matters because comms and training have long been the visible, billable, staffable core of change delivery. When that core compresses, the roles built around producing it compress too. McKinsey’s State of AI research found that around 65% of organisations were already regularly using generative AI, with marketing, sales, and content-heavy functions among the earliest adopters. Change teams sit squarely in that content-heavy category.
The tasks most exposed to automation tend to share a few features:
High volume and repetition, such as producing the same artefact for many audiences with small variations
A clear, well-understood output format, such as an email, an FAQ, or a slide narrative
Low dependence on organisation-specific context that is not written down anywhere
Language generation rather than judgement as the core activity
If a large part of your value is producing that kind of output faster than the next person, AI has already caught up. The practitioners who treated speed of production as their edge are the ones most at risk. The good news is that production was never the hard part of change. Knowing what is worth producing, and whether the output is actually right, always was.
Why judgement becomes the scarcest skill in change management in the AI era
Here is the shift that most commentary misses. AI does not remove the need for expertise. It relocates it. When a machine produces a plausible first draft in seconds, the scarce, valuable skill is no longer generation. It is critical evaluation: the ability to look at confident, well-formatted output and know, quickly, what is wrong with it.
The World Economic Forum’s Future of Jobs Report 2025 makes this concrete. Even as AI and big data top the list of fastest-growing skills, analytical thinking remains the single most sought-after core skill among employers, cited as essential by seven in ten companies. The tools change. The demand for people who can think critically about what the tools produce grows rather than shrinks.
The 80/20 problem no one flags
The most dangerous property of AI-generated change content is not that it is wrong. It is that it is mostly right. A generic AI change plan is typically around 80% sound, because it draws on widely accepted best practice, and around 20% wrong for your specific organisation. The problem is that the wrong 20% does not announce itself. It sits inside a credible, professional-looking document, and the surrounding 80% creates a halo that carries the whole thing through governance unchallenged.
Consider the failure modes an experienced practitioner learns to smell:
A sequencing recommendation that ignores the fact two of these initiatives hit the same frontline team in the same fortnight
An impact rating pitched at “medium” when local history says this exact team has already absorbed three system changes this year
A sponsor assumption that names the wrong leader as the credible voice for a sceptical audience
A training cadence that looks textbook but collides with the operational peak for that division
A channel mix optimised for an office workforce when half the audience works in the field
None of these errors are visible to someone reading the document cold. They are only visible to someone with the experience to know what the right answer looks like for this organisation. This is a different failure mode from a hallucination, which at least tends to look odd. This is the invisible 20%, and catching it is now the job. The practitioners who can reliably separate the sound 80% from the flawed 20% are worth more in the AI era, not less. For a deeper treatment of why organisation-specific data is what catches these errors at the point of recommendation, our article on why generic AI tools fall short of a change intelligence platform works through the data infrastructure behind it.
Spotting the generic approach
There is a second, related discipline: recognising when an approach is technically defensible but strategically hollow. AI is trained on the average of everything published about change management, which means it reliably produces the average approach. It will recommend a stakeholder matrix, a comms calendar, a training needs analysis, and a resistance-management plan, because that is what the literature says. All of it is generic best practice. Some of it will be exactly what your situation does not need.
An experienced practitioner reads a proposed approach and asks harder questions. Does this organisation actually have a resistance problem, or an attention problem? Is the real risk adoption, or is it capacity? Is a full training programme the right response, or is the change small enough that a well-designed job aid would land better and cost a fraction as much? This is the eye for detail that separates a change professional from a change administrator, and it is precisely the layer AI cannot supply, because it does not know which 20% of the standard playbook is wrong for you. The same experienced eye is what catches the initiative clashes that AI misses when it plans one change without seeing the rest of the portfolio.
The research backs the caution. The Harvard Business School and BCG study Navigating the Jagged Technological Frontier, which tested 758 consultants on realistic tasks, found that AI sharply improved performance on tasks inside its capability frontier, lifting quality by around 40%, but actively degraded performance on tasks that fell outside that frontier. The people who did best were not those who used AI most. They were those who knew which tasks to trust it with and which to override. That discernment is the skill.
The practitioner as data engineer
If judgement is the first pillar of the future practitioner, data fluency is the second, and it is the one the profession is least prepared for.
Here is the principle that will quietly separate high performers from everyone else: the right data structure is the true enabler of AI, not the model itself. The quality, accuracy, relevance, and precision of what AI produces is a direct function of what you feed it. The more you plug the right, well-structured organisational data into AI, the more accurate and specific the outputs become. Feed it thin, messy, or generic inputs, and you get thin, messy, or generic outputs dressed up in confident language. This is the “garbage in, garbage out” law, and it has not been repealed by better models.
The scale of the underlying problem is large. Salesforce’s State of Data and Analytics research, drawing on more than 10,000 leaders, found that data and analytics leaders estimate over a quarter of their organisational data is untrustworthy, and that 42% lack full confidence in the accuracy and relevance of their AI outputs. If the people closest to the data do not trust it, the change practitioner casually pasting a prompt into a chatbot has no reason to trust what comes back.
What data-savvy actually means now
Being data-savvy in change management is no longer about being comfortable with a spreadsheet. It is a genuine, if lightweight, engineering mindset. In practice it means being able to:
Troubleshoot AI mistakes by tracing a wrong output back to the input that caused it, rather than accepting or rejecting the answer wholesale
Identify and fix data errors, such as duplicated stakeholder records, inconsistent initiative names, mislabelled impact severities, or dates in three different formats
Prepare and structure data channels that feed AI, so that impact data, stakeholder data, and change calendar data are captured consistently enough to be usable
Understand how AI actually uses data, including why a model that has no record of your change calendar cannot possibly warn you about a saturation clash
This last point deserves emphasis. Much of what makes change advice valuable, the awareness that a team is already carrying too much, comes from data most organisations never capture in a structured form. If your change impact and capacity information lives in a hundred disconnected slide decks, no AI can reason about it. The practitioner who understands this, and who takes responsibility for building clean, structured data channels, becomes the person who makes AI useful rather than the person disappointed by it. Our guide to tracking change load across multiple initiatives shows what that structured capture looks like in practice.
A data-readiness checklist
Before trusting AI with anything consequential, an AI-era practitioner runs a quick mental audit of the inputs:
Is the data current, or am I feeding the model a snapshot from six months ago?
Is it consistent, using the same names, categories, and severity scales across sources?
Is it complete enough for the question, or is the model filling gaps with generic assumptions?
Is it specific to this organisation, or am I effectively asking for the industry average?
Can I trace any given output back to a source I can check?
Practitioners who cannot answer these questions are not using AI. They are gambling with it.
The benchstrength problem: A slow-burning risk for the profession
The fifth shift is the one the profession is not talking about, and it is the most strategically serious. It mirrors what is happening inside organisations more broadly.
Inside companies, AI is reducing the need for analysts and junior roles, because the model now does the first-pass analysis, the drafting, and the summarising that used to be a junior’s apprenticeship. That looks like an efficiency win in the current quarter. Over a longer horizon it creates a supply problem. Senior practitioners are not born senior. They become senior by spending years doing the junior work: sitting in the room, cleaning the data, drafting the comms, getting the impact assessment wrong and learning why. If AI removes the junior rung, the ladder to experienced practitioner loses its lower steps.
This is the benchstrength issue. The evidence outside change management is already stark, with entry-level postings down around 35% and the traditional apprenticeship path narrowing. The same logic will play out in change functions that decide they can run leaner because AI covers the production layer. The immediate effect is a smaller team. The delayed effect, felt three to five years later, is a shortage of experienced practitioners who came up through that work, because the roles that used to grow them no longer exist.
For the profession, this creates a set of second-order risks worth naming:
A thinning pipeline of practitioners with genuine hands-on experience, as junior roles are automated away
A widening gap between a small group of highly experienced practitioners and a large group who have only ever supervised AI outputs without building underlying judgement
Rising scarcity value, and cost, for the experienced practitioners who can do the evaluation and data work AI cannot
A real question about how the next generation develops the pattern recognition that only comes from repetition, when the repetitive work is gone
There is no clean answer to this yet, and anyone claiming one is overreaching. But individual practitioners can respond to it directly. If experience is becoming scarcer and more valuable, the rational move is to deliberately accumulate the judgement-heavy, data-heavy, strategic experience that AI is making rare, rather than competing on the production work AI is making cheap.
How to future-proof your practice
Pulling the threads together, the practitioner who thrives in the future of change management does not resist AI and does not defer to it. They supervise it, and they move up the value chain to the work it cannot do. Here is a practical agenda for getting there.
Reposition from producer to editor-in-chief. Let AI generate the first draft of comms, training, and assessments. Spend the time you save on evaluating, correcting, and tailoring the output to your specific context. Your value is now in the red pen, not the blank page.
Build a real critical-evaluation habit. For every AI output, actively hunt for the wrong 20% before you accept the right 80%. Ask what this recommendation assumes about your organisation, and whether those assumptions actually hold.
Develop genuine data fluency. Learn how your change data is structured, where it is dirty, and how to clean it. Treat data preparation as core change work, not an IT problem. The practitioner who owns clean data owns the quality of the AI output.
Move towards strategic and advisory work. As production commoditises, the durable value is in advising sponsors, shaping portfolio decisions, navigating politics, and making judgement calls under ambiguity. Deepen the skills that require presence, trust, and organisational read.
Protect your own experience curve. Seek out the hard, judgement-heavy assignments precisely because they are becoming scarce. In a world short on experienced practitioners, being demonstrably one of them is the strongest career position available.
The common thread is that every item moves you away from what AI does well and towards what it structurally cannot do: understand your specific organisation, exercise judgement, and take accountability for a decision.
Where digital change tools fit
Individual skill only goes so far without the right data foundation, and this is where purpose-built digital change tools earn their place. General-purpose AI can only reason about what it can see, and most change context, impact load, capacity, stakeholder saturation, and initiative timing, is never captured in a structured, connected form. A dedicated change platform such as Change Compass exists to solve that input problem: it captures change impact and analyses capacity data consistently across the portfolio, so that both practitioners and any AI layered on top are reasoning from an accurate, organisation-specific picture rather than a generic guess. In an era where the quality of AI output depends entirely on the quality of the data behind it, the structured data layer is not a nice-to-have. It is the enabler.
The shift that matters most
The future of change management in the AI era is not a story about practitioners being replaced. It is a story about the job changing shape. The production layer, the comms and training volume work, is being automated, and the roles built purely on that work will shrink. What grows in its place is demand for judgement: the ability to spot the flawed 20% inside a plausible document, to tell a generic approach from a fitted one, and to build the clean, structured data that makes AI accurate in the first place. The practitioners who lean into critical evaluation, data fluency, and strategic advisory work will not be competing with AI. They will be the reason it produces anything worth acting on. Start by picking one AI output this week and interrogating it properly, not as a user, but as the expert accountable for whether it is right.
Frequently asked questions
Will AI replace change managers?
AI is unlikely to replace skilled change managers, but it is already replacing a large share of the routine production work, such as drafting communications and training content, that many change roles were built around. The practitioners at risk are those whose main value is producing that output quickly. Those who move into critical evaluation, data preparation, and strategic advisory work become more valuable, not less.
What skills do change practitioners need in the AI era?
The three that matter most are critical judgement (spotting what is wrong in confident AI output), data fluency (structuring, cleaning, and troubleshooting the data that feeds AI), and strategic advisory capability (advising sponsors and making judgement calls under ambiguity). The World Economic Forum’s 2025 research confirms that analytical thinking remains the most in-demand core skill even as AI adoption accelerates.
Why does data quality matter so much for AI in change management?
AI output is only as good as its input. If a model is fed thin, inconsistent, or generic data, it produces confident but generic recommendations that miss organisation-specific realities like saturation and capacity. Structured, accurate change data is what allows AI to produce precise, relevant advice rather than textbook averages.
What is the “80/20 problem” with AI change plans?
A generic AI change plan is usually around 80% sound, drawn from accepted best practice, and around 20% wrong for your specific organisation, covering things like sequencing, impact ratings, and sponsor assumptions. The danger is that the wrong 20% is invisible inside a credible document, so it needs an experienced practitioner to catch it before it reaches governance.
Could AI create a shortage of experienced change practitioners?
Potentially, yes. As AI automates the junior, entry-level work that practitioners traditionally used to build experience, the pipeline that produces senior practitioners narrows. Over several years this can create a benchstrength problem, where experienced practitioners become scarce and more valuable precisely because fewer people are coming up through the hands-on work.
Most change teams that ask for “better visibility” already have a dashboard, a heat map, or some version of a portfolio view. The problem showing up in boardroom after boardroom isn’t that the picture doesn’t exist. It’s that the picture reads as FYI rather than as something built to force a decision. A saturation heat map with three shades of amber tells an executive something is elevated. It doesn’t tell them enough to say no to the third overlapping initiative landing in the same quarter. When change data is presented at awareness level instead of decision level, executives don’t see the risk clearly enough to act on it, so they approve the overlap and move on.
This is not a data problem. It is a presentation problem: the wrong level of detail for the decision at hand, data stripped of the business context that would make the risk feel urgent, and a visual that doesn’t match the shape of the risk it’s describing.
Change practitioners are trained to think in stakeholder groups, impact levels, readiness stages and activity counts. Executives are trained to think in risk, cost, timeline and competitive position. Both groups can be looking at the same single view of change and walk away with entirely different conclusions, because the information was never positioned, visualised and detailed in a way that connects to the decision the executive is actually being asked to make. Solving this gap is arguably a bigger lever for change management effectiveness than anything else on the practitioner’s desk right now, and it is almost entirely unaddressed in how change teams are trained or how change management software is designed.
The single view of change paradox: Visibility without influence
There’s a quiet assumption running through most change portfolio initiatives: if leadership could just see everything at once, they’d make better decisions. Build the dashboard. Consolidate the spreadsheets. Get every initiative into one system. Then walk into the steering committee and watch the sequencing conversation finally happen on merit instead of politics.
It rarely plays out that way, and often for a more basic reason than executives assume: most organisations don’t actually have a complete single view of change to begin with. What they usually have is a list of major initiatives sourced from project and portfolio management tools, capturing scope, timeline, budget and delivery status. That’s project planning and execution data. It says almost nothing about the other half of the picture: which teams get hit, how hard, and what it does to day-to-day operational performance while the change is landing. The view executives are shown is frequently a project status report wearing a change hat, built to summarise for awareness rather than force a decision.
Even where a genuine change portfolio view does exist, capturing initiatives, impacted teams and rough timelines, it tends to render that impact data at the level a status update needs, not the level a decision needs. A heat map that shows “elevated saturation” in amber is accurate. It is also, by design, too abstract to force a call. Executives register that something is busy and approve the third initiative anyway, because nothing in what they were shown was precise or consequential enough to make saying no feel necessary.
The most common version of this under-detail problem is a single impact rating for the whole initiative: “this initiative is High impact,” full stop, for its entire life. That one number collapses months of real variation into a single static score. It doesn’t show the peaks and troughs as the initiative moves through design, testing and go-live, it doesn’t show that Finance is barely touched while Operations is hit hard for six straight weeks, and it doesn’t show that impact on the contact centre in March looks nothing like impact on the same team in June. A whole-initiative rating averages away exactly the information a sequencing or saturation decision needs: when the peak lands, and who it lands on. In most contexts, one rating for the whole initiative provides very little useful insight on its own.
The mistake is assuming visibility and influence are the same capability. They are not. Visibility answers “can you see it.” Influence answers “will it change what you decide,” and that depends on whether the data was pitched at FYI level or built to force a specific call. A dashboard earns the first. It does nothing to guarantee the second, and change teams that treat the dashboard itself as the finish line are solving the easier half of the problem.
Two operating languages: How change practitioners think versus how executives decide
The reason a technically excellent single view of change can still fail to move a decision comes down to something more fundamental than dashboard design. Change practitioners and executives are, in a very real sense, running two different operating systems for how they process the same information.
That gap isn’t only vocabulary. It’s four compounding things: the words used, the business context the finding is placed inside (or isn’t), the visualisation chosen, and the level of detail shown for that specific type of risk. Get the words right but skip the business context and the finding still reads as an internal change concern, not a business risk. Get the context right but pick the wrong visual and it still doesn’t register. Vocabulary is the most visible symptom. It is not the whole problem.
How change practitioners think
Change practice has a well-developed internal vocabulary, and for good reason. Frameworks like ADKAR give practitioners a shared way to diagnose where an audience is in the change journey. Stakeholder impact assessments break a change down by group, role and level of disruption. Readiness scores, activity counts and heat maps make an intangible thing, organisational disruption, tangible enough to manage.
This vocabulary is precise, methodologically sound, and almost entirely foreign to how a chief operating officer or chief financial officer reasons about a decision. “Forty per cent of the frontline team is at the ‘awareness’ stage” is a meaningful diagnostic to a change manager. To an executive, it’s an abstraction requiring translation before it connects to anything they’re accountable for.
How executives decide
Executives, particularly at the level where sequencing decisions get made, process a different set of variables: cost, delivery risk, timeline exposure, competitive position, regulatory obligation, and what a board will ask at the next review. They are not resistant to change data. They’re evaluating it against a completely different decision frame, one built around consequence and accountability rather than method and process. This gap shows up constantly in how portfolio conversations get framed to leadership, where spotting a conflict early is often the difference between an initiative that lands cleanly and one that quietly derails delivery three months later.
What the change practitioner says
What the executive hears
“This initiative is in the ‘desire’ stage of ADKAR”
Unclear how this affects delivery
“Twelve stakeholder groups are impacted”
A number without a consequence attached
“Change saturation is elevated this quarter”
A soft warning, easy to override
“Our readiness score is 62 per cent”
Not obviously connected to risk or cost
“This will collide with the ERP rollout”
A concrete, specific, and actionable risk
Notice the pattern in the right-hand column. The items that land are the ones already expressed in terms of consequence: a collision, a risk, a cost. The items that don’t land are expressed in methodology terms that require the executive to do the translation work themselves, and executives in a steering committee meeting are not going to do that work. They will simply move to the next agenda item.
Why the language gap exists (and why it isn’t the practitioner’s fault)
It’s tempting to read the section above as a criticism of change practitioners. It isn’t. Change management has spent two decades building rigour into diagnosis and methodology, largely because that rigour was what the field lacked most. Certifications, frameworks and benchmarking studies have all reinforced a practitioner-facing vocabulary; very little of that same investment has gone into executive and board-level communication, a genuinely different skill from stakeholder analysis.
The research backs this up. Prosci’s Best Practices in Change Management research, now in its 12th edition, consistently finds active sponsorship the single largest contributor to change success, and consistently finds a large share of sponsors don’t understand their own role well enough to fulfil it. McKinsey’s analysis of change journey management found programmes with clearly structured governance, steering committee, change office, named sponsors, succeed at markedly higher rates, and that frequent progress communication matters. But frequency of what matters just as much: a weekly update in practitioner vocabulary doesn’t carry the same weight as one in the language the committee already uses for every other agenda item.
Deloitte’s Global Boardroom Program found two-thirds of board members and C-suite executives rank open, transparent communication the single most important leadership factor in organisational resilience. Change teams sit on some of the richest early-warning data in the organisation. The gap isn’t a lack of communication. It’s communication that hasn’t been converted into the form, and context, the audience is already primed to act on.
Change data needs a business context, not just a decision framing
Even consequence-framed change data can fail to land if it’s presented in isolation from the strategic and operational context executives are already tracking. A collision between two initiatives matters more, and reads as more urgent, when it’s tied explicitly to a named strategic priority the executive is accountable for, or an operational challenge already on their radar (a cost-out programme, a regulatory deadline, a customer-facing service risk), rather than presented as a standalone change-management finding. The more integrated a risk is with the business context the executive already holds in their head, the more attention it earns: “this collides with the Q3 cost-reduction priority the CEO reports to the board on” carries a different weight than the same risk on its own change-management slide.
This is also why change data can be accurate, correctly visualised and correctly worded, and still get waved through. It hasn’t been positioned inside the frame the executive is already using to prioritise everything else competing for their attention.
The cost of getting the translation wrong
The consequences of this gap compound into the next funding conversation, too. Change functions are asked, almost every budget cycle, to justify their existence in terms the finance team understands: cost avoided, delivery protected, adoption secured. A team that has spent the year presenting saturation scores and readiness percentages, without converting them into risk and cost, arrives at that conversation with a weak hand. The near-misses they prevented are invisible, because they were never described in terms anyone outside the practice would remember.
Teams that consistently frame portfolio data as business risk in business context build a track record executives can point to later, exactly the material a strong business case for change management investment is built from. Teams that never make that shift re-litigate their value from scratch every year, regardless of how good their underlying data was.
What earns executive attention: Lead with consequence, not method
If the diagnosis is a translation gap, the fix is not more dashboards or more detail. It’s a deliberate shift in what gets led with.
Lead with consequence, not method
Every piece of change data can be expressed two ways: as a methodology fact, or as a business consequence. “Change saturation is elevated” is a methodology fact. “Two of our highest-priority initiatives land on the same frontline team in the same six-week window, and that combination has historically pushed adoption down and error rates up” is a business consequence. Same underlying data. Completely different weight in the room.
This matters more than it might seem. Research on data storytelling from Harvard Business School has found the impact of a story on an audience’s beliefs holds up far better over time than a raw statistic, whose influence fades fast once the meeting ends. A sequencing recommendation that’s going to still shape a decision a week later needs to be carried by a consequence, not a number.
One chart, one decision, one ask
The second shift is about restraint. A single view of change is built to hold everything, which is exactly why it should never be presented in full to an executive audience. CIO Dive’s coverage of Gartner’s research on data storytelling in the boardroom describes leaders bridging technical detail and business understanding by combining visualisation, narration and context around a single focused message, not the full breadth of what they know.
For a change portfolio conversation, that means picking one chart that answers one question and forces one decision, rather than taking the committee on a guided tour of the dashboard. A saturation heat map that shows exactly where two initiatives collide, with a single clear recommendation underneath it, will do more work than twelve slides of stakeholder breakdowns. The detail should exist and should be available if someone asks. It should not be the opening move.
Match the visual and the detail to the type of risk
Not every risk needs the same visual or the same depth. A single scheduling collision is usually clearest as a simple timeline: two bars overlapping, one week called out. A saturation issue spanning multiple teams over multiple months needs the heat map, because the pattern across teams and time is the point. Use a heat map for a single collision and it’s too abstract for a black-and-white timing problem; use a two-bar timeline for a saturation pattern and it’s too narrow to show the accumulation. Matching the visual and the detail to the shape of the risk, then positioning it against the business context above, is as much a part of the translation as the words used. This is also where a whole-initiative rating fails outright: it has no time dimension and no group breakdown, so there’s nothing to visualise beyond a single static badge. The underlying data needs to be captured at stakeholder-group and time-period level before any chart choice can show the peaks, troughs and who-gets-hit-when that make a sequencing risk concrete.
Common mistakes worth watching for in your own reporting:
Leading with process, not consequence. Opening with “here’s where we are on the ADKAR journey” instead of “here’s what happens if we launch these together”
Too many charts, no clear ask. A dashboard tour with no single decision point at the end
Burying the risk in the data. Trusting the executive to spot the collision themselves rather than naming it explicitly
No business context attached. Presenting a finding as a standalone change-management metric instead of linking it to a strategic priority or operational challenge the executive already owns
Wrong visual for the risk type. Using a heat map for a single scheduling collision, or a bare list for a multi-team saturation pattern
One rating for the whole initiative. Averaging away the peaks and troughs over time, and the variation across stakeholder groups and business units, into a single score
No pre-empted “so what.” Presenting a finding without answering the question every executive is silently asking: what should I do differently because of this
Treating every audience the same. Using the same level of detail for a steering committee that you’d use for a fellow practitioner
A practical framework for translating your single view of change into executive language
Here is a four-step process for converting portfolio data into something an executive audience will actually act on, whatever change management software or portfolio tool you’re using to hold the underlying data.
Start with the decision, not the update. Before opening the dashboard, write down the single decision you need this audience to make. If there isn’t one, you’re delivering a status report, not a briefing, and status reports rarely change behaviour.
Convert every practitioner metric into a consequence metric. For each data point you plan to show, ask “so what happens if this is true.” Twelve impacted stakeholder groups becomes delivery risk to a named deadline. A readiness score of 62 per cent becomes a specific, quantified adoption risk tied to a business outcome the executive already cares about.
Attach it to business context. Link the consequence to a strategic priority, an operating challenge, or a line already on the executive’s own agenda, not just to the change portfolio in isolation. A risk connected to something they’re already accountable for is harder to wave through than one that only exists on a change-management slide.
Match the visual and the detail to the risk type. Pick the chart shape suited to the risk, a timeline for a single collision, a heat map for a spread pattern, and show only the depth of detail this specific decision needs. The wrong visual or too much detail buries the point as effectively as the wrong words.
Answer the “so what” before anyone has to ask it. Close with a direct recommendation, not just a finding. “We recommend sequencing initiative A ahead of initiative B, with a four-week gap” is a request the committee can approve, defer or challenge. A heat map on its own is not.
This is a discipline, not a one-off exercise. It’s worth revisiting every time you prepare for a steering committee, board update, or executive-level sequencing conversation, because the audience’s attention and patience for translation work is the scarcest resource in the room, not the underlying data.
How Change Compass closes the translation gap
A well-built single view of change should do more than store data. It should make the translation work in the previous section faster and more consistent, rather than leaving every practitioner to reinvent the framing from scratch before every executive conversation.
This is one of the areas where the design of the underlying change management software genuinely matters, not just as a data repository but as a communication tool. Part of that starts earlier than the presentation layer: capturing the people-impact and operational-performance data that project and portfolio management tools don’t hold in the first place, at the level of detail a whole-initiative rating can’t provide, by stakeholder group, by business unit, over time, so the change view isn’t just a project status report wearing a change hat and isn’t just one static score per initiative.
Change Compass has been built around exactly this problem, drawing on patterns observed across a large and varied base of change teams reporting to executive audiences. Certain visualisations and framings come up again and again in the platform as the ones that actually shift a sequencing conversation: a saturation heat map that makes a multi-team overlap visually undeniable, a simple timeline for a single collision where a heat map would be overkill, a simplified executive summary that strips a portfolio down to the initiatives that matter for this decision, and narrative templates that translate raw impact data into risk language positioned against the strategic priorities the executive is already tracking.
The point of these templates isn’t to remove judgement from the practitioner. It’s to remove the blank-page problem every time a change team needs to walk into a room and make a case, so the starting point is already halfway translated into the language that room speaks, rather than the language the practitioner’s methodology speaks. A single view of change that has this translation layer built in, rather than bolted on as an afterthought, closes a meaningful part of the gap described throughout this article before a single word of the presentation gets written.
If you’re still evaluating which platform to build this single view on, translation capability is worth adding to your shortlist criteria alongside the more familiar ones like integration options and reporting depth. Our buyer’s guide to change portfolio management tools covers the fuller list of criteria PMOs typically use to separate a genuine change portfolio platform from a generic project tracker with a change label on it, translation capability included.
Making the translation a discipline, not an afterthought
A single view of change is necessary. It is not sufficient. The organisations that actually change executive decisions with their portfolio data are not the ones with the most comprehensive dashboard. They’re the ones who have built a habit of converting practitioner data into consequence, business context, the right visual and the right level of detail, every single time, not just the right words.
That habit is learnable: lead with a decision, not an update; convert metrics into consequences; tie the finding to a strategic priority or operating challenge the executive already owns; match the visual and detail to the shape of the risk. Change management software can make this faster and more consistent, and it can close the more basic gap of holding people-impact data most project tools never capture in the first place. But it can’t replace the judgement of choosing, every time, what this specific audience needs to see and hear in order to act.
Frequently asked questions
What does “single view of change” mean? Every active and planned initiative, plus the teams, roles and timelines they affect, consolidated in one place instead of scattered spreadsheets and team trackers. Most organisations that think they have this actually have a project-level view only, timelines and delivery status without the people-impact and operational-performance layer. It’s the foundation for sequencing and saturation decisions, but on its own it only solves visibility, not whether that visibility changes what leadership decides.
Why don’t executives respond well to typical change management dashboards? Most change dashboards summarise for awareness rather than a decision: practitioner vocabulary, findings without the business context that would make a risk feel urgent, and often a visual or detail level that doesn’t match the risk shown. The data can be accurate and still fail to influence a decision if it reads as FYI rather than something built to force a call.
How is change management software different from just having a single view of change? A spreadsheet can technically deliver a single view of change. Purpose-built software goes further by structuring how data is captured, aggregated and translated into executive-ready visuals and narratives, positioned against the business context the executive already tracks, rather than leaving that work to whoever is preparing the next update.
What’s the difference between change data and business risk framing? Change data describes what’s happening: which groups are impacted, at what level, over what timeframe. Business risk framing describes what it means: the cost of a collision, the delivery risk to a deadline. The same underlying data can be presented either way, and only the second tends to change a decision.
How can change practitioners get better at speaking executive language? Practise converting every metric into a consequence before presenting it: for each data point, ask “so what happens if this is true, and what should the audience do differently because of it.” Over time this becomes a habit rather than a translation done under pressure before every steering committee meeting.
Why isn’t a single impact rating for the whole initiative enough? A whole-initiative rating (High, Medium, Low, applied once, for the entire life of the initiative) averages away the variation a sequencing decision actually needs: the peaks and troughs as the initiative moves through design, testing and go-live, and the very different impact levels for different stakeholder groups, business units and teams at different points in time. Two initiatives can both carry a “High” rating and still be nowhere near each other in when their real pressure lands or who it lands on. Without that time and group breakdown, there’s nothing underneath the rating to sequence against.
Most change plans are built the same way. Someone maps out the training, the communications, the workshops and the go-live support needed for the change, then trims that same list down as it moves up the organisation chart. Frontline staff get the full programme. People leaders get a condensed version. Executives get a briefing deck and a project update in the steering committee.
We recently analysed activity data spanning tens of thousands of initiative impacts, looking specifically at what kind of change activity each stakeholder group actually receives, not just how much. The pattern that emerged does not support the “same plan, smaller portion” model at all. Executives, people leaders, specialists, frontline staff and external partners are not getting a scaled version of the same experience. They are getting fundamentally different kinds of support, and in some cases, that difference looks less like intentional design and more like an oversight with real consequences for adoption.
This matters because most change practitioners already sense that different stakeholders need different treatment. What the data adds is specificity: which groups are getting trained but rarely reinforced, which are getting plenty of activity labelled “engagement” that is actually one-way, and which group is getting almost nothing at all. One of those findings, in particular, points to a structural gap that is easy to miss and expensive to leave unaddressed.
The assumption behind most stakeholder plans
Ask a change manager how their plan differs by stakeholder group and most will describe a cascade: senior leaders get briefed first, then the message and the supporting materials flow down through people leaders to frontline teams, getting shorter and more operational at each step. This is a reasonable model for communication. It is a poor model for change activity more broadly, because communication is only one of several distinct things a change plan can offer a stakeholder group: training, two-way engagement, go-live support, and post-launch reinforcement are different interventions with different purposes, and they do not scale down uniformly.
The cascade model implicitly assumes that what changes between stakeholder groups is depth and detail. What the data shows is that what actually changes is the type of activity a group receives, and that type is not always the right one for what that group needs to do differently.
What the data shows about activity mix by stakeholder group
Looking across many initiatives and pooling activity records by stakeholder archetype (frontline staff, people leaders, specialists, executives, and external partners), a clear and consistent pattern emerges in which activity types each group is most likely to receive.
Frontline teams are the group most likely to get formal training, and increasingly, some form of post-launch reinforcement once the change has gone live. Communication and training dominate their experience, with meaningful support extending after go-live in a substantial share of cases.
People leaders sit in an unusual position. They receive training at a moderate rate, but reinforcement after go-live and hands-on engagement both drop away sharply compared to frontline staff. Their plan is front-loaded and largely stops there.
Specialists and subject matter experts get a more balanced mix: solid training, and the highest rate of interactive, workshop-style engagement of any internal group, consistent with their role in shaping how a change actually gets implemented.
Executives are rarely formally trained. Instead, their change experience is dominated by activities tagged as engagement, briefings, updates and consultation, which makes sense given their role is to endorse and champion rather than execute.
External partners and vendors stand out for the wrong reason. They receive almost no interactive engagement of any kind. When they do appear in a change plan, it is overwhelmingly as a one-way communication or compliance touchpoint.
Not all “engagement” is the same
That word, engagement, is doing a lot of work in the paragraph above, and it is worth pausing on before drawing conclusions. A stakeholder plan can log a one-hour information session and a half-day co-design workshop under the same activity type, even though one is a broadcast with a Q&A bolted on and the other is a genuinely two-way exercise where the group shapes the outcome. Prosci’s research on the link between change management and employee engagement is explicit that ownership and commitment come from dialogue, not from being informed, however well that information is delivered.
This raises a question worth asking of any plan before assuming a stakeholder group is well engaged: is the mix within “engagement” itself skewed toward download-driven, one-way formats such as briefings, webinars and FYI sessions, or does it include enough two-way formats such as workshops, focus groups and structured consultation to actually shape the group’s understanding and buy-in? A plan can look well-engaged on paper, with a healthy count of engagement activities against a stakeholder group, and still be almost entirely one-way in practice. That distinction does not always show up in a simple activity count, but it tends to show up very clearly in adoption outcomes.
None of the pattern above, on its own, is surprising once you see it laid out. What is more interesting, and more useful for a business manager building a change plan, is what happens when you add a second dimension: not just what kind of activity each group gets, but how long their exposure to the change actually runs.
The duration gap nobody talks about
When you measure how long each stakeholder group stays actively involved in a change, from their first touchpoint to their last, a second pattern appears that activity type alone does not reveal.
Frontline teams typically stay engaged with a change over many months. Their involvement runs from initial communication through training, go-live support and, where it exists, post-launch reinforcement. Executives, by contrast, are typically involved for a much shorter window, often a fraction of the total length of the programme. Their engagement tends to cluster early, around approval and launch, and then tapers off well before the change has actually landed with the people who have to use it.
This is the finding that should change how a manager thinks about sponsorship. It is not that executives are under-engaged in absolute terms. It is that their engagement window is short relative to the change itself, and it often ends long before frontline adoption is complete.
Why a short sponsorship window is a bigger risk than it looks
What the research says sponsorship should look like
There is a substantial body of change management research on the importance of visible, ongoing executive sponsorship, and it consistently ranks it as one of the single strongest predictors of whether a change actually succeeds. Prosci’s long-running Best Practices research has identified active and visible sponsorship as the top contributor to change success for over two decades, most recently by roughly a three-to-one margin over the next most important factor, and found that an effective sponsor can lift a project’s chances of achieving its intended benefits from around 25 percent to as high as 85 percent.
Crucially, that research is explicit that sponsorship has to be sustained, not a single kickoff appearance. The distinction the research draws is between passive sponsorship, where an executive signs off once and steps back, and active sponsorship, where they remain visibly involved and continue to reinforce the “why” as the change progresses. That distinction is not a minor nuance. It is effectively the entire finding: the value of a sponsor comes from their continued presence, not from the initial endorsement that most plans already capture well.
What the duration data shows instead
Put the duration data next to that research and a specific, practical risk comes into focus. If your data shows executive engagement clustering in the first third of a programme and dropping off well before frontline teams reach the training and reinforcement stages, you are very likely losing visible sponsorship at exactly the point in the timeline when adoption research says it matters most: when frontline teams are being asked to actually change how they work, often months after the executive briefing that kicked things off.
It is entirely understandable, and often appropriate, for the intensity of a sponsor’s involvement to reduce as a programme moves past launch. Nobody expects an executive to sit in weekly working sessions six months into a rollout. The issue is not that involvement tapers, it is whether that taper is a deliberate design choice or simply the default outcome of a plan that never scheduled anything for a sponsor beyond the kickoff and the steering committee. A sponsor’s later-stage presence does not need to be frequent to be effective, but it does need to be designed: a standing slot in deployment reviews, a named checkpoint in planning and reporting cycles, a scheduled moment to speak at a reinforcement milestone. The difference between a sponsor who fades out by accident and one whose involvement is intentionally lighter but still present at the right moments is entirely a matter of whether anyone planned for it.
This is also a point where the data itself deserves a caveat. Change managers are not always capturing sponsor involvement at a level of detail that would show up in an activity log, a sponsor might be reviewing deployment dashboards, fielding escalations, or advocating in leadership forums that never get recorded as a formal change activity against their name. Some of the apparent drop-off in the data may reflect a visibility gap in how sponsor involvement is tracked, rather than an actual absence of sponsorship. That possibility does not weaken the underlying point. If anything, it strengthens it: an organisation that cannot see how its sponsors are actually spending their time on a change cannot deliberately design that involvement either, and the fix, better capture of what sponsors are doing and when, is the same fix either way.
The practical response is not simply more executive time. It is a small number of deliberately placed, and deliberately tracked, touchpoints, timed to coincide with frontline milestones rather than clustered around approval and launch. A short video message when training begins. A visible appearance at a go-live event. A named slot in the deployment review cadence. A mention in a leadership forum when the reinforcement phase starts. None of this requires the executive to be trained or to attend workshops. It requires their visibility to be timed to match the parts of the change that are actually happening on the ground, which is exactly the kind of portfolio-level timing view that becomes much easier to plan for once you can see where multiple initiatives are competing for the same stakeholders’ attention at once, and it is also the starting point for building the kind of change portfolio literacy in senior leaders that makes a sponsor’s occasional appearances land as informed rather than performative.
Middle managers are being asked to reinforce a change they were never reinforced on themselves
The second finding worth a business manager’s attention concerns people leaders, and it is arguably the more actionable of the two because it sits entirely within the organisation’s own control.
The gap in the data
Across the initiatives analysed, people leaders receive noticeably less post-launch reinforcement and less two-way engagement than frontline staff, despite the fact that people leaders are usually the ones expected to reinforce the change with their own teams once training has finished. In practice, this means many change plans train a manager once, early, and then expect that manager to coach, reinforce and answer questions for their team for months afterward, without giving that manager any equivalent ongoing support themselves. Picture a typical rollout: the manager attends a one-hour briefing in week two, then spends the next six months fielding questions from their team about a system or process they were only ever shown once, with no scheduled check-in of their own to ask what is actually going wrong on the ground.
Why this particular gap is expensive
This is not just a theoretical gap. McKinsey’s research on middle managers has found that managers already spend close to half their working time on non-managerial, administrative work, leaving less than a third of their time for people leadership of any kind, change-related or otherwise. Asking a manager who is already stretched thin to be the primary reinforcement mechanism for a change, without reinforcing that manager first, is asking a lot of a role that has very little slack to give.
There is also a well-established link between reinforcement and whether training actually sticks. McKinsey’s work on improving training effectiveness points to structured follow-up and ongoing reinforcement as the difference between training that changes behaviour and training that is quickly forgotten. If that is true for frontline staff, who at least receive some reinforcement in many of the plans we looked at, it is likely just as true, or more true, for the people leaders receiving almost none. The uncomfortable implication is that the group most responsible for making a change stick day to day is, on average, the group least equipped by the plan itself to do so.
A quick audit worth running on your own change plan:
Does your plan give people leaders any support after their own training finishes, or does their involvement effectively end once they have been briefed?
Are people leaders expected to answer frontline questions about the change without a channel to ask questions themselves?
Is there a manager-specific check-in scheduled at the same point frontline reinforcement activities happen, or does the plan assume managers will simply absorb and relay information indefinitely?
If a people leader is struggling to reinforce the change with their team, would anyone in the change programme actually know?
If the honest answer to most of these is no, the gap is not unique to your organisation. It shows up consistently in the data, and it is one of the more fixable findings in this analysis because it does not require new stakeholder groups or new activity types, only redirecting a small amount of existing reinforcement effort toward the managers who are meant to be delivering it onward.
The stakeholder group that gets almost nothing
The starkest finding in the data concerns external partners and vendors. Across the initiatives analysed, this group receives virtually no interactive engagement activity of any kind. When partners do appear in a change plan, it is almost always as a recipient of one-way communication or a compliance-style touchpoint, not as a group that gets consulted, tested with, or given the chance to flag problems before go-live.
Some of this may be a data problem rather than a design problem. Partners and vendors sit outside the organisation’s own systems, so their involvement is less likely to be logged with the same discipline as an internal stakeholder group’s, even when real consultation is happening informally through account managers or delivery leads. It is worth treating a near-empty partner engagement record as a prompt to check which is actually true: are partners genuinely being left out of two-way engagement, or is the organisation simply not capturing the full picture of how they are involved? Both are worth fixing, but they call for different responses, one is a planning gap and the other is a data-capture gap.
This matters more than it might first appear either way, because partners and vendors are frequently the group with the most direct visibility into whether a change will actually work operationally. A partner delivering a service that depends on a new internal process is often the first to know if that process has a gap, but if the plan never engages them beyond a notification email, or never records that engagement even when it happens, that knowledge has no reliable route back into the programme until something breaks in production.
For a business manager reviewing a change plan, the practical prompt here is simple: look at your stakeholder map and identify who is receiving communication only, with no engagement activity at all. If external partners, vendors or other groups outside the direct organisational hierarchy consistently fall into that category, treat it as a specific risk to close, whether the fix is adding real consultation or simply starting to record the consultation that already happens.
A simple way to check whether your own plan actually differentiates by group
The most useful thing a business manager can do with this data is not memorise specific figures, but adopt a habit of checking their own plans against the same four questions for every stakeholder group involved in a change:
What type of activity is this group actually getting, not what volume? A shortened version of the frontline training deck is not the same thing as genuine engagement, and a single briefing is not the same thing as sponsorship.
Within “engagement”, what is the actual mix? Count how much is workshop-style, two-way and consultative versus how much is download-driven, a briefing, a webinar, an information session with no real exchange. A healthy activity count can still hide a one-way plan.
How long does this group’s involvement actually run, from first touch to last, relative to the total length of the change? A group whose involvement ends in week three of a twelve-month programme is effectively disengaged for three quarters of the change, regardless of how well that first three weeks went.
Is anyone checking in on this group after their initial activity, or does the plan assume the first touchpoint is sufficient? This question alone tends to surface the people leader and partner gaps described above faster than any other single check.
Running a real change plan through these four questions, group by group, typically takes less time than a single planning meeting, and it tends to surface the same recurring issues in the data: engagement that is one-way in practice despite looking healthy on paper, sponsorship windows that are too short or simply undocumented, and reinforcement that never reaches the managers expected to deliver it.
Where digital tools help close these gaps
Most of the gaps described here are not visible from inside a single project plan. They only become obvious when you can see activity type, duration and stakeholder group laid out together, across a whole portfolio of initiatives rather than one at a time. This is where a dedicated change management platform like Change Compass earns its place: rather than manually cross-referencing spreadsheets to work out whether your people leaders are getting reinforcement or whether your executive sponsor’s engagement window is long enough, a proper single view of change makes stakeholder-level gaps visible at a glance, before they show up as an adoption problem months later.
Making it work in practice
The pattern in the data is consistent enough to be a useful starting assumption for any change plan: frontline teams tend to be trained but not always sustained, people leaders tend to be briefed but rarely reinforced, executives tend to be engaged early but not always for long enough or in a documented way, and external partners tend to be informed but rarely genuinely consulted, or at least rarely recorded as being consulted. None of these are inevitable. They are simply what happens by default when a plan is built once and then scaled down by volume rather than redesigned by purpose for each stakeholder group.
The fix does not require more resources across the board. It requires being deliberate about which of the four activity types, training, engagement, reinforcement and communication, each stakeholder group actually needs, being honest about how much of that engagement is genuinely two-way, and checking that involvement lasts as long as the change itself demands. Start with your next executive sponsor and ask a genuinely different question than usual: not “have they been briefed”, but “will they still be visible, in a way we can actually see, when frontline teams need them most”.
Frequently asked questions
Why shouldn’t a change plan just be scaled down for different stakeholder groups? Because different stakeholder groups need different kinds of support, not just less of the same kind. A shortened training module works for a group that needs to learn a new task, but it does nothing for a group that needs to be consulted, or one that needs ongoing reinforcement after go-live. Scaling down volume without changing the type of activity tends to leave real gaps in engagement and reinforcement.
How long should executive sponsorship actually last during a change programme? Sponsorship should remain visible for roughly as long as the change is actively landing with the people affected by it, not just through approval and launch. Research consistently links active, ongoing sponsorship, rather than a single early appearance, to significantly higher rates of achieving intended business benefits.
Why do people leaders often get overlooked in change plans? People leaders are usually treated as a communication channel to their teams rather than as a stakeholder group with their own change needs. Because they are expected to reinforce the change for others, a plan that trains them once and then leaves them without ongoing support is asking them to sustain something they were never given the tools to sustain themselves.
Should external partners and vendors be included in change engagement activities? Yes, particularly where they have direct visibility into how a change performs operationally. Limiting partners to one-way communication, or simply failing to record the consultation that does happen, removes an early warning channel that could otherwise surface implementation problems before they affect customers or operations.
Is every activity labelled “engagement” equally valuable? No. Engagement activity types typically span a spectrum from download-driven formats such as briefings and information sessions, which are essentially one-way, through to genuinely two-way formats such as workshops, focus groups and structured consultation. A stakeholder group can show a healthy volume of engagement activity while still receiving very little real, two-way input into the change.
What is the simplest way to spot these gaps in an existing change plan? Map each stakeholder group against four questions: what type of activity they are actually receiving, how much of any “engagement” activity is genuinely two-way versus one-way, how long their involvement runs relative to the total programme, and whether anyone follows up with them after their first touchpoint. Groups that fail more than one of these checks are the ones most likely to be under-supported.
Deloitte’s 2026 industry outlook puts a number on what every utility executive already feels: peak electricity demand is projected to grow roughly 26% by 2035, driven by data centre buildout, transport electrification and industrial reshoring, while more than 2 terawatts of new capacity sit stuck in interconnection queues waiting to connect.
At the same moment, more than half the utility workforce is 45 or older, with between a third and a half of that group eligible to retire within five to ten years. Demand is accelerating. The people who know how to run the grid are leaving.
Neither of those facts is a change management problem on its own. What turns them into one is that utilities are trying to solve both simultaneously, in the same control rooms and field crews, alongside a five-year regulatory reset cycle that was never designed with digital or AI transformation in mind. A grid modernisation programme, a workforce renewal effort, an OT/IT convergence project and a regulator-mandated capital works schedule do not queue up politely. They compete for the same linemen and the same control room shifts, often without anyone holding a single view of the collision.
This is the structural reason generic change management frameworks under-serve energy and utilities. They were built for corporate reorganisations where the main risk is disengagement. In a utility, the main risk is physical: a badly sequenced rollout that pulls a control room operator into training during storm season, or a digital tool a field crew abandons because it was never tested against a rural coverage blackspot. This article sets out what actually differentiates change management for energy and utilities, the four forces colliding in transformation portfolios right now, and a practical framework for sequencing regulated and discretionary change without breaking the people who deliver both.
What makes change management for energy and utilities structurally different
Compare the failure mode. In financial services, the change management conversation centres on regulatory compliance and conduct risk: did the change get documented, evidenced and signed off in a way a regulator would accept. In healthcare, it centres on clinical risk: did the change protect patient safety during the transition.
In energy and utilities, the primary risk is physical and operational. A poorly managed change to switching procedures, outage scheduling or field dispatch does not just create rework or a compliance finding. It can put a lineworker in the wrong place during a live fault, or leave a community without power longer than it should have been.
That single distinction reshapes almost everything about how change should be planned and sequenced in this sector:
Safety-critical operational change cannot be rolled out on a marketing-style go-live date. It has to work around shift patterns, storm season and mandatory safety stand-downs.
Field-workforce logistics are a constraint, not an afterthought. A change that assumes reliable connectivity and a desk does not survive contact with a crew working from a ute in a coverage blackspot.
Long-cycle regulated infrastructure programmes run for years, not months, and have to coexist with faster-moving digital transformation happening in parallel.
Asset-heavy, unionised, multi-generational workforces bring a different change psychology than a corporate head office does: tenure and safety culture carry more weight than in a typical office reorganisation.
None of this means change management matters less in utilities. If anything, the stakes are higher, because the artefact you are changing is the thing that keeps the lights on. It also means the unit of analysis has to shift: a financial services change function can often reason initiative by initiative and still catch most of its risk through governance and sign-off, but a utility change function that reasons the same way will keep missing the risk that only shows up when several long-cycle programmes land on the same crew in the same month.
Four forces colliding in utility transformation portfolios right now
Ask most utility transformation leaders to name their single biggest change risk and they will usually point to one initiative. The real risk sits in how four separate forces are converging on the same finite pool of people, capital and attention at the same time, against a backdrop of capital investment that is itself accelerating: Deloitte puts the US electric power sector’s capital needs at more than $1.4 trillion through 2030. That scale of capital deployment does not translate cleanly into scale of delivery capacity on the ground.
Grid modernisation and the interconnection backlog
More than 2 terawatts of renewable, storage and large-load capacity are currently stuck in interconnection queues globally, nearly double what is currently installed. Clearing that backlog means new planning processes and new ways of working between engineering, regulatory affairs and commercial teams that have historically operated in separate lanes. That is a change programme in its own right, running on a timeline utilities do not fully control.
The workforce cliff
More than half of utility employees are 45 or older, and a meaningful share of that cohort is retirement-eligible within the decade. When an experienced switching operator or protection engineer leaves, they take undocumented judgement with them, not just a job title. Any transformation programme that assumes stable institutional knowledge as a constant is planning against a workforce that will look materially different in five years.
OT/IT convergence and the cybersecurity change nobody scheduled
As operational technology and IT systems converge, utilities gain real operational benefits, but the attack surface expands with every new connected device. Power grids and water systems are high-value targets, and disruption does not stay local. Regulators increasingly expect continuous monitoring and rapid incident response as a baseline, not an aspiration, which means cybersecurity uplift has become a recurring, unscheduled change event competing for the same control room and engineering time as planned modernisation work.
Five-year regulatory reset cycles
In markets like Australia, network businesses submit a regulatory proposal to the Australian Energy Regulator every five years to determine how much revenue they can recover for safe, reliable service. That cycle dictates a large share of capital works, tariff structures and depreciation schedules for the following five years, so digital and AI initiatives not built into the current determination often have to be justified and sequenced around a regulatory calendar the transformation team does not set.
Individually, each of these forces has an established playbook. Together, they draw on the same finite pool of field crews, control room operators and engineering capacity, and almost no utility change function has a single, portfolio-level view of how they overlap.
Most change management templates assume a workforce that sits at a desk, has reliable internet, and can attend a one-hour training session between meetings. None of that describes a field crew. Rollout logistics in utilities have to account for shift-based scheduling, low-connectivity work sites, safety-critical windows that cannot be interrupted, and a workforce that is frequently mobile between depots.
The common mistakes are predictable once you see the pattern:
Scheduling training and go-live during storm season, when field crews are stretched thinnest and least able to absorb new process.
Assuming desktop-style connectivity and device access, when much of the workforce works from vehicles, substations or rural sites with patchy coverage.
Treating union and safety consultation as a compliance checkbox rather than genuine input into sequencing, which slows adoption and erodes trust for the next change.
Rolling out one initiative at a time without checking what else is already landing on the same crew, which is how a well-designed programme still produces change fatigue.
Measuring adoption through system logins rather than field behaviour, which hides the gap between “the tool was deployed” and “the crew actually changed how they work.”
EY’s research into utility digital transformation makes the same point from the workforce side: skills and technology readiness are inseparable from a low-carbon energy future, and EY explicitly frames change management and experience programmes as core to closing that gap, not an add-on to the technology rollout. Design the change around the shift pattern, not the other way around.
A change portfolio management framework for regulated infrastructure programmes
Sequencing a single change well is a project management problem. Sequencing grid modernisation, workforce renewal, OT/IT convergence and a regulatory capital programme against each other is a portfolio problem, and it needs a different discipline: change portfolio management, treated as its own capability rather than a by-product of individual project plans.
Build a capacity model that spans crews, not headcount
A capacity ceiling in a utility is not “how many people we have.” It is how many people with the right qualification, clearance and shift availability can absorb change in a given week, in a given depot or control room, without compromising safety margins. A model built at that level, cross-referenced against every initiative in flight, is what turns “we think Q3 is busy” into “the Overhead Lines crew in the northern region is carrying three concurrent changes in the same fortnight, and one of them can safely move.”
Give portfolio sequencing a single owner with authority to say no
The point of a capacity model is wasted if no one has the mandate to act on it. A practical framework needs four elements:
A single register of regulated and discretionary change, so capital works tied to the current AER (or equivalent) determination sit in the same view as voluntary digital and AI initiatives, not in separate spreadsheets.
A capacity ceiling by crew, shift and control room, not by headcount, so overlap shows up before go-live, not after.
Sequencing rules that protect safety-critical windows first, then fit discretionary change around outage seasons and mandatory safety stand-downs.
A named portfolio owner with the authority to re-sequence, rather than leaving that call to whichever project manager shouts loudest.
Picture how that plays out. A distribution business is midway through a five-year AER determination period, delivering a mandated pole and wire replacement programme. In the same quarter, the digital team wants to pilot an AI-based outage prediction tool with the same control room shift, and the workforce team wants to run a knowledge-transfer programme pairing retiring linesmen with apprentices before three senior crew members leave within eighteen months.
Run in isolation, each initiative looks manageable on its own project plan. Mapped against the same capacity model, the overlap is obvious: all three want meaningful time from the same twelve-person crew in the same six-week window, right before storm season. A single portfolio owner with visibility across all three can push the AI pilot six weeks, run the knowledge-transfer sessions in shorter blocks, and leave the regulated pole replacement programme untouched, because that one carries the least flexibility. None of the three plans would have surfaced that decision alone.
This is a direct extension of change conflict detection applied to infrastructure: the goal is to make the collisions visible early enough that sequencing becomes a choice instead of an accident.
Where AI is actually helping in utilities, and where it is creating new change risk
AI is not a single change in a utility transformation portfolio. It is dozens of smaller ones, arriving on different timelines, into a workforce already carrying grid modernisation, workforce renewal and a regulatory reset cycle.
What is working
Deloitte expects nearly 40% of utility control rooms to be using AI by 2027, largely for grid balancing, demand forecasting and outage prediction. Kyndryl’s research points to concrete wins: AI-driven distributed energy resource management systems orchestrating real-time power flow from renewables, and digital twins that let engineers simulate grid behaviour and anticipate failures before they happen. Where AI is scoped narrowly, against a specific operational problem, it is genuinely reducing outage time and easing pressure on a stretched engineering workforce.
What is not
Only around half of utilities report a positive return from autonomous agentic AI systems, and 70% of sector leaders say they feel unprepared for external business risk, well above the cross-industry average. The research’s own framing is the sharpest summary of the problem: the biggest grid risk over the next decade is not weather or cyberattack, it is organisational inertia. AI initiatives treated as a procurement decision rather than a change programme are the ones most likely to fail, particularly when stacked on top of a workforce already absorbing grid modernisation and OT/IT cybersecurity uplift without anyone checking capacity first.
The practical implication for transformation leaders is to treat every AI initiative as a line item in the same capacity model as everything else, not as a separate, faster-moving track that gets to skip the queue because it is strategically important. Strategic importance is exactly why it needs to be sequenced properly.
Using AI for the change management function itself, not just the grid
Almost all of the AI conversation in utilities happens on the operations side: grid balancing, predictive maintenance, outage prediction. That is only half the opportunity. The change management function carries its own administrative load and its own blind spot, and applying AI there is a distinct, complementary problem.
Cutting the administrative load
A distribution business running a capital programme alongside a digital transformation portfolio generates significant manual overhead: drafting impact statements for every crew a change touches, summarising updates from a dozen project managers, building first-cut readiness assessments, and translating rollout detail into plain-language communications a field crew will actually read. A capable AI layer, grounded in the organisation’s own change data rather than operating as a generic assistant, can absorb a meaningful share of that drafting work without removing the change manager from the decision.
Surfacing what a spreadsheet can’t
The higher-value use of AI is insight, not drafting. Applied to a utility’s own portfolio data, an AI layer can flag that three initiatives are landing on the same crew in the same fortnight, or that a discretionary AI pilot and a regulated capital milestone are converging on the same window before anyone has manually cross-referenced the schedules. This is the same class of insight covered in the capacity-model framework above, surfaced continuously instead of waiting for the next planning cycle.
It is also why general-purpose tools such as ChatGPT or Copilot cannot do this work alone. They can draft a competent impact statement, but they have no access to a utility’s crew rosters, safety windows or regulatory calendar, so they cannot tell a transformation leader that a crew is already at 90 per cent of safe load before a fourth initiative lands on it. The insight only exists if the AI is grounded in the organisation’s own structured change and capacity data, not a generic wrapper bolted onto a chat interface.
Building the infrastructure to see the whole portfolio
Most of what breaks utility transformation portfolios is not a single bad decision. It is the absence of a shared, current view of what is landing where, held by anyone with the authority to act on it. A change intelligence platform gives transformation leaders that view: a live register of regulated and discretionary change, cross-referenced against real crew and control room capacity, so conflicts surface as a planning input rather than a post-incident finding.
This is the same structural argument that has led PMO directors and transformation leaders at firms including NiSource, a regulated US gas and electricity utility, to treat change data as infrastructure in its own right, not a spreadsheet rebuilt every quarter. The Change Compass is built for exactly this problem: a single, live view of capacity, conflict and sequencing, with AI grounded in that same data, so portfolio decisions get made with evidence instead of guesswork.
The portfolio is the unit of risk, not the project
Every individual change programme in an energy or utilities transformation portfolio can be well planned, well resourced and well executed, and the portfolio can still fail, because the risk was never in any single initiative. It was in the collision between grid modernisation, workforce renewal, OT/IT convergence and a regulatory reset cycle that none of the project plans were built to see. Change management for energy and utilities has to operate at the level where that collision is visible: a shared capacity model, a single register of regulated and discretionary change, and someone with the authority to re-sequence when the plan and the calendar disagree.
Start smaller than a full portfolio rebuild if you need to. Pick the one crew or control room carrying the heaviest concurrent load right now, map every initiative landing on it over the next two quarters, and see what the collision actually looks like on paper. Most leaders who do that exercise once do not go back to planning change one project at a time.
Frequently asked questions
What is change management for energy and utilities?
The discipline of planning, sequencing and embedding organisational change within the constraints of safety-critical operations, field-based workforces, long-cycle infrastructure programmes and five-year regulatory reset cycles. It differs from generic corporate change management because the primary risk is physical and operational, not purely compliance-based.
Why can’t utilities use the same change management approach as other regulated industries?
Financial services centres on regulatory and conduct risk, and healthcare centres on clinical risk. In energy and utilities, the primary risk is physical and operational safety, and a large share of the workforce is field-based and shift-based, which requires different rollout logistics entirely.
What is change portfolio management, and why does it matter for utilities?
Managing the combined load, sequencing and conflicts of every change initiative across an organisation at once, rather than each in isolation. For utilities, grid modernisation, workforce renewal, OT/IT convergence and regulatory capital programmes routinely draw on the same finite pool of crews and control room staff, and only a portfolio-level view catches that overlap before it causes an operational problem.
How should utilities sequence AI rollouts against other transformation programmes?
AI initiatives should sit in the same capacity model as every other change, mapped against real crew and control room availability, and sequenced around safety-critical windows and regulated capital works. Treating AI as a separate track that bypasses portfolio sequencing is a common reason AI programmes underdeliver.
How can utilities address the ageing workforce and skills gap through change management?
By capturing undocumented operational judgement before experienced staff retire, designing rollouts around shift patterns rather than desk-based assumptions, and building genuine frontline and union consultation into sequencing decisions rather than a late-stage compliance step.
How can AI support the change management function, not just grid operations?
It can reduce the drafting load (impact statements, stakeholder communications, first-cut readiness assessments) and, more valuably, surface portfolio-level insight, such as flagging that a crew is approaching its safe capacity load before a human would have cross-referenced every initiative manually. This only works if the AI is grounded in the organisation’s own change data, not a generic assistant with no visibility into rosters or the regulatory calendar.
We use cookies to improve your experience and understand site use. Marketing cookies stay off until you accept, and in the EU, UK and Switzerland analytics does too. Cookie Policy.
Strictly necessary
Required for the site to work: security, load balancing, and remembering your choices. These cannot be switched off.
Always active
Analytics
Google Analytics and similar, so we can see which pages are useful and where visitors get stuck. Aggregated, never sold.
Marketing
Used to measure campaigns and show relevant content on other platforms such as LinkedIn.
