What is change management?

Change management brings together methods for preparing and supporting people through a defined transformation. It addresses impacts, stakeholders, management responsibilities, communication, learning, and adoption. Its purpose is to help people move from current practices to the practices a project requires. The work continues as those practices become part of normal operations.

Prosci's definition emphasizes preparing, equipping, and supporting individuals to adopt and use a new solution. Change management complements technical project management. A project may deliver software, an organizational structure, or a process; change management addresses how people put that result to use. A tool without relevant instruction or a strategy without management support leaves an obvious gap in implementation.

Mature approaches extend beyond communication campaigns and individual projects. They address individual, project, and enterprise capabilities. Prosci also discusses portfolios and change saturation, including collisions among initiatives. A useful comparison with change enablement acknowledges that scope rather than depicting change management as a discipline concerned only with announcing decisions.

What is change enablement?

UNREST uses change enablement to mean developing the individual, collective, and organizational capabilities needed to deliver repeated transformations. It covers skills and practices, together with the conditions that allow people to act with increasing autonomy. Its horizon includes the current change and the organization's ability to handle future changes without rebuilding exceptional support every time.

Enabling action involves resources and work design as well as the person. An employee may understand a change and support its purpose while lacking the time, decision authority, or opportunities to practice the new behavior. Applied behavioral science at work helps investigate those conditions. Work psychology and organizational development help connect them to roles, relationships, and the organization of activity.

The term has several professional meanings. In IT service management, ITIL uses change enablement for a practice concerned with assessing risk, authorizing changes, and managing change schedules. This article uses an organizational development meaning centered on capability building and learning through work. It is a professional framing supported by several research traditions rather than a single scientific theory or universally standardized methodology.

How do change management and change enablement differ?

Both can operate within the same transformation. The distinction here concerns the starting question and the time horizon. Change management generally begins with a defined initiative and its adoption requirements. UNREST's change enablement approach also investigates the state of the organization entering the project and the capabilities the intervention will leave behind.

DimensionChange management: common project focusChange enablement: UNREST's emphasis
Starting pointA defined initiative, its impacts, and affected groups.The initiative and the organization's condition after earlier changes.
Guiding questionHow will people adopt and use the change?What can the organization deliver, and which capabilities need development?
ScopeThe project, stakeholders, and associated practice changes.People, teams, work design, and the transformation portfolio.
LeversSponsorship, communication, learning, participation, and adoption support.Behavioral diagnosis, testing, skills, resources, rules, and working conditions.
Time horizonPreparation, implementation, and stabilization.Before, during, and after the project, including capability transfer.
MeasuresEngagement, adoption, use, proficiency, and project outcomes.Observable practices, work conditions, fatigue, learning, and available capacity.
Intended resultA solution used in everyday work.An adopted transformation that preserves or strengthens capacity for subsequent change.

These are overlapping areas of work. A change management engagement can build capabilities and address saturation; change enablement can include stakeholder analysis, communication, and training. The useful choice concerns what the organization needs the intervention to accomplish. Labels become secondary once the mandate, responsibilities, and outcomes are specified.

Every transformation inherits an organizational history

Each project has a sponsor, schedule, and objectives. The people implementing it have a history that crosses project boundaries. They may have abandoned a process before its replacement stabilized, kept operations running through repeated reorganizations, or learned routines that make the next change easier. A new project inherits those conditions even when it did not create them.

Planning separately for each initiative makes that cumulative experience difficult to see. Slow adoption may be interpreted as a feature of the latest project while unresolved decisions or earlier reversals remain outside the diagnosis. Employees may cooperate visibly while withholding the effort they previously invested. The project team then needs evidence about prior experience as well as the current solution.

Meyer and Stensaker (2006) framed capacity for change around the development and allocation of change and operational capabilities that sustain longer-term performance. Their account connects delivering the current change with continuing operations and retaining the ability to change again. It provides a research foundation for examining the organization's condition across successive initiatives.

In a qualitative study, Stensaker and Meyer (2012) found that constructive change experiences helped employees develop reusable capabilities and respond more calmly to later initiatives. Negative experiences could produce cynicism even when employees continued to cooperate outwardly. The history of changing matters to what apparent adoption means. A diagnosis therefore examines trust, available resources, relevant skills, and work rules before selecting an intervention.

