Key Change Management Metrics Examples You Should Avoid

Key Change Management Metrics Examples You Should Avoid

Successful change management relies on having the right metrics to measure progress, gauge impact, and communicate with stakeholders. Moreover, the right metrics can drive continuous improvement and help directly achieve change outcomes. However, not all metrics are beneficial, and some can mislead or fail to meet stakeholder needs, especially when managing change projects. Let’s check out the top change management metrics to avoid and go through examples to take note.

Understanding the Disconnect: Change Managers vs. Business Stakeholders

A significant reason certain change management metrics fall short is the differing perspectives between change managers and business stakeholders. Change managers and change practitioners are trained to view metrics through the lens of change management frameworks and methodologies, focusing on detailed assessments and structured approaches as a part of the change management strategy. These include applying ratings and judgments on aspects such as impact levels indicating levels and areas of impact.

In contrast, business stakeholders prioritize business operations, strategic outcomes, and practical implications.  The busy business stakeholder is often looking for practical implications from metrics that can be used to directly drive decision making, meaning “what do I do with this data to improve the ultimate business outcome”.  

Of course, different stakeholders have different data needs, and you need to show the right metric to the right type of stakeholder. For example, operations-focused stakeholders expect fairly detailed metrics and internal historical data to understand what that means in terms of organisation, coordination, capacity, and performance perspectives. Senior managers may prefer higher-level data with a focus on strategic impacts, overall progress, and adoption indicators of change success rate.

This disconnect can lead to the use of metrics that do not resonate with or are misunderstood by stakeholders that disrupt change success.

Change managers may leverage metrics that are derived from the various change management documents such impact assessments, training plan or communications plan.  Metrics are also often chosen for ease of use and ideally are not overly complicated to execute.

For example, impact assessments typically involve rating stakeholder groups and initiatives on a traffic light system (red, amber, green) based on their impact. While this approach is systematic, it can be problematic for several reasons:

  1. Lack of Sufficient Stakeholder Context: Business stakeholders might not understand the practical implications of these ratings. For instance, an “impact rating per initiative” may not clearly convey what the rating means for day-to-day operations or strategic goals. For example, if an initiative has a red impact rating, stakeholders might not grasp the specific operational changes or strategic adjustments needed, in essence, “what do I do with this?”. So, incorrect usage of data could result in lack of stakeholder engagement.
  2. Misinterpretation of Traffic Light Ratings: The red, amber, green system can be misleading. Stakeholders might interpret red as an indicator of alarm or imminent risk, while green may be seen as a sign that no action is needed.  This is because stakeholders are trained to interpret traffic light ratings this way (from the various project/business updates they’ve attended). In reality, red might simply mean high impact, requiring focused attention, and green might indicate a low impact but still require monitoring. For instance, a red rating might indicate significant process changes that need careful management, not necessarily a negative outcome.
  3. Hard to defend ratings if prompted: Business stakeholders may also want to drill into how the ratings are determined, and based on what basis.  They may expect a logical data-backed reasoning of how each colour scheme is determined.  If a rating is based on an overall ‘personal judgment’ this may be hard to defend infront of a group of stakeholders.

D83d12e7 2df8 4506 86b5 30d118f92907

Examples of Potentially Misleading Metrics

Certain metrics, although straightforward, can be easily misinterpreted and fail to provide a realistic picture of change impacts as a part of effective change management.  Often these are selected because they are easy to report on.  However, easy, make not give you the outcome you are looking for.

  1. Number of Go-Lives: Tracking the number of Go-Lives over time might seem like an effective way to represent change volume. However, the most significant impacts on people given time often occur before or after the Go-Live date. For example, the preparation and training phase before Go-Live and the adoption phase afterward are critical periods that this metric overlooks. A Go-Live date might indicate a milestone but not the challenges, progress or impacts faced during the implementation phase.
  2. Number of Activities Implemented: Similar to Go-Lives, this metric focuses on quantity rather than quality. Simply counting the number of activities does not account for their effectiveness or the actual change they drive within the organisation. For example, reporting that 50 training sessions were conducted does not reveal whether employees found them helpful or if they led to improved performance.
  3. Number of impacts or stakeholders impacted: Again, using a numerical way to indicate progress can be very misleading, or unmeaningful.  This is because it may be ‘interesting’ but with no real action for your stakeholder to take in order to somehow lead to a better overall change outcome.  If metrics do not result in some kind of action, then over time it will not shape your change(s) toward the targeted outcomes.   Or worse, your stakeholders may lose interest and lose confidence in the strategic impact of these metrics.
  4. Another common way to report change metrics is to use the number of impacts or number of stakeholders impacted by the organizational change.  This can be in terms of the following:
  5. Number of divisions impacted
  6. Number of stakeholder groups impacted
  7. Number of employees impacted
  8. Number of initiatives per division/stakeholder

Metrics That May Be Too Operational

Metrics that are overly operational can fail to capture meaningful progress or adoption.  Perhaps if the metric are for reporting within the Change Management team that may be OK.  However, when you are showing metrics to stakeholders, a different set of expectations should be cast. 

If you are presenting metrics to senior managers, you need to ensure that they hit the mark for that audience group.  If the group is more interested in strategic impact, and higher level progress outcomes, you need to tailor accordingly.

Examples of metrics that may be too operational include:

  1. Number of Communications Sent: This metric measures activity but not effectiveness. Sending numerous emails or messages does not guarantee that the message is received, understood, or acted upon by stakeholders. For instance, stakeholders might receive 100 emails, but if the content is unclear, the communication effort is wasted. Or worse, the emails may not even have been read.
  2. Number of Training Sessions Attended: This one is a classic. While training is crucial, the number of sessions attended does not necessarily reflect the attendees’ understanding, engagement, or the practical application of the training. For example, employees might attend training but not apply the new skills if the training is not relevant to their roles for various reasons.
  3. Number of workshops/meetings: Another way of articulating the change management progress in terms of activities is the number of workshops or meetings conducted with stakeholders including focus groups to indicate employee engagement.  Again, this may be good to track within the change management team.  However, presenting this metric to stakeholders may not be appropriate as it may not meet their needs nor indicate change management success. 
  4. Number of changes: This may be a common way to report on changes planned, but it doesn’t really inform the extent of the change. One change can be significantly impactful whilst another does not have major stakeholder impacts and are more system impacts. Listing number of changes may be deceiving or misleading. This kind of data may not get you the level of acceptance targeted.

To read more about reporting to executives or senior managers, check out our Ultimate Guide to Change Management Reports Your Executives Want to See.

The Importance of Effective Data Visualization

The way metrics are presented is just as important as the metrics themselves. Poor visualization can lead to misinterpretation, confusion, and misguided decisions. Here are some common pitfalls to avoid:

