Systems Thinking

A pattern keeps appearing across the organisations we work with. When we ask leaders about their resilience - how their teams handled recent disruption, how the organisation responded to unexpected pressure - the answers don't follow the script you'd expect.

The organisations that came through strongest weren't the ones with the most detailed contingency plans. They weren't the ones that had invested most heavily in risk frameworks or business continuity programmes. They were the ones where something less visible was already in place - a set of conditions that meant people could sense what was happening, talk to each other about it, and respond without waiting for permission.

That distinction - between organisations that had prepared for disruption and organisations where the conditions for adaptation already existed - turns out to be more important than most resilience thinking acknowledges. It's the difference between a building that's been reinforced against earthquakes and a tree that bends with the wind and grows its roots deeper after every storm.

Why resilience programmes can make organisations more fragile

There's a well-intentioned pattern in how most organisations think about resilience. A shock happens - a pandemic, a restructure, a market shift - and the response is to build defences. More detailed plans. Tighter protocols. Bigger walls around existing operations.

It makes intuitive sense. Something broke, so we'll make it stronger. But there's a problem hiding inside this logic.

When you optimise for efficiency and control, you strip out the very things that allow an organisation to adapt. The redundancy that feels like waste is the spare capacity that lets teams absorb unexpected demand. The informal networks that don't appear on the org chart are how information travels when formal channels are too slow. The messy overlap between teams is what creates the flexibility to reconfigure when priorities shift.

McKinsey's State of Organizations research (2023) found that leaders in faster-moving organisations reported 2.1 times higher operational resilience than their peers in slower-moving ones. But the crucial detail is what "faster-moving" meant. It wasn't about speed for its own sake. It was about the conditions that made rapid adaptation possible - distributed decision-making, connected teams, cultures where people could raise concerns and respond to signals without escalating everything upward.

The paradox is that many conventional resilience strategies work against exactly those conditions. They centralise control. They add layers of approval. They standardise responses. And in doing so, they make the organisation more brittle - more able to handle the disruptions it planned for, less able to handle the ones it didn't.

Nassim Nicholas Taleb named this distinction in his book Antifragile. Fragile things break under stress. Resilient things survive. Anti-fragile things get stronger. But where Taleb's concept is often treated as a methodology to implement - a set of practices to bolt onto the organisation - the organisations we see thriving under pressure suggest something different. Anti-fragility isn't a programme. It's what emerges when certain conditions are in place.

What ecology can teach us about organisational strength

Ecologists worked this out decades before the business world started talking about resilience. In 1973, the ecologist C.S. Holling published a paper that changed how scientists understood living systems. He showed that ecological resilience isn't about a system returning to its previous state after a disturbance - it's about the system's capacity to absorb change and reorganise while still functioning.

A forest that suppresses all fires doesn't become safer. It accumulates dry undergrowth until a single spark creates a catastrophic blaze that nothing survives. A forest that experiences periodic small fires clears out dead material, creates space for new growth, and develops a diverse ecosystem that can absorb much larger disturbances. The fires aren't the enemy. They're part of what keeps the forest healthy.

Holling's insight was that resilience is an emergent property - it arises from the relationships and diversity within the system, not from anything bolted on from the outside. A healthy ecosystem doesn't have a resilience department. It's resilient because of what it is: connected, diverse, able to reorganise.

Organisations are living systems too. They have the same properties as any complex adaptive system - feedback loops, self-organisation, emergence, interdependence. And the same principle applies: their ability to weather disruption comes from their internal conditions, not from their contingency plans.

The conditions that let organisations strengthen under stress

If anti-fragility is emergent rather than engineered, the question shifts. Instead of "how do we build anti-fragility?" the question becomes "what conditions need to be in place for it to emerge?"

Across the organisational development work we do, we keep seeing the same conditions in organisations that adapt well under pressure.

Connected intelligence across the system. In organisations that respond well to disruption, information doesn't follow the hierarchy - it flows through networks. People in different parts of the organisation can see what's happening, share what they're noticing, and make sense of it together. When disruption hits, this means the organisation is already sensing the change before any formal report reaches the leadership team.

This isn't about having better communication tools. It's about whether the culture allows people to share what they see. In organisations with high psychological safety, people raise signals early. In organisations where speaking up feels risky, those signals stay hidden until they become crises.

Diversity of response, not uniformity. Organisations that strengthen under stress have multiple ways of getting things done. Not because anyone designed redundancy into the system, but because teams have enough autonomy to develop their own approaches. When one approach breaks, others are already running. When something new is needed, there are people who've been experimenting in that direction already.

This runs counter to the efficiency drive that dominates most organisational thinking. Standardisation makes things predictable and measurable. But it also creates single points of failure and kills the variation that enables adaptation.

Capacity that isn't consumed. One of the most consistent patterns we see in organisations that struggle with disruption is that they were already running at full stretch before the disruption arrived. Every person, every team, every resource was fully allocated. There was no room to absorb anything unexpected.

Organisations that adapt well have what feels like slack - people with time to think, teams that aren't fully committed to delivery every hour of every week, resources that aren't earmarked. This isn't inefficiency. It's the equivalent of an immune system - capacity that exists precisely so the organism can respond when conditions change.

Trust in the spaces between teams. Perhaps the most overlooked condition. When disruption hits, the organisation's response depends on how well different parts of the system work together under pressure. If relationships between teams are transactional - governed by SLAs and escalation processes - the response is slow and fragile. If those relationships carry trust, people pick up the phone, share what they know, and figure things out together.

This is why organisations that invest in strategic alignment - not just aligning plans, but aligning the way people across the organisation understand and relate to each other's work - tend to be more adaptive than those that don't.

What this looks like in practice

None of this means abandoning planning or structure. It means recognising that the plan is never the thing that saves you. The conditions inside the organisation are.

A practical way to think about this: instead of asking "are we prepared for disruption?", ask "if something unexpected happened tomorrow, what would our organisation's natural response look like?"

Would information reach the people who need it? Would teams have the capacity and the permission to respond? Would people across different parts of the organisation trust each other enough to coordinate without waiting for instructions? Would the organisation learn from what happened, or would it just try to return to the way things were before?

These questions reveal something important. They're not questions about resilience programmes. They're questions about how the organisation works every day. The conditions that enable anti-fragility aren't crisis conditions - they're operating conditions. An organisation that's connected, diverse, has capacity, and trusts itself doesn't suddenly develop those qualities when disruption arrives. They're either there already or they're not.

This is why some organisations get stronger under stress. The disruption doesn't just test the system - it activates what's already healthy within it. Teams that already communicate well communicate better under pressure. People who already have autonomy use it more creatively. Relationships that already carry trust deepen.

And it's why other organisations crack. The disruption reveals what was missing. The gaps in connection, the absence of spare capacity, the trust deficits between teams - these don't cause the failure, but they determine whether the organisation can absorb the shock or whether it shatters.

An invitation, not a checklist

The temptation at this point is to turn this into a framework - "five conditions for anti-fragility" with a diagnostic tool and an implementation plan. But that would miss the point.

Living systems don't follow implementation plans. They grow, adapt, and strengthen through the quality of their connections and the conditions in which they operate. The question for leaders navigating complexity isn't "what programme do we need?" It's a quieter, more searching question: what are the conditions inside our organisation right now - and are they the kind that let people adapt, or the kind that make them brittle?

The organisations that get stronger under stress didn't decide to become anti-fragile. They cultivated the conditions for it, often without using that word at all. They built trust, distributed intelligence, protected capacity, and allowed variation. And when the storm came, the system did what healthy living systems do.

It bent. It reorganised. And it grew back stronger.