Structure alone is not what determines how a system performs.
This system pattern shows: underlying enablers, how they shape organisational operations, and how work actually happens over time.
When critical capabilities and functions are designed to rely on each other, you get organic connections and ongoing adaptation.
When functions are designed to hold responsibility on their own, you get a highly managed environment that is less responsive to changing needs.
What this pattern shows
Two organisations can have the same core capabilities and functions, but behave very differently.
The difference sits in the connections.
- One system is integrated and living.
- The other is dispersed and managed.
How the system behaves over time
In an integrated living system:
- capabilities are interdependent
- connections are active, reinforcing, and continuously evolving
- improvement is ongoing and informed by experience
- adaptation happens as part of normal work
The system regenerates. It responds to signals. It builds resilience over time.
In a dispersed managed system:
- capabilities operate more independently
- connections are transactional and often conditional
- improvement is intermittent and triggered
- adaptation is reserved for significant change
The system relies on control. It requires effort to coordinate. It is more predictable, but less responsive.
What’s really going on
The same elements exist in both systems.
What changes is how they are enabled and connected.
In the integrated system:
- identity is shaped in and by the environment
- knowledge flows and informs action
- experience feeds improvement
- capability and adaptation reinforce each other
In the dispersed system:
- identity is set and managed
- knowledge is uneven or underused
- experience is addressed as issues arise
- capability is built for specific needs
Connections are weaker, less consistent, and often dependent on intervention.
Why this is hard to shift
Most organisations are designed for clarity, control, and accountability.
That naturally creates independence between functions.
Over time:
- connections become optional rather than expected
- improvement becomes a separate activity
- adaptation is treated as disruption
- urgent work crowds out important work, reinforcing independence
Shifting this is not about adding new capabilities.
It is about changing how the existing ones connect and operate together.
What helps shift the pattern
- Design connections to be deliberate and expected, not incidental
- Invest in continuous improvement through multi disciplined, cross functional teams
- Use experience and knowledge as inputs to everyday decisions
- Strengthen shared identity and intent across the system
- Design for interdependence, not just clear roles
Small changes in how capabilities and functions connect can significantly shift identity and performance.
Reflection questions
- Where does your system rely on control rather than connection?
- Which capabilities operate in isolation?
- When does improvement actually happen, and what informs it?
- How easily does your system respond to new or unexpected signals?
- What connections would need to strengthen to make this easier?