Change management reports are the structured outputs that translate portfolio-level change activity, adoption progress, readiness signals and operational impact into the language and timeframes that executive sponsors, programme boards and senior leaders need to make decisions. The strongest reports combine four data layers: portfolio view (what is in flight and when), impact view (which groups are absorbing what), adoption view (whether new ways of working are sticking) and risk view (where saturation, sponsorship or capacity gaps threaten outcomes). Effective reporting cadences are tied to decision rhythms (monthly executive meetings, quarterly portfolio reviews) rather than producing data for its own sake.
Why Nailing the Right Change Management Metrics is Critical and Can Make or Break Your Reputation
As organizations strive to adapt and thrive in dynamic environments, how the change management process is tracked has become a strategic imperative. However, the success of any change initiative hinges not only on effective planning and execution but also on the ability to measure and communicate its impact accurately. After all, without the right measures how do we know that we are moving in the right direction? In this article, we explore critical change management reports that executives value in shaping organizational understanding and decision-making. We delve into the metrics that may compromise your credibility and, more importantly, highlight the metrics that executives truly value, providing a roadmap to creating reports that resonate with leadership.
Reading your executives and where they are
Prior to designing the right change management reports and metrics it is absolutely essential that you understand where they are coming from. Understanding their key concerns and perspectives will help you design the right content to engage them. Key questions you may want to delve into include:
What issues are top of mind for executives when it comes to managing change?
What has worked or not worked well in the past for change (within what timeline) that should be taken into account?
How experienced are these executives in driving complex change?
Putting your strategic hat on, what are the key business performance challenges that executives are facing into? What are the people and change connections to these?
What are the top key organisational risks that executives are focused on? What are the people and change connections to these?
Vanity Metrics – Metrics That Don’t Connect to Business Outcomes
One of the pitfalls in change management reporting is the reliance on vanity metrics—superficial measures that may look impressive but lack a direct connection to tangible business outcomes. Metrics such as the number of training hours delivered, numbers of stakeholder groups who received communications or the volume of communication materials distributed might seem impressive and easy to measure, but they provide little insight into the real impact of the change on the organization.
Executives are not interested in surface-level data; they want to understand how the change contributes to the achievement of strategic objectives and positively influences key performance indicators. To enhance credibility, change management reports must move beyond vanity metrics and focus on indicators that align with broader business goals.
Activity Metrics – Counting Without Context
Measuring the sheer volume of activities related to a change initiative can be misleading, or worse, meaningless, if not accompanied by context and relevance. Activity metrics, such as the number of workshops conducted, numbers of impact assessment activities conducted, number of deliverables worked on, or emails sent, might create an illusion of progress. However, these metrics fail to provide insights into the quality of engagement, the depth of understanding among employees, or the actual impact on work behaviours. Operational managers may find these interesting, but less likely for executives.
Instead of focusing solely on activities, change management reports should emphasize the effectiveness of these activities in driving desired outcomes. Metrics should, instead, highlight the quality of engagement, the level of understanding, and the behavioural shifts observed within the organization.
Cost-Focused Metrics – Counting Dollars Without Value
While cost-related metrics are important for financial stewardship, solely focusing on cost without considering the value generated by the change can undermine the perceived success of the initiative. Metrics such as the budget spent or the cost per participant may provide financial insights but do not necessarily convey the broader impact on organizational performance.
Change management reports should focus more on value metrics than cost metrics. Focusing purely on cost is restricting the value of managing change as another cost to the business. However, focusing on the value created in maximising business performance and achieving greater adoption can significant extend the understanding of change management value. Executives are interested in understanding what business value is created through managing change. Value includes how the targeted benefits are better realised and how the business performance is protected or maximised during the implementation of change.
Intra-Practice Metrics – Metrics That Only Change Management Cares About
It’s a common misstep to develop metrics that only resonate within the change management function and key project milestones but fail to capture the attention of other business units or executives. Metrics that focus exclusively on communication buzz generated, training satisfaction rates, or employee satisfaction with change processes might be valuable for internal assessments but lack the relevance needed to engage executives.
Even the focus on change maturity, that is often the single most critical focus for change management functions, may or may not appeal to a lot of executives. Unless you have already taken the executives on the journey of why focusing on change maturity is critical and you have them fully onboard with this, treat carefully in reporting on change maturity metrics.
At executive level, change management reports should transcend departmental boundaries and speak to the broader organizational impact. This means that your focus should be on reporting at a portfolio level and key strategic initiatives as relevant. Focus on generating insights of what the totality of changes mean to the organisation, and what employee experiences are across multiple initiatives. Metrics should also align with strategic goals and showcase how the change initiatives contributes to overarching business objectives.
The Right Metrics
I. Change Readiness Metrics – Assessing the Pulse of the Organization
Change readiness metrics serve as a barometer for understanding how prepared an organization is for a change initiative. To provide meaningful insights, these metrics should delve into the engagement journey, capturing key elements such as awareness, involvement, and participation.
Awareness: Measure the level of understanding and awareness of the upcoming change across different employee segments.
Involvement: Assess the degree to which employees are actively engaged in the change process, seeking their input and involvement.
Participation: Evaluate the extent to which employees are actively participating in change-related activities and initiatives.
Data Collection Methodology
Utilize a mix of quantitative and qualitative methods to gather data, including surveys, focus groups, and feedback mechanisms.
Ensure a representative sample across different organizational levels and functions to capture a comprehensive view of readiness.
Change Readiness Topic Areas
1. Awareness Assessment:
This section evaluates the extent to which employees are aware of the impending changes across initiatives. It includes an analysis of communication effectiveness, the clarity of messaging, and the overall visibility of the change initiatives. Metrics may encompass the percentage of employees who understand the change purpose and the reach of communication channels.
2. Involvement Evaluation:
Involvement is a key factor in gauging how actively employees are participating in the change process. This explores the degree to which employees feel engaged and have opportunities to contribute to the planning and decision-making aspects of the change. Employees may not have the opportunities to contribute to all types of change initiatives but for those that are relevant this can be quite insightful. Metrics include participation rates in change-related workshops, the number of submitted suggestions, and levels of engagement in feedback sessions.
3. Perceived Impact:
This area delves into employees’ perceptions of how the changes will affect them personally and professionally. It includes an analysis of perceived benefits, risks, and the overall impact on day-to-day responsibilities. Metrics may encompass the percentage of employees who feel well-informed about the impact of the change and qualitative insights from open-ended survey questions.
4. Change Champions performance:
Identifying and nurturing change champions can be crucial for successful change implementation, especially across the change portfolio. The presence of key business change champions who actively support and advocate for the changes within their teams and business units can shed light on how the change is performing. Metrics include the presence of key change champions across business areas, their engagement levels, and the effectiveness of their engagement strategies within their respective departments.
5. Learning and Development Readiness:
Learning and development play a vital role in equipping employees with the skills necessary for the upcoming changes. This section evaluates the organization’s readiness to deliver learning programs effectively, including the availability of resources, the alignment of learning content with change objectives, and the accessibility of learning materials. This can be outlined not just at initiative levels, but from business unit perspectives. Different business units may have different processes and channels from which to deploy learning and development across initiatives. The readiness and maturity of these can make or break the adoption of changes.
6. Resource Allocation and Availability:
Change initiatives often require additional resources, and this section examines the organization’s capacity to allocate and provide the necessary resources for a smooth transition. Metrics include the allocation and availability of SME resources, business representatives, the availability of technology and tools, and the overall preparedness of support functions for the myriad of change initiatives. Is there adequate allocation of these resources? For example, for digital transformation is there still reliance on manual work processes that should be upgrade to drive efficiency and effectiveness?
7. Leadership Alignment:
Leadership alignment is a critical factor influencing change readiness. This section evaluates the extent to which various leaders are aligned with the change vision and actively communicate their support. Metrics encompass leadership messaging consistency, visibility, and the perceived commitment of leaders to the success of the change.
8. Employee Feedback Mechanisms:
Establishing effective feedback mechanisms is essential for continuous improvement during change initiatives. This section assesses the availability, content and effectiveness of channels through which employees can provide feedback, ask questions, and express concerns. Metrics include response rates to feedback requests, the variety of feedback channels used, and themes of responses from targeted employee groups.
Change Readiness Data Collection Methods
Collecting data on change readiness is a crucial step in understanding an organization’s preparedness for a change initiative. Various approaches can be employed to gather relevant information. Here’s a list of key approaches:
Surveys and Questionnaires
Focus Groups
Interviews
Observation
Benchmarking
Document Analysis
Readiness Workshops
Network Analysis
Online Platforms and Social Listening
Pulse Surveys
Interactive Assessments
II. Change Journey Analytics – Navigating the Transformation Landscape
Change journey analytics provide a view of what key employee change experience highlights are, including insights on any behavioural changes, attitudinal changes, the volume of changes and how changes are being driven against key business performance challenges.
Change Volume Risks – Change volume risk measures highlight key change impact volumes across the business over time, with key call outs on any risks on heightened change periods.
Change Activity Design – The totality of change management activities across initiatives from the lens of impacted employee groups should be analysed with potential risks highlighted.
Single View of Change of BAU and Strategic Initiatives – Provide a consolidated view of ongoing business-as-usual (BAU) changes alongside strategic initiatives.
Business Performance – Link change activities to business performance metrics. Demonstrate how the change initiative contributes to key performance indicators and strategic goals.
Nurturing Lasting Transformation: The Role of Adoption Analytics in Sustainable Change
When we discuss adoption analytics, we transcend the traditional boundaries of project management. While implementation marks the beginning of change, adoption analytics guide us through the more profound stages, measuring the extent to which the organization has embraced and embedded the change.
1. Business Performance Metrics: Gauging Impact on Organizational Vital Signs
To truly understand the success of change initiatives, one must look beyond the surface and delve into its impact on key business performance metrics. This involves a holistic examination of factors such as productivity, efficiency, and customer satisfaction.
Productivity: Assessing the changes’ effects on productivity involves measuring the organization’s output and efficiency post-implementation.
Efficiency: Changes often aim to streamline processes and enhance efficiency.
Customer Satisfaction: In many cases, change initiatives are driven by a desire to improve customer experience.
By examining these metrics, organizations can gauge the real impact of the change on their vital signs, ensuring that the intended improvements manifest in tangible and measurable ways.
2. Benefit Realization: From Anticipation to Tangible Outcomes
Anticipated benefits form the backbone of any change initiative, but true success lies in the tangible realization of these expected outcomes. Benefit realization assessment through adoption analytics involves tracking key performance indicators (KPIs) directly influenced by the change.
Tracking KPIs: Identify and monitor KPIs that are closely tied to the specific objectives of the change.
Tangible Outcomes: Work hand-in-hand with initiative benefit owners to ensure clear ownership and tracking of benefits.
Continuous Improvement: Benefit realization is an ongoing process. Regularly review and adjust strategies based on the data collected.
Collaboration with Initiative Benefit Owners: A Crucial Element
A vital aspect of successful adoption analytics is collaboration with initiative benefit owners. Establishing clear ownership ensures accountability and facilitates a more targeted and effective approach to tracking and optimizing outcomes.
Crafting Compelling Change Management Reports
In the fast-paced world of change management, the ability to convey the impact of initiatives through well-crafted reports is a skill that cannot be underestimated. Executives require more than superficial metrics; they demand a nuanced understanding of how change aligns with strategic goals and influences organizational performance.
By steering clear of vanity metrics, activity-focused measurements, and overly cost-centric reporting, change management professionals can elevate their credibility and influence within the organization. Instead, a focus on change readiness, journey analytics, and adoption metrics provides a holistic perspective that resonates with executives.
A change management report for executive audiences should include: overall change programme status (on track, at risk, or off track); adoption and readiness metrics with trend direction; the top three risks with recommended mitigation actions; decisions required from the executive; and a summary of the change portfolio load on the most affected employee groups.
How often should change management reports be produced?
Portfolio-level change management reports should be produced monthly, aligned to the organisation’s governance calendar. Reports for active, high-risk change programmes should be produced fortnightly.
How do you make change management reports credible to senior leaders?
Credibility comes from data, not opinion. Reports that include quantitative adoption rates, readiness scores, and specific risk assessments are significantly more credible than reports that describe activities or use subjective language.
Infographic: Making impact with change management charts
Choosing the right chart type is as important as having the right data. This infographic summarises the key principles for selecting and designing change management charts that make an immediate impact with your audience.
Scaled Agile Framework (SAFe) has emerged as a leading methodology to address the organisational change demands of fostering flexibility, collaboration, and continuous improvement. A cornerstone of SAFe is the principle of ‘Measure and Grow,’ which emphasizes using data and fact-based decisions to enhance change outcomes over time, including predictability. Despite its centrality, SAFe does not explicitly detail the change management components essential for its success, including its deep understanding of SAFe’s measurement model that enables the design of a tailored metrics strategy for ensuring strategic alignment. Here we outline how change management practitioners can effectively apply the ‘Measure and Grow’ principle within an Agile Release Train (ART) to lead change and improve outcomes to support the Scaled Agile environment.
What does it mean to “measure and grow” in a business context?
In a business context, “measure and grow” refers to the process of evaluating performance metrics to identify how our work drives business value and areas for improvement, aligning with strategic business goals. By analyzing data, companies can implement strategies that foster growth, enhance productivity, and improve overall outcomes. This approach ensures continuous development aligned with organizational goals.
The “Measure and Grow” Principle in Scaled Agile
What does it mean to “measure and grow” in a business context?
“Measure and grow” in a business context refers to the process of assessing performance metrics and outcomes to identify areas for improvement. By analyzing data, businesses can implement strategies that foster growth, enhance customer satisfaction, and optimize resource allocation, ultimately driving sustainable success and competitive advantage.
“Measure and Grow” is integral to SAFe, focusing on systematic measurement and continuous improvement for overall business agility within the value stream. By leveraging data and analytics, organizations can quickly respond to market changes, make informed decisions that meet the needs of our customers, identify areas needing attention, uncover improvement opportunities, and iteratively enhance meaningful change in performance. For change management professionals, this principle translates into a structured approach to evaluate the effectiveness of change initiatives, pinpoint areas for improvement, and implement necessary adjustments.
In a Scaled Agile environment, “Measure and Grow” is a core tenant or principle that applies in all types of agile environments. By continuously assessing and refining change efforts, organizations can align their initiatives with strategic objectives, mitigate risks, and ensure sustained success.
In practice, a lot of organisations have not pinpointed exactly how change management measures can make or break the outcome of the change, and in a SAFe environment, across the program, portfolio as well as enterprise.
The ‘Measure and Grow’ principle as a core part of SAFe (From Scaled Agile Framework)
To operationalize the “Measure and Grow” principle in change management, it is crucial to establish a set of metrics and assessment frameworks. Here are some broad categories of different types of change measurements that are relevant. Note that since we are talking about SAFe, it is not just at the initiative level that we are talking about metrics. More importantly, it is about establishing a system to promote change improvement across the organisation.
Change Management KPIs and OKRs
Key Performance Indicators (KPIs) and Objectives and Key Results (OKRs) are essential tools for tracking the success of change management initiatives. KPIs provide quantitative measures of performance, while OKRs align change efforts with broader organizational goals. A change management stream or function should focus on establishing KPIs or OKRs to achieve laser focus on achieving change outcomes.
Examples of Initiative-Level Change Management KPIs that may roll out to form portfolio views
Employee Engagement Levels: This KPI assesses how change impacts employee morale and engagement, providing insight into the overall acceptance and support of the change initiative.
Learning Achievement Rates: This can include tracking the percentage of employees who have completed necessary training programs, as well as achieving the target level of competence to ensure that the workforce is adequately prepared for the change.
Feedback Scores: Collecting feedback from stakeholders through surveys or feedback forms helps gauge perception and identify areas needing improvement. It is important to note that depending on the change context, stakeholders may not be happy with the content of the change. However, understanding and tracking this perception is still important.
Change Adoption Rate: This KPI measures the percentage of stakeholders who have adopted the change. High adoption rates are the ultimate goal for initiatives.
Issue Resolution Time: Measuring the time taken to resolve user-related issues related to the change highlights the efficiency of support mechanisms and the responsiveness of the change management team. This is especially important during an agile environment where there may be constant changes.
Change Readiness and Stakeholder Engagement Metrics
Evaluating change readiness and stakeholder engagement is crucial to the success of any change initiative. These metrics help assess the organization’s preparedness for change and the level of involvement and support from key stakeholders. Readiness and engagement rates can also roll up at a portfolio level to provide oversight.
Change Readiness Metrics
Readiness Assessments: Conduct surveys or interviews to gauge the organization’s preparedness for the impending change. This can include evaluating awareness, understanding, and acceptance of the change.
Resource Availability: Measure the availability of necessary resources, such as budget, personnel, and tools, to support the change initiative.
Communication Effectiveness: Assess the clarity, frequency, and effectiveness of communication regarding the change to ensure stakeholders are well-informed and engaged.
Stakeholder Engagement Metrics
Engagement Scores: Use surveys or feedback forms to measure the engagement levels of stakeholders, indicating their commitment and support for the change.
Participation Rates: Track stakeholder participation in change-related activities, such as workshops, meetings, and training sessions, to gauge their involvement.
Influence and Support: Assess the influence and support of key stakeholders in driving the change, ensuring that influential figures are actively endorsing the initiative.
By monitoring these metrics, change management professionals can identify potential barriers to change and take proactive steps to enhance readiness and engagement.
Stakeholder Competency Assessment
Successful change initiatives rely on the competence and readiness of key stakeholders. Assessing stakeholder competency involves evaluating the capability of sponsors and change champions to support and drive the change.
Sponsor Readiness/Capability Assessment
Sponsor Engagement: Measure the level of engagement and commitment from sponsors, ensuring they are actively involved and supportive of the change.
Decision-Making Effectiveness: Assess the ability of sponsors to make timely and effective decisions that facilitate the change process.
Resource Allocation: Evaluate the sponsor’s ability to allocate necessary resources, such as budget and personnel, to support the change initiative.
Change Champion Capability Assessment
Training and Knowledge: Measure the knowledge and training levels of change champions to ensure they are well-equipped to support the change.
Communication Skills: Assess the ability of change champions to effectively communicate the change message and address stakeholder concerns.
Influence and Leadership: Evaluate the influence and leadership capabilities of change champions, ensuring they can effectively drive and sustain the change.
By conducting these assessments, change management professionals can ensure that key stakeholders are prepared and capable of supporting the change initiative.
Change Adoption Metrics
Change adoption metrics provide insight into how well the change has been accepted and integrated into the organization. These metrics help assess the effectiveness of the change initiative and identify areas for improvement. At a portfolio level, there may be different levels of change adoption set for different initiatives depending on priority and complexity.
Key Change Adoption Metrics
Adoption Rate: Measure the percentage of stakeholders who have adopted the change, indicating the overall acceptance and integration of the new processes or systems.
Usage Metrics: Track the usage of new tools, processes, or systems introduced by the change to ensure they are being utilized as intended.
Performance Metrics: Assess the impact of the change on key performance indicators, such as productivity, efficiency, and quality, to determine the overall success of the change initiative.
By monitoring these metrics, change management professionals can gauge the success of the change initiative and identify opportunities for further improvement. To read more about change adoption metrics check out The Comprehensive Guide to Change Management Metrics for Adoption.
Change Impact and Capacity Metrics
Understanding the impact of change and the organization’s capacity to manage it is crucial for successful change management. Change impact metrics assess the effects of the change on the organization, while capacity metrics evaluate the organization’s ability to manage and sustain the change.
Change Impact Metrics
Aggregate impacts: Aggregate impacts across initiatives to form a view of how various teams and roles are impacted by various changes.
Risk Assessments: Identify potential risks associated with the change and evaluate their impact, ensuring that mitigation strategies are in place. A particular focus should be placed on business performance during change, across initiatives.
Capacity Metrics
Resource Capacity: Assess the availability of resources, such as personnel, budget, and tools, to support the change initiative and optimize flow time, enhance flow velocity, and improve flow efficiency while monitoring Flow Load.
Change Fatigue: Measure the risk for potential fatigue within the organization and its impact on stakeholders, ensuring that change initiatives are paced and driven appropriately.
Support Structures: Evaluate the effectiveness of support structures, such as training programs, information hubs, and help desks, in facilitating the change. Support structures may also include change champion networks.
By assessing change impact and capacity, change management practitioners can ensure that the organization is well-equipped to manage and sustain the change initiative.
Change Maturity Assessment
Change maturity assessments provide a comprehensive evaluation of the organization’s capability to manage change effectively. These assessments help identify strengths and weaknesses in the organization’s change management practices and provide a roadmap for improvement.
The Change Management Institute (CMI) Change Maturity Model is a comprehensive framework that takes a holistic approach to enhancing an organization’s change management maturity. It’s divided into three core functional domains, each playing a vital role in the overall journey toward maturity:
Project Change Management
Business Change Readiness
Strategic Change Leadership.
These domains serve as the foundation for achieving higher levels of maturity within the organization.
Within each of these domains, the CMI model outlines a structured path, consisting of five distinct maturity levels. These levels represent a continuum, starting at Level 1, which serves as the foundational stage, and progressing all the way to Level 5, the zenith of maturity and effectiveness. This multi-tiered approach offers organizations a clear roadmap for growth and development, ensuring that they have the tools and insights necessary to navigate the complexities of change management.
By conducting regular change maturity assessments, change management professionals can identify areas for improvement and develop targeted strategies to enhance the organization’s change management capability.
The “Measure and Grow” principle is a powerful tool for improving change outcomes in a Scaled Agile environment. By leveraging data and fact-based decision-making, change management professionals can ensure that change initiatives are effective, aligned with strategic objectives, and continuously improving. Establishing robust metrics and assessment frameworks, such as KPIs, OKRs, change readiness and stakeholder engagement metrics, stakeholder competency assessments, change adoption metrics, change impact and capacity metrics, and change maturity assessments, is essential to applying the “Measure and Grow” principle effectively.
Incorporating these metrics and assessments into change management practices enables organizations to identify areas for improvement, make informed decisions, and drive continuous improvement. By doing so, change management professionals can enhance the effectiveness of change initiatives, ensure successful adoption, and ultimately achieve better business outcomes.
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:
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.
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.
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.
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.
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.
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.
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.
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:
Number of divisions impacted
Number of stakeholder groups impacted
Number of employees impacted
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:
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.
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.
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.
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.
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.
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
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.
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
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.
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.
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.
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.
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.
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
Simplify Visuals: Use clear, simple visuals that highlight the key messages. Avoid clutter and ensure that the most important data points stand out.
Example: Use bar charts or line graphs to show trends over time rather than pie charts that can be harder to interpret.
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.
Example: Accompany a Go-Live count with a visual showing the varying impact level of various implementation activities of the changes.
Example: Use bar charts or line graphs to show trends over time rather than pie charts that can be harder to interpret.
Example: Accompany a Go-Live count with a visual showing the varying impact level of various implementation activities of the changes.
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.
Example: Instead of presenting raw data, provide a summary that explains key trends, successes, and areas needing attention.
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.
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.
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.
Example: Hold monthly review meetings with stakeholders to discuss the latest metrics, address concerns, and adjust strategies as needed.
Example: Instead of presenting raw data, provide a summary that explains key trends, successes, and areas needing attention.
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.
Example: Hold monthly review meetings with stakeholders to discuss the latest metrics, address concerns, and adjust strategies as needed.
Examples of Effective Metrics
Employee Adoption and Engagement
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.
Implementation: Use software usage analytics or surveys to track tool adoption rates.
Visualization: A graph showing adoption rates over time.
Employee Feedback Scores: Collect feedback on change initiatives through surveys or stakeholder ratings to measure sentiment/feedback and identify areas for improvement.
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).
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.
Implementation: Use software usage analytics or surveys to track tool adoption rates.
Visualization: A graph showing adoption rates over time.
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).
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
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.
Implementation: Identify relevant KPIs and measure their performance before and after change initiatives.
Visualization: Use line/bar graphs to show trends in KPI performance over time.
Operational Efficiency Metrics: Measure improvements in operational processes, such as reduced cycle times, error rates, or cost savings.
Implementation: Track specific operational metrics relevant to the change initiatives.
Visualization: Bar charts or heatmaps showing improvements in efficiency metrics across different operational areas.
Implementation: Identify relevant KPIs and measure their performance before and after change initiatives.
Visualization: Use line/bar graphs to show trends in KPI performance over time.
Implementation: Track specific operational metrics relevant to the change initiatives.
Visualization: Bar charts or heatmaps showing improvements in efficiency metrics across different operational areas.
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 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.
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.
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.
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.
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.
Metric
System implementation
Compliance change
Restructure
Reach and active-use rate
High priority
Moderate
Low
Feature or workflow depth
High priority
Low
Low
Process compliance rate
Moderate
High priority
Moderate
Incident or error rate
Moderate
High priority
Low
Manager observation or coaching
Moderate
High priority
High priority
Assessed proficiency
Moderate
High priority
Moderate
Engagement or clarity pulse
Low
Moderate
High priority
Reversion rate
High priority
Moderate
Moderate
Productivity vs pre-change baseline
High priority
Moderate
High 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 see
Likely meaning
Where to look
High reach, low depth
People log in but bypass the core workflow
Process design, training on the critical steps
High usage, low proficiency
Use without the intended behaviour
Coaching, job aids, manager reinforcement
Strong pilot, weak elsewhere
Local conditions, not a general result
Team-level segmentation, champion coverage
Good at go-live, decline at 90 days
Reinforcement withdrawn too early
Sustainment plan, manager accountability
Good adoption, no outcome movement
Wrong behaviour targeted, or benefit case flawed
Revisit 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.
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:
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 benefit
Change steps required
Adoption measure
Baseline
Target
Higher customer satisfaction and productivity
Users 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 coaching
Set before go-live
Agreed with the project manager
Faster resolution
Users proactively apply new features to drive conversations
Monthly benefit tracking shared in team meetings; customer communication about the improved process
Customer satisfaction score; call volume handled
Current score
Agreed 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.
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.
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.
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.
Plan the reporting process once the measures are set. These are the main considerations:
Make reporting easy. Automate collection wherever possible, using in-app data and tools, so the burden stays low and the cadence survives busy periods.
Set contribution expectations. Get stakeholder support so it is clear who supplies which data, and when.
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.
Choose recipients deliberately. Include the business leaders who own the benefit and the middle and first-line managers who shape daily behaviour.
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.
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.