Ineffective Use of Pie Charts

Pie charts can be misleading when used to show data points that are not significantly different. For example, using a pie chart to represent the percentage of divisions impacted by a change might not effectively communicate the nuances of the impact if the differences between the divisions are minimal. A pie chart showing 45%, 30%, and 25% might not convey the critical differences in impact levels among divisions.  

Misleading Traffic Light Ratings

Using red, amber, and green to indicate high, medium, and low impacts can send the wrong message. Stakeholders might associate these colours with good and bad outcomes rather than understanding the actual levels of impact.  Stakeholder may be used to interpreting these in the context of their usual project or business updates where red indicated alarm and ‘bad’. This can lead to unnecessary alarm or complacency. For instance, a green rating might suggest no need for action, while in reality, it might require ongoing monitoring.

Overuse of Colours

Using too many colours in charts and graphs can overwhelm stakeholders, making it difficult to discern the key message.  Using colours in data visualisation can be two-edged sword.  Colour can effectively point your stakeholders are the area where you want them to focus on.  But, too many colours can lose your audience. A cluttered visual can obscure the critical data points and lead to misinterpretation. For example, a graph with ten different colours can confuse stakeholders about which data points are most important.

8e98e632 0540 45a7 Acce B1972a737898

Data visualisation tools are also important. A lot of people use Power BI which works for a foundational level of charts. For tailored charts, specifically designed to to influence stakeholders to clearly see certain angles of risks and opportunities leverage tools such as Change Compass.

Practical Takeaways for Senior Change Managers

To ensure that change management metrics are effective and take into account best practices practices, consider the following practical takeaways:

Align Metrics with Key Stakeholder Perspectives

  1. Understand Stakeholder Priorities: Engage with stakeholders to understand their business goals, priorities and concerns. Tailor your metrics to address these aspects directly. For example, if stakeholders are concerned about operational efficiency, focus on metrics that reflect improvements in this area.
  2. Use Business Language: Frame your metrics in a way that resonates with business stakeholders. Avoid change management jargon and reference, and ensure that the implications of the metrics are clear and actionable. For example, instead of using technical terms, explain how the metrics impact business outcomes.  Think in terms of business activities, milestones, busy periods, and capacity challenges.

Focus on Meaningful Metrics

  1. Measure Outcomes, Not Just Activities: Change leaders should prioritize metrics that reflect the outcomes and impacts of change indicate level of knowledge, rather than just the activities performed as a part of change management KPIs. For example, instead of counting the total number of employees attending change management training sessions, measure the improvement in employee performance or knowledge retention post-training.
  2. Example: Instead of reporting that 100 employees attended training sessions, report that 85% of attendees showed improved performance in their roles after training, or that certain level of competencies were gained. Note that quantifiable metrics have more impact on the audience.
  3. Track Engagement and Adoption: Monitor metrics that indicate the level of engagement and adoption among stakeholders or their perception of the change. This could include surveys, feedback forms, or direct measures of behaviour change and the overall success rate of the change.
  4. Example: Use post-training surveys to measure employee confidence in applying new skills or managerial rating of application of learnt skills rather than employee satisfaction of the training sessions using satisfaction scores. Track the percentage of employees who actively use new tools or processes introduced during the change.
  5. Example: Instead of reporting that 100 employees attended training sessions, report that 85% of attendees showed improved performance in their roles after training, or that certain level of competencies were gained.
  6. Example: Use post-training surveys to measure employee confidence in applying new skills or managerial rating of application of learnt skills. Track the percentage of employees who actively use new tools or processes introduced during the change.

Improve Metric Visualization

  1. Simplify Visuals: Use clear, simple visuals that highlight the key messages. Avoid clutter and ensure that the most important data points stand out.
  2. Example: Use bar charts or line graphs to show trends over time rather than pie charts that can be harder to interpret.
  3. Contextualize Data: Provide context for the data to help stakeholders understand the significance. For example, instead of just showing the number of Go-Lives, explain what each Go-Live entails and its expected impact on operations.  Or better, focus on showing the varying levels of impact on different stakeholders across time within the initiative.
  4. Example: Accompany a Go-Live count with a visual showing the varying impact level of various implementation activities of the changes.
  5. Example: Use bar charts or line graphs to show trends over time rather than pie charts that can be harder to interpret.
  6. Example: Accompany a Go-Live count with a visual showing the varying impact level of various implementation activities of the changes.

To read more about effective data visualisation tips in presenting change data, check out Making impact with change management charts infographic.

Communicate Effectively

  1. Narrative Approach: Combine metrics with a narrative that explains the story behind the numbers as a part of the change management process. This can help stakeholders understand the broader context and implications.
  2. Example: Instead of presenting raw data, provide a summary that explains key trends, successes, and areas needing attention.
  3. Educate your stakeholders: Depending on stakeholder needs you may need to take them on a phased approach to gradually educate them on change management metrics and how you ultimately want them to drive the outcomes.
  4. Example:  You may start the education process to focus on more simplistic and easy-to-understand measures, and as your stakeholders are more change-mature, move to drill into more detailed metrics that explain the ‘why’ and ‘how’ to drive outcome success.
  5. Continuously improvement: Provide regular updates on key metrics and adjust them based on feedback from stakeholders. Continuous communication ensures that everyone remains aligned and informed.
  6. Example: Hold monthly review meetings with stakeholders to discuss the latest metrics, address concerns, and adjust strategies as needed.
  7. Example: Instead of presenting raw data, provide a summary that explains key trends, successes, and areas needing attention.
  8. Example:  You may start the education process to focus on more simplistic and easy-to-understand measures, and as your stakeholders are more change-mature, move to drill into more detailed metrics that explain the ‘why’ and ‘how’ to drive outcome success.
  9. Example: Hold monthly review meetings with stakeholders to discuss the latest metrics, address concerns, and adjust strategies as needed.

D3365dfd A872 4ab2 Bf81 76ac391a1e5a

Examples of Effective Metrics

Employee Adoption and Engagement

  1. Percentage of Employees Adopting New Process/System: This metric measures the rate at which employees are using new processes or systems introduced during the change. High adoption rates indicate successful integration.
  2. Implementation: Use software usage analytics or surveys to track tool adoption rates.
  3. Visualization: A graph showing adoption rates over time.
  4. Employee Feedback Scores: Collect feedback on change initiatives through surveys or stakeholder ratings to measure sentiment/feedback and identify areas for improvement.
  5. Implementation: Conduct regular surveys asking employees about their experience with the change process.  Do note that depending on the change you may expect negative feedback due to the nature of the change itself (vs the way it was implemented).
  6. Visualization: Bar/Line charts comparing feedback scores across different departments or time periods.  Bar/Line charts are the standard go-to for data visualisation.  They are easy to understand and interpret.
  7. Implementation: Use software usage analytics or surveys to track tool adoption rates.
  8. Visualization: A graph showing adoption rates over time.
  9. Implementation: Conduct regular surveys asking employees about their experience with the change implementation process. Do note that depending on the change you may expect negative feedback due to the nature of the change itself (vs the way it was implemented).
  10. Visualization: Bar/Line charts comparing feedback scores across different departments or time periods.  Bar/Line charts are the standard go-to for data visualisation.  They are easy to understand and interpret.

