How to Measure the Business Value of Change Management

Every change leader has faced some version of the same executive question:

What value will this change management investment deliver?

It is a fair question. Organizations are investing in new technologies, operating models, processes, workforce structures, and ways of working at a pace that shows no sign of slowing. Leaders want confidence that those investments will lead to measurable outcomes, not just executed change activities.

The challenge is that change management is often measured through activity: how many communications were sent, how many people attended training, how many employees logged into a system, or how many leaders participated in a town hall. Those metrics are useful, but they do not answer the bigger question: Did people adopt the change in a way that helped the business achieve its goals?

Industry research can help make the case that change management matters. But to measure value inside a specific organization, leaders need a more localized model: one that defines adoption, connects it to business outcomes, and improves over time as the organization learns from its own portfolio of change.

# The Problem With Relying Only on Broad Change Management Studies

External studies and data points are useful because they establish the broader case for change management. They show that organizations with stronger change management are more likely to achieve outcomes, move faster, and capture value from transformation.

But broad studies are built to show patterns across many organizations. They can point to a trend line, but that trend line is still an average, and every average has outliers. Some organizations will outperform the trend. Others will underperform it. Many will sit somewhere in the middle. All of this is dependent on how strong your change capability is and how well you plan and execute business strategy.

That makes broad research difficult to apply at the project level. The data may show that stronger change management is associated with greater value capture, but it cannot answer the question leaders are really asking: Which dot are we?

Two companies can invest in similar systems, follow similar change plans, and have similar goals and objectives, yet experience very different outcomes. Sponsorship, leader capability, data quality, workforce capacity, competing priorities, and reinforcement all influence whether adoption takes hold. The trend line may be directionally true, but it will not tell either organization what level of adoption is realistic, when to intervene, or how likely a project is to achieve its business KPIs.

That is why change measurement needs to move from generic proof to local evidence.

# How To Build Your Own Change Management Dataset

To understand how adoption connects to business outcomes, organizations need to collect the same kinds of change data across projects. The goal is not to build a perfect model on day one. It is to create a consistent dataset that helps leaders see patterns in their own environment.

The process is straightforward:

1. Set adoption thresholds. Define the minimum engagement, learning, and behavior signals that indicate whether a change is ready to move forward.
2. Compare projects against those thresholds. Use historical data where it exists and begin tracking current projects consistently going forward.
3. Document business outcomes. Capture whether each project achieved its intended KPI or business result.
4. Calculate the relationship over time. Compare projects that met adoption thresholds against those that did not, then monitor how often each group achieved its intended outcomes.

Over time, this creates an internal evidence base leaders can use to plan, resource, and improve future change efforts.

# Define What Change Adoption Actually Means

Before organizations can set meaningful thresholds, they need to define what they are measuring. Adoption is not one number; it builds through signals that show whether people are aware, understand the change, and are working in the new way.

A useful measurement model separates adoption into three signals - engagement, learning, and behavior - and then connects those signals to business outcomes.

The risk is stopping too early. High town hall attendance does not mean employees understand the change. Strong training completion does not mean people are prepared to apply it. Frequent system logins do not always mean users are following the process correctly.

That is why behavior is the most important adoption signal. Engagement and learning show whether people are ready for the change. Behavior shows whether the change is taking hold in the work itself.

But behavior does not happen on its own. If engagement is low, employees may never absorb the training. If learning is weak, behavior is unlikely to shift consistently. Measuring all three helps leaders use data to guide change management strategy and see where adoption is breaking down before they expect business results.

# Define Your Change Adoption Thresholds

With those signals defined, leaders can decide what level of evidence gives them enough confidence to move forward.

Start With the Minimum Signal

The goal is not to get every metric to 100%. That would be too resource-intensive for most changes. The better question is: What minimum signal tells us this change is ready for the next stage?

Thresholds help answer that question before teams are in the middle of rollout. Without them, teams may keep moving because the project plan says it is time. With them, leaders have a clearer basis for deciding whether to proceed, pause, or intervene.

Use Your Organization’s Context First

The best thresholds come from your organization’s own experience. Start by asking experienced change leaders and business sponsors:

• Engagement: What level of sentiment would make us confident that people are aware, paying attention, and ready to learn more?
• Learning: What knowledge score would suggest people understand what is changing and what they need to do differently?
• Behavior: What behavior rate would show that the new way of working is taking hold?

