If teams are to act coherently in a changing environment, they need more than autonomy and coordination. They need shared clarity about what creates value, whose needs matter most, and which signals deserve a response, and a deliberate system design that enables them to act on that clarity.

An Octopus is not effective simply because each arm can act independently. It is effective because those arms remain connected in a way that allows the whole organism to respond fluidly and without delay. The same is true of organisations. An adaptive organisation is not simply one where teams can operate independently. It is one where teams can come together effectively when they need to, separate cleanly when they do not, and do both without unnecessary friction.

The Octopus Organisation offers a metaphor for distributed sensing and action. An Octopus arm is responsive because it is part of a system with clear roles, relationships and responsibilities that enable action to happen locally while remaining coherent overall. Organisations are no different. If you want adaptability, start by asking whether your teams know when to act, when to coordinate, and when to defer. Because ownership clarity is one of the conditions that makes adaptability possible.

Becoming more adaptive is often framed as a question of speed, but speed alone is not the goal. The goal is to respond in a way that is both timely and coherent, and that requires more than pushing decisions to the edge. It requires clarity about what matters, and the deliberate design of a system that allows teams to act on that clarity.

Responsibility and authority are not the same thing. A team may be accountable for an outcome, yet lack the authority to change the conditions required to achieve it. They are asked to improve speed, but another group controls the pipeline. They are measured on customer experience, but priorities are set elsewhere. They are expected to reduce incidents, but key technical decisions sit outside their remit. So responsibility sits in one place, decision rights sit in another.

The bystander effect reminds us that people often fail to act not because they do not care, but because they are in a situation where responsibility is unclear. And the same is true inside organisations. When ownership is clear and visible, people step forward. When ownership is blurred, people step back.

The real test of ownership isn’t clarity in documentation; it’s clarity at the moment of interaction. When two teams disagree about priority, or a cross-cutting decision has implications for several domains, or when risk appears and no one is certain who carries it. That’s where ambiguity reveals itself.

Every metric contains a theory about how value flows. If you measure velocity, you are assuming that more estimated output corresponds to more meaningful progress. If you measure utilisation, you are assuming that busyness equates to productivity. If you measure features shipped, you are assuming that output reliably translates to impact.

These assumptions are rarely made explicit, but they govern decisions. The theory embedded in the metric becomes the architecture of the organisation. So Goodhart’s Law is not about gaming the system; it’s about design.

When the conversation turns from “how do we eliminate this?” to “what is this forcing us to choose?” the dynamic shifts. The group begins to prioritise more honestly. Peripheral ambitions fall away. Trade-offs become explicit rather than implied.

Instead of asking, “How do we work around this constraint?” Ask, “What does this constraint tell us about what matters?” That second question changes the conversation. It forces prioritisation, surfaces hidden preferences and exposes which initiatives are truly strategic and which are comfort projects.

Constraints don’t just restrict, they clarify. When considered carefully, they reveal what truly matters; expose assumptions about value that otherwise remain implicit and force prioritisation. The problem isn’t the presence of constraints, it’s how they’re interpreted.

Shared goals are often treated as the end state of alignment. If everyone agrees on what matters, the assumption is that the right decisions will naturally follow. What I tend to see is that goals hold only until they meet constraint. Capacity tightens, an urgent request appears, or two important initiatives compete for the same resource. In that moment, the goal itself rarely tells people what to do. It offers direction, but not judgment.

Agreement tends to focus on what we want to achieve. Alignment becomes visible later, when people have to decide how to act under constraint — what to prioritise when capacity tightens, what to defer when two important things compete, and whose needs take precedence when compromise is required.

When “control” becomes the wrong instinct in complex systems

I've been exploring AI less as a destination and more as a diagnostic. If AI is best understood as a diagnostic, then the most important leadership work isn’t deciding where to deploy it, but deciding how to respond to what it reveals.

AI is not forcing a new structure into existence. It is revealing where the current one no longer fits the work it is being asked to support. And that is why it can feel destabilising. Not because it introduces chaos, but because it removes the comfort of slack and makes structural misalignment visible. Seen this way, the opportunity is not to reorganise around AI, but to treat the friction it surfaces as actionable feedback on team design.

In slower environments, coupling is masked by experience and goodwill. People bridge gaps manually and absorb the cost. Under AI-driven pressure, that absorption capacity diminishes. Dependencies do not disappear with better tools- they become more apparent.

One way to think about the current wave of AI adoption is not as a transformation programme, but as a diagnostic for how our organisations actually function under pressure. When you look at it through that lens, decision-making is often the first thing to show strain.

AI isn’t the transformation, it is the stress test that reveals where organisational change has been overdue for some time.

Teams often find it helpful to have a way of describing where they are. Whether it’s through surveys, assessments, retrospectives, or research-backed models, being able to say “this roughly reflects our situation” can bring a sense of clarity and shared understanding. It gives teams language for the conditions they’re operating within, and often creates a moment of recognition.

What tends to be harder is knowing what that recognition should lead to. Once a team can describe the environment it’s in, the question shifts from understanding to action. What would actually make a difference here? Which changes are worth attempting, and which would simply make the current situation run a little more smoothly without really changing it? That’s the question I want to explore.