Impact on Business Outcomes

  1. Improvement in Key Performance Indicators (KPIs): Track changes in KPIs that are directly impacted by the change initiatives, such as productivity, customer satisfaction, customer experience, improvement in process inconsistencies or financial performance.
  2. Implementation: Identify relevant KPIs and measure their performance before and after change initiatives.
  3. Visualization: Use line/bar graphs to show trends in KPI performance over time.
  4. Operational Efficiency Metrics: Measure improvements in operational processes, such as reduced cycle times, error rates, or cost savings.
  5. Implementation: Track specific operational metrics relevant to the change initiatives.
  6. Visualization: Bar charts or heatmaps showing improvements in efficiency metrics across different operational areas.
  7. Implementation: Identify relevant KPIs and measure their performance before and after change initiatives.
  8. Visualization: Use line/bar graphs to show trends in KPI performance over time.
  9. Implementation: Track specific operational metrics relevant to the change initiatives.
  10. Visualization: Bar charts or heatmaps showing improvements in efficiency metrics across different operational areas.

To read more about change adoption metrics visit The Comprehensive Guide to Change Management Metrics for Adoption.

Change management effectiveness requires metrics that not only measure progress but also resonate with business stakeholders and accurately reflect the impact of change initiatives. They should provide valuable insights. Avoiding common pitfalls such as relying on easily misinterpreted or overly operational metrics is crucial. By aligning metrics with stakeholder perspectives, focusing on meaningful outcomes, improving visualization, and communicating effectively, senior change and transformation professionals can ensure that their metrics truly support the success of their change initiatives.

The top change management metrics to avoid are those that fail to provide clear, actionable insights to business stakeholders. By understanding and addressing the disconnect between change managers and business stakeholders, and by prioritizing metrics that truly reflect the impact and progress of change, you can drive more effective and successful change management efforts by influencing your stakeholders in your organisation.

As a next step, Chat with us if you would like to discuss more about leveraging AI and technology to generate high-impact change management metrics and data for your stakeholders, both at project and portfolio levels, using data visualisation tools.

Change Management Adoption Metrics: The Complete Tracking Framework (With Dashboard Template)

Change Management Adoption Metrics: The Complete Tracking Framework (With Dashboard Template)

Change adoption metrics are the usage, proficiency, sustainment and outcome indicators that show whether people are working differently after a change, not merely that the change was delivered to them.

The average organisation uses only 54% of the software licences it pays for, according to Zylo’s 2026 SaaS Management Index, which is the adoption problem in one number: Access is not use. The same gap runs through change programmes. A project can report full training attendance, every account provisioned and a green status, while the new process is used for the easy cases and bypassed for the hard ones.

This article is for change, HR and transformation leaders who already know they should measure adoption and need to decide what, exactly, to put on the page. It argues that credible adoption evidence rests on four families of metric (usage, proficiency, sustainment and outcome), that each family fails in a predictable way when read alone, and that the skill is in reading them together. By the end you will be able to choose a short, defensible metric set for a given initiative and interpret it without overclaiming. If you need the method for collecting this data, see our guide to how to measure change adoption; for the wider framework, start with the ultimate guide to measuring change.

The four families of adoption metric

An adoption metric is any measure of what people do after the change that can be tied to a specific behaviour the change requires, and the strongest sets combine usage, proficiency, sustainment and outcome measures.

Prosci’s research gives practitioners a useful starting taxonomy. It describes speed of adoption, ultimate utilisation and proficiency as the core measures once people have reached the ability stage: How quickly people begin to use the change, how many are using it, and how well they apply it. We add two more families, because a programme that stops at those three cannot answer the questions executives actually ask later.

  • Usage: Are the intended people using the change, how often, and how fully? (Speed of adoption and ultimate utilisation.)
  • Proficiency and behaviour: Are they doing it correctly, in the way the benefit depends on?
  • Sustainment: Does use hold after launch support is withdrawn, or does work drift back?
  • Outcome: Is the business result the change was funded for visibly moving?

Each family answers a different question, and each has a blind spot. Usage can be high while proficiency is poor. Proficiency can be strong in the pilot team and absent elsewhere. Sustainment is invisible if you stop measuring at go-live. Outcomes move for many reasons other than adoption. The rest of this article takes each family in turn and then shows how to read them together.

Usage metrics: Reach, frequency and depth

Usage metrics tell you whether the intended population is using the change, how often and how deeply, and the most common error is treating login counts as evidence of any of these.

B2d0b5ea 4fef 45ff Bb76 561f43c53df6

Gallup’s May 2026 indicator shows how misleading access data can be. Nearly half of US employees (47%) say their organisation has integrated AI tools, yet only 30% use them a few times a week or more and 15% use them daily. Implementation, in Gallup’s words, does not guarantee use. Any programme that reported adoption from provisioning or first-login data would have overstated it by roughly half.

Split usage into three measures, because each exposes a different failure:

  • Reach: The share of the intended population who have used the new process or tool at all, by role and by team. This is your speed-of-adoption view when plotted weekly from go-live.
  • Frequency: How often the people who use it do so, compared with how often the work requires it. A tool needed daily and used monthly is not adopted.
  • Depth: The share of use that happens in the core workflow, measured on the two or three features or steps the benefit depends on, not on every feature.

The depth measure matters most. For a system implementation it might be the percentage of orders created in the new system rather than raised by spreadsheet, or the share of customer records completed to the required standard at first save. For a process change it is the proportion of cases that follow the new sequence end to end. Choose the critical few and ignore the long tail of features.

Read usage by segment, not by average

An enterprise average hides the teams that matter. Report usage by role, location and manager, then look for the lowest quartile. A 78% overall rate that conceals one division at 35% describes a rollout that has succeeded in some places and not started in others, and the response to each is different.

Proficiency and behaviour metrics: Are people doing it right?

Proficiency metrics show whether people perform the new way correctly and consistently, and they are the family most often missing from adoption reports because they require more than system data.

Change management adoption The metrics compass

