The Structural Solution: Communities of Practice + Systems Convening
TL;DR: Silos aren't a behavior problem; they are a design flaw. You cannot "culture" your way out of a broken axle. To dissolve silos, you need two things: Communities of Practice (the infrastructure for learning) and Systems Convening (the leadership that connects that learning to strategy).
Stop Telling People to "Collaborate More"
In Part 1, we established that silos are systems problems, not people problems. In Part 2, we looked at why the most common "fixes"—task forces, more meetings, and new software—consistently fail.
Now, let's talk about what actually works. Not as a temporary patch, but as a permanent structural shift.
The core insight: if silos are created by systems designed for vertical efficiency, the solution isn't to work harder against those systems. It's to build different ones, designed for horizontal connection.
That requires two things working together: a container where shared practice can deepen, and leadership that ensures that practice changes the wider system.
1. Communities of Practice: The Infrastructure
A Community of Practice (CoP) isn't just a Slack channel or a standing meeting. As Etienne and Beverly Wenger-Trayner define it, a CoP is a group of people who share a concern or passion for something they do, and who learn how to do it better as they interact regularly.
That last clause is doing more work than it looks like.
The reason CoPs succeed where task forces fail isn't that the people in them are nicer or more committed. It's the time horizon. A task force dissolves before trust forms. A CoP persists long enough for people to reveal what they actually know — the unwritten heuristics, the workarounds, the judgment calls that never make it into a process document.
Once that tacit knowledge starts moving, three things change:
The shared vocabulary across departments stops being jargon and starts being a working language.
Invisible duplication surfaces, and teams stop reinventing the wheel.
Help becomes reciprocal rather than transactional — people contribute today because they trust the community will contribute tomorrow.
None of this is achievable on a six-week timeline. It's why patches keep failing and why infrastructure works.
What this looks like in practice
A few years ago, we worked with the New York Hall of Science on a problem familiar to most museums: educators were doing extraordinary work, but most of what they knew lived in their own heads. Workshops happened. Trainings came and went. But the knowledge — how to read a room, when to abandon a script, what works for a particular school group on a Tuesday afternoon — wasn't moving between people. Each educator was, in effect, their own silo.
The instinct in that situation is to schedule more training. We pushed for something different: a community of practice designed as ongoing infrastructure, not as a program with a start and end date. Facilitators were positioned as conveners rather than content deliverers. Participation was structured around the rhythms of the educators' actual work — reflection, peer exchange, shared inquiry — rather than bolted on top of it.
What changed wasn't dramatic in any single moment. It was that tacit knowledge started moving. Educators began naming the heuristics they'd been operating on without language for. Newer staff had somewhere to go besides the most senior person on shift. Practice became visible enough to build on.
The lesson we took from that work: a community of practice isn't a program you launch. It's a piece of infrastructure you design, and then keep tending. And the tending matters as much as the community itself — without someone holding the shape of the thing, the easy default is back to isolated practice with occasional training events on top.
That's where the second piece comes in.
2. Systems Convening: The Leadership Layer
Communities of Practice can become their own silos if no one is tending to how they connect to the wider organization. This is where Systems Convening comes in.
Systems Conveners, as the Wenger-Trayners describe them, are leaders who don't just operate across boundaries — they actively reshape the landscape those boundaries define. A good cross-functional leader bridges existing groups. A Systems Convener changes which groups exist, how they relate, and where the productive friction lives. They're working on the configuration, not just the conversation.
In practice, three capacities distinguish them:
Boundary Legitimacy. They speak "Clinical," "Finance," and "Operations" fluently enough that each group recognizes its own concerns in their framing. Without this, they get dismissed as outsiders the moment a hard tradeoff appears.
Systems Awareness. They can see where knowledge currently lives, where it needs to flow, and — critically — which connections are missing rather than merely weak. They're diagnosing the landscape, not just the relationships within it.
Complexity Agency. They engage with messy, undefined problems rather than waiting for executive clarity. They're comfortable working in the space before there's a mandate, because that's usually where the real reconfiguration happens.
The pairing matters because CoPs without convening tend to drift inward — they deepen practice but don't reshape the system around them. Convening without CoPs has nowhere durable to land. The two functions are reciprocal: communities generate the practice, conveners ensure that practice changes the landscape.
Five Strategic Shifts for Leaders
If you're ready to move from patches to permanent structures, start here:
Design for continuity, not one-offs. Stop asking "How do we solve this specific cross-functional problem?" Start asking "Where does learning need to live between our initiatives?"
Invest in community, not just meetings. A task force ends when the project does. A CoP provides the long-term organizational memory that prevents the same mistakes from happening twice.
Build convening capacity internally. Identify your bridge-builders — the people others naturally go to for help. Give them the formal mandate, training, and resources to act as Systems Conveners.
Make contribution visible. Create recognition systems that value those who share knowledge across boundaries. If "helping another department" isn't rewarded, it won't happen.
Treat silos as signals. When a silo appears, don't blame the people. Ask: "What is this telling us about our infrastructure? Where is the connection broken?"
The Bottom Line
Breaking down silos isn't about getting people to "play nice." It's about designing a system where collaboration is the path of least resistance.
When you invest in the right structures — communities, convening, and shared learning — alignment stops being an aspirational goal and starts becoming an operational reality.
Is your organization ready to build the infrastructure?
At Community Works Collective, we specialize in designing and sustaining these systems for mission-driven organizations. We don't just tell you what to do; we help you build the structures that make silos obsolete.
[Click here to book a strategy audit with our team.]
This is Part 3 of a three-part series on rethinking organizational silos.
I'd love to hear from you: of the five shifts above, which feels most urgent in your organization right now?