Insights

Change management when nobody has time for change management

· 9 min read

The textbook change program assumes a department. Most organizations have a project team of two, a vendor and six months. Five moves fit in that time, and they are the ones that decide whether the change lasts.

A new system goes live in six months. The project team is two people and a vendor. The managers whose teams will use it have full jobs already. Nobody has been assigned to change management, because there is nobody to assign, and the phrase itself brings to mind a communications plan, a network of champions, a training curriculum and a readiness survey. All of that assumes a department. This organization has a Tuesday afternoon.

It also has more change than ever to absorb. Gartner research, reported in Harvard Business Review in 2023, found that the average employee experienced 10 planned enterprise changes in 2022, up from two in 2016. Nobody has time for change management partly because everybody is already in the middle of several changes.

The good news is that the department-sized program is not what makes change last. In our experience most of it is volume, and volume is not what is missing. What is missing is a handful of specific moves, made at the right time, by the people who already have the authority to make them.

A statistic worth retiring

Almost every article on this subject opens with the claim that 70 percent of change programs fail. We do not, because the number does not hold up. When Mark Hughes of the University of Brighton traced it back through five published instances in the Journal of Change Management in 2011, he concluded that “there is no valid and reliable empirical evidence to support such a narrative.”

Change does fail, often enough. But it does not fail at a known rate, and it does not fail where most programs put their effort.

Where change actually fails

A change is announced, explained and launched. The plan covers all three. Then the project team moves on, the vendor’s support window closes, and the people who have to live with the change go back to work.

That is where it fails: in the weeks after go-live, when the new way is still awkward and the old way is still available. The spreadsheet is still there. The old approval route still works if you know whom to ask. The manager who was never quite convinced says nothing, and the team reads the silence. Six months later the system is used for the minimum the organization can get away with, and everyone agrees it was a disappointing system.

None of this is new. Machiavelli wrote in The Prince in 1513 that “there is nothing more difficult to take in hand, more perilous to conduct, or more uncertain in its success, than to take the lead in the introduction of a new order of things, because the innovator has for enemies all those who have done well under the old conditions, and lukewarm defenders in those who may do well under the new.” He also gave the reason the weeks after launch matter so much: people “do not readily believe in new things until they have had a long experience of them.”

It was not the system. It was the gap between the announcement and the habit, and nobody was watching it.

Five moves that fit in the time you have

Name who is affected, and how

An impact map is one page: down the side, each group whose work changes; across, what they do today, what they will do instead, and what they lose. It takes an afternoon with the people who know the work. Its value is not the document but the conversation, which surfaces the group everyone forgot and the loss nobody mentioned. Machiavelli’s “all those who have done well under the old conditions” are exactly the rows this map exists to find. A change that costs a group something they value, without acknowledgment, will be resisted quietly and for a long time.

Remove the reasons the old way is easier

For each row of the map, ask what makes the old way easier than the new one, and remove it. If the spreadsheet is still accepted, stop accepting it on a named date. If the old approval route still works, close it. If the new system takes longer because the data is wrong, fix the data before go-live rather than asking people to be patient after it.

Behavioral science has made this its first rule. The Behavioural Insights Team, which began in the UK government, opens its EAST framework with it: “If you want to encourage a behaviour, make it easy, attractive, social and timely.” It warns that “Even apparently small features that make a task more effortful can have a disproportionately large effect on behaviour,” and that these “friction costs” are often ignored when a policy, product or service is designed. People do not resist change out of character. They choose the easier path, and the easier path is a design decision.

Give managers the words and the time

The line manager is the change program. Gallup, from its research on manager-led teams, reports that “The manager or team leader alone accounts for 70% of the variance in team engagement.” That is a finding about engagement, not about change, but it describes the same lever: what a team believes about its work runs mostly through one person. If a manager can explain, in their own words, what is changing, why, what it means for their team and what they personally expect, the team will follow. If the manager cannot, no amount of corporate communication will substitute.

So the manager gets a one-page briefing, not a deck: the three sentences that explain the change, the two questions the team will ask and the honest answers, and the one thing the manager should do this week. And the manager gets fifteen minutes in an existing team meeting, not a town hall. Reaching all of the managers this way takes one person a few days.

Measure the habit, not the attendance

Training attendance tells you who sat in a room. Adoption is whether the work is now done the new way. The difference is well documented: the same EAST report cautions that “Changing behaviour is different from changing people’s intentions, beliefs or attitudes,” and that people often intend something they then do not do, a tendency it calls the “intention-action gap.”

Pick one measure per affected group that shows the habit: the proportion of orders entered in the new system, the number of approvals still arriving by email, the days between a request and its first action. Read it weekly, out loud, in the leadership meeting. A measure that is read is a measure that moves, because the manager whose number is lagging will act before being asked.

Stay past go-live

The project ends at go-live. The change does not. Habits take longer to form than a project plan allows. In a study published in the European Journal of Social Psychology in 2010, Phillippa Lally and her colleagues at University College London followed people adopting a new daily behavior; the time it took them to reach their peak of automaticity “ranged from 18 to 254 days.” The often-quoted figure from that study is about 66 days, and Lally herself, asked in 2026 whether 66 days is a rule, answered: “No. I mean for someone somewhere for one habit yes, but for most people most of the time, no.” Either way, it is longer than the vendor’s support window.

And what is not sustained tends to fade. The EAST report describes a megastudy of 54 four-week programs to encourage exercise: 45% increased gym visits during the programs, but “Only 8% of these programmes showed significant changes in behaviour following the four-week intervention period.” Gym visits are not order entry, but the shape is the same: support that stops at launch buys a launch.

Someone has to keep reading the measure and keep closing the easier paths for the first quarter, which is exactly the period when the project team has been reassigned. Naming who does that, and giving them the standing to act, is the single most neglected decision in a small organization’s change.

What to drop

Drop the newsletter. Drop the roadshow. Drop the generic training course that teaches every screen to everyone. Drop the readiness survey nobody will act on. Each of these consumes the little time there is and produces the appearance of a program without the substance of one. If any of them earns its place later, it will be because a measure said so.

Who does this when nobody has time

The line managers do most of it, inside the jobs they already have, because the moves above are mostly management: deciding, explaining, closing paths, reading a number. What they need is a coordinator for a few hours a week whose job is to keep the list of moves honest, keep the impact map current, and bring the measures to the meeting. In a small organization that is often someone from the project team, kept on for a quarter after go-live at a fraction of their time. It costs far less than the program nobody had time for, and it is the part that works.

The honest limit

None of this rescues a change that is wrong. If the system does not fit the work, if the reorganization solves a problem the organization does not have, no sequence of moves will make people adopt it, and it would be wrong to try. The impact map usually reveals this early, in the row where the loss is large and the gain is nobody’s. When we see that, we say so, before go-live rather than after.

Change management when nobody has time is not a lighter version of the program. It is the part of the program that was doing the work all along, done by the people who were always going to have to do it, with someone keeping count. That fits in six months and a Tuesday afternoon.

Sources

Recognize your organization in this? Tell us what is happening.