The gap between use and effect shows up clearly in Gallup’s data. Of employees in organisations that have implemented AI, 65% say it has improved their productivity, but only 14% strongly agree it has transformed how work gets done. Most people have used the tool inside their existing workflow, which is adoption of a sort, but not the changed way of working the investment assumed. Usage metrics alone would have called that a success.

Proficiency is measured through observable behaviours (sometimes called micro-behaviours): The small, specific actions that show the change is embedded. Useful examples:

  • Error and rework rate: The share of transactions returned, corrected or escalated because the new process was not followed.
  • Time to complete a key task against a pre-change baseline, once the learning curve has passed.
  • Workaround rate: The proportion of work still routed through the legacy spreadsheet, email or manual step.
  • Assessed competency: A short practical check or manager sign-off, rather than a quiz on course content.
  • Manager coaching frequency: How often team leaders observe and reinforce the new behaviour. Gallup finds that employees whose managers actively support their team’s AI use are 1.7 times as likely to use it a few times a week or more, and only 36% of employees in AI-integrating organisations strongly agree their manager does.

Behaviour data is cheaper to collect than it sounds if you decide in advance which three or four behaviours the benefit depends on. For a deeper treatment of how behaviours form and hold, see our guide to behaviour change in the workplace.

Adoption metrics in one view: The Change Compass tracks adoption measures for each initiative alongside the change load on each team, so you can see whether low usage is a design problem or a capacity problem. See how The Change Compass works or book a demo.

Sustainment and outcome metrics: Does it last, and does it pay?

Sustainment metrics test whether adoption survives after launch support ends, and outcome metrics test whether the benefit the change was funded for has actually arrived; reporting neither leaves the programme unable to prove its value.

Most of the value in a change is realised, or lost, after the programme team has moved on. BCG’s 2025 analysis of transformation concluded that only about a quarter of transformations successfully create value, which is a reminder that delivery and realisation are different events. Go-live is the start of the measurement window, not the end.

Sustainment indicators

Re-measure the same usage and proficiency indicators at fixed intervals after support ends (30, 90 and 180 days is a workable pattern) and add one specific measure:

  • Reversion rate: The share of work, by team, that has returned to the old process or an unapproved workaround.
  • Stability of use: Whether each team’s usage is flat or rising without fresh intervention. A decline that begins when champions or project staff withdraw points to a reinforcement gap, not a design flaw.
  • Support demand: The trend in help requests per user. A fall followed by a rise often signals a second wave of problems as edge cases appear.

Outcome indicators

Outcome metrics connect adoption to the business case: Cycle time, cost to serve, error cost, compliance incidents, customer satisfaction, or revenue per seller, depending on the change. Their discipline is attribution. Where possible compare adopting teams with lagging ones, or a team before and after it reached a stable usage level, rather than reading a portfolio-wide trend that moves for many reasons. Where you cannot isolate the effect, say so in the report. Our guide on the problem with change management metrics covers the most common ways outcome claims overreach.

Choosing metrics by change type

The right adoption metrics depend on what the change asks people to do, so start from the target behaviour and pick the two or three metrics in each family that evidence it.

A system implementation turns on depth of use in the core workflow. A compliance change turns on observed behaviour and incident trends, because logins say nothing about whether the rule is followed. A restructure has few clean usage measures, so engagement, role clarity and collaboration patterns carry more weight, though these are better described as readiness and outcome indicators than adoption in the strict sense.

MetricSystem implementationCompliance changeRestructure
Reach and active-use rateHigh priorityModerateLow
Feature or workflow depthHigh priorityLowLow
Process compliance rateModerateHigh priorityModerate
Incident or error rateModerateHigh priorityLow
Manager observation or coachingModerateHigh priorityHigh priority
Assessed proficiencyModerateHigh priorityModerate
Engagement or clarity pulseLowModerateHigh priority
Reversion rateHigh priorityModerateModerate
Productivity vs pre-change baselineHigh priorityModerateHigh priority

How many metrics is enough?

Aim for a core set of 8 to 15 metrics per initiative, grouped under the four families, with only the handful that answer the sponsor’s question reported upward. Include a metric only if you can name the decision it would change and you can collect it reliably at the cadence you need. Mix system data with at least some observation or survey data, because system logs cannot tell you why a team is lagging.

How to read the numbers together

Adoption is established when usage, proficiency and sustainment point the same way, and every divergence between them is a diagnosis waiting to be made.

Read the families as a set and look for the patterns below.

What you seeLikely meaningWhere to look
High reach, low depthPeople log in but bypass the core workflowProcess design, training on the critical steps
High usage, low proficiencyUse without the intended behaviourCoaching, job aids, manager reinforcement
Strong pilot, weak elsewhereLocal conditions, not a general resultTeam-level segmentation, champion coverage
Good at go-live, decline at 90 daysReinforcement withdrawn too earlySustainment plan, manager accountability
Good adoption, no outcome movementWrong behaviour targeted, or benefit case flawedRevisit the benefit logic

Leading and lagging indicators

Treat reach, frequency and early proficiency as leading indicators: They move first and can still be acted on. Treat reversion, incident rates and outcome measures as lagging: They confirm or contradict the story weeks later. Report both, and set thresholds in advance (for example, 70% reach in the target population by week six) so that a number triggers a decision rather than a discussion about whether it is good.

Make the data visible where decisions happen

A metric set earns its keep when managers and sponsors see it regularly. Spreadsheets and BI tools work for a single programme, but they struggle once an organisation runs many changes at once and needs a consistent view by team. Digital change platforms such as Change Compass bring adoption and impact data for multiple initiatives into one view, so leaders can see where adoption is lagging by team without rebuilding the report each month. For the layout of such a view, see our guide to designing a change adoption dashboard.

Where to start next week

Pick one live initiative and write down the two or three behaviours its benefit depends on. For each, name one usage metric, one proficiency metric and a sustainment check at 90 days, then agree with the sponsor what level would count as adopted. That small set will tell you more than a dashboard of twenty indicators, because every number on it is tied to a behaviour and a decision. Retire any existing metric that nobody acts on, and add the outcome measure only once you can say how you will separate the effect of adoption from everything else that moved. Revisit the set after the first reporting cycle: If two metrics always move together, keep the cheaper one. The aim is not a complete picture of the organisation but a trustworthy answer to one question, whether people are working differently and whether it is lasting.

Frequently asked questions

What are the most important change adoption metrics?

The most useful set covers four things: Usage (reach, frequency and depth of use), proficiency (whether people perform the new way correctly), sustainment (whether use holds after launch support ends) and outcome (whether the intended benefit is showing up). Prosci frames the first three as speed of adoption, ultimate utilisation and proficiency. No single metric is enough, because each can look healthy while another is failing.

What is the difference between adoption, utilisation and proficiency?

