the collaboration principle

The hierarchical model that shaped the twentieth century was built for a world that changed slowly enough to be managed from the top down. It gave us stability, predictability, and scale. But it was also built on an assumption that has quietly collapsed: that the people at the top could hold enough of the picture to make the right calls for everyone below them.

That assumption no longer holds. Not in a world where AI is reshaping entire industries in the span of months, where geopolitical disruption outpaces strategic planning cycles, where the complexity organizations face has long since exceeded the cognitive bandwidth of any single leadership team.

The typical response? Add a new workstream. Convene a task force. Appoint a Chief Something Officer. In other words: more boxes, more process, more structure layered onto an architecture that was already struggling to breathe.

We call this the patch reflex. And it is making things worse.

What organizations were actually built for

In “The Nature of the Firm”, an article published in 1937, Ronald Coase argues that firms emerge because they are better equipped to deal with the transation costs inherent in production and exchange than individuals are. He was awarded a Memorial Nobel prize in Economics for this paper in 1991.

In other words, organizations exist to simplify the coordination between people who need to work together. That’s it. Nothing mystical. A car does not require a company to exist, but building one affordably requires synchronizing designers, engineers, suppliers, distributors, and customers in a way that no informal arrangement could sustain at scale.

The org chart is the attempt to draw that coordination on paper. And on paper, it often looks rational. But here is what the chart never captures: the real forces that hold any organization together are not reporting lines. They are passion and indifference, loyalty and quiet betrayal, the energy of people who care deeply and the drag of those who checked out two years ago. They are the informal conversations, the cross-functional relationships that nobody sanctioned, the individuals who bridge silos because they happen to trust each other.

The connections that generate the most value are almost never the ones that appear in an org chart. They are the ones that cross it.

The Patches and Nodes model

The framework we work with at TCP starts from a different premise: that organizations are not machines to be engineered but living systems to be cultivated.

In that system, every person is a Node. An individual with a unique set of experiences, capabilities, and relationships. Nodes are not cogs. They are the actual sources of intelligence in the system, and they are naturally oriented toward connection.

A Patch is a community of intent: a group of people gathered around a shared purpose, a common task, or a lived experience. A business unit is a Patch. So is a project team. So is the informal network of people across your organization who care about the same thing and have found each other anyway.

A Patchwork is the whole: the sum of all Patches and, critically, the density and quality of the connections between them. The health of a Patchwork is not measured by how well-defined its boxes are. It is measured by how well information flows, how quickly learning travels, and how effectively the system can reconfigure itself around what actually matters right now.

No one drives a Patchwork. No one owns it. It is governed by the same principles that govern any living, adaptive system: variety matching complexity, signal amplification through connection, distributed intelligence outperforming centralized control.

Why this matters now more than ever

The Law of Requisite Variety, formulated by the cybernetician W. Ross Ashby, states that a system can only regulate itself against complexity if it contains at least as much variety as that complexity. In plain terms: if your environment is more complex than your organization, your organization will lose.

Most organizations today are losing that race. Not because their people are not capable, but because the architecture suppresses the very variety it needs. Hierarchy homogenizes. It filters signal into noise. It rewards conformity at precisely the moment when the world is punishing it.

The Patches and Nodes model is not a structural fix. It is not a new org chart. It is a shift in how people relate to each other and to the work, governed by three principles that sound deceptively simple:

First, ship what you learn. Every insight, every discovery, every lesson from failure: share it, deliberately and quickly, with the people who could use it. Not in a quarterly knowledge-management review. Now.

Second, use what you get. Whatever reaches you through the network, integrate it. Let it change how you work. The point of information flowing is that it should move something.

Third, optimize your Patch. Know who is in your immediate community of intent. Know what they are capable of. Distribute responsibility in a way that stretches people and wastes no one.

These three rules, applied consistently, produce something that no process redesign or leadership offsite can manufacture: an organization that learns faster than its environment changes.

What this looks like in practice

Our work at TCP is to help organizations build those conditions deliberately.

This happens primarily through large-group facilitation: immersive sessions of twenty to two hundred people, designed to surface the real connections and the real obstacles in a system, to activate the distributed intelligence that exists across an organization but has never been given a room to work in together.

We bring together people who do not normally share a table. We design interactions that make the informal visible. We create the conditions for cross-Patch connections to form, strengthen, and carry learning back into the work.

We do this for multilateral organizations navigating structural transformation, for global corporations facing discontinuous change, and for leadership teams that have understood, finally, that the answer to increasing complexity is not a smarter strategy document. It is a more connected, more adaptive, more genuinely intelligent organization.

Matt and Gail Taylor who first played with and taught us about Patchwork Architectures and Designs wrote : ” Life must be lived, not managed.” .

It’s not easy for leaders and managers to just let things be, but this is what a patchwork needs.

What becomes possible

The value of this work is not always easy to put in a slide. But organizations that have gone through it tend to describe the same things: decisions that used to take months start moving in days, because the people who need to align have actually met each other, understood each other’s constraints, and built enough trust to move without waiting for permission. Silos that had calcified over years begin to dissolve, not through mandate but through the simple experience of having solved something together that neither side could have solved alone.

At a human level, people remember that their work can mean something. Engagement, that most elusive of organizational metrics, tends to follow when people feel that their contribution is visible and that the system around them is actually responsive to what they bring. The talent that hierarchies routinely suppress, the person in the middle of the org chart who holds the relationships and the institutional knowledge and the goodwill that no one thought to make official, comes into the light.

At a strategic level, the organization develops what might be the most valuable capability available in a volatile world: the ability to reconfigure quickly around what matters now. Not because a leader told it to. Because the Patchwork already knew what needed to happen, and had the connections to make it happen.

The investment is a few days, sometimes a few weeks. The return, when the conditions are right and the intent is genuine, is an organization that is measurably more capable of facing what comes next. Whatever that turns out to be.