The metaphor for business organizations has long been the machine. Like machines, most companies are designed for efficient, predictable outputs — minimizing variation, standardizing processes, maintaining control. For decades, this model worked well enough. In environments where the competitive landscape changed slowly and the primary challenge was operational excellence, machine-like organizations outperformed more chaotic alternatives.

That model is now breaking down. Not because execution no longer matters, but because the environment has changed in a way that makes rigidity costly. As Phil Le-Brun and Jana Werner — both enterprise strategists at Amazon Web Services, authors of a widely discussed book on the subject — argue: we need a different metaphor. The one they’ve landed on is the octopus.

Why an Octopus

The octopus has three functional qualities that make it a useful model for organizational design.

First, distributed intelligence. An octopus has a central brain, but the majority of its neurons are dispersed through its eight arms. Each arm can receive sensory information, process it, and respond — without waiting for the central brain to issue instructions. The arms don’t replace the central brain. They extend its reach.

Second, constant sensing. Octopuses detect changes in their environment in real time, through photoreceptors in their skin, pressure sensitivity across their bodies, and chemical sensing through their suckers. They’re not waiting for quarterly reports to tell them conditions have changed.

Third, radical adaptability. An octopus can change its shape, its color, and even — under certain conditions — alter its RNA at the molecular level to adapt to temperature changes. It doesn’t wait for a transformation program to approve the change. It adapts because the environment requires it.

The book Le-Brun and Werner wrote in November 2025 — HBR Press — was timed to a specific organizational moment: most companies are spending trillions on transformation efforts and seeing limited lasting results. Their diagnosis is that the problem isn’t investment or intent. It’s architecture. Organizations are trying to execute modern transformations with management structures designed for a different era.

The Tin Man Problem

Le-Brun and Werner contrast the Octopus Organization with what they call the Tin Man organization — rigid, rule-bound, uncomfortable with ambiguity, and structurally incapable of adapting without a formal change program.

Tin Man organizations share recognizable pathologies. Decision-making is centralized even when the people closest to the problem have the best information. Teams are organized around functions rather than outcomes, which means coordination happens through hierarchy rather than shared purpose. Innovation is treated as a separate process — something that happens in a lab or a skunkworks — rather than as a daily expectation of frontline teams.

The result is predictable: these organizations can execute reliably in stable conditions and fail dangerously in volatile ones. They mistake rigidity for stability. They’ve optimized for a world that no longer exists.

Distributing Decision-Making Without Losing Coherence

The central design challenge in building an Octopus Organization is one that most leadership teams get wrong: how do you decentralize authority without losing alignment?

The wrong answer is “give teams freedom and get out of the way.” Autonomy without clarity is not empowerment — it’s confusion. Teams that don’t know what they’re optimizing for, or where the boundaries of their authority lie, will either freeze or diverge in ways that undermine the broader strategy.

The Octopus model solves this through what Le-Brun and Werner call the “playground fence” concept. The leader’s job is not to stand in the middle of the playground and direct traffic. It’s to set the boundaries clearly — to define the fence — and then give teams the freedom to operate fully within that space. When the fence is clear, the freedom it contains is real. When it isn’t, autonomy collapses into either permission-seeking or organizational chaos.

The “neural necklace” is how this coherence is maintained at scale. In the octopus, the arms coordinate through a bundle of nerves that allows one arm to work with another without involving the central brain. In organizations, this requires information architecture: shared visibility into what other teams are doing, common metrics that connect local actions to organizational outcomes, and communication rhythms that keep the whole system aligned without requiring everything to route through the top.

Stripe offers a concrete example of this working at scale. In March 2025, the company released an AI-powered checkout optimization suite that dynamically adjusts payment method ordering based on customer attributes and purchase context — built on its $1.4 trillion in annual payment data. That kind of system isn’t possible in an organization where product, data, and engineering work sequentially through approval layers. It requires distributed teams with shared context and clear authority over their domain.

From Transformation Events to Continuous Adaptation

The most fundamental shift the Octopus model asks for is not structural — it’s temporal.

Traditional organizations think about change in discrete episodes: a transformation program, a strategic pivot, a digital initiative. Between these episodes, the organization is in execution mode, defending the status quo against disruption. The transformation is a temporary state. Stability is the default.

This model is increasingly untenable. The pace of market change — driven by AI capability deployment, geopolitical volatility, shifting consumer behavior — means that organizations that can only adapt in scheduled episodes will consistently find themselves behind. By the time the transformation program is complete, the conditions that justified it have changed again.

Octopus Organizations treat adaptation as a continuous process rather than a periodic event. This doesn’t mean constant reorganization — which is its own form of dysfunction. It means that sensing, learning, and adjusting are built into how work happens every day, not added on top of it.

This requires a specific leadership posture that most executives were not trained for. The machine model puts leadership at the center: leaders set direction, deploy resources, monitor outcomes, and correct deviations. The Octopus model relocates leadership’s primary contribution: leaders define intent, shape culture, and build the systems that make distributed decision-making safe and aligned. They intervene when the system produces results outside the acceptable range — but they intervene at the system level, not at the operational level.

The Three Capabilities Octopus Organizations Build Deliberately

Clarity about purpose and boundaries. Not mission statements — specific, operationally useful answers to the questions frontline teams face when they’re making decisions without approval from above. What does good look like? What would make us stop doing something? What would make us start? What are we unwilling to compromise on?

Genuine ownership. Not responsibility without authority. Not accountability without resources. The ownership model in an Octopus Organization is the same one that works in entrepreneurial contexts: the people closest to the problem have the authority and the resources to address it, and they’re held accountable for outcomes rather than compliance with process.

Curiosity as an organizational muscle. Le-Brun and Werner identify curiosity as one of the three defining traits of Octopus Organizations (alongside clarity and ownership). This is not incidental. Curiosity is what generates the sensing function — the ongoing awareness of what’s changing in the environment and what it might require. Organizations that suppress curiosity — through cultures of certainty, through punishment of experimentation, through leadership that treats questions as insubordination — are systematically depriving themselves of the inputs they need to adapt.

What Leaders Misread About This

The most common misreading of the Octopus model is that it’s about loosening control. It isn’t. It’s about relocating control — from the hierarchy to the system.

Centralized control is fragile. It fails when the person at the center doesn’t have good information, when the environment changes faster than the approval chain can respond, or when the organization scales beyond what centralized decision-making can handle. Distributed control — embedded in shared purpose, clear authority, and strong information architecture — is more robust under all three of these conditions.

The second misreading is that this is a technology story. It isn’t primarily that either. Technology enables the information architecture. But the bottleneck in most organizations is not the availability of information — it’s the organizational permission to act on it. Building an Octopus Organization requires leadership courage to relinquish operational control, not just investment in data infrastructure.

The companies that get this right — that build genuine distributed intelligence rather than performing it — will have a structural advantage in environments that continue to change faster than traditional organizations can respond. That advantage compounds. Each cycle of sensing, learning, and adapting makes the next one faster and better-calibrated.

The organizations that don’t get this right will keep investing in transformation programs that produce limited lasting results — spending heavily to prepare for a world that has already moved on by the time they’re ready for it.