Adoption is the point at which people start using the change, utilisation is how many of the intended people keep using it and how fully, and proficiency is how well they perform with it. A team can show 95% utilisation and low proficiency if people use the new system but work around its intended process. Measure all three separately.

How many adoption metrics should we track for one initiative?

Most initiatives are well served by a core set of 8 to 15 metrics, grouped under usage, proficiency, sustainment and outcome, with only a handful reported to executives. More than that dilutes attention and turns data collection into a burden. Choose metrics tied to the specific behaviour the change needs, and drop any you cannot act on.

Are system logins a good measure of adoption?

Logins show access, not adoption. Gallup’s May 2026 data shows 47% of US employees say their organisation has integrated AI tools, yet only 30% use them weekly or more. Track feature use in the core workflow, the share of work processed the new way, and proficiency, and treat logins only as a first signal.

How do you know whether adoption has been sustained?

Check the same usage and proficiency measures at 30, 90 and 180 days after launch support ends, and watch the reversion rate: The share of work that returns to the old process or a workaround. Sustained adoption shows as stable or rising use in each team without extra intervention. A drop after support ends usually points to a manager reinforcement or process design gap.

References

This guide focuses on tracking adoption, what people are actually doing with the change. Three closely related guides on this site each cover a distinct angle, pick the one that matches what you need now:

 

How to measure change adoption

How to measure change adoption

Measuring change adoption means checking, with observed data and against a pre-change baseline, whether the people affected are consistently working the new way, group by group, at fixed intervals after go-live.

Teams that measure whether the change is actually being followed meet or exceed their project objectives 76% of the time, against 24% for teams that do not, according to Prosci’s best practices research. Yet most change reporting still stops at go-live dates, training completions and a pulse survey, none of which show a single person working differently. This guide is for change, HR and transformation leaders who are asked to prove that a change has landed, and who suspect that the numbers they report are measuring effort rather than adoption. It argues that adoption is established by observed behaviour, in a defined group, over time. By the end you will have a five-step method you can apply to a system rollout, a process change or a behavioural shift: define what adoption means, choose behaviours and data you can observe, take a baseline, track at fixed intervals, and act on the gaps. If you want the list of metrics itself, read our guide to change adoption metrics; for the wider measurement picture, start with the ultimate guide to measuring change.

What adoption measurement covers, and why it earns its effort

Adoption measurement tracks whether the people affected by a change have shifted to the new ways of working that the change required, and it is separate from project delivery and from awareness. Delivery tells you the system went live on time. Awareness tells you people know about it. Adoption tells you whether the new process or tool is used consistently, whether day-to-day behaviour has visibly changed, whether the outcomes that depended on the change are appearing, and whether workarounds have disappeared. Because adoption can decay once launch support fades, it needs measurement after go-live, not only at it.

The gap between those layers is large in practice. A 2025 Gartner survey of business leaders found that only 32% said the last change they led achieved healthy adoption by employees. That is the population your measurement has to work for: most changes are not landing cleanly, and leaders need an early, honest read of where.

Adoption versus compliance

A group can comply without adopting. Compliance means doing the required thing because it is required or watched; adoption means doing it because it has become the normal way of working. Staff who only comply revert when oversight eases, which is why the measurement window must extend past the end of hypercare and not stop when the project team rolls off.

Why it is worth the effort

Measurement is the nearest thing a change practitioner has to proof that the interventions worked. It also shows progress to the project team and to stakeholder groups, and it points leaders at the specific places that need their attention. Done well, it lets you influence the direction of the initiative, build momentum with senior stakeholders and steer the organisation toward the change objectives. It takes time, though. You need deliberate measurement design, a reliable way of collecting data and a visual that stakeholders understand at a glance, so budget for it early rather than bolting it on in the final fortnight.

Step 1: Define adoption in terms of the benefit

The first step in measuring adoption is to state, in observable terms, what people must do differently for the benefit the change was funded to deliver to appear. Work with the project manager to understand which benefits are targeted and how they will be tracked, because adoption measures that do not connect to a benefit are vanity metrics. Prosci reports that when organisations define success well and measure performance against objectives, their odds of meeting or exceeding those objectives can increase by up to 5X.

Start from the benefit

Benefit targets usually fall into three groups:

  • Business success factors, such as revenue or cost targets.
  • Product integration measures, such as usage rates.
  • Market objectives, such as user base or revenue growth.

Some targets are harder to quantify but still matter: competitive positioning, employee relations, employee experience, employee capability and customer experience. The project manager may value benefits with payback time (the point at which cumulative cash flow turns positive), net present value or internal rate of return. Your job is not to run those models. It is to understand the targeted benefit, how it will be tracked, and which change management steps stand between the current state and the future state.

Map the benefit to steps and measures

A simple table keeps the logic visible. Here is a worked example for a new customer service system:

Project benefitChange steps requiredAdoption measureBaselineTarget
Higher customer satisfaction and productivityUsers operate the new system; use new features in customer conversations; managers coach and give feedback% of users passing the proficiency test; feature usage rate; user feedback on manager coachingSet before go-liveAgreed with the project manager
Faster resolutionUsers proactively apply new features to drive conversationsCustomer issue resolution time; call-handling capacityCurrent averageAgreed target
Benefit visibilityMonthly benefit tracking shared in team meetings; customer communication about the improved processCustomer satisfaction score; call volume handledCurrent scoreAgreed target

Fill in baseline and target for every row before go-live. A measure with no baseline cannot show movement, and a measure with no target cannot show success. Which indicators sit best in each row is a question for the adoption metrics guide; for concrete examples, see our change management adoption metric examples.

Adoption across several changes: Tracking adoption group by group across several changes at once is where spreadsheets break. The Change Compass shows adoption and change load by team in one view. See how The Change Compass works or book a demo.

Step 2: Choose behaviours and data you can observe

The second step is to select the behaviours that evidence adoption and to pair each with an objective data source, because what people do is a firmer signal than what they say. Prosci’s ERP research draws the line sharply: activity metrics such as training completion and communications sent help manage delivery, while steering metrics, such as whether employees can complete critical transactions independently, show whether the change is working. In that research, organisations with strong metrics were 2.5 times more likely to exceed expectations for their ERP programmes, and those with poor metrics succeeded only 7% of the time, against 26% for organisations with no formal metrics.

Look past training completion and readiness

Most practitioners measure what is easy: stakeholder perceptions, readiness and training completion. These have value, but they are forward-looking indications that adoption is on its way, not adoption itself. Be wary of vanity metrics that look good and are simple to explain but do not connect to business outcomes; our piece on the problem with change management metrics covers the common traps. For readiness data, see this strategic view of readiness assessment. To measure adoption itself, look for system usage, behaviour change, correct use of the new process, or the achievement of cost or service targets, with particular attention to early adopters.

