Adaptability is often treated as a cultural characteristic.
We want people to embrace change, become more agile, experiment, collaborate, and respond faster.
All of that may help.
But adaptability is also a design outcome.
An organisation cannot consistently behave adaptively if its structure makes adaptation difficult.
Consider what happens:
- When every meaningful decision requires three management layers.
- When teams depend on five other departments to deliver customer value.
- When funding is fixed around annual projects even though priorities change every quarter.
- When information moves quickly but authority does not.
In those environments, asking people to “be more agile” will only take you so far.
Adaptive organisations tend to make a few design choices differently.
- They shorten the distance between information and decision-making.
- They organise more work around value than around functional boundaries.
- They give teams enough context to act without constant escalation.
- They make priorities visible.
- They build feedback into the way work is managed.
- And they accept that some structures should evolve as the environment changes.
This does not mean removing governance or turning the organisation into a collection of autonomous teams.
Adaptability still requires alignment.
In fact, autonomy works best when strategic intent is unusually clear.
The question is therefore not whether an organisation should be centralised or decentralised, agile or traditional. The more useful question is:
Where do decisions need to be made for the organisation to respond effectively?
Once you understand that, you can design structure, governance, teams, roles, funding, and ways of working around it.
Culture matters.
But when people repeatedly behave in ways the organisation says it does not want, it is worth looking at the system around them.
Sometimes behaviour is simply the rational response to the organisation we designed.