The Silo Trap: Why Self-Organized Teams Must Understand the Entire Process Chain
The Fractal Cell Part III: Moving from local optimization to end-to-end ownership.
In my previous articles on The Fractal Cell, we explored how to replace the classic middle-management bottleneck with self-organizing cells. By distributing leadership functions across four clear roles within the team—Curator, Performance Scout, Intelligence Scout, and Meeting Host—we create highly autonomous, adaptable units.
But autonomy has a hidden dark side: The Silo Trap.
When you give a team total focus on its own performance, it tends to optimize locally. The sales team optimizes for the maximum number of signed contracts. The production team optimizes for standard execution. The customer success team optimizes for ticket-closing speed.
The fatal flaw? Local optimization often destroys the global process. Sales sells something that production has to fix with massive overtime, and customer success spends days cleaning up the resulting mess. It is the classic “throw it over the wall” mentality.
If we abolish the middle managers who traditionally bridged (or forced) these gaps, how do we prevent the company from fracturing into isolated islands?
The answer is not to hire a new “Process Manager.” The answer is to build end-to-end process awareness directly into the DNA of every single team member. We need systemic thinking for everyone. And the mechanism that makes this possible is not a new reporting structure—it is the rhythm of doing and undergoing.
1. Lateral Networks: Correspondence, Not Just Communication
In traditional hierarchies, information flows vertically: up to the manager, across to the other manager, and down to the other team. It is slow and prone to distortion. The message gets filtered, summarized, and sanitized at every stage. By the time it reaches the team that needs it, the original signal has been lost.
In the Fractal Company, the roles connect laterally. The Intelligence Scout of Team A doesn’t just talk to their own team; they regularly sync with the Intelligence Scouts of Team B and Team C. The Performance Scouts across the entire value chain form a horizontal network.
But here is the critical nuance: This is not just about exchanging information. It is about correspondence—a concept from the anthropologist Tim Ingold that describes a responsive, reciprocal engagement between an actor and the world around them. The Intelligence Scout of the sales team doesn’t just report what they observe in the market. They bring that observation into a lateral meeting, where the Intelligence Scout of the production team responds to it from their reality. That response, in turn, changes how the sales scout perceives the original observation.
This back-and-forth is what Ingold calls the rhythm of doing-undergoing. You act. The world answers. You absorb that answer. Then you act again—differently. In a lateral network, the “world” that answers is the adjacent team. The sales representative does (sends a contract with a tight delivery promise). The production team undergoes (absorbs the impact of that promise—the overtime, the stress, the compromised quality). When a lateral network functions, that undergoing is fed back directly to the sales team. Not through a manager. Not through a quarterly report. Through a direct, human correspondence between the people doing the actual work.
Suddenly, the sales representative understands: “If I document this requirement poorly during the handover, the production team loses three days.” The process chain becomes transparent because the people actually doing the work are corresponding directly with each other, rather than through a managerial proxy.
2. Handoffs as Moments of “Undergoing”
In most organizations, a process handoff is treated as the end of one team’s responsibility and the beginning of another’s. Sales closes the deal, throws the contract over the wall, and moves on to the next lead. The act of handing off is pure doing: I did my part, now it’s your problem.
This is precisely where silos become lethal.
In the Fractal Company, a handoff is not the end of a doing. It is the beginning of an undergoing. A handoff is the moment where one team must absorb the reality of the next team in the chain.
Important literature has found and described the concept of Boundary Objects—artifacts, documents, or standards that sit at the intersection of different teams and allow them to collaborate without needing to understand every detail of each other’s world. A well-designed handoff document is a Boundary Object. It is robust enough to carry essential information (specs, deadlines, customer context), but plastic enough to be interpreted and adapted by the receiving team according to their local needs.
To design this object correctly, a team member must step out of their bubble and genuinely undergo what the next team in the chain actually needs to succeed. They cannot build a good handoff if they do not understand the overall system. This forces what I call process undergoing—the deliberate act of absorbing the downstream consequences of your upstream actions.
Consider what happens when a developer hands a feature to the QA team. If the developer treats the handoff as pure doing—”I wrote the code, here it is”—the QA team will spend hours trying to understand undocumented edge cases. But if the developer first undergoes the QA perspective—if they sit with a tester for even thirty minutes and absorb how their code is actually experienced on the receiving end—the handoff document changes fundamentally. It becomes richer, more precise, more useful. The developer’s doing in the next sprint is now shaped by what they have undergone.
This is how silos dissolve: not through process diagrams, but through the repeated rhythm of acting, absorbing the response, and acting again with greater awareness.
3. Expanding the Soft KPIs: The Systemic Perspective
As established in Part I, Fractal Teams use Soft KPIs to measure impact, not just activity. To prevent silo thinking, we must expand these questions beyond the team’s own boundaries. The Performance Scout doesn’t just ask, “Did our team make a real impact today?”
They add systemic questions to the team’s reflection:
“Did we make the next team’s job easier or harder today?”
“Which unnecessary step in the overall company process did we uncover this week?”
“Have we understood the root cause of a delay that happened three steps down the line?”
These questions are not abstract management theory. They are structured invitations to undergo the broader system. When a team asks, “Did we make the next team’s job harder?”—they are forcing themselves to absorb the downstream consequences of their upstream actions. They are stepping into the reality of a colleague they may never meet face-to-face, and allowing that reality to reshape how they work tomorrow.
Thinking about the overall process is no longer a coincidence or something reserved for executives; it becomes a structured, recurring habit for everyone. The weekly standup, moderated by the Meeting Host, becomes the rhythm that enforces this systemic doing-undergoing cycle.
4. Process Immersion Through Rotation
Because the four fractal roles are not full-time jobs and can rotate, the concept of rotation can also be applied across the process chain itself. Imagine if, once a quarter, a team member shadows the upstream or downstream team for half a day. Not to manage them. Not to audit them. To undergo their reality.
This is not simply “process empathy”—a term that risks reducing the experience to a cognitive exercise, as if understanding a colleague’s frustration were merely a matter of imagination. True process immersion is embodied. It is the developer sitting in the customer support queue, feeling the frustration of a user whose feature doesn’t work. It is the sales representative standing in the warehouse, absorbing the physical reality of what “rush delivery” actually means for the people who have to execute it.
This creates radical systemic awareness. Suddenly, the software developer understands the frustration of the customer support agent, and the operational worker understands the hurdles of the sales team. They see the whole board—not because someone drew them a diagram, but because they inhabited a different position in the process chain and allowed it to change how they perceive their own work.
In the language of creativity research, this is what Vlad Glăveanu calls repositioning: the act of physically, socially, or symbolically moving yourself into a different vantage point so that you perceive possibilities—affordances—that were invisible from your original position. In the Fractal Company, process rotation is not a soft team-building exercise. It is a structured mechanism for systemic repositioning.
The Ultimate Goal: An Organization That Responds Together
When team members understand the entire process chain through direct correspondence—through the repeated rhythm of acting, absorbing, and acting again—they stop just executing tasks and start co-designing the system. They become active participants in continuous improvement because they finally perceive how the gears interlock.
A truly Fractal Cell company doesn’t just make individual teams smarter. It weaves those teams together into a single, responsive organism. The lateral networks carry the signal. The handoff documents carry the context. The systemic KPIs carry the reflection. And the rotation carries the embodied understanding that no diagram, no process map, and no middle manager could ever transmit.
“You cannot optimize a complex system by managing its parts in isolation. True organizational intelligence emerges when every cell corresponds with the whole.”
This article is inspired by the upcoming book “Creativity in Entrepreneurship and Innovation — Reading Forward” (coming soon, by Harald Leibinger).
Disclaimer: This manifesto is an independent concept on organizational design, developed entirely in my personal time and published in a private capacity (© Harald Leibinger, 2026)