Many change and transformation initiatives reach employees with little or no warning. From their perspective, they often appear almost out of nowhere. Maybe there have been closed doors, with all the important people on the other side of them. Maybe a few rumours have already surfaced in the informal grapevine. But nothing has been clear, confirmed, or explainable.
Until, suddenly, an announcement comes from the top, and it lands like a Big Bang.
From the organisation’s perspective, this moment may not feel sudden at all. Leaders may have discussed the topic for months. Project teams may have worked through analyses, scenarios, risks, timelines, and dependencies. By the time the announcement is made, the change may already feel mature to those who shaped it. For almost everyone else, it suddenly hits with full force.
It becomes even more difficult when several change initiatives happen at once, as they often do in complex transformations. On paper, they may be separate projects. For employees, they become one combined reality shaped by uncertainties.
This may well be one of the great misunderstandings of organisational change: organisations often look at initiatives individually, while employees experience them collectively. A project may be well designed, well justified, and well managed on its own. But people do not work inside one business case at a time. They work inside the accumulated reality of all of them.
It is not always avoidable to start several changes at once. Sometimes several issues need immediate attention. Sometimes leadership feels the organisation has delayed too many decisions and now needs to move with speed. And sometimes there is the tempting thought: if we do everything now, at least we will get it over with.
It is an understandable thought. It is also a risky one. Change does not become lighter because it is compressed. A new programme can be installed on a computer in one session, followed by a bug fix if something does not work. Human beings do not work like that. They need to understand what is changing, test whether it makes sense in practice, build trust that it will actually work, and repeat new behaviours often enough for them to become familiar. This takes time, attention, and emotional energy. Business as usual rarely pauses politely while transformation settles in.
Prosci uses the term “change saturation” for situations in which many change initiatives happen at the same time and leadership does not sufficiently consider them together. The consequences can include poor adoption, change fatigue, and turnover. The useful point here is the shift in perspective: the key question is no longer only whether every single change is justified, but whether the organisation can still absorb the total amount of change it has created.
This is where transformations lose force. The launch has taken place. The system has gone live. The new process has been published. Formally, implementation has happened. In reality, much of the organisation is still operating through old habits, workarounds, and familiar decision patterns.
When many things change at once, orientation becomes the most important anchor. It helps when change follows a recognisable logic: how it is introduced, explained, supported, prioritised, and followed up. Predictability does not make difficult change easy, but it helps people understand how to move through it.
It also helps to classify change from the beginning. Is this mainly a technical or system change? Or is it a behavioural and cultural change? The distinction matters because each type of change asks something different from people.
A technical or system change mainly requires learning and practice. People need clear guidance, support, and enough repetition to become confident. A behavioural or cultural change goes deeper. If people are expected to collaborate differently, decide differently, or take responsibility differently, the change cannot simply be announced into existence.
It needs enough involvement from the people who have to make it real. If cultural change is treated as a shared development process with employees, the chances of moving the culture in the intended direction are much higher. Otherwise, the organisation may simply change the language, but not the way people actually work together, decide, or lead.
Prioritisation can also provide relief. Every project can explain why it matters, and priorities may even be clear inside each individual project. That is not enough when several initiatives compete for the same time, attention, and energy. When everything is important, people do not experience ambition. They experience pressure without sequence.
Dependencies deserve attention, too. If one project changes roles, another changes systems, and a third changes reporting lines, these initiatives meet in the same teams. They may look separate in steering documents, but they are not separate for the people working with the consequences.
Communication has a central role here, but not as decoration around decisions already made. Employees need to understand what is different now and what is expected of them. Leaders need to see what is still unclear and where the employees’ perspective should inform the next steps.
If the Big Bang cannot be avoided, the task is to bring calm, sequence, and orientation into the system. Organisations cannot remove all pressure. But they can reduce unnecessary noise. They can create clarity where possible, honesty where certainty is not yet available, and enough order for people to keep moving.
That may not make the Big Bang quiet. But it can make sure it does not become overload.