Leading organisational change without change fatigue

Most organisations do not suffer from too little change. They suffer from too much change landing on the same people at once. A new ERP system, a restructure, a revised performance framework and a culture programme can each be sensible on their own, and still exhaust the finance team that has to absorb all four in the same year.

This article treats change fatigue as a management problem you can control rather than an employee attitude you have to put up with. I cover how to map change load, how to decide what to sequence, merge or stop, how to read resistance, how to handle culture clashes in mergers and restructures, and how to run change in stages so you can adjust along the way.

Change fatigue is a portfolio problem

In the GCC the pace of transformation is high. Government entities are merged, restructured and given new mandates. Semi-government companies are prepared for privatisation or listing. Family groups professionalise their governance while expanding into new markets. Each of these produces a stream of initiatives, and each initiative has a sponsor who sees only their own.

That is the root of the problem. Every sponsor believes their change is a priority and plans it as if it were the only one. Nobody looks at the total load arriving on a given team, so nobody notices when it becomes too much.

The signs are familiar: engagement falls in specific teams, new systems are used reluctantly or worked around, good people leave, and cynicism grows. You hear the same remark in different words, that this initiative will pass like the last one. By then, even a well-designed change will struggle.

The fix starts with a shift in ownership. Someone, usually a transformation office or the head of OD, has to own the portfolio view of change, not just individual projects.

Map the change load

You cannot manage what you cannot see, so the first tool is a change load map. It takes a few days to build and is one of the most useful documents a leadership team can look at.

Here is the method:

1. List every initiative that will affect how people work in the next 12 to 18 months. Include technology, structure, process, policy and culture changes. Ask each function, because many initiatives are invisible to the centre.
2. List the affected groups. Use groups people recognise, such as front-line customer service, finance, line managers or HR business partners.
3. Rate the impact of each initiative on each group: 1 for light (awareness only), 2 for moderate (some new skills or processes), 3 for heavy (new role, new system used daily, new reporting line).
4. Place each rating in the quarter when the impact will be felt most, usually at go-live, not at project start.
5. Add up the ratings per group per quarter and colour-code the totals.

Say a 2,500-person entity lists nine initiatives. When the map is complete, most groups score between 2 and 4 in any quarter. Line managers score 11 in the third quarter, because a restructure, a new performance system and a new HR self-service platform all go live then, and managers carry each one to their teams. That single cell explains a lot of the fatigue the organisation is about to create.

The thresholds are a judgement call. What matters is that leaders see the concentration and discuss it together.

Sequence, merge or stop

Once the map shows the hotspots, the leadership team needs clear rules for what to do about them. These are the ones I use.

Stopping things is the hardest step and the most valuable. Employees notice when leadership removes an initiative to make room for another. It is one of the few actions that rebuilds trust in the change agenda itself.

Stopping an initiative, and saying so publicly, does more for change capacity than any communication campaign.

Sequencing also applies within a single initiative. A restructure that changes reporting lines, job titles, grades and locations at once is harder to absorb than one that moves reporting lines first and settles titles and grades a quarter later, provided people know the full plan from the start.

Resistance is information

Resistance is often treated as a problem to overcome through more communication. In my experience it is more useful to treat it as information. People resist for specific reasons, and each reason needs a different response.

• Unclear purpose. People do not understand why the change is needed. Explain the problem it solves, in terms of their work, and have their own leader explain it rather than a central team.
• Lack of capability. People understand the change but do not feel able to work the new way. Provide training close to go-live, practice time and floor support for the first weeks.
• Low trust. Previous changes were announced and abandoned, or promises were broken. Acknowledge that history directly and make small, visible commitments you then keep.
• Real loss. The change removes status, authority, income or a role someone valued. Say so honestly, and deal with it fairly. Pretending there is no loss is the fastest way to lose credibility.

Models such as Prosci's ADKAR are helpful here because they focus on the individual transition: awareness, desire, knowledge, ability and reinforcement. They help you diagnose where someone is stuck rather than repeating the same message louder.

Middle managers deserve special attention. They are asked to carry every change to their teams while absorbing the same changes themselves. If the change load map shows them as the hotspot, as it often does, reduce their load first and equip them properly before asking them to lead anyone else.

Handling culture clashes in mergers and restructures

Some of the most draining changes in the region come from bringing organisations together: merged government entities, acquired companies, or a family business absorbing professional managers from outside. Structures can be combined in months. Ways of working take far longer.

Culture clashes show up as practical friction. One side expects decisions to go up to the top, while the other expects managers to decide. One side values speed, the other values process and approvals. Meetings are run differently, and each side quietly concludes that the other is doing it wrong.

A few steps make this manageable:

1. Diagnose before you design. Run short interviews and a pulse survey in each legacy organisation to understand how decisions are made, how conflict is handled and what people value. Look for the few differences that will cause most friction.
2. Define a small number of target behaviours. Three to five, stated concretely, for example "decisions below a set value are made by the head of section without further approval".
3. Avoid default dominance. The larger or acquiring organisation's habits often become the norm without discussion. Choose deliberately, and take good practices from both sides.
4. Have leaders from both sides model the behaviours visibly, and use culture champions from each legacy organisation to spread them.
5. Watch the early signals, such as attrition among high performers on one side, or parallel processes that refuse to die.

Run change in stages and adjust as you go

The traditional approach to change is a detailed plan executed from start to finish. It works for predictable changes. Most organisational change is not predictable, and rigid plans produce fatigue because they keep pushing forward after the evidence says to adjust.

An adaptive approach treats large changes as a sequence of stages, each with a decision point. Pilot the new structure or process with one unit. Gather feedback, both data and conversation. Decide explicitly whether to proceed, adjust or pause, then scale.

This needs a small, stable central team that holds the portfolio view, runs the change load map, coordinates between initiatives and tracks adoption. Some organisations call this a transformation office or an integration centre. The name matters less than its authority to recommend sequencing and stopping decisions to the executive team.

It also needs evidence. Short pulse surveys on specific changes, adoption data from new systems and turnover in heavily affected teams are enough to spot trouble early. For ways to show whether a change or OD programme is delivering value, see measuring the return on organisation development.

Where to start

1. Build a change load map for the next four to six quarters, covering every initiative that affects how people work.
2. Take the map to the executive team and agree which hotspots to resolve by sequencing, merging or stopping.
3. Name one owner for the change portfolio with the authority to recommend changes to timing and scope.
4. Check the load on middle managers specifically, and reduce it before the next major go-live.
5. For your largest current change, add a pilot stage and a formal decision point before full roll-out.

At Humanyx we help leadership teams design organisational change around the capacity of the people who have to carry it, so that transformation lands and lasts.