Read Time:
The Siloed Leader usually isn’t protecting turf. They’re protecting something harder to name.
The common assumption about siloed leaders is that they’re “politically” motivated. Guarding resources. Protecting headcount. Playing an institutional long game.
Sometimes that’s accurate. But more often, the Siloed Leader isn’t calculating, they’re cautious. And the thing they’re protecting isn’t always obvious, even to them.
Understanding which root cause is driving the pattern is what makes change possible. Here are the three we see most often:
Distrust of others’ standards. The Critical Thinker leader has usually built a track record through rigorous control of quality. Collaboration means working alongside people whose standards they can’t verify. Sharing data or work product means it may be used, interpreted, or cited in ways they wouldn’t choose.
Their response is to keep things close. Not as a power move, but as a quality control measure. In the leader’s internal logic, this is responsible. What they haven’t examined is whether that logic still holds—or whether it ever fully did.
Fear of exposure. Some siloed leaders have learned, through experience, that visibility is risk. Sharing work before it’s finished invites criticism. Participating in cross-unit initiatives means being associated with outcomes they don’t control. A failed collaboration reflects poorly even on the partner who brought the most.
The silo therefore becomes a defensive perimeter. A way to ensure that what carries their name is something they can fully stand behind.
Institutional reinforcement. Higher education structures often reward unit-level performance over institutional contribution. Departmental budgets, divisional accountability, tenure and promotion criteria, annual reviews: Many of these are calibrated to what happens inside the unit, not across it. Siloed leaders have frequently developed these patterns in environments that made siloing rational. However, the behavior persisted when the environment changed, often because no one named the shift.
Members must be logged in to view this content.