Cultivating conditions

You can't force an organisation to be tuned to change. It's an emergent property - it arises from conditions, not from change management methodologies. But in our work with organisations, certain patterns keep showing up in the ones where change happens naturally and sustainably. Not as a formula, but as observations about what seems to matter.

People aren't tired of change. They're tired of poorly handled change. This distinction changes everything. The common narrative - change fatigue, change saturation, too much change - assumes people have a limited capacity for adaptation. But that's not what we see in practice. People are remarkably adaptable. What exhausts them isn't adaptation. It's the experience of being changed without understanding, without involvement, without honesty, and without care. Every poorly handled change doesn't just fail on its own terms - it reduces the organisation's capacity for the next one. And every well-handled change does the opposite. The organisations that handle change best treat each transition as an investment in the organisation's future capacity to change, not just as a project to deliver.

The pace of change matters as much as the direction. Most change conversations focus on what needs to change and why. Far fewer focus on pace - how quickly, in what sequence, with what breathing room between initiatives. But pace is often the difference between change that lands and change that overwhelms. Too fast and people can't absorb it. Too many things at once and nothing gets the attention it needs. The organisations that are most tuned to change tend to be the ones that think about pace as deliberately as they think about content. One leadership team we worked with introduced what they called a "change load" conversation into their planning cycle. Before launching anything new, they assessed how much change was already in the system and whether there was genuine capacity for more. Sometimes the answer was no. And having the discipline to wait - even when the change was urgent - was what allowed the next one to succeed.

Honesty during uncertainty is more valuable than certainty. There's a powerful instinct during change to present confidence. To have all the answers. To project control. But people can almost always tell when certainty is being performed. And performed certainty erodes trust faster than honest uncertainty. The organisations that navigate change best are the ones where leaders are comfortable saying "here's what we know, here's what we don't, and here's what we're going to do to find out." We've seen this single shift - from performed certainty to honest uncertainty - transform how people experience change. Not because people enjoy uncertainty. They don't. But they'd rather be honestly uncertain than dishonestly reassured. One leader described it this way: "The moment I stopped pretending I had all the answers, people started trusting me more, not less. It turns out they already knew I didn't. They were just waiting for me to admit it."

Involvement is not the same as consultation. Many organisations consult people about change. Fewer genuinely involve them. The difference matters. Consultation asks people what they think and then decides anyway. Involvement gives people genuine influence over how change happens - not necessarily what changes, but how it's designed, sequenced, and implemented. People who are involved in shaping change don't experience it as something done to them. They experience it as something they're part of. One organisation we worked with had run extensive consultation processes on every major change - and people still felt like change was imposed on them. The problem wasn't the amount of consultation. It was the quality of involvement. When they shifted to genuinely involving people in designing how changes would be implemented, resistance dropped dramatically. Not because the changes were different. Because people's relationship with the change was different.

Change needs to be metabolised, not just implemented. There's a mechanical view of change that treats it as a project - plan it, communicate it, implement it, close it. But organisations don't work that way. Change needs to be absorbed, processed, made sense of. People need time to grieve what's lost, to understand what's new, to find their place in the changed reality. The organisations that handle change best build this metabolic time into the process rather than treating it as delay. One organisation we worked with noticed that every change initiative had a strange dip about three months after implementation. Performance would drop, engagement would wobble, problems would surface. Their instinct was to push through - add more support, increase communication, maintain momentum. Then they tried something different. They built in a deliberate settling period. Reduced the pace. Created space for people to process. The dip still happened. But it was shallower and shorter. And what emerged on the other side was more sustainable. The change had been metabolised, not just installed.