When Programs Stop Talking to Each Other, You Don't Have a Collaboration Problem. You Have an Incentive Problem.

Silos aren't a culture failure. They're a rational response to a system that rewards protection over transparency.

When programs stop sharing information, the diagnosis is almost always cultural.

Lack of trust. Poor communication. Not enough cross-functional connection. The solution is usually a retreat, a new channel, a collaboration initiative with an optimistic name that quietly loses momentum within a quarter.

The dysfunction remains. Because the diagnosis was wrong.

What's actually happening

People protect their lane when the system gives them no structural reason not to.

This is not a motivation failure. It is not indifference to the mission. In most cases it is the opposite; people who care deeply about their work, who have built something meaningful, who are operating in an environment where resources are constrained, visibility is limited, and the consequences of exposure (fault finding, duplication of efforts etc) feel higher than the rewards of openness.

Assume best intent: when transparency carries risk and protection carries reward, discretion is the rational choice. The incentive structure is producing exactly the behavior it was designed to produce. The organization just hasn't admitted it designed things that way, even if it’s doing what it always has done. 

The donor funding accelerant

In mission-driven organizations, restricted funding makes this structural dynamic explicit.

When a donor funds Program A specifically, Program A has concrete reasons to protect its resources, its data, its relationships, and its results — even from Program B that shares the same mission and the same building. The org chart says one organization. The funding architecture says several competing ones.

This isn't unique to external funding. It surfaces anywhere that headcount, budget, credit, and organizational visibility flow to programs rather than to collective outcomes. When the measurement system rewards individual program performance and has no mechanism for valuing what programs contribute to each other, competition is not a cultural problem to be solved. It is a structural outcome to be expected.

What gets lost

The cost of this dynamic is almost always underestimated because what's lost doesn't show up on any report.

It shows up in the program doing extraordinary work that no one else in the organization knows about. The team that could have championed that work to a donor, a partner, a board member — if they'd known it existed. The colleague in another department whose network, expertise, or relationships would have accelerated your work by months, but the connection was never made because the work was never shared.

Transparency isn't just operationally efficient. It is how organizations build internal allies. It is how individual effort becomes collective momentum. It is how the people doing the work find others who believe in it; who can amplify it, connect it to resources, carry it into rooms it would never otherwise reach.

When programs don't share what they're doing, they don't just lose efficiency. They lose the relational infrastructure that makes mission-driven work sustainable. They deprive their own people of advocates. They mistake insulation for strength, when openness would have built something stronger.

The information flow problem

Underneath the incentive structure is an expectation problem.

In most siloed organizations, no one ever set clear norms for what information flows where, at what cadence, to whom, and why. Transparency was assumed to be a cultural value rather than a designed expectation. When the expectation was never set and the infrastructure was never built, people filled the gap with what felt safe. Protection. Discretion. Minimum required disclosure.

This is not a character failure. It is what happens when organizations treat information sharing as a matter of goodwill rather than organizational architecture.

The fix

Collaboration cannot be mandated. But the conditions for it can be designed.

That means shared metrics with real teeth; measures that cross program lines and make collective outcomes visible alongside individual ones. It means funding conversations that reward integration. It means leadership that models transparency rather than hoarding it. And it means building deliberate structures for how work gets seen across the organization, not another meeting, but streamlined architecture that makes it easy.

Most of all it means understanding what transparency actually offers: not exposure, but amplification. Not vulnerability, but alliance.

The programs that share what they're doing don't just build goodwill. They build an organization that knows what it is capable of.