Chain of command: your organization's biggest single point of failure

A cyclone was forming off the coast. They told us to drive south as fast as possible, because there was only one road going south.

One single road. And if that road flooded, we'd be stuck. There was no alternative, no detour, basically no way out. We'd be trapped in our campervan, in a cyclone.

Not exactly the trip we'd imagined.

The concept comes straight from military thinking. Generals give orders to colonels, colonels to majors, majors to captains, and so on down to the private who actually does the work. It worked for armies conquering continents, so naturally businesses adopted it wholesale during the industrial revolution.

The assumption seems logical: one clear line of authority equals clarity and order. No confusion about who's in charge. No conflicting instructions. No chaos.

But what if that single line is actually a vulnerability? What if the very thing designed to create order is what makes your organization fragile?

Think about it. That chain of command is exactly like that single Australian road I was racing down, trying to outrun a cyclone.

The one-road problem

Image: our campervan in northeast Australia, just before the cyclone forced us to drive south on the only road available.

We made it in time, after driving almost non-stop for a few days. But the experience stuck with me.

Because that single road is exactly how most hierarchical organizations work.

Information from the frontline travels up through a team lead, then a department head, then a VP, then the CEO. That is one chain of command. Exactly like that Aussie road.

And if one person in that chain is sick, on holiday, or decides to hide bad news? Then the connection is gone. The chain is broken. Just like a flooded road.

Think about every corporate disaster you've read about. Volkswagen's emissions scandal. Wells Fargo's fake accounts. Boeing's 737 MAX crashes. In each case, people on the frontline knew something was wrong. But that information got stuck somewhere in the chain of command. A middle manager didn't want to look bad. A department head thought they could fix it quietly. An executive decided the board didn't need to know yet.

One person. One blockage. Total system failure.

This isn't just bad luck or bad actors. It's mathematics.

What a mathematician proved in 1927

In the early 1920s, a young Austrian mathematician named Karl Menger was working at the University of Amsterdam. Unlike his famous father (Carl Menger, founder of the Austrian School of economics) Karl wasn't interested in markets.

He was interested in networks.

In 1927, he published a theorem that remains deeply relevant to how we design organizations today. Here's what it says, in simple terms:

Now think back to that Aussie road. One main road between the Daintree and Mackay means one flood kills the connection entirely. As Menger's theorem says: One independent path equals one point of failure.

Now imagine five completely separate roads. To cut off all access, you'd have to flood all five simultaneously. The number of backup routes you have equals the number of breakdowns you can survive.

This isn't abstract theory. It's why the internet was designed with multiple pathways between any two points. It's why power grids have redundant connections. It's why your heart has multiple arteries feeding each section.

And it's why your chain of command is fundamentally broken.

Menger's Theorem: a hierarchy has one path (and one point of failure), while a network stays connected even when multiple nodes fail.

Apply this to the single chain of command in most organizations. How many independent paths exist between a frontline worker and the CEO? Usually one. Maybe two if you're lucky and there's some kind of skip-level meeting once a quarter.

That means removing just one or two people severs the connection entirely.

One middle manager who blocks bad news. One department head who filters information. That's all it takes to stop the information from flowing to the right places.

From roads to organizations

Now think about how a flat organization structured as a network of teams solves this.

Take NER Group, the network of companies in the Basque Country, and companies like Indaero in Sevilla and Alumipres in Barcelona. These aren't theoretical case studies. They're real companies with real revenues and real employees who've structured themselves completely differently.

In all these companies, autonomous teams connect directly to each other through representatives in regular decision-making meetings. But here's the clever part: there are different kinds of representatives in every team. And when one can't be there, another team member fills the spot.

On top of that, all information is radically transparent. Everybody can see and access almost everything. Financial data, strategic plans, customer feedback, production issues. It's all out in the open.

As a result, information flows through peers, through other teams, through shared assemblies, through open financial data, and through direct conversations across the entire network.

That means between any two people in the network there aren't one or two paths that connect them to each other. There are dozens.

And Menger's theorem tells us exactly what that means: to cut off the flow of information in a network of teams, you'd have to remove dozens of connection points simultaneously.

That's what mathematical resilience looks like.

How network organizations build resilience

Let's get specific about how these organizations actually work.

At NER Group, teams elect their own representatives to coordination meetings. Not managers appointing delegates. These representatives rotate regularly, so knowledge and connections spread throughout the organization.

But the meetings are just one path. Team members also visit other teams directly when they need help or information. They access shared databases where all operational data lives. They join cross-functional project groups that form and dissolve based on need.

Bill Gore, founder of W.L. Gore, understood this decades ago when he created what he called the Lattice Organization. As he put it:

Gore didn't just observe this. He built W.L. Gore around it. No fixed chain of command. No hierarchy of titles. Just a lattice of connections where anyone could reach anyone. The company has been running this way since the 1950s, with over 12,000 employees today.

That's the power of a true organizational network in practice.

The subtle part most people miss

But there's a catch. Having lots of connections isn't enough on its own.

A network where each person has many links can still be fragile: if all paths between two critical people pass through the same three intermediaries, you still only need three floods to sever the connection.

It's about how many independent connections they have. Not just about how many connections people have.

That's the difference between a network on paper and a network in practice.

Many organizations claim to have "matrix structures" or "cross-functional teams." But look closer. The project teams all report to the same steering committee. The cross-functional groups all need approval from the same three executives. The matrix still has a hidden hierarchy underneath.

These are multiple lanes on the same road. And when that road floods, all the lanes flood together.

True network resilience means genuinely independent pathways. The production team can reach customers directly. The customer service team can change product specifications. The finance team can launch new initiatives. Without asking permission. Without going through headquarters. Without climbing the chain of command.

The lesson

Most leaders spend their time optimizing the one road. Making it wider. Paving it better. Adding traffic lights. Installing better communication systems. Running leadership development programs. Creating skip-level meetings.

But the real question isn't how good your one road is. It's how many roads (and roundabouts) you have.

Menger proved it in 1927.

Almost a hundred years later, most organizations haven't caught up.

They're still building better chains of command instead of questioning why they need a chain at all.

Stop optimizing the one road. Build the network instead.

You've seen the math: a single chain of command is a single point of failure, and resilient organizations are built as networks of autonomous teams. But knowing that and building it are two very different things.

That's what our Progressive Organizational Masterclass is for. You'll learn the exact structures behind network organizations like NER Group, straight from the pioneers who run them, alongside Buurtzorg, Viisi, and Haier. No academics theorizing. No consultants selling recycled frameworks. Just proven blueprints from the 200+ organizations we've actually visited, plus a global network of 1,200+ fellow pioneers across 38+ countries.