Why most change measurement falls short

The most common change measurement approach is to track the activities of a specific change programme: how many people were trained, how many communications were sent, what the survey results showed at go-live. This is not without value. Programme-level activity data provides accountability for change delivery and allows teams to identify when specific components — training, communication, stakeholder engagement — are underperforming relative to plan.

But activity measurement has a fundamental limitation: it measures what the change programme did, not whether what it did worked. A programme can achieve 95 percent training completion and still fail to produce the behaviour change the business needs. Prosci’s research on change management ROI consistently finds that programmes with excellent activity metrics but poor adoption outcomes are common — and that the gap between activity and adoption is the primary measurement failure in the field.

The second limitation is that programme-level measurement is blind to the portfolio effect. A team absorbing three major changes simultaneously may show adequate readiness on each programme’s assessment, while its actual adaptive capacity is severely depleted. No programme-level measurement system can detect this, because each programme sees only its own impact on the team. Portfolio-level measurement — the enterprise and business unit levels of the framework — is required to make the cumulative picture visible.

The three levels of change management measurement

A comprehensive change measurement framework operates simultaneously across three levels. Each level has its own measurement purpose, its own data requirements, and its own primary audience. Building measurement capability at all three levels is what distinguishes organisations that can genuinely manage their change portfolio from those that can only report on individual programme activities.

Enterprise level

Enterprise-level change measurement answers the question: how well is our organisation managing change as a strategic capability? It is concerned with the aggregate picture — the total change load being absorbed across the organisation, the distribution of that load across different parts of the business, and the organisation’s overall change capacity and maturity. The primary audience for enterprise-level metrics is the executive team and board, for whom change management is a risk and capability question rather than a delivery question.

Key enterprise-level measures include the total volume of change programmes in flight across the portfolio, the concentration of change load in specific divisions or role groups, trend data on change saturation and fatigue indicators (attrition rates during high-change periods, engagement score movements, absenteeism), and overall adoption rates across major transformation programmes. Enterprise-level measurement also includes benchmarking: how does the organisation’s change capacity compare to research-derived standards or to prior periods?

The enterprise-level view is what enables the most consequential change governance decisions: whether to defer a programme because specific teams are already at or beyond their absorption capacity, whether to invest in additional change resources because the portfolio is systematically under-resourced, or whether specific divisions require targeted capability development to handle the rate of change expected of them.

Business unit level

Business unit-level measurement answers the question: how well is change landing in this part of the organisation? It operates at the level of a division, department, or significant team, and is primarily concerned with the change experience of a defined employee group across all the changes affecting them simultaneously — not just the changes coming from a single programme.

Business unit-level measures include the aggregate change impact score for the group — a composite measure of how many changes are affecting the group, how significant those changes are, and how they are distributed across the year. They include readiness assessments that capture the group’s preparedness for their current change load, not just for individual programmes. They include adoption indicators aggregated across the changes the group has been through in the past 12 months, providing a baseline against which new changes can be assessed. And they include the qualitative picture: what are managers and employees in this group experiencing, and what does that tell us about the group’s current adaptive capacity?

Business unit-level measurement is most valuable to the leaders who are accountable for the performance of those groups — general managers, division heads, and the people leaders who sit one or two levels below them. It gives them data they cannot obtain from programme-level reporting, because programme-level reporting does not aggregate across programmes and does not show the cumulative picture.

Project level

Project-level measurement is the most familiar tier and the most developed in most organisations. It answers the question: how well is this specific change programme delivering its intended outcomes? The primary audience is the programme sponsor, the change management team, and the project governance board.

Best-practice project-level change measurement tracks through three phases: plan, execute, and realise. In the planning phase, measurement focuses on impact assessment quality — how thoroughly the change’s impacts on specific roles and teams have been identified and documented. In the execution phase, it covers the full range of change activity metrics (stakeholder engagement, communication reach, training completion) alongside early readiness and comprehension indicators. In the realisation phase, it shifts to adoption and benefit metrics: are employees performing in the new way? Are the business benefits the change was designed to produce materialising?

Prosci’s ADKAR model provides a useful framework for structuring project-level measurement across the individual adoption journey: awareness, desire, knowledge, ability, and reinforcement. Measuring at each stage of the ADKAR sequence helps change teams identify where in the adoption journey the programme is losing traction, rather than receiving undifferentiated feedback that “the change isn’t landing.”

