Is Your Business a Machine or an Animal? Be the Octopus!

We have long been taught to view the organization as a machine. It’s a comfortable metaphor: blueprints, gears, systems, predictability, and control. But there is a problem with machines, they are rigid. When the environment changes with time, as will always happen, the machine will break.

I was reading a fascinating article from the Harvard Business Review recently regarding the concept of the “Octopus Organization.” It suggests that the typical organization is less like a well-oiled machine and more like the Tin Man from The Wizard of Oz, rusted solid, waiting for an outside fix just to move again.

This rigidity explains a startling statistic: despite the trillions invested in corporate transformation, only 12% of these initiatives result in sustainable performance gains.

So, if the machine is the wrong model for the Agile Enterprise, what is the right one?

The “Silo Tax” and the Horizontal Breakdown

Before we can become agile, we have to look at why the “Machine” model is failing. The HBR authors suggest we look to the octopus because of its distributed intelligence. Its arms can think and act independently while working in concert with the brain.

Most organizations today are the opposite. They suffer from a “horizontal breakdown.” Research by Sull, Homkes, and Sull highlights a massive disparity in trust: while 84% of managers rely on their bosses and direct reports, only 9% say they can rely on colleagues in other functions.

This creates a “Silo Tax”, the invisible cost of doing business when departments treat expertise and information like a guarded secret. It may have been a transformative idea, but execution fails because the “arms” of the octopus aren’t talking to each other.

The Great Confusion: Output vs. Outcome

The second major failure of the “Machine” mindset is how we communicate strategy.

I see this very often. A leadership team announces a new strategy: “We are going to increase EBITDA by 50%.” But let’s be clear: That is not a strategy. That is a number. This highlights a fundamental confusion between Organizational Output and Outcome.

  • Outputs are the directed work delivery – the projects, the tasks, and the initiatives we execute.
  • Outcomes are the results – the KPIs (like EBITDA) that tell us if the work was valuable.

When you hand down a financial target without connecting it to the necessary work delivery, you are engaging in wishful thinking, not strategic planning. In an agile enterprise, you must link the activity (what we are doing) directly to the metric (why we are doing it).

Enter the Octopus: Sensing, Learning, and Responding

To solve the Silo Gap and the Output/Outcome confusion, we need to stop building machines and start behaving like an organism. The HBR article notes that Octopus organizations “sense subtle signals, learning and shifting course at speed”.

This aligns perfectly with the philosophy behind StrategyBlocks. We built our platform to ensure that strategy isn’t just a document for the boardroom, but a living system that connects the brain to the arms.

  1. Connecting Work to Value | StrategyBlocks is designed to bridge the gap between delivery and results. We allow you to model the link between Output (your projects and initiatives) and Outcome (your risks and metrics). This ensures that “Increasing EBITDA” isn’t just a poster on the wall, it is the measurable result of specific, visible, directed work.
  2. Distributed Intelligence (StrategyBlocks Ideas) | The HBR authors note that adaptive organizations “create mechanisms for invention everywhere”. We have operationalized this with the latest release of StrategyBlocks and our new Planner functionality.

Innovation is a distributed capability. StrategyBlocks Ideas allows your strategic plan to grow dynamically from the bottom up. It enables anyone, from the C-suite to the frontline, to contribute ideas. This captures the “distributed intelligence” of your people, allowing the organization to sense and respond to the market instantly, rather than waiting for a top-down directive.

  1. Visualizing the Whole (The Cascading Value Tree) | Finally, to defeat the “Silo Tax,” you need radical visibility. StrategyBlocks utilizes a Cascading Value Tree, a highly customizable layout that offers real-time visibility into initiatives across all departments. When everyone can see the same “blocks” of the strategy, trust increases, and the 9% reliability gap begins to close.

In Summary

The world is no longer complicated (predictable like a machine); it is complex (unpredictable like the ocean). We can no longer afford to be the Tin Man.

If you are looking to clear up the confusion between outputs and outcomes, and create an agile enterprise that can “sense and respond” to change, come take a look at the new StrategyBlocks. Let’s stop building machines and start building something alive.