Pick observable behaviours

Most changes involve behaviour change, whether it is a different way of operating a system, new steps in a process or a new conversation with a customer. These tips keep the selection practical:

  • Make it observable. A behaviour is something another person can see or a system can record. Thoughts and attitudes are not behaviours.
  • Choose the right grain. Clicking a button is too fine to be worth tracking. “Proactively understands customer concerns” is too broad to rate. “Asks about the customer’s needs in the three agreed areas during each interaction” works.
  • Find the trigger. Behaviours usually follow a cue, such as a customer saying “not happy”, which should start the new complaints process. Name the trigger and you can measure the response.
  • Limit the count. Too many behaviours create extra work for the project team; too few cannot evidence the benefit.
276754dc D34a 4d34 B481 79a82718794f

Break broad behaviours into micro-behaviours

Behaviour change can feel elusive. Micro-behaviours make it practical: small, specific, observable steps rather than a cluster of behaviours. A broad aim such as “build customer rapport” becomes four measurable actions: use the customer’s name (“Is it OK if I call you Michelle?”), open with a short check-in (“How has your day been?”), reflect the customer’s feeling (“It sounds like that was frustrating”), and agree the next step (“Would it help if I escalate this for you?”). Each can be rated yes or no from call listening or case sampling. For the fuller picture of measuring and driving behaviour change, see our ultimate guide to behaviour change.

Rank your data sources

Prefer sources in this order: system logs and records, process audits and quality data, sampled observation by managers, then self-reported surveys. Surveys are useful to explain why a group is lagging, not to prove that it has adopted.

Steps 3 and 4: Take a baseline, then track at fixed intervals

Adoption is measured as movement from a known starting point, so record current performance on every chosen indicator before go-live, then re-measure at consistent intervals after it, commonly at 30, 60 and 90 days. Report each stakeholder group separately, not as one blended average, because an average of 80% can hide a team stuck at 30%. Gallup’s May 2026 tracking of AI use shows why the curve matters: 15% of US employees use AI daily, 30% use it a few times a week or more, and 52% use it a few times a year or more. Experimenting is widespread; regular use is not. A single reading would have called that a success or a failure depending on the line you drew.

Expect an S-curve, not a change curve

The most popular chart in change management, the Kubler-Ross change curve, was built to describe how terminally ill patients cope with dying. A 2025 review in the Journal of Organizational Change Management traces its path into workplaces and notes that empirical support for a universal sequence of stages in organisations is limited. Treat any model that is simple and intuitively right with care: it can steer you away from stakeholders’ real input, which is often where the best ideas sit. For measuring adoption, the more defensible shape is the S-curve, familiar from technology and new-product adoption. It starts slowly, climbs steeply as the majority joins, then flattens. Our World in Data’s chart of US household technology adoption shows the same shape across a century of technologies.

4cf97b71 70e4 4a4e Acc1 C64abaeadd13

chaucer.com

6de4750b D4a3 43dc 8411 C882e4d9afa3

The curve’s steepness depends on the change:

  • Minor process change. A small step from the current process gives a gentle curve, reached quickly.
  • Complex new technology. A long, shallow start and a late climb are normal.
  • Iterative or agile change. Each release that touches users is a small S-curve of its own, and the releases should add up to a larger one.

The familiar adoption categories (innovators, early adopters, early majority, late majority and laggards) are useful here for targeting. Support that suits innovators does not suit late majority groups, so tailor your communication and help by where each group sits, and watch the early adopters first, since they signal whether the main wave will follow.

Set the interval schedule

As a working guide, simple process changes often stabilise within 30 to 60 days, significant system or behavioural changes within 90 to 180 days, and cultural or leadership changes can take a year or more. These are planning ranges from practice, not benchmarks, so confirm them against a pilot group before you commit leaders to a date.

Step 5: Report, diagnose and act

Measurement only changes outcomes when the right people see it on a rhythm and respond to it. Gallup finds that employees whose managers actively support AI use are 1.7 times as likely to use it a few times a week or more, yet only 36% of employees in AI-integrating organisations strongly agree their manager does. Managers are therefore part of the audience for your reporting, not only the executives who own the benefit.

Design the reporting routine

Plan the reporting process once the measures are set. These are the main considerations:

  1. Make reporting easy. Automate collection wherever possible, using in-app data and tools, so the burden stays low and the cadence survives busy periods.
  2. Set contribution expectations. Get stakeholder support so it is clear who supplies which data, and when.
  3. Make the dashboard readable. Design for quick understanding. Our guide to designing a change adoption dashboard and the reports executives want to see cover layout and audience.
  4. Build reinforcement. If a measure relies on people’s input, such as a survey, design a reason for them to respond. Without one, response rates drop.
  5. Choose recipients deliberately. Include the business leaders who own the benefit and the middle and first-line managers who shape daily behaviour.

Example of a change adoption dashboard from Change Automator

Example of change adoption dashboard from Change Automator

Diagnose before you intervene

When a group lags, work out which of three gaps explains it, because each has a different fix:

  • Awareness gap. People do not know what is changing or why. Communicate more clearly and more often.
  • Capability gap. People know, but cannot yet do it. Add training, practice or hands-on support in the specific tasks that fail.
  • Motivation gap. People can, but are not choosing to. Look to manager engagement, incentives and removal of the old way of working.

Then track whether the intervention moved the number at the next interval. That closes the loop that most change reporting leaves open.

Measuring adoption across several initiatives

Comparing adoption across initiatives needs a common scale, even though each initiative defines adoption differently. If you run a programme or portfolio, three common ways to report are the overall percentage of identified adoption elements achieved, the percentage of milestones reached, and the share of the target population showing the behaviour, supported by manager reports and system utilisation records. These give like-for-like comparison without forcing every initiative onto one definition.

Portfolio measurement also shows something single-initiative reporting cannot: which teams are absorbing several changes at once, and which interventions lead to higher adoption across the whole portfolio. For the strategic angle, see how to align multiple initiatives for maximum benefit realisation.

Where digital tools fit

Manual adoption tracking in spreadsheets works for one initiative and breaks down at portfolio scale. Digital platforms such as The Change Compass collect adoption data in the flow of work, report it by group and initiative, and show which change interventions are associated with higher adoption. Whatever tool you choose, apply the same five steps: the tool automates collection and reporting, but the definition, the behaviours and the baseline are still yours to set.

Start with one change and one baseline

