You can always custom build your own custom course, Why not explore our building blocks library or book a consultation with our team
Are your people ready for change - or just being told about it?
Most change plans have a communications workstream. Very few have a capability one - on the assumption that if people understand what's happening, they'll be able to handle it.
But understanding a restructure doesn't tell you how to manage your own reaction to it, sustain performance through six months of ambiguity, or decide whether to speak up. Those are separate skills, and they can't be delivered in the week of the announcement.
What's the difference between being informed and being equipped?
Being informed means you know what is happening. Being equipped means you can do something about it.
Most organisations resource the first and assume the second follows. It rarely does. A well-written announcement tells someone their team is restructuring; it doesn't help them manage the three weeks of uncertainty that follow, recalibrate what their role now is, or raise a concern without feeling like they're being difficult.
That gap is where change programmes quietly lose people. Not at the point of announcement, but in the months afterwards, when the comms plan has finished and the capability was never built.
Why does change feel more worse than it usually is?
Because change at work is mostly something done to people rather than with them.
They hear late, they're expected to adapt quickly, and the part they're expected to play is rarely spelled out. That combination — high consequence, low control, poor information — produces stress regardless of whether the change itself is positive.
Which is worth knowing, because it means employee discomfort isn't reliable evidence that a change is wrong.
Research published by Perceptyx in 2026 adds a point most change plans miss: change fatigue doesn't discriminate between positive and negative change. Even changes people actively want deplete their capacity to absorb the next one. Capacity is finite, and it gets spent whether or not the change was welcome.
The practical implication is uncomfortable. A run of well-received, well-executed initiatives can still leave an organisation unable to take on the one that really matters.
Ambient change
The constant motion - priorities shifting, systems updating, teams reshaping. None of it significant enough to warrant an announcement, all of it accumulating. The demand here is stamina: sustaining resilience and momentum over long periods with no finish line.
Change events
The defined ones - a restructure, a system implementation, a merger, a new manager. The demand is different: absorbing a spike of uncertainty, moving through a rapid transition, recalibrating what the role actually is.
Most organisations resource only the second, and are then surprised by the fatigue generated by the first.
What can you do before the next change lands?
The first is to build capability ahead of need — human skills developed before a change create genuine readiness, whereas the same work done mid-change is remedial and considerably harder. Alongside that, name the ambient change. People can't manage what nobody has acknowledged, and simply saying "the last eighteen months have involved a lot of small changes" is often the most useful thing a leader does.
Then close out the last change properly. It's the phase most often skipped: recognise what was achieved, capture what carries forward, and be honest where it fell short. Without that, your next initiative starts from a deficit. Reducing the concurrent load helps too — sequencing three changes usually beats running all three at once, even though it looks slower on the plan. And give people the language, because much of what reads as resistance is simply an absence of vocabulary for what someone is experiencing.
Proven across industries
Frequently asked questions
Trusted by global organisations across industries, we build the human capability that decides whether change actually happens:
-
People who can make sense of change rather than just absorb it
-
Managers prepared to lead others through it, not just briefed on it
-
Organisations that close out one change well enough to start the next from strength
Change readiness is the individual and collective capacity to meet change well — before it arrives. It combines self-awareness about personal responses to change, emotional agility, the habits that protect wellbeing under pressure, and the ability to move from reacting to participating. Unlike a communications plan, it can't be delivered in the week of the announcement; it's a capability built in advance, and it costs considerably less to build before a change than to repair afterwards.
Change fatigue is the exhaustion and disengagement people feel after repeated organisational change, particularly where previous changes were poorly closed out or didn't deliver what was promised.
It shows up as compliance without engagement rather than open resistance, so more communication rarely fixes it. Notably, change fatigue doesn't discriminate between positive and negative change — even changes people support deplete their capacity to absorb the next initiative. Addressing it starts with closing out the last change honestly, reducing the concurrent load, and building human capability before the next one lands rather than during it.
All three, and the first and last are the ones most often skipped. Before builds capacity: understanding personal responses to change, strengthening resilience in advance of need, helping leaders anticipate reactions rather than react to them.
During sustains performance through the ambiguous stretch where the old way has gone and the new way isn't established. After consolidates new behaviours into habits and captures what should carry forward - without it, organisations repeat the same change badly.