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.
On 1 July 2025, APRA’s Prudential Standard CPS 230 came into force, and with it, a requirement most financial services change functions still have not absorbed: boards must now oversee operational risk arising from their own institution’s change activity, as a standing governance responsibility, not a project-level concern raised only when something has already gone wrong. It is one of the first times a regulator has said explicitly, in a binding prudential standard, that a poorly sequenced portfolio of change is a board-level risk in its own right, and it is one instance of a pattern now playing out in board rooms well beyond Australia, from London to Toronto to Singapore.
CPS 230 did not invent this problem. It named it. And it forces a question most financial services change functions have never had to answer cleanly: at which level of the organisation, exactly, is the volume and sequencing of change actually governed, and does the board see the performance and benefit impact of that portfolio, or only a status summary of individual projects.
Most change management for financial services content treats regulatory pressure as one more generic source of “change volume” to manage. It is not generic. It is a structural governance question that plays out differently at three distinct levels, the frontline teams absorbing change day to day, the business unit coordinating it across them, and the enterprise and board reviewing what it is doing to performance and value. This article sets out a working governance model across those three levels, and shows why regulators well beyond Australia are now converging on the same demand.
Why this is now a board-level governance question
CPS 230 is not an isolated Australian requirement. Over the past three years, financial services regulators across several major markets have independently converged on treating change-related operational risk as a governance obligation, not a delivery detail. A few examples make the pattern clear.
Australia: alongside CPS 230’s operational risk requirement, the Financial Accountability Regime requires banks (from March 2024) and insurers and superannuation trustees (from March 2025) to name accountable persons against specific responsibilities, backed by formal accountability statements.
The United Kingdom: in April 2023, the Bank of England’s Prudential Regulation Authority personally fined TSB Bank’s former Chief Information Officer for breaching the PRA’s Senior Manager Conduct Rules, following a 2018 core banking migration that locked out 5.2 million customers and eventually cost the bank £48.65 million in combined FCA and PRA fines. The regulators were explicit that the failure was not the migration itself, migrations fail regularly, but that no one had both the authority and the full picture needed to stop it going ahead once the warning signs were there.
Canada: the Office of the Superintendent of Financial Institutions’ Guideline E-21, finalised in August 2024, explicitly lists change management alongside business continuity and crisis management as a named component of operational risk and resilience that federally regulated institutions must govern.
Singapore: the Monetary Authority of Singapore’s Guidelines on Individual Accountability and Conduct require financial institutions to clearly identify the senior managers responsible for each core function and hold them accountable for the conduct of the business under their purview.
The European Union: the Digital Operational Resilience Act, in force since January 2025 across roughly 22,000 financial entities, ties ICT and change-related operational resilience directly to internal governance obligations, with penalties reaching €1 million for individual senior managers.
None of these regimes were written with change management in mind specifically. All of them arrive at the same practical requirement: a financial services change portfolio needs real governance at every level where a decision about sequencing, capacity or risk actually gets made, not a single dashboard the board glances at once a quarter. If you already have a strong grip on the different categories of transformation running through your organisation, our companion piece on the eight core types of financial services transformation is the right place to map what is actually in your portfolio before applying the governance model below.
A governance model for change portfolios: operations, business unit, enterprise
Most financial services change functions have governance on paper, a steering committee here, a change advisory board there, but it rarely maps cleanly onto the three levels where decisions about change risk and value actually get made. Here is a model that does, built around a single artefact each level contributes to and draws from: a risk-in-change register, a live record of what change is landing where, how much capacity it is consuming, and what operational, consumer-outcome or performance risk it is creating, that exists as one shared view rather than three disconnected reporting lines.
Operations level: the source of real signal
The operations level, claims processing teams, contact centre agents, branch tellers, loan servicing staff, is where change load is actually experienced, not where it is reported from a spreadsheet. This is the frontline delivering the customer interaction every disclosure and prudential regime ultimately cares about. This level should surface three specific things upward:
Real capacity data, not estimated capacity. How many hours per week is this team realistically able to absorb in new process, system or product change, given its existing operational workload, not a generic FTE assumption inherited from a project template.
Early psychosocial and readiness signals. Frontline supervisors are the first people to see when concentrated change load is producing disengagement, error rates, or attrition risk, well before it shows up in a portfolio dashboard.
First-hand evidence from the customer interaction itself. Where a change affects a customer-facing product or process, frontline staff are the ones who can confirm whether customers actually understand what changed, not just whether a disclosure document was technically issued.
The failure mode at this level is not incompetence. It is that most portfolio governance never asks operations teams for this information in a structured, recurring way, so it only surfaces informally, if at all, until it becomes an incident.
Business unit level: the sequencing function
This is the divisional or business-unit layer, retail banking, claims, wealth advice, coordinating operations teams underneath it, and it is the level TSB’s case shows was structurally missing: someone with a live, cross-initiative view who can see that two individually “green” projects are about to land on the same operations team in the same fortnight, one driven by a hard regulatory deadline and one entirely discretionary.
This level should own:
Cross-referencing regulatory deadlines against operational capacity data, not managing regulatory and discretionary change as separate, uncoordinated streams reporting into different committees.
The sequencing and trade-off recommendation, deciding, with evidence, which discretionary initiative slows down when a mandatory obligation is added to a team’s load, rather than leaving that decision to whichever project manager escalates loudest.
Genuine change conflict detection across the business unit’s initiatives, treating overlapping change on the same team as a standing risk to monitor, not a coincidence discovered after go-live.
Aligning frontline readiness and engagement data with the customer communication plan, rather than letting the two run on separate tracks. A business unit that knows its contact centre team is stretched thin two weeks out from a major product change should be the same function deciding when and how customers hear about that change, because a rushed or poorly staffed customer response is exactly when a communications gap turns into a complaint, an escalation, or a DDO and Consumer Duty evidence problem.
Without a real system of record spanning every initiative, not a folder of individual project plans, this function is guesswork dressed up as governance. This is precisely the gap a dedicated change portfolio platform is built to close.
Enterprise and board level: performance and portfolio benefit impact
The board and executive committee should not be reviewing individual project statuses, and their interest in this governance model is not primarily who is personally accountable for what. It is performance: what is the change portfolio, taken as a whole, doing to operational performance, customer outcomes and the benefits the organisation committed to when it funded each initiative. This level should own three things:
A portfolio-wide performance and benefit-impact view, showing where concurrent change is degrading operational metrics, error rates, service levels, adoption, or customer satisfaction, against the benefit case that justified the investment in the first place, not a status roll-up of red, amber and green.
The change capacity ceiling, set as an explicit decision: how much combined regulatory-mandated and discretionary change the organisation can absorb in a given period without measurably eroding performance, informed by what the business unit and operations levels are reporting, not set once a year and forgotten.
The trade-off decision when capacity and benefit realisation conflict, deferring or resequencing discretionary transformation when the evidence shows it is putting delivery of committed benefits, or day-to-day performance, at risk. TSB’s board found this out only after the fact; CPS 230 and its international equivalents now expect boards to be asking the question before it happens.
If your board only ever sees a portfolio-wide status summary with no visibility of the performance and benefit impact underneath it, you do not yet have this layer, regardless of how many steering committees exist beneath it.
Customer disclosure obligations are now a change design constraint
Two regimes change what “ready to launch” means for any customer-facing financial services change. Under ASIC’s Design and Distribution Obligations, issuers and distributors must define a target market and take reasonable steps to keep distribution within it on an ongoing basis, not through a one-off disclosure document; ASIC has already secured an $8 million penalty against Firstmac and issued more than 80 preliminary stop orders for DDO contraventions. In the UK, the FCA’s Consumer Duty, in force since July 2023, goes further still, requiring firms to evidence good outcomes across products, price, consumer understanding and consumer support, with an annual board-level assessment of whether they achieved this.
The practical effect is that the customer communications and monitoring plan, historically a downstream deliverable finished once “the real work” was done, is now itself a compliance artefact that has to be designed before a change goes live, not written up afterwards. For any financial services group operating across more than one of these regimes, and most larger insurers and wealth managers do, a single change rolled out on one timeline needs two distinct evidence trails, not one disclosure pack adapted after the fact, because DDO and Consumer Duty ask genuinely different questions of the same change.
Inside the governance model, this obligation sits at the intersection of the operations and business unit levels, and it fails when it is treated as belonging to neither. Three things need to move earlier in the change lifecycle to close that gap:
Target market and product governance checks belong inside the change design phase, reviewed alongside scope and timeline, not bolted on as a compliance sign-off after design is locked.
Frontline readiness and engagement data has to be read alongside the customer communication plan, not separately. If operations-level signals show a team is already stretched, that is a reason to reconsider the timing or intensity of the customer-facing message going out at the same time, not just a resourcing footnote for the business unit to manage quietly.
Consumer-facing changes need enough lead time built into sequencing to construct the outcomes evidence base regulators expect, which the business unit level can only protect if it has visibility of the deadline early, not discover it competing with an unrelated regulatory-mandated change for the same launch window.
Overlapping customer segments need to be visible at portfolio level, because a segment absorbing three separate product changes in one quarter is a consumer-understanding risk even where each change individually cleared its own DDO or Consumer Duty review in isolation.
Two risk domains most governance models still bolt on instead of owning
AI as its own governance lane
APRA’s April 2026 letter to industry, following targeted engagement with large banks, insurers and superannuation trustees, found that “AI governance, risk management and assurance are struggling to keep pace” with adoption, with specific gaps in identity and access management, patch management and testing of AI-generated code. The governance model above answers this directly: an AI-enabled change, a new underwriting model, an AI-assisted advice tool, needs its own line in the enterprise-level performance and benefit-impact view and its own capacity and risk data at the operations and business unit levels, not a place inside the general “technology change” category where AI-specific risk gets diluted into a bucket it does not fit.
Badly managed change as a named operational and legal hazard
Canada’s OSFI Guideline E-21 is unusual among the regimes above in naming change management explicitly as a component of operational risk and resilience regulators expect institutions to govern, not folding it into generic technology or project risk. Australia’s Safe Work Australia Model Code of Practice on psychosocial hazards reaches a parallel conclusion from the workplace health and safety side, naming badly managed change, alongside high job demands and low role clarity, as a specific hazard organisations have a legal duty to identify and control. Read together, these two regimes from two different regulatory traditions are saying the same thing: change load concentration on a team is not a soft people-risk footnote. It belongs in the operations and business unit levels of the governance model as a tracked risk, on the same footing as a system outage or a compliance breach.
For financial services specifically, this hazard concentrates in exactly the operations and frontline teams carrying the heaviest regulatory-mandated load, claims, contact centre, lending operations, the same teams disclosure and prudential regimes place under the most scrutiny. A governance model that tracks capacity and readiness at the operations level is therefore not a parallel wellbeing initiative sitting alongside risk management. It is the same data serving both obligations at once, which is precisely why it belongs in the risk-in-change register rather than a separate HR dashboard nobody in risk or compliance ever sees.
What this looks like in practice
Take a claims operations team absorbing three concurrent changes: a mandatory process update to meet a new disclosure deadline, a core system upgrade, and a discretionary efficiency initiative the business case was signed off eighteen months ago. Under most current governance arrangements, each of these reports green individually, three separate project managers, three separate steering committees, no shared view of the team underneath them. Under the three-level model, operations would have flagged the combined load against real team capacity weeks earlier; the business unit would have used that signal to recommend deferring the discretionary initiative and to hold back the customer communication until the team had capacity to handle the resulting enquiries well, since the disclosure deadline is fixed and the system upgrade is nearly complete; and the enterprise level would have seen the benefit-realisation and performance trade-off explicitly, on the record, rather than discovering it once the team’s error rate, complaint volume or attrition spikes. That is the exact sequence of missing decisions TSB’s post-mortem points to, replayed at a smaller, everyday scale.
A governance model is only as good as the data feeding it. In practice, the financial services change functions doing this well share four disciplined habits.
They maintain a rolling, not point-in-time, change readiness assessment at the operations level, because readiness collected once at project kickoff is stale within weeks in a fast-moving regulatory environment.
They give the board a single portfolio-level view of performance and benefit impact, where regulatory deadlines, capacity and consumer-facing change intersect, rather than a stack of individual project RAG statuses that hide exactly the kind of overlap TSB’s failure exposed.
They treat the organisational structure question, centralised, federated or hybrid change governance, as a deliberate design choice rather than an accident of history; if this decision has not been made explicitly in your organisation, our guide to choosing the right enterprise change management structure is a useful next step.
They tie change delivery to sustained benefit realisation, not milestone completion, so the enterprise level’s capacity-ceiling decisions are informed by what previous change actually protected or delivered, not just what it shipped on time.
None of this is achievable through steering-committee reporting alone. It requires a system of record spanning the whole portfolio that can answer, for any team, at any level, “what is landing here, from every source, this quarter, and what is it doing to performance,” as a standing question rather than a special request pulled together after something has already gone wrong. This is the specific gap a change intelligence platform like Change Compass is built to close for financial services portfolios: giving each governance level, operations, business unit and enterprise, the same live view of change load, sequencing, readiness and benefit impact, rather than three disconnected versions of the truth.
Where governance actually has to start
TSB’s board found out only after the fact what its change portfolio was doing to operational performance and customer outcomes. That is the test worth applying to your own portfolio today: can your board see, right now, the performance and benefit impact of everything landing on your frontline teams this quarter, not just a status roll-up of individual projects. If the answer is no, that is where your governance model needs to start, at whichever of the three levels, operations, business unit or enterprise, currently has the least visibility, before the next regulatory deadline forces you to find out the hard way.
Frequently asked questions
What does governance at the operations, business unit and enterprise level mean for change management? It means splitting change portfolio governance into three distinct levels: operations teams who surface real capacity, readiness and customer-interaction data, a business unit layer that sequences change and aligns frontline readiness with customer communication, and an enterprise or board level that reviews the performance and benefit impact of the whole portfolio and sets the capacity ceiling. Most financial services change functions have committees at each level but rarely this clean a division of what each one actually owns.
Why do financial services regulators increasingly treat change-related operational risk as a board-level issue? Regimes such as Australia’s CPS 230, Canada’s OSFI Guideline E-21, the EU’s DORA and the UK’s Senior Managers regime were all designed to close a gap regulators saw repeatedly: institutional failures where no one at the right level had both the visibility and the authority to prevent them. Some of these regimes go further and require a named accountable individual, but the underlying demand in every case is board-level oversight of the risk change activity creates, not just after-the-fact accountability.
How is change management treated as an operational risk under regimes like CPS 230 and OSFI Guideline E-21? Both regimes require boards to oversee operational risk arising from an institution’s own change activity, not just external threats. OSFI’s Guideline E-21 goes further by explicitly naming change management as a component institutions must govern, alongside business continuity and crisis management, rather than treating it as a generic project management concern.
Why do design and distribution obligations affect how a change is rolled out, not just how it is communicated? DDO and the FCA’s Consumer Duty both require ongoing evidence that a product or service change is reaching its intended market and delivering good customer outcomes, not a one-off disclosure at launch. This means the monitoring and evidence plan has to be designed into the change itself before go-live, rather than treated as a communications task completed afterwards.
Is AI-enabled change different from other technology change in a governance model? Yes. Regulators including APRA have found that AI governance, risk management and assurance are not keeping pace with the speed of AI adoption in financial services. This means AI-enabled change needs its own line in the enterprise-level performance view and its own risk data at the operations and business unit levels, rather than being managed inside a general technology change category where AI-specific risks are easy to miss.
Why should frontline readiness data be linked to customer communication planning? If a frontline team is already stretched by concentrated change load, that is directly relevant to when and how a customer-facing message about that change should go out, because an under-resourced team is more likely to produce inconsistent answers, longer wait times or missed follow-up when customers respond. Treating readiness and customer communication as two separate workstreams is a common reason DDO and Consumer Duty evidence gaps appear even when each team believes it delivered its part correctly.
Most change practitioners build the same thing first: a spreadsheet with a tab for each project, a column for status, and a colour-coded RAG rating that everyone agrees to update “by Friday.” It’s a genuinely good tool, and it can comfortably hold six to eight initiatives if those initiatives are simple: different teams, different timing, no real overlap. Then, without any change in the initiative count, two project teams schedule mandatory training for the same 200 branch staff in the same week, nobody notices until the complaints start, and the practitioner spends the next afternoon reverse-engineering what went wrong from five different versions of the same file. This is not a story about too many initiatives, or bad discipline. It’s what happens when the complexity of the change outgrows a format that was only ever built to list projects, not to show where they collide.
This article is a practical guide to that whole arc. It starts with the spreadsheet almost everyone builds first, including exactly how to build one properly, because there is nothing wrong with starting there. It then covers the specific point where spreadsheet-based tracking stops showing you what you need to see, what that actually costs in hours and in risk, and how to make the case for something better when the time comes. The case, as you’ll see, is not really about saving time. It’s about what a portfolio of change looks like to the people who are betting the year’s strategy on it going well.
The point where spreadsheet-based change initiative tracking breaks down
A spreadsheet is a genuinely good tool for a portfolio of six to eight initiatives, provided the changes themselves are simple: a single stakeholder group each, no shared timing, no shared teams. Each has an owner, a timeline, a handful of stakeholders, and updates happen often enough that one person can keep the file current in their head. The failure mode isn’t sudden, and it isn’t really about count. It creeps in as complexity increases, and by the time it’s obvious, the practitioner has usually been quietly compensating for weeks: cross-checking two tabs by hand before a steering committee meeting, emailing three project managers to confirm a stakeholder count nobody trusts anymore, or maintaining a “master” version that only exists because the shared one kept getting overwritten.
The question worth asking isn’t “how many initiatives are we tracking?” A team running eight straightforward, non-overlapping changes can often stay on a spreadsheet indefinitely. The questions that actually predict whether your tracker is about to fail you are different, and none of them are about volume:
How complex are the changes this team is actually facing, not how many of them there are. A single high-impact system change with five stakeholder groups and three dependencies is harder to track than four simple, contained ones.
What’s the real risk of saturation building up underneath the numbers? A spreadsheet can tell you an initiative count. It can’t easily tell you whether the same people are being asked to absorb change faster than they can adapt.
Where are changes overlapping? Specifically: within one role, within a specific team, within a single week, or within a business unit, carrying more than one change at the same time. This is the question a row-per-initiative format is structurally worst at answering, because the overlap only exists in the relationship between rows, not in any single row.
A spreadsheet can hold the initiative count indefinitely; it’s the saturation and overlap questions it fails on, usually well before the sheet itself looks unmanageable. The signs are consistent enough to check yourself against. Your tracking has stopped working if:
Updating one initiative’s timeline doesn’t automatically update the shared view everyone else is looking at
Two people have edited the file this week and you’re not fully sure whose version is current
You’ve missed, or nearly missed, a scheduling conflict between two initiatives touching the same group of people
Building the monthly executive update takes the better part of a day, most of it spent reconciling data rather than analysing it
Nobody outside your team can self-serve an answer about portfolio status; they all have to ask you
None of these individually is a crisis. Together, they describe a practitioner spending an increasing share of their week being a human database instead of a change professional. The rest of this guide assumes you’re somewhere on that curve, whether you’re building your first tracker or you’re already living with three or four of the symptoms above.
Build a basic change initiative tracker in an hour
If you don’t have a tracker yet, or the one you have has sprawled past usefulness, start here. This is the structure that scales furthest before it needs to be replaced, and it takes about an hour to set up properly.
The three tabs you need
A workable spreadsheet tracker needs exactly three tabs, no more. Extra tabs are usually where trackers go to die, because each one is another place data can drift out of sync with the others.
Initiative log. One row per initiative. Columns: initiative name, sponsor, owner, business unit, start date, go-live date, current status (RAG), and a one-line description. This is your portfolio anchor; every other tab refers back to the initiative name here.
Sample initiative log for a portfolio of six concurrent changes across two business units.
Stakeholder impact matrix. One row per stakeholder group per initiative (so a single initiative touching three teams gets three rows). Columns: initiative name (matched to the log), stakeholder group, headcount, impact type (process, system, role, or location), impact level (high/medium/low), and the week the impact lands.
The same portfolio’s stakeholder impact matrix. The highlighted rows show Branch Tellers and Contact Centre Agents each carrying two initiatives in the same week, an overlap invisible from the initiative log alone.
Timeline view. A simple week-by-week or month-by-month grid, with initiatives as rows and time periods as columns, shaded to show when each initiative is actively impacting people (not just its overall project timeline, but specifically when change hits the ground).
The timeline view of the same portfolio. The July column flags exactly where the overlap sits: two initiatives, one team, one month.
Read on their own, each tab answers a different question: the log tells you what’s running, the matrix tells you who’s carrying it, and the timeline tells you when it lands. Read together, as in the example above, they answer the harder question a spreadsheet is otherwise bad at surfacing: which team, in which week, is quietly carrying two changes at once.
Step-by-step: setting it up
Create the initiative log first and populate it with everything currently running or approved to start in the next quarter. Don’t wait for a “complete” list; add rows as new initiatives are approved.
Build the stakeholder impact matrix as a separate tab, using the initiative name as a lookup key (a simple data validation dropdown pulling from the log keeps names consistent, which matters more than it sounds like it should).
Sum total headcount impact per stakeholder group per week using a pivot table or SUMIFS formula referencing the matrix. This single calculation is the difference between a list of projects and an actual view of change load.
Build the timeline grid manually or with conditional formatting keyed off the start/go-live dates in the log.
Set a fixed weekly or fortnightly cadence to update all three tabs together, and put it in the calendar as a recurring task, not an ad hoc one.
Before every steering committee or portfolio review, manually scan the stakeholder matrix for any group appearing in more than one initiative in the same week. This is the conflict-detection step, and at this stage it has to be done by eye.
This will comfortably serve a portfolio of six to eight concurrent initiatives, as long as they’re relatively simple and don’t share stakeholder groups or timing. It will not comfortably serve a portfolio that’s grown more complex than that, regardless of how few or many initiatives are actually in it, for reasons covered next.
What spreadsheet tracking starts to hide as your portfolio grows
The specific limitation isn’t capacity in a literal sense; a spreadsheet can technically hold a hundred rows as easily as ten. What breaks is the set of questions the format can actually answer. Three facets, in particular, become invisible right when they matter most, which tend to be exactly the facets an executive audience is asking about.
The first is aggregate load over time. A pivot table can sum stakeholder headcount for a single week if you build it correctly, but showing how cumulative change impact rises and falls across a rolling twelve-month view, filterable by division or stakeholder group, requires the kind of dynamic recalculation spreadsheets do badly at scale. This is the same underlying problem addressed by a practical methodology for measuring change saturation: saturation isn’t a property of any single initiative, it’s a property of the portfolio at a point in time, and a tool built around one-row-per-initiative structurally struggles to show it.
The second is cross-initiative conflict detection. Manually scanning a matrix for overlapping stakeholder groups, the way the July column in the timeline example above was found, works fine at six or seven initiatives. At fifteen, with multiple business units, regional variations, and shifting timelines, the manual scan either takes hours or misses things, and it usually does both.
The third is a single, trusted source of truth. The moment more than one person touches the file, version control becomes a live problem. Someone opens the file locally, someone else edits the shared copy, a formula gets accidentally overwritten, and the practitioner ends up spending real time each week confirming which version is “the” version before trusting anything in it enough to present it.
None of this is a criticism of the people building these trackers. It’s a description of what a row-and-column format was never designed to do: represent a dynamic, overlapping, many-to-many system where the same 200 people might sit inside three different initiatives at once, each with a different owner who has no visibility into the other two.
The manual cost of keeping it updated in 2026
The maintenance burden is worth being honest about, because it’s easy to underestimate how much of it is happening in the background of a busy change function.
Where the hours actually go
Every week, someone has to chase updates from initiative owners who are, understandably, more focused on delivering their own project than keeping a shared file current. Every steering committee cycle requires manually reconciling three tabs, checking totals by hand, and rebuilding at least part of the executive-facing view from scratch because the raw data was never structured to present cleanly. This is not unique to change management. Asana’s Anatomy of Work research found that knowledge workers spend roughly 60% of their time on “work about work”: chasing updates, reconciling status, and switching between tools rather than doing the work itself. Manual spreadsheet-based portfolio tracking is a concentrated version of exactly that pattern, sitting inside a function that is meant to be helping the rest of the organisation absorb change, not generating its own administrative load.
The error problem no one budgets for
The other cost is quieter and harder to see until it surfaces at the worst possible moment: error. Spreadsheet error research is one of the more consistently reproduced findings in applied computing, precisely because the format makes mistakes easy to make and hard to catch. A widely cited academic review of the spreadsheet-error literature summarised more than a decade of independent studies with the same conclusion each time: spreadsheet errors are common, not rare, and they are rarely caught by the people who made them, because a formula that returns a plausible-looking wrong number doesn’t announce itself. In a change portfolio tracker, that might mean an impact count that’s silently wrong, a stakeholder group double-counted across two tabs, or a formula that quietly stopped updating three tabs ago. None of that shows up until a number gets challenged in a steering committee, and by then it’s a credibility problem, not just a data problem.
In an environment where every other business function, from finance to sales to operations, is moving toward live dashboards and automated reporting, a change function still reconciling spreadsheets by hand each week looks increasingly like an outlier, and it is one of the more visible signals to executives that the practice hasn’t yet matured to match the rest of the business.
Why the funding conversation should be about risk and adoption, not hours saved
When practitioners eventually ask for budget to move beyond spreadsheets, the instinctive pitch is almost always about time: “this will save the team ten hours a week.” It’s true, and it’s the weakest version of the argument. Ten hours a week is a real but modest line item against most transformation budgets, and it invites an easy counter: hire an analyst, or just accept the manual work as the cost of doing the job.
The stronger argument, and the one that actually lands with a CFO or a transformation sponsor, is that a spreadsheet cannot show them the three things they are actually accountable for.
Risk
Gartner’s research on change fatigue found that the average number of major enterprise changes employees were expected to absorb rose from around two per year in 2016 to roughly ten per year by 2022, while the proportion of employees willing to support organisational change fell from 74% to 38% over the same period. That is a five-fold increase in change volume landing on a workforce that has become dramatically less willing to absorb it, and almost none of that risk is visible from an initiative-by-initiative spreadsheet, because the risk lives in the overlap between initiatives, not inside any single one. An executive asking “what’s our exposure to change fatigue this quarter” cannot get a real answer from a tool that was never built to show cumulative load across a portfolio.
Adoption
Portfolio blindness doesn’t just create fatigue risk; it actively undermines the return on the initiatives themselves. McKinsey’s research on large-scale transformations found that, on average, only about 2% of employees are directly involved in shaping a typical transformation effort, and organisations that meaningfully expand that participation see substantially better outcomes. Every initiative competing for the same finite attention, without a portfolio-level view of who is already stretched thin, makes that problem worse, not better. Adoption isn’t just a property of how well one initiative was managed; it’s a property of how much room the people affected actually had to adopt it, and that’s a portfolio-level question a spreadsheet isn’t structured to answer.
Capacity
Prosci’s Best Practices research found that 73% of organisations report being near, at, or beyond their change saturation point, largely because, as Prosci’s own analysis notes, no one in the organisation is keeping a genuine portfolio view of everything underway at once. That is precisely the gap a spreadsheet-based tracker leaves open even when it’s being maintained conscientiously: it tracks initiatives, not the cumulative capacity being drawn down across all of them.
Put those three together and the funding conversation changes shape entirely. You are no longer asking for a tool that saves the team time. You are asking for the organisation’s only reliable early-warning system for change fatigue, adoption failure, and capacity overrun across a portfolio worth, in most enterprises, many multiples of what the tool itself costs. That is the argument that gets budget approved, because it is framed in terms executives are already accountable for, not in terms of a practitioner’s weekly workload. It is also, not coincidentally, the same reframe that works when building the broader business case for change management investment: risk avoided and adoption protected are usually larger, more defensible numbers than hours saved, and they are the numbers a CFO already has a mental model for evaluating.
When to move from a spreadsheet to dedicated change initiative tracking software
There’s no single headcount that marks the exact moment to switch, and initiative count on its own is a weak signal, as the earlier reframe should make clear. A short, honest checklist gets most practitioners to the right answer. If two or more of the following are true, the spreadsheet is very likely costing more than a dedicated platform would:
You’ve moved past eight or so concurrent initiatives, or fewer than that but complex and overlapping (shared stakeholder groups, shared timing, shared business units)
More than one person needs to update or rely on the tracker
You produce a portfolio-level executive report on a recurring cycle (monthly or more often)
You’ve had, or narrowly avoided, a scheduling or stakeholder conflict between initiatives in the last quarter
Building the executive update takes longer than actually analysing what it shows
Leadership is asking questions about the portfolio (saturation, capacity, sequencing) that the spreadsheet structurally can’t answer
If that’s you, the natural next step is evaluating dedicated change initiative tracking software rather than continuing to patch the spreadsheet. That evaluation is its own piece of work, and a buyer’s guide covering the criteria that actually separate a real change portfolio tool from a generic project tracker is worth reading in full before shortlisting vendors, because the features that matter here (aggregation logic, saturation modelling, conflict detection) rarely show up clearly in a sales demo unless you know to ask for them specifically.
What a change intelligence platform gives you that a spreadsheet never can
This is where a platform like Change Compass earns its place, not as a fancier spreadsheet, but as a structurally different tool. Instead of one row per initiative that has to be manually cross-referenced against every other row, a dedicated change intelligence platform aggregates stakeholder impact automatically across every initiative in the portfolio, in real time, as initiative owners update their own data. The same 200 branch staff appearing in three initiatives in the same week shows up as a visible spike the moment the third initiative is entered, not three weeks later when someone happens to notice.
That structural difference is what the case for treating a change intelligence platform as core infrastructure actually rests on: change data, like HR data or financial data, only becomes useful at the moment it can be aggregated, queried, and trusted as a single source of truth, rather than reassembled by hand each reporting cycle. A spreadsheet can describe individual initiatives well. It cannot, by design, become that kind of system of record. Everything covered above, saturation visibility, conflict detection, a version-controlled shared view, executive reporting without a day of manual reconciliation, comes from that one structural shift, not from any single feature.
Start with a spreadsheet. Just don’t stay there.
There’s nothing wrong with building your first change portfolio tracker in Excel. It’s a genuinely good tool for six to eight simple initiatives, and the template in this guide will comfortably see most practitioners through their first year of managing concurrent change. The mistake isn’t starting there. It’s mistaking initiative count for the real signal, and staying on a spreadsheet past the point where the format can show what the organisation actually needs to see: how complex the change has become, how close the portfolio is to saturation, and where changes are overlapping on the same team, role, or business unit in the same week. Then, when the funding conversation comes, lead with risk and adoption, not hours. That’s the version of the pitch that gets funded.
Frequently asked questions
What is change initiative tracking software?
Change initiative tracking software is a purpose-built platform for managing multiple concurrent organisational change initiatives, as distinct from generic project management tools. It typically aggregates stakeholder impact data across initiatives, visualises change load and saturation over time, and flags scheduling or capacity conflicts automatically, rather than requiring manual cross-referencing.
Can I track multiple change initiatives in Excel?
Yes, and it’s the right starting point for most practitioners. A spreadsheet can comfortably handle six to eight concurrent initiatives, provided they’re relatively simple: different stakeholder groups, different timing, no real overlap. Use a three-tab structure (initiative log, stakeholder impact matrix, timeline view) with the initiative name as a shared lookup key across tabs, and set a fixed update cadence. What actually limits a spreadsheet isn’t the initiative count, it’s complexity and overlap: the same stakeholder group appearing in two initiatives in the same week is a much stronger signal that the format is breaking down than the number of tabs you’re maintaining.
How do you know when it’s time to move from a spreadsheet to dedicated software?
Two or more of the following are a reliable signal: you’ve moved well past eight concurrent initiatives, or have fewer than that but they’re complex and overlapping; you can’t say which team or role is carrying the most concurrent change this month, only how many initiatives exist in total; more than one person is maintaining the tracker; there’s a recurring executive reporting cycle; there’s been a recent near-miss on a stakeholder conflict; the executive update takes longer to build than to present; or leadership is asking portfolio-level questions (saturation, capacity, sequencing) the spreadsheet can’t answer.
What should a change portfolio funding request focus on?
Not hours saved. The stronger case is built on the three things a spreadsheet structurally can’t show an executive: change fatigue risk building up across the portfolio, adoption being undermined by initiatives competing for the same limited attention, and capacity being drawn down faster than the organisation can see. These map to risks executives are already accountable for, which makes the funding case easier to approve than a productivity argument.
How many change initiatives can a spreadsheet actually handle?
Volume alone isn’t the right measure. A spreadsheet can comfortably hold six to eight simple, non-overlapping initiatives, but a portfolio of three or four complex, overlapping initiatives will break it faster than eight simple ones will. The three questions that actually matter are how complex the changes are (not how many there are), how close the portfolio is to saturation, and whether changes are overlapping within the same role, team, week, or business unit.
What’s the difference between a project tracker and a change portfolio platform?
A project tracker, spreadsheet or software, is organised around delivery milestones for individual initiatives. A change portfolio platform is organised around cumulative impact on the people affected, aggregating stakeholder load, saturation, and adoption risk across every concurrent initiative at once, which is a structurally different question than “is this project on schedule.”
