Change Saturation: How to Plan Change People Can Actually Absorb
Change saturation is a capacity issue, not resistance
Change saturation is not a sign that people are unwilling to change. It happens when the same teams are asked to absorb too many initiatives at once. Each programme may make sense on its own, but attention, time for learning and manager capacity are finite. When they are overdrawn, even well-designed changes can become noise.
The effect is often felt first in the day job. Customer work takes longer, routine decisions are delayed, service levels become harder to maintain and experienced people spend more time explaining new processes than delivering their usual work. Teams may appear resistant when, in reality, they are trying to protect essential delivery.
A sound project plan can still create pressure elsewhere
A single project plan can be well structured and still add to the pressure on people. This is why project management needs to look across the portfolio as well as within an individual delivery plan.
Which teams are affected? When do training, communications and new ways of working land? Where are the same managers, operational experts or subject-matter specialists needed by several initiatives? Just as importantly, what are those people expected to keep delivering while the changes are introduced?
If a finance team is closing the month, a customer-services team is dealing with seasonal demand, or managers are already covering vacancies, their capacity for training, testing and reinforcing a new process will be lower. These ordinary operational realities should be visible in the plan, not treated as an issue only after deadlines begin to slip.
Make impact on normal delivery visible
A simple impact view can reveal collisions that a delivery schedule will miss. It does not need to become a complicated dashboard. Start by mapping the groups affected by each change, the periods that demand most attention from them and the business-as-usual commitments they cannot step away from.
This can include:
Peak delivery periods, deadlines and customer commitments
Training, testing and go-live activity
Manager capacity for briefings, coaching and issue resolution
Reliance on the same subject experts across several projects
The likely temporary reduction in productivity while people learn a new way of working
The aim is not to eliminate all pressure. Change always requires some additional effort. The aim is to see where the organisation is asking too much of the same people at the same time, then make an informed decision about what to sequence, pause, reduce or support.
Use PRINCE2 controls to make better decisions
PRINCE2 provides useful discipline here, particularly when it is tailored sensibly to the organisation. Continued business justification should include more than the benefits the project may create. It should also consider the capacity required to deliver the change without causing unacceptable disruption to normal operations.
Clear roles and responsibilities matter too. Project managers can coordinate plans and dependencies, while operational leaders can describe the practical effect on service, workloads and team morale. Sponsors need a clear view of the trade-offs so they can decide whether the timing, scope or approach still makes sense.
Managing by stages is particularly helpful. Rather than committing every part of a change programme in one sweep, use each stage boundary to review readiness: are the expected benefits still credible, have risks changed, and can the affected teams absorb the next step while maintaining their usual delivery?
Treat workload pressure as a live risk
Technical readiness is only one part of readiness. A solution may be ready to launch while the people who need to use it are handling another major change, an operational peak or a difficult period of business-as-usual delivery.
In PRINCE2 terms, this should be treated as a live risk or issue, with a named owner, planned response and clear escalation route. Agree tolerances around service levels, capacity and operational impact early. If the pressure exceeds what was expected, managers should not feel they have to quietly absorb it. They need permission to raise an exception and ask for a decision.
That decision may be to narrow a pilot, delay a non-essential activity, phase implementation, provide temporary support or adjust the scope. These are not signs of weak delivery. They are practical choices about how change will land successfully.
Coordinate the message as well as the plan
There is a communications dimension too. People need one coherent view of what is changing, rather than a stream of disconnected announcements. Where several initiatives affect the same work, coordinate the message, acknowledge the competing demands and explain the sequence honestly.
Managers are central to this. They need practical context and a clear conversation guide: what matters now, what can wait, what support is available and where concerns should be raised. Trust grows when people can see that leaders understand the full picture, including the work that still has to be delivered every day.
Prioritise benefits alongside capacity
One practical starting point is to ask each sponsor to name the three changes currently drawing most heavily on their teams. Compare the audiences, deadlines, manager demands and expected benefits. This turns a general feeling of overload into something that can be discussed and acted on.
A project with a credible, time-sensitive benefit may deserve protected attention. Another may be better postponed until the organisation can use it well. This is a stronger basis for prioritisation than treating every approved initiative as equally urgent.
Plan for sustainable adoption
Change management helps identify impacts, support needs and likely pressure points. Project management turns those insights into sequencing, risks, decisions, controls and delivery actions. Together, they make it more likely that a project will achieve its intended benefits without unnecessarily undermining the work teams already need to do.
The most useful question is not simply, “Can we launch this?” It is: “Can this group absorb, use and sustain it now while continuing to deliver what the organisation depends on?”
A realistic roadmap that people can absorb will achieve more than a crowded plan that only looks good on paper. If you are balancing several changes across the same teams, I would be happy to discuss a practical approach to sequencing, communications and delivery.
About Mark M Barton
I am a Change Management, Change/Internal Communications, and Project Delivery and Operations professional with over 25 years' experience helping organisations deliver complex projects, improve operations and navigate organisational change.
Certified in both Prosci Change Management and PRINCE2, I work across change management, project delivery, operational improvement, internal communications and transformation initiatives, helping organisations achieve successful outcomes through both structured delivery and effective people engagement.
If I can help you, your team, or your organisation do reach out.
