Most organisations treat change management as something that happens within projects. A sponsor is appointed, a communication plan is written, some training is delivered, and the initiative moves on. Then the next project starts, and the whole cycle repeats from scratch, as if the organisation learned nothing from the last one.
This project-by-project approach is the hallmark of low change management maturity. And it has a measurable cost. Prosci’s research shows that organisations with excellent change management are seven times more likely to meet project objectives. WTW’s 2023 global study of 600 organisations found that companies taking a proactive, data-driven approach to change management drove nearly three times more revenue than those with below-average change effectiveness. These results do not come from applying change management to one project at a time. They come from building it as a permanent organisational capability.
This guide provides a practical framework for assessing and advancing your organisation’s change management maturity, moving from ad hoc project support to embedded organisational competency.
What change management maturity means
Change management maturity describes the degree to which an organisation has embedded change management as a consistent, scalable, and continuously improving capability, rather than an activity performed inconsistently within individual projects.
Two established models have shaped the field. The Prosci Change Management Maturity Model evaluates organisations across five capability areas: leadership, application, competencies, standardisation, and socialisation. The Change Management Institute (CMI) model takes a similar five-level approach but emphasises three domains: project change management, business change readiness, and strategic change leadership.
Both models share a core insight: maturity is not about doing change management on more projects. It is about building the systems, governance, leadership behaviours, and measurement practices that make effective change management the default way the organisation operates.
The five levels of change management maturity
While the Prosci and CMI models differ in their specifics, they converge on a five-level progression. The framework below synthesises both into a practical model you can use for self-assessment.
| Level | Name | Characteristics | Typical pain points | |——-|——|—————-|——————-| | 1 | Ad hoc | No consistent CM approach. Success depends on individual heroics. | Repeated mistakes, no institutional learning, inconsistent stakeholder experience | | 2 | Emerging | Some projects apply CM, but methods and quality vary widely. | Pockets of excellence alongside projects with no CM at all; no shared tools or templates | | 3 | Standardised | Organisation-wide CM standards exist. Common tools, templates, and training. | Standards exist on paper but are not consistently enforced; compliance is uneven | | 4 | Managed | CM integrated into project governance. Metrics tracked and reported. Portfolio-level visibility. | Governance can feel bureaucratic; risk of CM becoming a checkbox exercise rather than strategic | | 5 | Optimised | CM is a core organisational competency. Continuous improvement, data-driven, enterprise-wide. | Maintaining momentum; avoiding complacency; adapting to new types of change (AI, automation) |
Most organisations sit at Level 1 or 2. Gartner’s research found that only 32% of business leaders report achieving healthy change adoption, which suggests that the majority of organisations have not yet built the capability infrastructure needed for consistent success.
Diagnosing your current maturity level
Before you can advance maturity, you need to know where you are. The following diagnostic questions map to each level and can be used as a practical self-assessment.
Level 1 diagnostic: Ad hoc
Is change management applied inconsistently, with some projects having dedicated CM support and others having none?
Do project teams create their own approaches from scratch each time?
Is there no central function, community of practice, or shared methodology for change management?
If you answered yes to most of these, your organisation is at Level 1. The priority is to establish a baseline methodology and begin demonstrating value on a small number of visible projects.
Level 2 diagnostic: Emerging
Do some project teams apply change management using a recognised methodology, but others do not?
Are there pockets of CM expertise but no organisation-wide standard?
Is change management viewed as a project-level activity rather than an organisational capability?
Level 2 organisations need to standardise their approach, building shared tools, templates, and training that create consistency across the project portfolio.
Level 3 diagnostic: Standardised
Does the organisation have a documented CM methodology, standard templates, and training programmes?
Are change practitioners trained in a common approach?
Is CM expected on all significant projects, even if enforcement is inconsistent?
Level 3 organisations have the foundations in place. The challenge is moving from standards that exist to standards that are enforced and integrated into governance. For more on building assessment capability, see our guide to change management assessments.
Level 4 diagnostic: Managed
Is CM formally integrated into project governance (gate reviews, investment decisions, steering committees)?
Are CM metrics tracked, reported, and used to inform decisions?
Does the organisation assess change at the portfolio level, not just initiative by initiative?
Is there executive-level accountability for change management effectiveness?
Level 4 organisations are performing well. The opportunity is to move from managed governance to true organisational capability, where CM is embedded in culture, not just process.
Level 5 diagnostic: Optimised
Is CM viewed as a strategic organisational competency, not a project support function?
Does the organisation continuously improve its CM practices based on data and lessons learned?
Are leaders at all levels competent in change leadership, not just change practitioners?
Is change management integrated into strategic planning, not just project delivery?
Level 5 is rare. Organisations that reach it treat change capability as a competitive advantage and invest accordingly.
The business case for investing in change management maturity
The evidence linking maturity to performance is strong and growing.
McKinsey’s research found that only 26% of transformations succeed at both improving performance and sustaining those improvements. However, organisations that take a rigorous, structured approach report success rates of 79%, three times the average. That gap represents the difference between ad hoc project-level change management and mature, systematic capability.
The financial implications are equally clear. WTW’s research found that “change accelerator” organisations outperformed on one-year revenue change (6% versus -30% for less capable organisations), three-year revenue growth (4% versus -7%), and gross profit margin (19% versus -13%).
These are not marginal differences. They represent the compounding effect of consistently managing change well across the entire organisation, which is precisely what maturity enables.
Common maturity traps to avoid
The journey from Level 1 to Level 5 is not linear, and several common mistakes can stall progress or create the illusion of maturity without the substance.
Over-investing in training without governance
Sending 200 people through change management certification does not build maturity if there is no governance framework requiring them to apply what they learned. Training builds individual competency; maturity requires organisational systems that activate and sustain that competency.
Confusing activity with capability
An organisation that produces change impact assessments, communication plans, and training schedules for every project may look mature. But if those artefacts are produced by rote without influencing decisions, they are documentation, not capability. True capability means the organisation uses change management data to make different decisions than it would otherwise make.
Trying to jump levels
Organisations at Level 1 sometimes attempt to leap directly to Level 4 by implementing enterprise-wide governance without first building the foundational methodology and skills. This typically produces a bureaucratic framework that practitioners resent and circumvent. Each level builds on the one below it.
Treating maturity as a destination
Level 5 is not a finish line. Organisations that reach high maturity must continue investing to maintain it, adapting their practices to new types of change (AI-driven transformation, continuous delivery models, distributed workforces) and refreshing their capability as experienced practitioners move on.
How to advance from your current level
Moving from Level 1 to Level 2
Focus on demonstrating value. Select 2-3 high-visibility projects and apply a structured CM methodology rigorously. Document outcomes and build an internal evidence base. Establish a small community of practice to begin sharing approaches and lessons learned.
Moving from Level 2 to Level 3
Standardise the methodology. Create organisation-wide templates, tools, and training. Establish minimum CM requirements for all projects above a defined threshold. Build or hire a central CM capability that supports project teams.
Moving from Level 3 to Level 4
Integrate CM into governance. Add CM criteria to project gate reviews and investment decisions. Build portfolio-level visibility of change load and adoption. Establish metrics and reporting that reach executive leadership. See our guide on measuring change management outcomes for practical measurement frameworks.
Moving from Level 4 to Level 5
Embed CM into culture. Develop change leadership competency at all management levels, not just among CM practitioners. Build continuous improvement mechanisms that use data to refine practices. Integrate CM into strategic planning, not just project delivery. Invest in digital platforms that enable real-time, portfolio-wide change intelligence.
How digital platforms accelerate maturity
Building change management maturity at Levels 3-5 requires data infrastructure that manual methods cannot provide. Portfolio-level visibility, real-time adoption tracking, cumulative impact analysis, and measurement dashboards all require tooling.
Digital change management platforms such as The Change Compass enable organisations to manage change at the portfolio level, visualise cumulative impact across stakeholder groups, and track adoption metrics in real time. This is particularly valuable for organisations at Level 3 and above, where the shift from project-level to portfolio-level capability requires data that spreadsheets and manual processes cannot sustain. For organisations moving beyond heatmaps toward dynamic analytics, digital platforms are not optional; they are foundational.
Change management maturity is not about achieving a perfect score on a model. It is about building the organisational capability to manage change consistently, measure its impact rigorously, and improve continuously. Start by diagnosing where you are today using the five-level framework. Identify the specific gaps between your current level and the next. Invest in the systems, governance, skills, and leadership behaviours that will close those gaps. The organisations that build change management maturity do not just deliver better individual projects; they build a compounding advantage that makes every subsequent transformation more likely to succeed.
Frequently asked questions
What is change management maturity? Change management maturity describes the degree to which an organisation has embedded change management as a consistent, scalable, and continuously improving capability. It progresses through five levels, from ad hoc project support to a core organisational competency integrated into governance, culture, and strategic planning.
How long does it take to advance change management maturity? Moving one level typically takes 12-24 months of sustained effort. Moving from Level 1 to Level 3 can take 2-4 years. Progress depends on executive sponsorship, investment in capability building, and willingness to integrate CM into governance. Trying to compress timelines by skipping levels typically backfires.
Do you need a consultant to build change management maturity? External consultants can accelerate specific stages, particularly initial methodology design and benchmarking against industry peers. However, sustainable maturity must be built internally. The most effective approach is to use external expertise to establish foundations and transfer capability, then build and maintain maturity through internal teams and systems.
What is the relationship between change management maturity and organisational culture? Culture and maturity reinforce each other. An organisation with a strong change culture, where leaders model adaptive behaviours and employees expect continuous improvement, will find it easier to advance maturity. Conversely, building maturity practices (governance, measurement, shared methodology) gradually shifts culture toward greater change capability. Neither can be built in isolation.
Can an organisation be at different maturity levels for different types of change? Yes. Many organisations demonstrate higher maturity for technology-driven changes (where project methodologies enforce CM) than for cultural or structural changes. This is common and worth diagnosing explicitly, as it reveals where targeted investment is needed.
How do you measure change management maturity? Use a structured self-assessment against the five maturity levels, evaluating capability areas such as methodology standardisation, governance integration, leadership competency, measurement practices, and portfolio-level visibility. Complement self-assessment with benchmarking against industry standards (Prosci or CMI models) and track progress annually.
Suggested title: Change management maturity: a practical guide to building organisational capability
Suggested meta description: Assess your change management maturity across 5 levels with diagnostic questions and a practical framework for advancing organisational capability.
How can understanding the change adoption curve benefit organizations?
Understanding the change adoption curve benefits organizations by identifying how different individuals or groups respond to change. By recognizing these stages—innovators, early adopters, early majority, late majority, and laggards—companies can tailor their strategies to enhance communication, support, and ultimately improve the success of change initiatives.
Measuring change adoption is one of the most important parts of the work of change practitioners. It is the ultimate ‘proof’ of whether the change interventions have been successful or not in achieving the initiative objectives. It is also an important way in which the progress of change management can clearly be shown to the project team as well as to various stakeholder groups. The ability to show clearly the progress of change outcome is critical to focus your stakeholders’ actions on the right areas. It is one of the key ways to ‘prove your worth’ as a change practitioner.
Measurement takes time, focus and effort. It may not be something that is a quick exercise. There needs to be precise data measurement design, a reliable way of collecting data, and data visualisation that is easily understood by stakeholders.
With the right measurements of change adoption, you can influence the direction of the initiative, create impetus amongst senior stakeholders, and steer the organisation toward a common goal to realise the change objectives. Such is the power of measuring change adoption.
The myth of the change management curve
One of the most popular graphs in change management, and often referred to as the ‘change curve’, is the Kubler-Ross model that outlines the stages of personal transition. The model was specifically designed by psychiatrist Elisabeth Kubler-Ross to refer to terminally ill patients as a part of the book ‘On Death and Dying’. For whatever reason, it has somehow gained popularity and application in change management, making it crucial to be very careful when applying this model to address potential adoption barriers in a change context.
There is little research evidence to back this up even in psychological research. When applied in change management, there is no known research that supports this at all. So be careful when you come across models such as this one that is simple and seem intuitively ‘correct’, as they may overlook stakeholders’ voices and input, which can lead to new ideas. On the other hand, there is ample research by McKinsey that shows the best way for effectively managed initiatives and transformations is that stakeholders do not go through this ‘valley of death’ journey at all.
If the ‘change curve’ is not the correct chart to follow with regard to change adoption, then what is the right one to refer to? Good question.
The ‘S’ curve of change adoption is one that can be referenced. It is well backed in terms of research from technology and new product adoption. It begins with a typically slow start followed by a significant climb in adoption followed by a flattened level at the end. Most users typically do not uptake the change until later on.
Here is an example of key technologies and the speed of adoption in U.S. households since the 1900s.
With the different types of change contexts, the shape of the S curve will be expected to differ as a result. For example, you are working on a fairly minor process change where there is not a big leap in going from the current process to the new process. In this case, the curve would be expected to be a lot more gentle since the complexity of the change is significantly less than adopting a complex, new technology.
On the other hand, if you are working on many iterative agile changes, each iteration that impacts users may be a small S curve in themselves. Ideally, each iteration work together towards a greater piece of overarching change.
Going beyond what is typically measured
Most change practitioners are focused on measuring the easier and more obvious measures such as stakeholder perceptions, change readiness, and training completion. Whilst these are of value, they in themselves are only measuring certain aspects of the change process. They can be viewed as forward-looking indications of the progress that supports moving toward eventual change adoption, versus the eventual change adoption.
To really address head-on the topic of measuring adoption of new products, it is critical to go beyond these initial measures toward those elements that indicate the actual change in the organisation, especially focusing on early adopters. Depending on the type of change this could be system usage, behaviour change, following a new process or achieving cost savings targets.
Project Benefit realization
It goes without saying that to really measure change adoption the change practitioner must work closely with the project manager to understand in detail the benefits targeted, and how the prescribed benefits will be measured. The project manager could utilise a range of ways to articulate the benefits of the project. Common benefit categories include:
Business success factors such as financial targets on revenue or cost
Product integration measures such as usage rate
Market objectives such as revenue target, user base, etc.
These categories above are objectives that are easier to measure and tangible to quantify. However, there could also be less tangible targets such as:
Competitive positioning
Employee relations
Employee experience
There could be various economic methods of determining the targeted benefit objectives. These include payback time or the length of time from project initiation until the cumulative cash flow becomes positive, or net present value, or internal rate of return on a new tool.
Employee capability
Customer experience
There could be various economic methods of determining the targeted benefit objectives. These include payback time or the length of time from project initiation until the cumulative cash flow becomes positive, or net present value, or internal rate of return.
The critical aspect for change practitioners is to understand what the benefit objectives are, how benefit tracking will be measured and to interpret what steps are required to get there. These steps include any change management steps required to get from the current state to the future state.
Here is an example of a mapping of change management steps required in different benefit targets:
Increased customer satisfaction and improved productivity through implementing a new system. | Users able to operate the new system.Users able to improve customer conversations leveraging new system features.Users proactively use the new system features to drive improved customer conversations.Managers coaching and provide feedback to usersBenefit tracking and communications.Customer communication about improved system and processesDecreased customer call waiting time . | % of users passed training test.System feature usage rate.Customer issue resolution time.User feedback on manager coaching.Monthly benefit tracking shared and discussed in team meetings.Customer satisfaction rate. Customer call volume handling capacity.
Measuring behavioural change
For most change initiatives, there is an element of behaviour change, especially for more complex changes. Whether the change involves a system implementation, changing a process or launching a new product, behaviour change is involved. In a system implementation context, the behaviour may be different ways of operating the system in performing their roles. For a process change, there may be different operating steps which need to take place that defers from the previous steps. The focus on behaviour change aims to zoom in on core behaviours that need to change to lead to the initiative outcome being achieved.
How do we identify these behaviours in a meaningful way so that they can be identified, described, modelled, and measured?
The following are tips for identifying the right behaviours to measure:
Behaviours should be observable. They are not thoughts or attitudes, so behaviours need to be observable by others
Aim to target the right level of behaviour. Behaviours should not be so minute that they are too tedious to measure, e.g. click a button in a system. They also should not be so broad that it is hard to measure them overall, e.g. proactively understand customer concerns vs. what is more tangible such as asked questions about customer needs in XXX areas during customer interactions.
Behaviours are usually exhibited after some kind of ‘trigger’, for example, when the customer agent hear certain words such as ‘not happy’ or ‘would like to report’ from the customer that they may need to treat this as a customer complaint by following the new customer complaint process. Identifying these triggers will help you measure those behaviours.
Achieve a balance by not measuring too many behaviours since this will create additional work for the project team. However, ensure a sufficient number of behaviours are measured to assess benefit realisation
Measuring micro-behaviours
Behaviour change can seem over-encompassing and elusive. However, it may not need to be this. Rather than focusing on a wide set of behaviours that may take a significant period of time to sift, focusing on ‘micro-behaviours’ can be more practical and measurable. Micro-behaviours are simply small observable behaviours that are small step-stone behaviours vs a cluster of behaviours.
For example, a typical behaviour change for customer service reps may be to improve customer experience or to establish customer rapport. However, breaking these broad behaviours down into small specific behaviours may be much easier to target and achieve results.
For example, micro-behaviours to improve customer rapport may include:
User the customer’s name, “Is it OK if I call you Michelle?”
Build initial rapport, “How has your day been?”
Reflect on the customer’s feeling, “I’m hearing that it must have been frustrating”
Agree on next steps, “would it help if I escalate this issue for you?”
Each of these micro-behaviours may be measured using call-listening ratings and may either be a yes/no or a rating based assessment.
After having designed the right measurement to measure your change adoption, the next step would be to design the right reporting process. Key considerations in planning and executing on the reporting process includes:
Ease of reporting, you should aim to automate where possible to reduce the overhead burden and manual work involved. Whenever feasible leverage automation tools and in-app options to move fast and not be bogged down by tedious work
Build expectations on contribution to measurement. Rally your stakeholder support so that it is clear the data contribution required to measure and track change adoption
Design eye-catching and easy to understand dashboard of change adoption metrics.
Design reinforcing mechanisms. If your measurement requires people’s input, ensure you design the right reinforcing mechanisms to ensure you get the data you are seeking for. Human nature is so that whenever possible, people would err on the side of not contributing to a survey unless there are explicit consequences of not filling out the survey.
Recipients of change adoption measurement. Think about the distribution list of those who should receive the measurement tracking. This includes not just those who are in charge of realising the benefits (i.e. business leaders), but also those who contribute to the adoption process, e.g. middle or first-line managers.
Example of change adoption dashboard from Change Automator
Measuring Adoption Across Initiatives
You may be driving multiple initiatives as a part of a large program or a portfolio of initiatives. The key challenge here is to establish common adoption measures that are apple-to-apple metrics comparisons across initiatives. Yes, each initiatives will most likely have different sets of what constitutes adoption. However, there are still common ways to report on adoption across initiatives such as overall percentage of adoption of identified adoption elements, or percentage of the number of milestones reached. You can also utilise manager reports of behaviours adopted, as well as system records of utilisation of certain features for example.
Understanding change adoption is not only helpful to understand what works for one initiative, it can also be a linchpin to help you scale change adoption across change initiatives across your whole portfolio. Talk to us to find out more about how The Change Compass, a digital adoption platform, can help you understand what change interventions lead to higher change adoption rates in the flow of work, through data. Using a data-led approach in deciphering what drives change adoption can truly drive successful change outcomes.
Change adoption refers to the extent to which employees have actually changed their behaviour to work in the new way required by a change initiative. Full adoption means the new behaviour has been embedded and the old way of working has been replaced. Partial adoption – where employees comply in some contexts but revert to old habits in others – is a common failure mode that is often mistaken for success.
How long does change adoption take?
Simple process changes may reach full adoption within 30-60 days of go-live. Significant system changes or behavioural changes typically take 90-180 days to reach stable adoption. Cultural or leadership changes may take 12-24 months or more to fully embed.
What is the difference between change adoption and change compliance?
Compliance is doing the required thing when observed or required; adoption is doing the new thing consistently because it has become the normal way of working. Employees who are complying but not adopting will revert to old behaviours when oversight is reduced.
In the world of scaled agile, “Release on Demand” is a concept that has profound implications for agile teams and their project approaches. It guides teams on how to release and deliver value when stakeholders and customers are truly ready to receive it. However, a crucial, often-overlooked factor in this concept is the role of change management. While Release on Demand has primarily been framed as a technical approach within the Scaled Agile Framework (SAFe), the readiness of people—including end-users, stakeholders, customers, and partners—forms an equally vital part of determining the demand for release.
As change management practitioners, understanding and actively shaping “Release on Demand” can significantly impact project outcomes. In this article, we’ll explore how change management can enhance this core SAFe concept through strategic timing, prioritisation, and thoughtful execution of each release. We’ll also discuss how to structure governance cadences to ensure operational and people readiness, going beyond the technical lens.
Understanding Release on Demand in SAFe
Within SAFe, Release on Demand means that project outputs or new functionality are delivered when the organisation, teams, and stakeholders are ready to adopt and benefit from it. It enables flexible delivery rather than a rigid release schedule. The four key activities for Release on Demand are:
Release – Delivering the product or change to users.
Stabilise and Operate – Ensuring the release is operationally sound and running smoothly.
Measure and Learn – Assessing the release’s impact and learning from the results.
Adjust – Making necessary improvements based on insights gained.
The goal of these activities is to minimise risk, gather user feedback, and optimise the release to maximise impact. While these steps seem straightforward, they demand thoughtful change management to ensure all stakeholders are prepared to support, use, and benefit from the release. Let’s delve deeper into how a change management approach can strengthen each of these activities.
People Readiness as the Core Demand Factor
The “demand” for a release is often misunderstood as being purely about project or market readiness. However, the reality is that it depends on multiple factors, including how ready people are to adopt the change. For any release to succeed, people readiness is crucial and requires focus on:
End-User Readiness: Ensuring that end-users are prepared for the new tools, processes, or functionalities. This could mean conducting user training, crafting support resources, and managing expectations.
Stakeholder Readiness: Stakeholders at all levels need to understand the change, its rationale, and its anticipated impact. This may involve regular briefings, updates, and even individual consultations.
Customer and Partner Readiness: For customer-facing or partner-facing releases, it’s essential to gauge external readiness as well. A clear communication plan and alignment of goals with partners or clients can smooth the path for a successful launch.
These readiness efforts form a significant part of the “demand” in Release on Demand and reflect the reality that people’s capacity to adapt often determines when a release will be genuinely effective.
The Broader Change Landscape
People readiness isn’t only determined by a single project or team but by the broader change landscape within an organisation. Multiple changes or ongoing initiatives can either enhance or inhibit readiness for a new release. For instance, if an organisation is already undergoing a significant digital transformation, adding another change may lead to overload and resistance.
Change practitioners should map the change landscape to identify concurrent changes and evaluate how these may impact readiness for Release on Demand. By assessing the timing and impact of other changes, change managers can:
Avoid change fatigue by spacing out initiatives.
Synchronize related changes to reduce redundancy.
Communicate the overall strategic direction to help stakeholders and users understand how individual changes fit into the bigger picture.
By accounting for these interdependencies, change management can improve people readiness and ensure the Release on Demand aligns with the organisation’s capacity to handle it.
Applying the Four Key Steps in Release on Demand
Let’s explore how change management activities can amplify each of the four Release on Demand steps:
1. Release: The release phase requires both technical and people preparation. Beyond deploying the technical elements, change management practitioners should:
Develop targeted communication plans to inform all affected stakeholders.
Offer targeted training sessions or resources that build users’ confidence and competence.
Ensure adequate support is in place for the transition, including help desks or peer mentoring.
2. Stabilise and Operate: After a release, it’s crucial to monitor adoption and support operational stability. The change team can:
Collect feedback from end-users and support staff on initial challenges and address these promptly.
Identify and celebrate quick wins that demonstrate the release’s value.
Work closely with operations teams to resolve any unforeseen issues that may inhibit adoption or cause frustration.
3. Measure and Learn: This step goes beyond tracking technical metrics and should also capture change-specific insights. Change management can contribute by:
Conducting surveys, interviews, or focus groups to gauge user and stakeholder sentiment.
Monitoring adoption rates and identifying any training gaps or knowledge shortfalls.
Collaborating with product or project teams to share insights that may refine or prioritisation subsequent releases.
4. Adjust: Based on insights gained from the Measure and Learn phase, change managers can advise on necessary adjustments. These might include:
Refining future communication and training plans based on user feedback.
Addressing any gaps in stakeholder support or sponsorship.
Adjusting the timing of subsequent releases to better align with people readiness.
The iterative nature of these four steps aligns well with agile methodologies, allowing change managers to continuously refine and enhance their approach.
The Critical Role of Sequencing, Prioritisation, and Timing
FFor change management practitioners, Release on Demand isn’t just about executing steps—it’s about doing so in the right sequence and at the right time. The impact of a release depends significantly on when it occurs, who is prepared for it, and how well each group’s readiness aligns with the release cadence and continuous integration.
Here are some tips to help change managers get the timing right:
Analyze stakeholder engagement levels: Regularly assess how engaged and ready stakeholders are, tailoring messaging and interventions based on their feedback and sentiment.
Prioritisation change activities based on impact: Not all releases will have the same impact, so change teams should focus resources on those that require the most user readiness efforts.
Create phased rollouts: If full-scale readiness across the board isn’t achievable, a phased rollout can provide users with time to adapt, while allowing the change team to address any emergent issues in stages.
By managing the release cadence thoughtfully, change managers can avoid the disruptions caused by hasty releases and ensure the deployment feels both manageable and meaningful for users.
Release governance in SAFe is often perceived as a predominantly technical or project-focused process. However, effective governance should encompass business operations and people readiness as well. Change management plays a pivotal role in designing governance cadences that account for these critical aspects.
To integrate change governance within release governance, change practitioners should:
Establish clear communication channels with project teams and product owners to ensure people readiness factors are consistently part of release discussions.
Implement a readiness checklist that includes technical, operational, and people readiness criteria. This checklist should be reviewed and signed off by relevant stakeholders before any release.
Maintain a cadence of review and feedback sessions where project teams, change managers, and stakeholders discuss readiness progress, key risks, and post-release outcomes.
This approach ensures that each release is evaluated from multiple perspectives, minimising disruption and maximising its potential for success.
The above is from Scaledagileframework.com
Developing a Change Cadence that Complements Agile Delivery
SAFe’s principle of “develop on cadence; release on demand” is central to effective agile delivery. For change management practitioners, developing a strong change cadence is equally important. This cadence, or rhythm of activities, aligns with the agile teams’ development cadence and helps build stakeholder momentum, maintain engagement, and reduce surprises.
Here’s how to develop a cadence that works in tandem with agile teams:
Planning Cadence: Hold regular planning sessions to align change activities with upcoming releases and identify readiness gaps. This could be quarterly for major releases or bi-weekly for smaller, iterative releases.
Execution Cadence: Establish a reliable cycle for change interventions, such as training, communication, and stakeholder meetings. This cadence helps stakeholders build expectations and fosters a predictable rhythm in change activities.
Feedback Cadence: Collect feedback at consistent intervals, aligning it with release intervals or sprint reviews. Consistent feedback keeps the change process agile and responsive to evolving needs.
A well-defined change cadence not only prepares users effectively but also reinforces trust and transparency in the change process.
Release on Demand may have originated as a technical concept within SAFe, but its success is deeply tied to how well people, stakeholders, and users are prepared for each release. For change management practitioners, Release on Demand is an opportunity to enhance the broader release process by prioritizing people readiness, orchestrating thoughtful sequencing, and establishing governance that prioritisations user success as much as project outcomes.
By proactively engaging in each of the four stages of Release on Demand—Release, Stabilise and Operate, Measure and Learn, and Adjust—change management can ensure releases are not just technically ready but fully integrated into the people and business context they serve. Embracing this role allows change managers to become essential partners in agile delivery, maximising the impact of each release for end-users, the organisation, and the overall success of the project.
Every change leader has seen the heat map. It sits in the deck, a grid of red, amber and green cells showing which business units are being hit hardest over the next 12 months. The leadership team glances at the red cells, nods gravely, and the meeting moves on. Decisions are made. Resources are allocated.
But here is the problem: the heat map may be the most widely used change planning tool in organisations today, and one of the most misleading. It answers the wrong question. It flattens nuanced impact into a single colour. And it creates a false sense of certainty that can actively harm your change planning.
This article is a change management heat map explained for senior practitioners. We will cover what a heat map is, where it genuinely adds value, and why relying on it as your primary decision-making tool puts your programme at risk. We will also explore what better approaches look like in practice.
What is a change management heat map?
A change management heat map is a visual tool that maps the volume or intensity of change impacts across an organisation over time. Typically displayed as a grid, it plots business units or employee groups on one axis against a timeline on the other. Each cell is colour-coded, usually using a traffic light system, to indicate the relative level of change exposure.
The premise is straightforward: where the cells are red, change intensity is high. Where they are green, the change load is manageable. Leaders can scan the map quickly and form a view of where the organisation is under pressure.
According to a 2024 review of change management decision-making tools on ResearchGate, organisations that use structured, visual change data to support planning decisions are significantly more likely to align stakeholders and maintain project momentum than those relying on narrative reporting alone. That finding reflects why heat maps became popular, they translate complex programme data into something immediately scannable for executives. Their appeal is real.
How heat maps are constructed in practice
Most heat maps are built by change managers or PMO leads who collect data from individual project teams, typically asking each team to rate how much impact their initiative will have on each business unit in each quarter. Those ratings are then aggregated into a single heat level per cell.
There are two common formats:
Project-versus-stakeholder group: Each row is a project, each column is a business unit, and the cell shows that project’s impact on that group. This format works well when you need to communicate a specific initiative’s reach.
Business unit over time: Each row is a business unit, each column is a quarter, and the cell aggregates all project impacts on that group for that period. This is the more popular format for portfolio-level planning.
Both are useful. Both are also problematic when treated as the primary basis for change decisions.
Where the change management heat map adds genuine value
Before dismantling the heat map, it is worth acknowledging what it does well, because used appropriately, it remains a valuable part of the change practitioner’s toolkit.
It makes the case for change management resourcing. When a heat map shows a business unit sitting under sustained red for three consecutive quarters, it is a compelling argument for additional change capacity. The visual is immediate. Executives who struggle to grasp the volume of concurrent change often respond well to seeing it rendered spatially.
It supports initial triage. Early in a programme, when you are still gathering impact data, a heat map gives you a rough signal of where to direct attention first. It is not the final word, but it is a useful starting point for conversations.
It builds stakeholder alignment. Showing a leadership team a heat map of their organisation’s change exposure can generate productive dialogue. Leaders who assumed their business unit was not heavily affected may be surprised. That conversation, however imperfect the underlying data, can be valuable.
It communicates portfolio scale. For boards and executive committees who need a summary view, the heat map provides a visual shorthand for “this organisation has a lot happening simultaneously.” That message matters and the heat map delivers it efficiently.
The problem is not the heat map itself. The problem is what happens when it is used as the definitive basis for change planning decisions rather than one input among many.
Why the change management heat map creates risk when used alone
The aggregation problem distorts reality
The fundamental flaw in the standard heat map is that it aggregates impact ratings into a single score per cell. When a business unit is rated “red” in Q2, that cell may represent three projects each scoring moderate impact, or it may represent one catastrophic system implementation layered with a restructure and a compliance change. The cell colour is identical. The response required is entirely different.
This aggregation problem compounds when you consider that different types of change create different demands on employees. A technology rollout requires training time, system access, and behaviour change. A restructure creates psychological uncertainty and role ambiguity. A process change requires procedural relearning. Combining these into a single heat score does not reveal the nature of the burden, only the rough magnitude. And even the magnitude is suspect, because it depends entirely on how each project team calibrated their rating.
Prosci’s research on the correlation between change management and project success consistently finds that the quality of change management practice, not the quantity of change, is the primary driver of outcomes. Organisations that apply structured, high-quality change management are six times more likely to meet project objectives. The heat map, by focusing purely on volume, misses the quality dimension entirely.
Red cells do not tell you what to do
Suppose a business unit is sitting in red for Q3. What does that tell you? It tells you there is a lot happening. It does not tell you:
Which projects are driving the heat
Whether the impacted employees have capacity to absorb the change
Whether the business unit’s leadership is aligned and actively sponsoring the change
Whether there is any time within the quarter for training and adoption activities
Whether any of the projects could be de-scoped, delayed or phased
The heat map surfaces a symptom but provides no diagnostic information. It tells you the patient has a fever, not what is causing it or how to treat it. Senior leaders who see a red cell often ask the obvious question, “what should we do about this?” The heat map cannot answer that question.
Heat maps obscure the employee experience
The most significant limitation of the heat map is that it represents organisational units, not people. A business unit of 500 employees may have 50 people in roles that are heavily impacted by three concurrent changes, and 450 who are barely touched. The entire unit turns red because of the concentrated experience of a minority.
Conversely, a business unit showing amber or green may have pockets of employees who are completely overwhelmed because the changes affecting them happen to fall below the threshold that triggers a red rating at the aggregate level.
Research on change saturation in large organisations highlights that change overload is often a localised experience, felt acutely by specific groups, roles or teams, while the broader unit appears to be coping. A tool that averages across the business unit will consistently miss these hot spots. And it is the hot spots where change fails.
Better approaches to change impact decision making
The heat map should not be abandoned. It should be contextualised, supplemented, and in many cases, replaced as the primary planning tool with approaches that provide richer and more actionable insight.
Stakeholder-level impact analysis
Rather than mapping change at the business unit level, more sophisticated change teams map impact at the role or stakeholder group level. This means asking: which specific roles are affected by this change, and what does the change require of those people in terms of behaviour, process, systems and mindset?
This approach produces a much more granular picture of change exposure. It allows you to identify the roles carrying the highest load, where those roles cluster across the organisation, and whether those clusters correlate with your heat map’s red cells or deviate from it. Frequently, they deviate significantly.
Stakeholder-level analysis also supports much more targeted change activities. Rather than deploying a generic communications and training plan to an entire business unit, you can tailor your approach to the specific groups facing the highest impact and the lowest readiness.
Change volume over time, by impact type
A more informative version of the heat map separates change volume by impact type: process changes, technology changes, structural changes, and so on. This allows you to see not just how much change is happening to a group, but what kind. A quarter that contains significant technology change and structural change requires a very different response to one containing a series of smaller process updates, even if both produce the same aggregate heat score.
Adding a capacity dimension, actual available time for change activities within the quarter, makes this even more powerful. A business unit that is in a critical operational period, such as a financial year-end or a major product launch, has less capacity to absorb change regardless of the nominal heat level. Surfacing that constraint visually can prevent change teams from scheduling major activities during windows when employees simply cannot engage.
Integrated change analytics
The most effective change teams have moved beyond the heat map to integrated change analytics platforms that allow them to slice impact data by multiple dimensions simultaneously: project, business unit, role, impact type, timing, readiness, and adoption progress. This is not just a more complex heat map. It is a fundamentally different way of generating insight.
Prosci’s 2024 analysis of change management trends identifies data-driven change management as one of the most significant emerging practices in the field. Organisations that invest in change analytics capabilities are building a durable competitive advantage, not just for the current programme but for their long-term transformation capacity.
The shift from heat mapping to integrated analytics mirrors what has happened in project management, finance and HR over the past two decades. In each case, the move from summary dashboards to richer, multi-dimensional data produced better decisions. Change management is on the same trajectory.
Using digital tools to go beyond the heat map
Digital change management platforms are making it significantly easier for change teams to move from manual heat maps to integrated analytics without requiring data science expertise or custom IT development. Tools like The Change Compass allow change teams to input impact data at a granular level and then generate views that surface the insights a traditional heat map cannot: which roles are carrying the highest load, how change volume correlates with adoption outcomes, and where readiness gaps are most likely to translate into project risk.
Critically, these platforms allow the heat map to exist as one view among many, rather than the only view. Leaders who want the executive summary can see the heat map. Programme leads who need to understand the detail can interrogate the underlying data. Change managers who are designing interventions can filter by role, project, or time period to understand the specific context they are working in. This layered approach preserves the communicative value of the heat map while removing its limitations as a decision-making tool.
If your organisation is ready to explore what this looks like in practice, The Change Compass offers a weekly demo where you can see how leading organisations are using integrated change analytics to make better portfolio decisions.
Conclusion: use the heat map, but do not stop there
A change management heat map explained to its fullest is both a useful communication tool and a dangerous oversimplification. It makes complex portfolio data accessible to senior audiences. It supports initial triage. It creates a shared visual language for conversations about change volume and timing. These are genuine contributions.
But it was never designed to be the primary basis for change planning decisions, and treating it as such creates real risk. It flattens the nuance of different impact types, hides the employee-level experience of change saturation, and provides no diagnostic information about what to do when cells turn red.
The organisations managing change most effectively are those that use the heat map as an entry point, not a destination. They supplement it with stakeholder-level analysis, impact-type breakdowns, capacity data, and integrated analytics that allow them to understand not just where change is concentrated but why it is concentrated there and what the right response is. That is what good change portfolio management looks like in practice.
Frequently asked questions
What is a change management heat map?
A change management heat map is a visual tool, typically a grid, that displays the volume or intensity of change impacts across different parts of an organisation over time. Cells are colour-coded, most commonly using a traffic light system, to show where change load is highest. It is widely used in portfolio-level planning to give leaders a summary view of change exposure across the business.
Why do organisations use heat maps for change management?
Heat maps are popular because they translate complex programme data into a format that is immediately scannable for executives. They help build the case for change management resourcing, support initial triage of where to focus attention, and create a shared visual language for conversations about change volume and timing. Their simplicity is both their appeal and their limitation.
What are the main limitations of change management heat maps?
The main limitations are threefold. First, they aggregate impact into a single score per cell, losing the nuance of what types of change are happening and to whom. Second, a red cell tells you there is a problem but provides no information about what to do. Third, they operate at the business unit level, which can hide pockets of severe change saturation affecting specific roles or teams while the broader unit appears manageable.
How should a change management heat map be used effectively?
A heat map should be used as one input among several, not as the primary decision-making tool. It works best for executive communication and initial portfolio triage. For operational change planning decisions, it should be supplemented with stakeholder-level impact analysis, change volume breakdowns by impact type, capacity data, and, where possible, integrated change analytics that allow multi-dimensional interrogation of impact data.
What are the alternatives to change management heat maps?
Better alternatives include stakeholder group or role-level impact matrices, change volume timelines segmented by impact type, capacity-adjusted planning views, and integrated change analytics platforms that allow you to slice data by project, business unit, role, timing and readiness simultaneously. These approaches provide the diagnostic information that heat maps cannot, specifically what is driving the heat and what the right response is.
How do digital tools improve on traditional heat maps?
Digital change management platforms allow teams to input impact data at a granular level and generate multiple views from the same dataset. Leaders can access the summary heat map view for executive reporting while change managers can interrogate underlying data by role, project, or time period. This layered approach preserves the communicative value of the heat map while removing its limitations as a primary planning tool.
References
Prosci. The Correlation Between Change Management and Project Success. https://www.prosci.com/blog/the-correlation-between-change-management-and-project-success
Prosci. Change Management Trends Outlook: 2024 and Beyond. https://www.prosci.com/blog/change-management-trends-2024-and-beyond
ResearchGate. The Role of Change Management in Enhancing Data-Driven Decision Making: Insights from Business Intelligence Initiatives (2024). https://www.researchgate.net/publication/384017092_The_Role_of_Change_Management_in_Enhancing_Data-Driven_Decision_Making_Insights_from_Business_Intelligence_Initiatives
The Change Compass. Why Change Saturation Is a Pandemic for Most Large Organisations. https://thechangecompass.com/why-change-saturation-is-a-pandemic-for-most-large-organisations/
IMPLEMENTATION NOTES
Post ID: 13272
Suggested title: Change management heat map explained: what it tells you, what it hides, and what to do instead
Meta description: A change management heat map explained for senior practitioners , what it does well, its critical limitations, and how to make better change decisions.
Measuring behaviours as a part of change adoption is a key part of effective change management, ensuring the full achievement of initiative benefits and helping practitioners understand whether impacted stakeholders are truly moving toward the future state. Behaviour change, particularly in domains like physical activity and health behavior, has been the subject of significant empirical research, with findings published in major outlets like Google Scholar. To design behaviour change interventions and select the right behaviours to measure, change practitioners should take a structured approach, informed by research findings and practical experience. There are different approaches to effective measurement and we explore some of these.
Selecting the Right Behaviours to Measure
Start with a clear understanding of the initiative’s objectives, the current state, the complexity of the change, different impacts, the change approach, target behaviours, and the quantum of the change being introduced. Not every behaviour is equally important; focus on the key elements most closely tied to initiative success and the full adoption of behaviours required for the future state.
Consider the impacted person’s perspective toward the desired future state: What will they have to do differently? From adopting new physical behaviours (such as physical effort required in physical activity interventions) to changes in decision-making or collaboration, choose behaviours that best reflect actual change, not just awareness or intent.
Prioritize observable and measurable actions. Research suggests that reminders of events or structured prompts can support behaviour change, but measuring the visible results of these reminders—such as compliance rates, social norm adherence, or reduction in social deviance—is essential for meaningful metrics.
Design and Measurement Considerations
Resist the heavy design of change interventions that lead to measurement overload. Simplicity and ease of understanding are crucial, both for those being measured and those collecting the data.
Draw from behavioral change frameworks supported by significant empirical research. For example, a Stanford professor’s work on social norm dynamics highlights how aligning behaviours with group expectations—rather than just individual compliance—can create more durable change.
Integrate measurement as part of a series of change interventions. Behaviour rarely shifts overnight; structured reinforcement, monitoring, and feedback, as supported by research findings, are necessary for full adoption.
Best Practice Tips
Use multiple sources of data: direct observation, self-reports, digital analytics, and reminders of events all have roles in robust measurement systems.
Anchor behaviour change efforts to broader elements like organizational culture (social norms) and systems for monitoring and feedback, to sustain behavioural change and minimize social deviance.
Apply the old adage, “what gets measured, gets managed,” but with the right focus—select measures tightly linked to initiative success.
Ultimately, successful behaviour change – and its measurement – depends on aligning the structured approach of change management with an empathy for the impacted person’s journey. Choosing the right behaviours to measure, grounded in significant empirical research and designed for ease of understanding, supports not only the full achievement of initiative benefits but also continuous improvement for future state readiness
Whilst there could be a wide range of different behaviours depending on the initiative in concern, what are some of the tips in selecting the right behaviours to measure?
Check out our infographic on the top 4 elements to pay attention to when measuring behaviours as a part of change adoption metrics. Also check out Dr BJ Fogg’s model (Stanford University) on effective behaviour change.
