We are conditioned to look for the center of things. When we try to understand an organization, we ask for an organizational chart. When we look at a nation, we look to its capital. Traditional architecture—whether of a building, a company, or an army—relies on a classic playbook: a strong hub, radiating outward. You find the center, you secure it, and the system holds.
But what happens when you try to decapitate an enemy, or a technology, that has no head?
In 1964, a brilliant engineer named Paul Baran sat at his desk at the RAND Corporation, trying to solve a Cold War nightmare: How do you maintain a communications network after a catastrophic nuclear strike? Baran realized that traditional networks were centralized—like a wheel with spokes. If you destroy the hub in the center, every single spoke becomes useless.
His solution was the distributed network, the foundational blueprint for what would eventually become the Internet.
“Under the proposed system, each station would need to be connected to only a few of its nearest neighbors… The system would be highly reliable, even if a large fraction of the stations were destroyed.”
Baran mathematically proved that if you remove the center, the edges don’t die. They simply reroute. A few decades later, telecom engineers used a remarkably similar logic to build cellular telephone networks. Instead of one massive, high-power radio tower serving an entire city, they broke the terrain into a grid of small, low-power cells. If one tower goes offline, the network degrades gracefully rather than collapsing. It bends, but it refuses to break.
There is a profound, poetic irony buried here. The United States government originally funded Baran’s research to create a distributed network so that its centralized monolith could survive. Decades later, asymmetric adversaries across the globe adopted that exact architectural philosophy for their physical defense doctrines—creating “Mosaic Defense” systems designed specifically so that when you destroy the center, the edges keep fighting.
They copied our homework to survive our strength.
I find myself thinking about this tension far beyond the realms of military strategy or software engineering. It is a metaphor for how we construct our lives. We often build centralized lives—anchored entirely to a single identity, a single career, or a single institution. We project a monolith of strength to the world. But monoliths are brittle. When the center is struck, the whole architecture crumbles.
The lesson of our modern architecture is becoming increasingly clear, whether you are managing a network, building an organization, or navigating the quiet complexities of a human life. The fragile monolith is an illusion of safety.
The future belongs to the web that knows how to reroute.