Why Silos Persist (Even When Everyone Wants Them Gone)
TL;DR
Systems over People: Silos aren't caused by unwilling people—they're caused by systems designed for vertical efficiency, not horizontal connection.
The Paradox: Organizations are more technologically connected than ever, yet operationally more fragmented.
The Cost: The impact is measurable—up to 35% productivity loss and millions in data quality issues.
The Fix: It isn't more meetings; it's redesigning how knowledge lives and moves.
⸻
If you've led a mission-driven organization for any length of time, you've probably said some version of this: "We need to break down silos."
Maybe it surfaced during strategic planning. Maybe after a project fell through the cracks between departments. Or maybe when you realized two teams were solving the same problem—without knowing the other existed.
The frustration is real and nearly universal. But after years of working with nonprofits, foundations, universities, and healthcare systems, we've learned a hard truth:
Silos are rarely a people problem. They are almost always a systems problem.
Until we understand why silos form—not just that they exist—we'll keep applying temporary solutions that don't stick.
The Paradox: More Connection, More Fragmentation
We live in the most technologically integrated era in history. Most organizations now have shared drives, Slack channels, and cross-functional committees. And yet, operational fragmentation is increasing. Why?
Because there's a difference between connectedness and connection.
Technology connects nodes—people, systems, and databases. But it doesn't automatically connect meaning. Access to a shared drive doesn't equal shared understanding. A Slack channel doesn't guarantee that tacit knowledge—the unwritten "know-how" that lives in people's heads—will transfer.
What Silos Actually Look Like
Silos don't usually look dramatic; they look ordinary. They show up as:
Parallel Play Different teams working on similar challenges without awareness. (e.g., Two departments purchasing the same software subscription independently.)
Trapped Intelligence Critical knowledge living in inboxes or in the heads of long-tenured staff. (e.g., The only person who knows how to navigate a critical funder relationship is retiring next month.)
Organizational Amnesia The phrase "We tried that before," with no shared record of why it failed or what was learned. (e.g., Three different pilot programs tested similar approaches over five years with no documentation of results.)
Performative Meetings Cross-functional check-ins that feel more like "status reporting" than actual collaboration.
Strategic Drift Frontline staff who care deeply about the mission but can't see how their daily work connects to the department next door.
The Real Cost of Fragmentation
Silos are often treated as an inconvenience—something that would be "nice to fix." The data tells a different story.
Research shows that organizational silos can reduce productivity by up to 35%. For a mid-sized nonprofit, that is the equivalent of losing two to three full-time staff members to organizational friction.
The impact is staggering:
Financial Loss: Gartner estimates that poor data quality—often caused by siloed systems—costs organizations an average of $12.9 million per year.
Innovation Stagnation: Breakthrough ideas emerge at the boundaries between disciplines. When those boundaries become rigid walls, cross-pollination stops.
Mathematically, the true capacity of your organization (C) is often its theoretical potential (P) minus the friction (F) created by these gaps:
C=P−F
Why "It's a People Problem" Doesn't Hold Up
When silos become visible, the default diagnosis is often: "People need to communicate better." This framing places the burden on individuals. But what looks like "hoarding information" is usually a rational response to a broken system.
Consider these systemic barriers:
Misaligned Incentives When teams are measured on conflicting goals, collaboration becomes "irrational."
Information Friction If sharing requires navigating three different software logins and an approval layer, people default to keeping things local.
Lack of Reciprocity If past sharing wasn't valued or utilized, keeping knowledge close becomes a survival tactic.
The problem isn't that people won't connect. It's that the system doesn't allow connection to happen naturally.
The Legacy We're Working Against
Most modern organizations are still running on an operating system designed for the industrial era. Scientific management optimized for vertical efficiency: specialization, hierarchy, and control.
But today's challenges—whether homelessness, student success, or coordinated care—are fundamentally interdependent. They require knowledge to flow horizontally. Silos are what happen when 20th-century structures collide with 21st-century complexity.
What This Means for Leaders
If silos are a systems problem, treating them as a people problem is demoralizing. It asks committed staff to overcome structural friction through sheer willpower.
Instead, ask:
Where does learning need to live between our initiatives?
What knowledge is currently invisible to the rest of the team?
How do we make collaboration the default, not the exception?
What's Next?
In our next post, we'll look at why the most common "silo-busting" efforts—like task forces and new tools—tend to fail, and what those failures reveal about what actually works.
⸻
This is Part 1 of a three-part series on rethinking organizational silos.
Does your organization suffer from "Organizational Amnesia" or "Parallel Play"? We'd love to hear which of these resonates most with your current challenges. Grab some time to chat here to share your experience.