Pick the change you are most worried about, and write down in one sentence what a person would be doing differently if it had worked. Choose three observable behaviours, find the data source for each, and take a baseline this week, before the next milestone gives you a reason to postpone it. Then book the 30, 60 and 90-day readings in the diary and agree who will see them. A rough baseline taken now is worth more than a polished one taken after go-live, and it gives you the one thing leaders rarely get from change reporting: evidence of movement they can trust. When you are ready to choose indicators for each behaviour, the adoption metrics guide is the next step, and the ultimate guide to measuring change puts it in context.

For the four stages of adoption, metrics by initiative type and how to set adoption targets, see our guide to change adoption stages, metrics and targets.

Frequently asked questions

How do you measure change adoption step by step?

Define what adoption looks like in observable terms, choose the behaviours and data sources that show it, record a baseline before the change, track each affected group at fixed intervals after go-live (commonly 30, 60 and 90 days), and use the gaps to trigger targeted action. Report by group rather than as one average, so lagging teams are visible.

What is the difference between change adoption and change compliance?

Compliance is doing the required thing because it is required or observed. Adoption is doing the new thing consistently because it has become the normal way of working. Employees who comply without adopting tend to revert when oversight eases, so measure behaviour again after support is withdrawn, not only at go-live.

How long does change adoption take?

As a working guide, simple process changes often stabilise within 30 to 60 days of go-live, significant system or behavioural changes within 90 to 180 days, and cultural or leadership changes can take 12 to 24 months or more. These are planning ranges drawn from practice, not research benchmarks, so set your own expected curve from a baseline and a pilot group.

How do you measure adoption when there is no system data?

Use observed behaviour instead of opinion: manager observation checklists, call or case sampling, process audits, and downstream quality or cycle-time data. Break the change into small observable micro-behaviours that can be rated yes or no, and sample a consistent number of cases per group at each interval. Use surveys to explain a gap, not to prove adoption.

How do you compare adoption across several change initiatives?

Define adoption separately for each initiative, then report on a common scale: the percentage of identified adoption elements achieved, the percentage of milestones reached, and the share of the target population showing the behaviour. This lets you compare like with like across a portfolio, and spot where several changes are landing on the same teams at once.

References

Measuring behaviours in change adoption – Infographic

Measuring behaviours in change adoption – Infographic

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.

Building change portfolio literacy in senior leaders: the missing link in enterprise transformation

Building change portfolio literacy in senior leaders: the missing link in enterprise transformation

Ask a senior leader whether they have adequate sponsorship for each of their change programmes, and most will say yes. Ask them how much cumulative change load their front-line teams are carrying across the full portfolio right now, and very few can answer. This gap, between confidence at the programme level and blindness at the portfolio level, is one of the most consistent and consequential failure patterns in enterprise transformation.

Change portfolio literacy is the ability to read, interpret, and act on a portfolio-level view of organisational change: what is changing, for whom, at what pace, and with what cumulative effect on the people being asked to absorb it all. In most organisations, this literacy is concentrated in change functions, if it exists at all. Senior leaders, the people with the authority to make the sequencing, resourcing, and prioritisation decisions that actually determine portfolio outcomes, typically lack it.

Closing this gap does not require turning executives into change managers. It requires giving them the information and the language to ask different questions of their change portfolios, and to act on the answers.

Why executives default to programme-level thinking

The governance structures that senior leaders use to oversee change are almost universally designed around individual programmes. Investment committees evaluate programmes. Executive sponsors are assigned to programmes. Status reporting comes from programmes. RAG dashboards present programme-level health. The system trains leaders to ask programme-level questions: Is this initiative on track? Is the business case holding? Are the milestones being met?

These are legitimate questions. The problem is that they are the wrong level of analysis for understanding whether organisational change is actually being managed well.

Prosci’s 12th edition Best Practices in Change Management study found that 52% of executive sponsors do not have an adequate understanding of their role in change. More revealing is what they are not being asked to do. Sponsor briefings cover individual initiative progress. They rarely cover cumulative load, portfolio interaction effects, or how a specific programme’s timeline is affecting the absorption capacity of the teams it targets.

This is a literacy problem, not an engagement problem. Most senior leaders are genuinely committed to sponsoring their change programmes. They are simply not equipped to see, or therefore to manage, the portfolio-level dynamics that determine whether the aggregate of those programmes succeeds.

What change portfolio literacy looks like in practice

A change-literate senior leader can engage meaningfully with four categories of information that portfolio-illiterate leaders typically cannot.

Cumulative impact by employee group

The most important thing a senior leader needs to understand about their change portfolio is not what each programme is doing, but how much aggregate change is landing on specific employee groups and when. A front-line operations team handling a systems migration, a restructure, and two new process changes simultaneously is in a materially different position from a team handling one of those changes in isolation. The risks to adoption, productivity, and retention are different. The support investment required is different.

Change-literate executives understand this. They can read a cumulative impact view by business unit or role group, recognise when load is elevated, and ask the right questions about whether the current portfolio plan is creating avoidable saturation risk.

Adoption evidence, not delivery evidence

Delivery reporting, milestones hit, go-lives completed, budgets on track, tells leaders that work is being done. It does not tell them whether change is actually occurring. A programme can be on time, on budget, and fully compliant with its governance requirements, while adoption in the target group is running at 40% of plan.

Change-literate executives insist on seeing adoption data alongside delivery data. They understand that a portfolio where every programme is green from a delivery perspective can simultaneously be in serious trouble from a change perspective, if adoption is consistently underperforming across multiple initiatives.

Change load relative to absorptive capacity

Every employee group has a finite capacity to absorb change over a given period. That capacity is shaped by prior change history, current baseline workload, the quality of management support, and the degree to which prior changes have genuinely embedded. When demand exceeds capacity, adoption quality degrades across the board.

Change-literate executives can engage with the concept of absorptive capacity and understand when their portfolio plan is structurally likely to exceed it for specific groups. This understanding changes how they approach sequencing decisions. Instead of defaulting to the programme that has the most political momentum or the most urgent business driver, they can weigh the organisational cost of proceeding on the current timeline against the cost of adjustment.

Portfolio governance authority

Effective change portfolio management requires a governance body that can make cross-programme decisions: delay a go-live, consolidate two programmes with overlapping target groups, redirect resource from a low-priority initiative to a high-saturation-risk group. Individual programme sponsors cannot make these decisions, because each has a rational incentive to advocate for their programme’s priority.

Gartner’s research indicates that by 2026, 30% of organisations will have invested in the talent and tools needed for strategic portfolio management. Change-literate senior leaders understand that this portfolio governance body needs to exist, what authority it requires, and why it cannot be replaced by bilateral conversations between programme sponsors.

The language executives need to understand

Building change portfolio literacy is partly a matter of vocabulary. Executives who can use these terms precisely are better equipped to ask useful questions of their change functions.

