Every Arm Is Still Searching: The Octopus Model of Agency

There's a video by Mark Rober where he builds an underwater maze just to watch an octopus solve it. What stays with me isn't the outcome — it's the animal's process along the way. The octopus doesn't stop when the obvious path fails. One arm explores a gap. Another circles back from a dead end. Another investigates a surface it hasn't touched before. Nothing about the animal looks frozen by the fact that it doesn't yet know the answer. It just keeps exploring until the environment hands it new information.

I've written before about turtling — looking directly at a problem and deciding, I can't solve this, someone else has to. It isn't avoidance. It's surrendering ownership of an outcome while remaining fully aware of the obstacle in front of you.

The octopus is the opposite move. Not louder, not busier. It simply keeps searching. And the more I've sat with that video, the more it looks like a second, necessary half of the same idea.

Why the octopus is a useful metaphor, and not just a cute one

The biology is part of what makes this compelling rather than just whimsical. Roughly two-thirds of an octopus's neurons live in its arms rather than its central brain. That doesn't make each arm an independent mind, but it does let each one sense, explore, and solve local problems with real autonomy while the brain coordinates the animal as a whole.

That's the part worth sitting with.

The octopus doesn't commit everything to a single plan and wait to see if it works. It learns through many local interactions happening in parallel. One arm finds a dead end and stops pushing there. Another discovers a better grip and the animal shifts its weight toward it. The brain integrates what the body is learning in real time, and the search continues without anyone needing to call a meeting about it first.

Persistence isn't really the mechanism here. Distributed search is. Persistence is just what distributed search looks like from the outside, to someone who can't see all the local feedback loops happening underneath it.

It's also worth being honest that the searching isn't aimless. Every arm's movement serves the same objective — finding food, escaping danger, staying alive. Take away that shared objective and the same behavior stops looking like intelligence and starts looking like noise. An arm exploring for the sake of exploring, disconnected from any real goal, isn't agency. It's just motion.

Turtling and octopusing are both, fundamentally, about agency

Turtling is giving up agency. The person understands the problem clearly — often more clearly than anyone else in the room — but has decided, usually without saying so out loud, that the outcome now belongs to somebody else.

Octopusing is the opposite habit: retaining ownership of the outcome by continuing to generate informed attempts after the earlier ones fail.

That's a different thing from hustle, and it's a different thing from relentless optimism. Agency isn't refusing to fail — plenty of arms hit dead ends in that maze. Agency is refusing to conclude that one failed attempt exhausted the possibilities. As long as there's still useful information to be found, there's still work to do. The moment someone decides there's nothing left to try is the moment they've stopped being an arm and started waiting to be picked up, which is exactly the posture I described in the turtling piece.

The two patterns are easy to tell apart if you watch closely, and almost impossible to tell apart from a single glance. A stalled ticket and a ticket mid-search can look identical in a status update. The difference only shows up in what happens next: does the person generate another reasonable move, or do they explain, again, why the last one didn't work?

What management style actually produces this

Organizations turtle for the same reason people do. Somewhere along the way, they teach their employees that trying isn't worth it — that the effort of generating another attempt doesn't get rewarded any differently than quietly waiting for someone else to solve it.

I don't think the opposite of that is issuing more instructions or writing more detailed runbooks. In practice, the environments that produce octopusing behavior tend to share a few things.

They push authority to the people closest to the problem, and they mean it. Not authority on paper, granted in a values deck, but authority that survives contact with an actual disagreement. If someone closest to the blocker still has to route every reasonable next step through three layers of approval, you haven't distributed the search. You've just added latency to the same single-threaded decision you always had.

That's the first shift.

They treat unsuccessful attempts as information rather than incompetence. Every failed experiment narrows the search space — that arm found a dead end, which is exactly the outcome the arm needed in order to try somewhere else. Punish every miss as if it were the failure itself, rather than a data point on the way to one, and people stop exploring after the first attempt. They learn, correctly, that the safest move is to stop moving.

And they keep exploration tethered to a real business need, not novelty for its own sake. This is the part that's easy to lose. Distributed authority without a shared objective doesn't produce an organization full of octopus arms working in parallel toward the same outcome — it produces a pile of arms flailing in different directions, each convinced its own direction is correct. The octopus's arms aren't creative for creativity's sake. They're all serving the same brain's objective. An organization has to do the same thing deliberately, because unlike an octopus, it doesn't have a single nervous system holding it together by default.

I've watched teams get the first two of these right and still stall out, because nobody ever answered the third question clearly enough — what is all this searching actually for? Without it, autonomy just produces two people solving the same ticket two different, mutually incompatible ways, each certain their arm found the right grip.

The test

Every team, every project, every organization eventually reaches a dead end. That part isn't optional and isn't a sign anything went wrong. It's just what happens when you're doing something hard enough to be worth doing.

The question was never whether the first attempt works. Almost nothing important works on the first attempt.

The real question is what happens next. When the obvious path closes, does anyone generate another informed attempt? Does someone try the next reasonable thing, based on what the last attempt just taught them? Or does everyone retreat into their shell and wait for someone else to flip them back over?

Every arm won't find the answer. Most of them won't. But if every arm is still searching, one of them usually does.

Explore More

• Turtling: When a Team Stops Looking for the Door — a related exploration of what it looks like when a team quietly surrenders ownership of a blocker
• Accountability and Authority: Walking the Tightrope — what happens when the authority to act and the accountability for the outcome don't line up
• When the Pressure is On: Late Sprint Hotfix Governance — holding onto ownership and rational decisions when everyone is screaming "rush"
• AI and Critical Thinking in Software Development — the quiet erosion that happens when we stop doing the hard thinking