<p>Most organizations think they have a collaboration problem when what they actually have is a defensiveness problem. People show up to meetings, share updates, hit their deadlines, and call it teamwork. But underneath that surface-level cooperation, something else is often happening: information gets filtered before it&#8217;s shared, credit gets quietly hoarded, and problems get hidden until they&#8217;re too big to hide anymore. Cooperation keeps the lights on. It does not build resilient teams.</p>
<p>James W. Tamm and Ronald J. Luyet&#8217;s book Radical Collaboration has been a guiding influence on how I lead, for the better part of my career. I don&#8217;t reference it here as an interesting framework I once read about. It shapes how I try to run teams, and it&#8217;s the standard I hold myself to more than any team I&#8217;ve led. Their central insight is simple and uncomfortable: most workplace dysfunction is not a strategy problem, it is a defensiveness problem. People protect themselves before they contribute, and that self-protection, multiplied across a team, quietly destroys the thing the team was supposed to produce together.</p>
<h2>The zone that decides everything</h2>
<p>The book&#8217;s most useful idea is what it calls the Green Zone and the Red Zone. In the Green Zone, people operate from curiosity and shared purpose. They ask what is actually true, they assume good intent until proven otherwise, and they treat disagreement as information rather than as an attack. In the Red Zone, people operate from self-protection. They manage impressions instead of solving problems. They withhold information that might make them look bad. They compete quietly for control even inside teams that are supposed to be pulling in the same direction.</p>
<p>The uncomfortable part is that almost nobody chooses the Red Zone consciously. It shows up as a default reaction to pressure, uncertainty, or a history of being burned. A leader who has been blindsided by a supplier failure once will start double checking everything, which looks like distrust to the team even when it&#8217;s really just scar tissue. A team member who raised a concern early and got ignored will stop raising concerns, not out of malice but out of learned caution. Red Zone behavior is rarely a character flaw. It is almost always a rational response to an environment that punished openness at some point in the past.</p>
<p>This is why I don&#8217;t believe collaboration can be mandated through a value statement on a wall. I&#8217;ve tried to build it the slower way, through consistent, small, repeated proof that openness will not be punished. That proof has to come from the leader first, every time, before anyone else has a reason to trust it.</p>
<h2>Truth as infrastructure, not virtue</h2>
<p>Tamm and Luyet treat truthfulness less as a moral position and more as operational infrastructure. Their principle of surfacing the hardest information first, rather than easing into it, is not about bluntness for its own sake. It is about respecting the other person&#8217;s ability to act on accurate information in time to do something about it.</p>
<p>This is one of the principles I hold hardest to in practice. In any environment where timing matters, and few environments punish delay as unforgiving as supply chains and physical operations, a truth delivered late is barely different from a lie. A capacity problem flagged three days before it becomes visible on the floor is useful. The same problem flagged three days after is just an explanation. I try to make sure the people around me know that bringing me a problem early is always the right call, even when the problem is their own mistake. Teams that reward the messenger who stays quiet until things are unavoidable are training their best people to become quiet, and I&#8217;ve seen how expensive that habit becomes once it sets in.</p>
<h2>Accountability without self-erasure</h2>
<p>The self-accountability skill in the book is easy to misread as a call for constant self-blame. It is closer to the opposite. Genuine accountability requires enough psychological stability to look honestly at your own contribution to a problem without collapsing into shame or flipping into defensiveness. People who cannot tolerate being wrong tend to become people who cannot admit being wrong, and a team full of people who cannot admit being wrong will spend enormous energy managing blame instead of managing the actual problem.</p>
<p>This matters especially in cross-functional or cross-border work, where a failure rarely has a single cause. When a shipment is late, it is almost never one department&#8217;s fault in isolation. It is a chain of small decisions and small delays across planning, procurement, warehouse execution, and transport, each of them defensible in isolation. I try to model this myself before I ask it of anyone else: naming my own part in a failure openly, before looking for anyone else&#8217;s. A team that can sit with that complexity, and let multiple people say &#8220;this is where I could have done better&#8221; without anyone using it as ammunition, solves the underlying process. A team that needs a single person to blame solves nothing, because the next failure will just find a different name to attach itself to.</p>
<h2>Knowing what you&#8217;re actually reacting to</h2>
<p>The book leans on FIRO theory, the idea that much of our interpersonal friction comes down to unmet needs around inclusion, control, and connection, to explain why some conflicts feel disproportionate to their apparent cause. A disagreement over a process change is rarely just about the process. Sometimes it&#8217;s about a person&#8217;s need to feel consulted. Sometimes it&#8217;s about a need to retain a sense of control over an area they&#8217;ve been responsible for a long time. Sometimes it is about wanting to be seen as competent in front of peers.</p>
<p>None of this means every conflict has a hidden psychological cause that needs unpacking in a meeting. It means that leaders who only address the stated content of a disagreement, and never notice the unstated need underneath it, will keep solving the same conflict in different clothes. Awareness of others is not about analyzing people. It is about staying curious enough to ask what someone actually needs, instead of assuming their objection is only about the words they used. This is, honestly, the skill I&#8217;ve had to work hardest at over the years, and I still don&#8217;t always get it right.</p>
<h2>Why this matters more as complexity increases</h2>
<p>The argument for radical collaboration gets stronger, not weaker, as operations get more distributed, more automated, and more cross-border. Automation removes a layer of manual buffer that used to quietly absorb miscommunication. Cross-border teams remove the shared cultural shorthand that used to make intent easy to read. Both of these trends mean that the assumptions people used to lean on, that someone will just figure it out, that context will fill the gaps, become less reliable every year.</p>
<p>What replaces those old buffers is not more process documentation. It is teams that default to the Green Zone even under pressure, that treat early honesty as a habit rather than a favor, and that can hold each other accountable without turning every mistake into a referendum on someone&#8217;s competence. I&#8217;ve built my leadership around these principles for long enough to say with confidence that they are not a soft skill bolted onto operational excellence. They are the operational foundation everything else depends on.</p>

Why Most Teams Cooperate but Never Collaborate