Connecting the three levels: the measurement flow

The three measurement levels are not independent. They form a connected system in which data flows upward from project to business unit to enterprise, and governance decisions flow downward in the opposite direction. Understanding how this flow works is essential to building a measurement framework that actually influences decisions rather than simply producing reports.

The upward flow begins with structured impact assessment at the project level. Each programme systematically identifies which teams and role groups are affected, what types of impacts they are experiencing, and how significant those impacts are. This data is aggregated at the business unit level to produce a picture of the cumulative change load on each group. That business unit data is then aggregated at the enterprise level to produce the portfolio-wide picture that executives need to make strategic resource and sequencing decisions.

The downward flow of governance decisions takes the enterprise and business unit data and translates it into constraints and guidance for individual programmes. If the enterprise-level data shows that a specific division is at capacity, the governance decision might be to defer a planned programme affecting that division by one quarter. If the business unit data shows that a team’s adoption of a recently completed change is low, the governance decision might be to provide additional stabilisation support before launching the next wave of change on that team.

This connected measurement system is what platforms like The Change Compass are designed to support. By providing a shared data layer across all three measurement levels — with structured impact data collected at the project level and automatically aggregated to business unit and enterprise views — these platforms make the full measurement framework operationally viable rather than theoretically sound but practically unworkable.

Making measurement actionable

The purpose of change measurement is not to produce reports. It is to enable better decisions. A measurement framework that generates data that no one acts on has failed its purpose, regardless of how sophisticated the metrics are. Making measurement actionable requires three things: the right data at the right time, a clear governance process for acting on it, and decision-makers who have both the authority and the appetite to make difficult calls based on what the data shows.

The right data at the right time means measurement that is aligned to decision windows. Enterprise-level data needs to be available when portfolio investment decisions are being made — typically quarterly, in alignment with financial planning cycles. Business unit-level data needs to be available to division leaders when they are making decisions about programme timing and resourcing. Project-level data needs to be available to programme teams on a continuous basis, so that course corrections can be made during implementation rather than identified in a post-implementation review when it is too late to act.

The governance process for acting on measurement data is frequently the weakest link. Many organisations collect reasonable change data but have no clear process for what happens when the data shows a problem. McKinsey research on change programme failures consistently finds that the most common cause of poor change outcomes is not the quality of the change design but the quality of the in-flight decision-making when early signals indicate the programme is not landing as expected. A measurement framework without a governance process for acting on what it reveals is a reporting system, not a management tool.

Frequently asked questions

What are the three levels of change management measurement?

A comprehensive change management measurement framework operates at enterprise, business unit, and project levels. The enterprise level measures the organisation’s overall change portfolio, capacity, and management maturity. The business unit level measures the aggregate change load and adoption experience of specific employee groups across all concurrent changes affecting them. The project level measures the delivery and adoption outcomes of individual change programmes. Each level serves different decision-makers and requires different data.

Why is measuring training completion not enough?

Training completion is an activity measure — it tells you someone participated in a training programme, not whether they understood the content, can apply it, or have adopted the new process or behaviour. Outcome measures — adoption rates, error rates in new processes, productivity recovery — are what demonstrate whether a change programme has achieved its purpose. Organisations that rely primarily on activity measures consistently overestimate their change effectiveness and underestimate their adoption gaps.

How does change measurement support portfolio governance?

Portfolio-level change measurement makes visible the aggregate change load on specific employee groups across all concurrent programmes — information that is invisible to programme-level measurement systems. This data enables portfolio governance decisions about sequencing, pacing, and resourcing that cannot be made without it. When enterprise and business unit-level measurement shows that specific teams are at or beyond their absorption capacity, the governance body has the evidence it needs to defer or descope programmes affecting those teams rather than proceeding and generating resistance and attrition.

What does effective change measurement look like in practice?

Effective change measurement is structured, consistent, and connected to decision processes. It uses a shared taxonomy for impact types across all programmes, so that data can be aggregated across the portfolio. It is timed to decision windows rather than reporting cycles. It covers all three measurement levels — not just project-level activity. And it has a clear governance process for what happens when the data shows a problem, so that measurement informs action rather than just generating reports.