What happens when changes overlap?

Weick and Quinn (1999) distinguish episodic change, associated with an identifiable discontinuity, from continuous change emerging through ongoing adjustments. Many projects fit a current-state, future-state, and transition model. Overlapping initiatives add a different coordination problem: the same people must adapt to several changes while delivering current work. Individual project plans can look feasible even when their combined demands are incompatible.

Change saturation describes a situation in which change requirements exceed the capacity available to implement them. Prosci describes it in terms of people's ability to adopt and use changes effectively. In its benchmark research, 73% of respondents placed their organizations near, at, or beyond saturation. The figure is a self-reported assessment from a consultancy survey, useful as an indication of perceived exposure rather than a universal capacity threshold.

Change fatigue concerns people's experience of repeated change. Cox and colleagues (2022) examined its predictors and consequences in two cross-sectional studies. More frequent change was associated with fatigue, which was linked to strain, exhaustion, and lower engagement; associations with performance involved job satisfaction and organizational commitment. Because the studies measured these variables cross-sectionally, the temporal sequence remains a question for longitudinal investigation.

The distinction guides action. Saturation concerns the relationship between implementation requirements and available organizational capacity. Fatigue describes the experience of individuals within that situation. Preventing exhaustion associated with change involves decisions about the portfolio, staffing, priorities, and the quality of implementation. A message encouraging resilience will leave a conflict between project schedules unresolved.

Why does a completed rollout tell us so little about adoption?

A project can be declared deployed while use remains fragile. Access is available, courses are complete, and managers have received the materials. Older routines may still organize much of the work, particularly when cases are difficult. Delivery measures establish what was provided; observing practice establishes how people use it.

The COM-B model links behavior to capability, opportunity, and motivation (Michie et al., 2011). Training mainly develops capabilities, while communication can affect understanding and motivation. Contradictory objectives, inaccessible tools, or incentives favoring the old practice may still prevent the expected action. A diagnosis that begins and ends with employee motivation overlooks those conditions.

Adoption measures need to fit the transformation. In management development, they might examine how decisions are prepared or delegated. In AI adoption, they might track verification of outputs, handling of sensitive information, or selection of tasks appropriate for assistance. Organizational development connects those behaviors to decision rights, roles, and dependencies that individual support alone cannot change.

How can the two approaches work together?

A specific project provides a practical starting point. Change management organizes impacts, stakeholder involvement, messages, learning, and stabilization. Change enablement adds an explicit examination of available capability and what participants can reuse. The same engagement can address immediate adoption and the ability to work more independently on the next change.

Before launch, the team examines prior change experiences, concurrent projects affecting the same groups, and conditions that could obstruct the required behavior. During implementation, it observes trials and difficulties in actual work. After rollout, it checks whether the practices continue and what the organization has learned about making change happen. Each stage produces evidence for an operational decision.

Consider a hypothetical AI adoption program. Impact analysis, communication, training, and management support remain necessary. The capability-building work also examines whether teams can experiment, exercise judgment, delegate tasks with appropriate checks, and learn together from errors. Time, security rules, and decision rights determine whether those behaviors are practical. The engagement can address the rollout while reducing dependence on external specialists.

How do organizations develop capacity for change?

Capacity needs to be assessed against the work and changes concerned. There is no universal number of transformations a team can handle, or single score that captures every aspect of its ability to change. Requirements vary with the type and overlap of initiatives, affected roles, operational conditions, and prior experience. The concept of change fitness focuses attention on retaining the capabilities needed for subsequent changes.

An intervention can organize the work around four operations:

  • Map concurrent initiatives and identify groups facing competing requirements.
  • Specify behaviors that matter to the transformation in identifiable work situations.
  • Investigate capability, opportunity, and motivation in relation to those behaviors.
  • Test selected interventions and track practice over time.

The diagnosis determines what follows. Some situations require practice and feedback; others require clearer roles, accessible information, or removal of a contradictory rule. UNREST's MEET© protocol, Model, Engineer, Experiment, Transfer, structures that reasoning and the transition to independent use. It connects the intervention to decisions about implementation and evaluation.

Heckmann, Steger, and Dowling (2016) found a relationship between organizational capacity for change and change project performance. Experience becomes useful when organizations examine it and turn it into reusable learning. Merely completing more projects adds experience without ensuring that this learning occurs. Teams need an opportunity to change the practices and decisions that created recurring difficulties.