Change load refers to the aggregate demand that active and planned change initiatives place on a specific employee group over a defined period. High load is not inherently bad. Load that exceeds absorptive capacity is the problem.

Change saturation is the condition that occurs when cumulative load has depleted an employee group’s capacity to engage with change meaningfully. Saturated groups show characteristic patterns: disproportionate resistance to new initiatives, declining engagement scores, elevated support demand after go-live, and adoption curves that plateau well below target.

Change collision occurs when two or more initiatives demand significant behavioural change from the same group simultaneously, without coordination of timing or support. Collision reduces adoption outcomes for both initiatives and is almost entirely preventable with adequate portfolio visibility.

Absorptive capacity is a group’s ability to take on and embed new changes given their current and recent change history. It is not a fixed attribute. It is shaped by management quality, support availability, and the embedding status of prior changes.

Portfolio sequencing is the deliberate ordering and timing of change initiatives across the portfolio to minimise collision, respect absorptive capacity, and prioritise strategically important changes when load is high.

Building change portfolio literacy in your senior team

The most effective approach to building executive change portfolio literacy is showing, not telling. Most senior leaders do not become change-literate through briefings or methodology overviews. They become change-literate through repeated exposure to portfolio-level data and the decision-making conversations it enables.

The practical steps that change functions have found most effective include:

  • Starting with a portfolio view presentation. The first exposure to a cumulative impact map, showing load by business unit across the next two quarters, typically generates immediate questions from executives who have never seen change represented this way. The visual is more effective than any explanation. Use it to introduce vocabulary and invite questions rather than present conclusions.
  • Integrating portfolio data into existing governance forums. The most sustainable path to change portfolio literacy is connecting it to forums that already have authority: transformation steering committees, executive leadership team meetings, and business unit leadership reviews. A dedicated change forum that sits outside the existing governance structure will struggle to influence sequencing and resourcing decisions.
  • Framing in the language executives use. Change functions that speak the language of adoption rates, impact dimensions, and change saturation scores when executives are thinking in terms of revenue risk, talent retention, and business case delivery lose the room. The translation layer is the change leader’s job: “this programme’s go-live creates a 12-week window where our customer operations team carries a load equivalent to three major initiatives, based on what we know about their prior absorption rate.”
  • Making sponsor coaching a regular practice. Prosci’s research consistently finds that active and visible executive sponsorship increases change success rates by up to six times. But sponsorship quality depends on sponsor understanding. Regular, structured coaching conversations with programme sponsors, covering not just their individual programme but the portfolio context their programme sits within, is one of the highest-return investments a change function can make.

What good looks like: the change-literate leadership team

In organisations where change portfolio literacy is genuinely embedded at the senior level, the conversations in governance forums are qualitatively different. Rather than programme-by-programme status reviews, leadership teams engage with portfolio-level questions:

  • Which employee groups are carrying the highest cumulative load over the next quarter, and is the planned timeline for the new system programme going to push them into saturation risk?
  • Are our adoption rates across the portfolio consistent with our transformation ambitions, or are we systematically leaving value on the table by treating change management as a delivery function?
  • What would we need to do differently in the next six months to build absorptive capacity in our most change-impacted groups, rather than continuing to deploy at the current pace?

These are the questions that change-literate leaders ask. They are also the questions that drive the resourcing, sequencing, and investment decisions that determine whether an enterprise transformation programme delivers its intended value.

Developing the digital infrastructure to support these conversations, through portfolio platforms that aggregate impact data, track adoption across programmes, and generate the portfolio views that executive conversations require, is a practical prerequisite. Tools such as The Change Compass are built specifically for this purpose: providing the portfolio visibility that makes change portfolio literacy actionable rather than aspirational.

Where to start

Building change portfolio literacy in a senior team takes time, but the first step is quick. Prepare a single portfolio view: all active and planned change initiatives, mapped against the employee groups they affect, with a simple cumulative load indicator for the next 90 days.

Present it at a senior forum where decisions about transformation investment and sequencing are made. Do not frame it as a change management presentation. Frame it as a risk and capacity picture for the organisation’s transformation programme. The questions it generates will do more to build change portfolio literacy in 20 minutes than any amount of methodology briefing.

From there, the task is to make this view a regular feature of the governance conversation, not a one-off analysis. Literacy builds through repeated engagement with data and the decisions it informs.

Frequently asked questions

What is change portfolio literacy?

Change portfolio literacy is the ability of senior leaders to read and act on a portfolio-level view of organisational change: understanding cumulative change load by employee group, interpreting adoption evidence across multiple programmes, recognising change collision and saturation risk, and making portfolio-level sequencing and resourcing decisions that reflect these dynamics.

Why do senior leaders struggle with change portfolio management?

The governance structures most organisations use for managing change are designed around individual programmes, not portfolios. Status reporting, sponsorship briefings, and investment decisions all happen at the programme level. This structure trains senior leaders to ask programme-level questions and leaves them without the visibility to engage with portfolio-level dynamics, even when they are the primary driver of adoption outcomes.

How is executive sponsorship different from change portfolio literacy?

Executive sponsorship is the active, visible support a senior leader provides to a specific change initiative. Change portfolio literacy operates above this level. It is the ability to understand the collective effect of all change initiatives across the portfolio, and to make cross-programme decisions that optimise overall adoption outcomes rather than individual programme outcomes. Both are necessary for effective enterprise change management.

What data does a change portfolio view need?

At minimum: a list of all active and planned change initiatives, the employee groups affected by each, the intensity and duration of impact, and the current adoption or readiness status. Aggregated across programmes, this data produces the cumulative load view by employee group that is the foundation of portfolio-level decision-making.

How do you develop change portfolio literacy in a senior team?

The most effective approach is repeated exposure to portfolio-level data in governance forums where decisions are made. Starting with a single portfolio view presentation, integrating change data into existing leadership forums, and making sponsor coaching a regular practice are the three interventions that change functions consistently find most effective for building executive change literacy over time.

References

  • Prosci. Best Practices in Change Management, 12th Edition, Executive Summary. https://empower.prosci.com/best-practices-change-management-executive-summary
  • Prosci. 5 Strategic Decisions for Building Organizational Change Capability in 2026. https://www.prosci.com/blog/5-strategic-decisions-for-building-organizational-change-capability
  • Gartner. Top Trends for Program and Portfolio Management Leaders for 2025. https://www.gartner.com/en/documents/6533602
  • Smartsheet. 2025 Project and Portfolio Management Priorities Report. https://www.smartsheet.com/content-center/inside-smartsheet/research/2025-ppm-priorities-report-key-takeaways
  • OCM Solution. 2025-2026 Organizational Change Management Trends Report. https://www.ocmsolution.com/organizational-change-management-ocm-trends-report/