Change Is Not a Project: Why Your Managers Need a Capability, Not a Plan

Ask most organizations about change management and they will describe a particular initiative: a system migration that stalled, a restructure that never quite took, an operating model announced with conviction and absorbed with a shrug. The framing is almost always singular — this change, that program.

It is the wrong unit of analysis. And the most-quoted statistic in the field is part of the reason why.

The Statistic Everyone Quotes

Almost every conversation about organizational change opens with the same number: 70 percent of change initiatives fail. It appears in consulting decks, in conference keynotes, and on the first slide of more workshops than anyone can count.

It is worth knowing how thin the evidence for it is. The figure is usually traced to McKinsey, which in 2015 attributed roughly 70 percent of failures to employee resistance and insufficient management support. The underlying research tells a messier story. The Corporate Leadership Council’s own study found 34 percent of initiatives fully succeeded, 50 percent failed outright, and 16 percent delivered mixed results. Academic reviews put the range at 60 to 70 percent. Depending on which source you pick, and on how you define failure, the number moves considerably.

This matters less as a point of accuracy than as a point of diagnosis. If 70 percent of initiatives fail, the obvious conclusion is that you need better initiatives — stronger project plans, tighter communication cascades, a more rigorous stakeholder matrix. An entire industry has grown up around making individual change programs succeed.

That framing made sense when change arrived occasionally. It does not describe the situation most organizations are now in.

What Actually Changed

The more useful numbers are the ones nobody puts on an opening slide. Between 2016 and 2022, the number of planned enterprise changes the average employee lived through in a single year went from two to ten. Over the same period, the share of employees willing to support organizational change fell from 74 percent to 43 percent.

Read those two lines together and they describe something more fundamental than a run of badly managed projects. A fivefold increase in the volume of change, set against a collapse in the capacity to absorb it, is not a project problem. It is a condition.

Change stopped being an event. It became the weather.

And the forecast is not improving. At its HR Symposium in October 2026, Gartner estimated that the number of skills each role demands is climbing about five percent a year, and that as many as 32 million jobs a year may need redesigning through 2031. Nearly eight in ten chief human resources officers said their managers are already overwhelmed.

The Gap Is Not Where Most Organizations Look for It

When a transformation stalls, attention usually travels upward, to strategy and sponsorship, or downward, to employee resistance. The evidence points somewhere else entirely.

This is the layer where change is actually delivered. The executive announces the restructure; the manager explains to a direct report what it means for their role on Thursday afternoon. The strategy deck says the operating model is changing; the manager has to keep a team shipping while half its processes are rewritten underneath them. Research consistently finds that managers are employees’ primary source of information during change, and just as consistently finds that most of them receive little formal preparation for it.

Meanwhile the ground keeps shifting. Only 43 percent of employees now believe their organization manages change effectively, down from 60 percent in 2019, according to Willis Towers Watson. Capterra found that 71 percent of employees feel overwhelmed by the volume of change, and that 54 percent of those experiencing change fatigue are considering leaving. Change fatigue is not a morale issue. It is a retention and execution issue.

What You Would Notice

Like most structural problems, this one does not announce itself. It shows up as a set of observations that each look like something else:

None of these reads as a change-capability problem from the inside. They read as a demanding year.

Project Management Is Not Change Management

One confusion sits underneath more failed change efforts than any other, and it is worth naming precisely.

The two disciplines are routinely treated as one, usually by assigning both to the same person and hoping the distinction does not matter. It matters, and the difference is not academic.

A project can finish on time and on budget and still fail, because the people it was built for carried on working the way they always had. That is the most common form of change failure, and it is invisible to a project plan — because by every measure the project tracked, it succeeded.

The skills are genuinely different too. Project management is largely a discipline of structure. Change management is largely a discipline of influence — and influence without authority is a learned skill, not a personality trait.

What Building the Capability Actually Looks Like

If change is a standing condition rather than a project, the response has to be a standing capability rather than a program. In practice that means three shifts.

• Establish the baseline before you design anything. Change capability is unevenly distributed, and rarely where leaders assume. Some teams have absorbed four reorganizations and have nothing left; others have capacity nobody has drawn on. Assessment instruments — team cohesion, emotional intelligence, leadership style, individual strengths — tell you which teams need support and which need to be left alone for two quarters. Designing a change program without that picture is guesswork with a budget attached.
• Develop managers before the change, not during it. The capabilities that carry a team through disruption — coaching, difficult conversations, giving feedback when nobody has certainty, adapting leadership style as confidence drops — take months to build. They cannot be issued as a briefing pack the week a restructure is announced. The organizations that handle change well are the ones that built those capabilities while things were calm.
• Treat it as continuous, because it is. A single workshop produces a good day and very little else. Capability that survives contact with a real reorganization is built over time, reinforced in practice and sustained with coaching. This is the difference between a course and a learning journey, and it is the single biggest predictor of whether anything taught is still in use a year later.

None of the three is exotic. What makes them rare is that each has to be funded before there is a crisis to justify it.

Change Does Not Belong to One Department

There is a structural reason change capability is so often underdeveloped: no single function owns it. It shows up everywhere, which means it is nobody’s responsibility in particular.

• Management and Leadership. Coaching through transition, influence without authority, leading when you have no more certainty than your team does.
• Project Management. Where adoption is either planned for alongside delivery, or discovered to be missing after go-live.
• Agile and Scrum. Change agility as an operating habit — iterating in public, responding to what the last cycle taught you.
• Collaboration, Inclusion and Belonging. The psychological safety that decides whether anyone tells you the change is not working while there is still time.
• Business Analysis. Requirements shift as organizations do; eliciting what people actually need mid-transition is its own discipline.
• Lean Six Sigma and Business Resource Management. Process change that holds, rather than reverting quietly to the old way within two quarters.

Any serious attempt to build change capability runs through several of these at once. That is precisely why it tends to fall between the cracks of a training catalog organized by department.

The Question Worth Asking

Most organizations, asked whether they do change management, will say yes and point to a methodology, a communications plan and a set of templates. All of which describe how they run a change initiative.

The more revealing question is a different one: when the next change arrives — and it will arrive before the last one has finished — will the managers who have to deliver it be any more capable than they were for the previous one?

If the honest answer is no, then the plan was never the variable. Change keeps arriving and finding the same organization waiting for it: the same managers, with the same preparation, holding a different template.

Where to Start

If this describes your organization, the first move is not to buy a methodology. It is to find out where capability actually sits: run an assessment across the management population before designing anything, and ask which teams have absorbed the most change in the last two years.

If the pattern holds, the design question follows from it. Where the pressure is constant change rather than scope, Developing Change Agility is the natural starting point. Managers leading for the first time are served by Emerging Leaders; those already carrying a full span by Developing Leaders; an executive team by Strategic Leadership. In every case, sequencing matters as much as content — capability built during a reorganization arrives too late to help with it.

If you would rather test the water than commit a cohort, CEG’s free webinars run about an hour, live and on demand. Managing and Coaching Through Change is the one that maps directly onto this article.

Sources: Gartner, HR Symposium/Xpo, October 2026 · Gartner survey of 473 HR leaders, July 2024 · Gartner, managers not equipped to lead change, 2024 · Gartner, enterprise change volume and employee willingness, 2016–2022 · Corporate Leadership Council, 2016 · McKinsey, 2015 · Willis Towers Watson, 2023 · Capterra, 2022 · Errida & Lotfi, 2021.

A related question, from the other direction: why the managers who most need development never get to it looks at whether this capability can be delivered at all. This article is about what to build once it can.