What should be measured?

Measurement covers the initiative and the state of the organization. Adoption indicators retain their value: use, proficiency, quality of execution, and continuation over time. They can be complemented by measures of fatigue, trust, available resources, and constraints. Each construct needs a measure suited to its purpose rather than a combined score with an unclear meaning.

At portfolio level, management can track which projects affect the same teams, their timing, intensity, and dependencies. At work level, observation examines whether people have the information, time, and authority they need. Behavioral measurement establishes whether the selected practices occur when relevant opportunities arise. The findings help distinguish a lack of skill from a conflict in the work system.

Financial outcomes require the same attention to interpretation. A McKinsey survey published in 2023 reported that an average of 42% of potential transformation benefits was lost during implementation and sustainment. It drew on 908 respondents' accounts and concerned unrealized value, rather than the specific cost of change fatigue. It directs attention to the stages in which new practices have to survive everyday operating conditions.

Does change enablement replace change management?

Change enablement complements change management when the mandate includes reusable organizational capability. A defined project still needs sponsorship, impact assessment, learning, and adoption support. Those activities contribute directly to the current outcome. Their scope can also include how participants learn to handle future situations.

Planning each transformation as a self-contained event misses what successive projects leave behind. The team responsible for change needs to examine that inheritance, protect operational capability, and convert experience into useful learning. UNREST's approach connects the current initiative with work conditions and future capacity. The intended result is an adopted transformation and an organization better equipped to deliver the next one.

Frequently asked questions

Is change enablement a recognized scientific method?

It is a professional framing with several meanings. Its rigor depends on the models, measures, intervention methods, and evaluation actually used. Research on organizational capacity for change, readiness, learning, fatigue, and behavior supplies relevant foundations without turning the label into a single validated method.

How is this different from ITIL change enablement?

ITIL addresses change enablement in IT service management, including risk assessment and authorization of changes. The meaning used here concerns organizational capability and behavior during repeated transformations. Both involve enabling change, but they answer different professional questions.

How much change can an organization handle?

The answer depends on the initiatives and resources involved. A change affecting a rarely used reporting field differs from a reorganization changing decision authority, staffing, and customer relationships. The assessment needs to identify which teams must do what, alongside their existing commitments.

When is a change enablement engagement useful?

It is especially relevant when initiatives compete for the same teams, new practices fade after rollout, or managers report difficulty mobilizing people for another change. Work can begin before launch or during implementation. A bounded diagnosis can establish whether the problem calls for a broader engagement.

Who owns change enablement?

Responsibility is usually shared among executives, HR, transformation leaders, managers, and affected teams. A central function can coordinate portfolio decisions and methods. Operational leaders still need the authority and resources to change the conditions in which the required behaviors occur.

About the author

Maxime Rabéchault is the founder and president of UNREST, a change enablement and organizational development consultancy grounded in applied behavioral science. Trained at Université Paris Dauphine-PSL, the Conservatoire national des arts et métiers (CNAM), University College London (UCL), and Sciences Po Paris, he also teaches as an adjunct at IAE Paris-Sorbonne. His work connects observable professional practices with the organizational conditions that make transformation possible.

References

Cox, C. B., Gallegos, E., Pool, G. J., Gilley, K. M., & Haight, N. (2022). https://doi.org/10.1108/JOCM-12-2021-0369 Journal of Organizational Change Management, 35(4/5), 718-733.

Heckmann, N., Steger, T., & Dowling, M. (2016). https://doi.org/10.1016/j.jbusres.2015.07.012 Journal of Business Research, 69(2), 777-784.

Meyer, C. B., & Stensaker, I. G. (2006). https://doi.org/10.1080/14697010600693731 Journal of Change Management, 6(2), 217-231.

Michie, S., van Stralen, M. M., & West, R. (2011). https://doi.org/10.1186/1748-5908-6-42 Implementation Science, 6, 42.

Stensaker, I. G., & Meyer, C. B. (2012). https://doi.org/10.1108/00483481211189974 Personnel Review, 41(1), 106-124.

Weick, K. E., & Quinn, R. E. (1999). https://doi.org/10.1146/annurev.psych.50.1.361 Annual Review of Psychology, 50, 361-386.