Change Management Without Breaking Your Team's Stability

Most organizations do not have a change problem. They have a change accounting problem. Every initiative is planned as though it were the only one, budgeted against its own business case, and measured on its own adoption curve. Nobody adds them up. The result is a portfolio that looks reasonable in each individual paper and is unlivable in aggregate for the people expected to absorb all of it at once.

In our work with senior leadership teams across East Africa over the past decade, the complaint we hear from executives is that their people resist change. The complaint we hear one layer down is different and more specific: that the last three changes were never finished, and nobody has said which of the current ones matters most. Those are not the same problem, and only one of them is about resistance.

What follows is the case for treating stability as an input to performance rather than an obstacle to it, what the evidence on change management actually supports once the folklore is removed, and how to run both at once without pretending the tension is resolvable.

What the Change Management Evidence Supports

Start by discarding the most quoted statistic in the field. The claim that 70% of organizational change initiatives fail has been repeated in consulting decks for three decades. Mark Hughes went looking for its basis in the Journal of Change Management, reviewing five widely cited published instances, and concluded that while the narrative certainly exists, there is no valid and reliable empirical evidence supporting it. The number was repeated into authority rather than measured into it.

What does hold up is narrower and more useful. Prosci's benchmarking research, in the 12th edition of Best Practices in Change Management drawing on more than 10,800 professionals, found that 88% of projects with excellent change management met or exceeded their objectives, against 73% with good, 39% with fair and 13% with poor. That is a correlation from self-reported benchmarking rather than a controlled experiment, and it is still the strongest signal available.

The interesting part of that ladder is not the extremes. It is the collapse between good and fair, a 34-point drop. Change management appears to have a threshold rather than a gradient: below a certain standard of execution it stops buying you anything, which is a poor argument for doing a little of it.

Change management as a discipline exists because the alternative is assuming that a decision communicated is a decision adopted. The Association for Project Management frames it as the structured approach to moving an organization from a current state to a future one, and the structure is the entire value. Without it, adoption is left to whoever happens to be enthusiastic.

What the Change Curve Does and Does Not Tell You

Almost every change program eventually shows this slide.

Elisabeth Kübler-Ross developed the stages from work with terminally ill patients. The application to organizational change was an adaptation made by other people much later, and the stages have never been well supported as a sequence people reliably pass through, even in the grief context they were written for.

That does not make the curve useless. It makes it a vocabulary rather than a forecast. Its real value is that it gives a leadership team permission to expect a performance dip and not panic at it, which is a genuine service, because the most common management error during the dip is to interpret it as failure and add another initiative on top. Where it misleads is in implying that everyone travels the same path at the same speed and comes out the other side by default. Plenty of people simply stay in frustration, and the curve offers no way to tell the difference.

Use it to normalize the dip. Do not use it to predict when the dip ends, and never use it to explain away a specific person's objection as a stage they are passing through.

Stability as a Performance Input

The organizational default treats stability as the thing you are moving away from. That framing is backwards, and the argument against it is the most useful thing written on this topic in years.

Ashley Goodall makes the case in Harvard Business Review that creating stability is just as important as managing change. His point is not that change is bad. It is that the conditions under which people do their best work are conditions of stability, and that organizations systematically dismantle those conditions in the process of pursuing improvements.

The conditions he identifies are worth stating plainly. People perform at their best when:

1. the environment is predictable
2. they have a degree of control over their surroundings
3. they are supported by stable relationships
4. they feel connected to routines and to a place
5. they understand the purpose of what they are doing

Read the list against a typical restructure and the problem becomes obvious. A reorganization breaks reporting relationships, which is condition three. It changes routines, which is four. It introduces uncertainty about role and future, which removes one and two. Purpose usually survives on paper and is the first thing people stop believing.

The practical conclusion is not to change less. It is that the team is the unit worth protecting. Intact teams that have learned how to work together carry an enormous amount of an organization's actual capability, and that capability is invisible on an org chart, which is why it gets destroyed so casually.