Historical data can make those answers stronger. Look across completed projects and compare adoption metrics against whether each project achieved its intended business result. The data may be incomplete at first, but even a small set of projects can help reveal patterns: which adoption signals were present in successful projects, where adoption broke down, and where teams needed more reinforcement.

Over time, this creates something more useful than an external benchmark: an internal evidence base.

Use a Starting Benchmark if You Need One

For organizations that do not yet have enough internal data, a starting benchmark can help. Based on Propeller’s work across change projects, one useful model is:

These are not universal targets. They are readiness thresholds to test and refine. A 60% engagement threshold, for example, does not mean engagement should stop there. It means there is enough early traction to justify deeper investment in learning, with engagement continuing to build through sponsorship, communications, training, and reinforcement.

Thresholds should also evolve based on the type of change. A technology rollout may not require the same level of engagement, learning, and behavior as a job architecture redesign, organizational restructuring, or broader transformation effort. A compliance-driven change may require near-total adoption, while a behavioral or cultural shift may need a longer measurement window and more qualitative evidence. The more projects an organization tracks, the clearer it becomes what level of adoption is needed in different contexts.

# Connect Change Adoption Thresholds to Business Outcomes

Once adoption thresholds are defined, the next step is to measure how often those thresholds correspond with business success.

This is where change measurement becomes more useful to leaders. Adoption does not cause business success on its own. A project can meet its adoption thresholds and still miss its KPI because of strategy, technology, timing, market conditions, or operational constraints. But adoption data can help show whether strong change management increases the likelihood of achieving business outcomes.

Two questions matter most:

1. How often does your organization hit its behavior threshold?
2. When that threshold is hit, what percentage of projects achieve their business KPIs?

Together, those answers help make the value of change management more tangible.

For example, say an organization reviews 10 completed projects. Six met the behavior threshold, and five of those achieved their business KPIs - an 83.3% success rate. Of the four projects that missed the threshold, only one achieved its KPI - a 25% success rate.

In this example, projects were 3.33x more likely to hit their business metrics when adoption thresholds were met. That gives leaders a more concrete way to account for change management in future planning.

If a new project is targeting 30% time savings, the organization can use its own historical data to create a more realistic value expectation. Without strong adoption, expected value may be closer to 7.5%. With adoption thresholds met, expected value may be closer to 25% (the difference between 7.5% and 25% --- that 3.33x factor)

This does not make adoption the only driver of value. It makes adoption a measurable part of the value equation.

# Build a Portfolio View of Change Measurement

Mature organizations do not treat change measurement as a one-time project exercise. They build a portfolio view.

You can start by tracking adoption metrics and business outcomes in one centralized place across initiatives, functions, and change types. It does not need to be complicated; a simple tracker can capture the same core data across projects.

Over time, this gives leaders a clearer view of questions that are difficult to answer project by project:

• Which types of change are hardest for our organization to absorb?
• Where do we consistently lose momentum: engagement, learning, or behavior?
• Which interventions appear to improve adoption?
• Where should we invest change resources earlier?

This also makes the data more useful for resourcing and planning. If a certain type of change regularly struggles to reach behavior adoption, leaders can plan for more reinforcement, manager coaching, or stakeholder engagement earlier. If projects that meet adoption thresholds are more likely to achieve KPIs, change teams have stronger evidence to support future business cases.

That is especially important as change becomes a continuous operating reality. When every initiative has its own timeline, sponsor, dashboard, and definition of success, leaders can lose sight of how change is being experienced across the business. A portfolio view helps restore that visibility.

The long game is not building a perfect measurement system overnight. It is creating a repeatable, lightweight process that helps the organization learn from each change and make better decisions about the next one.

# Start With the Data You Can Collect Now

Change measurement does not need to start with a perfect model. It can start with a few consistent practices: define the business outcome, choose a small number of adoption metrics, set initial thresholds, track behavior after go-live, and follow up later on results.

The model will improve over time. The more projects an organization tracks, the more it can refine thresholds, identify patterns, and understand what level of change investment is needed for different types of work.

Broad studies can help make the case. But your own data can help you make better decisions.

If your organization is working to define adoption thresholds, connect change metrics to business outcomes, or build a more consistent approach to change measurement, our change management consultants can help.