Measuring the Change Load

The volume question is the one most organizations have never asked. Writing in Harvard Business Review, drawing on Gartner research, the finding is stark: in 2022 the average employee experienced ten planned enterprise changes, up from two in 2016. Restructures, culture programs, system replacements, each individually justified.

Nobody set out to quintuple the change load. It happened because every initiative was approved against its own business case, and no function owns the total. Ask most executive teams how many active change initiatives are currently landing on a given team and they cannot answer, which means the load is unmanaged rather than accepted.

That is a fixable governance gap and it does not require a new framework. It requires a single list, maintained centrally, of every change currently being asked of each part of the organization, reviewed before anything is added. Organizations that keep this list start sequencing rather than stacking, and sequencing is most of the fix.

How to Run Change and Stability Together

The balance is not a midpoint. It is a set of deliberate decisions about what is explicitly not changing.

Name the constants

At the start of any significant change, state what will stay the same: which teams remain intact, which routines survive, what the purpose still is. This costs nothing and is almost never done, because leaders are focused on communicating the change. People calibrate their anxiety against the size of the unknown, and an unbounded unknown produces unbounded anxiety.

Sequence and publish the order

A team can absorb one significant change well or three badly. Publishing the order is a form of stability in itself, because it tells people what they will not have to deal with this quarter.

Finish things visibly

Most change fatigue is not caused by the volume of change so much as by the volume of unfinished change. An initiative that quietly loses momentum teaches everyone that the next one can also be waited out. Declaring completion, including partial completion, is a stability practice.

Protect the team boundary

Where a structural change can be delivered without breaking up working teams, do it that way even at some cost to the elegance of the design. Elegant org charts are cheap; functioning teams are not.

Use a structured method properly

Kotter's eight steps, ADKAR or anything else all outperform improvisation, and per Prosci's ladder, doing a bit of one is close to doing none.

How the Balance Differs in East Africa

Most writing on this topic assumes an operating environment where the background conditions hold steady and change is something the organization introduces. Across much of East Africa that assumption does not survive contact with reality.

Currency movement, regulatory shifts, power reliability and shifting import costs already supply a substantial amount of involuntary change. An organization here is rarely choosing between stability and change; it is deciding how much discretionary change to add on top of a baseline it does not control. That materially raises the value of internal stability, because it may be the only predictability available to the people doing the work.

There is a second regional factor that cuts the other way. In organizations where deference to seniority is strong, resistance to change tends not to present as objection. It presents as compliance without adoption: the new process is acknowledged, the training is attended, and the old process continues. A leadership team reading the absence of pushback as successful adoption will discover the truth roughly two quarters later, usually through a number rather than a conversation.

Three Common Change Management Mistakes

The permanent-transition trap

The organization is always mid-change, so nothing is ever the current state. Staff stop investing in improving how things work because they expect it to be replaced. The tell is that nobody can describe the present operating model without using the word "transitioning".

The resistance-diagnosis trap

Every difficulty is attributed to resistance, which conveniently locates the problem in the people rather than in the plan. Some resistance is genuinely people knowing something the plan does not account for. Treat the first serious objection as information before treating it as a barrier, because after that point you will stop being told.

The stability-as-excuse trap

The opposite failure, and a real one. "Our people need stability" becomes the argument against every necessary change, usually deployed by whoever is most comfortable with the current arrangement. Stability means protecting the conditions in which people work well. It does not mean protecting a business model that has stopped working.

Frequently Asked Questions

Conclusion

The organizations that handle this well rarely have the best methodology. They are the ones keeping a single list of everything currently being asked of each team, treating any addition to it as a decision that needs an argument. That list costs nothing, sits in one document, and is the closest thing to a solution anybody has produced.

If you asked your team today what is definitely not going to change this year, could any of them answer?

If you are working through this balance right now, our Leadership and Management Development program is built for it. Book a free strategy call and we will look at what your organization is currently asking its teams to absorb.