The Real Reason Your Team Won't Collaborate (Hint: It's Not the Org Chart)

TL;DR: Collaboration problems often get blamed on org charts and departmental silos, but changing the structure doesn’t necessarily change what happens between people. Nicole Hollar, behavior change keynote speaker and coach, looks at how fear, unclear ownership, and ego can undermine collaboration—and why restructuring alone won’t fix a team whose members don’t feel safe being wrong in front of one another.

Every few months, a new article makes the rounds explaining that companies fail at collaboration because of structural walls: functional silos, sequential handoffs, teams that only show up once it's "their turn." The fix, supposedly, is cross-functional teams that work together from day one instead of tossing work over a fence.

I don't hate that idea. Structural fixes can genuinely help. But I've sat in plenty of cross-functional teams that were structured beautifully on paper and still couldn't collaborate their way out of a wet paper bag. So clearly the org chart isn't the whole story.

You can put people in the same room and still not get collaboration

If structure were the real fix, every reorganized, flattened, cross-functionally blended team would suddenly start collaborating well. That's not what happens. What usually happens is you get the same behaviors — withholding information, waiting to be told what to do, protecting turf — just now happening in the same Slack channel instead of across departments.

That tells you the wall was never really made of org-chart lines. It was made of behavior. And behavior doesn't dissolve just because you moved the furniture.

Three things often driving the "collaboration problem" that have nothing to do with structure

1. Fear of being wrong in front of people who matter. Collaboration requires floating half-formed ideas before they're polished. If your team has learned that half-formed ideas get mocked, dismissed, or quietly held against them later, they will protect themselves by saying less regardless of how the seating chart is arranged.
2. Unclear ownership. When nobody knows who's accountable for a decision, people default to doing only the piece they're sure is theirs, and nothing else. That's not disengagement that's self-protection in the absence of clarity. Ambiguity about ownership creates silence faster than any org chart ever could.
3. Ego dressed up as expertise. Some collaboration failures are simpler than they look; someone doesn't want to share credit, doesn't want their idea challenged, or genuinely believes their function's judgment outranks everyone else's in the room. That's not a structural problem. That's a person who hasn't examined what they're protecting.

Why leaders reach for the structural explanation first

Restructuring is easier to talk about than confronting the emotional reality underneath a team's dysfunction. It's much more comfortable to redesign a chart than to have a direct conversation with someone about why they shut down every idea that isn't theirs. Structure is a lever you can pull without ever having an uncomfortable conversation. That's exactly why it gets reached for first, and why it often underdelivers.

What needs attention

If you want a team that genuinely collaborates, structure can create the opportunity, but someone still has to build the safety, clarity, and self-awareness that make people willing to use it. That's slower work. It's also the work that moves the needle.

Listen to the discussion about this topic on The OWN IT Podcast

Questions for Reflection

1. If your team was restructured tomorrow into the "perfect" cross-functional setup, do you honestly believe collaboration would improve, or would the same behaviors just relocate?
2. Where on your team is ownership genuinely unclear, versus clear but being ignored?
3. Is there a version of "protecting my expertise" that you've been calling collaboration, when it's more like control?

Frequently Asked Questions

Does restructuring teams ever actually fix collaboration problems?
It can help when the barrier truly is structural like sequential handoffs that exclude people from early input. But restructuring without addressing trust, safety, and clarity of ownership tends to just relocate the same behaviors into a new configuration.

How do you fix a lack of psychological safety on a team?
It starts with leaders modeling that being wrong or incomplete in front of the group has no real cost, which usually means changing how mistakes and half-formed ideas get responded to in real time, not just saying "we value honesty" in a meeting.

What's the difference between healthy expertise and ego getting in the way of collaboration?
Healthy expertise invites challenges and treats other perspectives as useful information. Ego-driven expertise treats challenge as a threat and dismisses input from people outside the "right" function. The tell is usually how someone reacts when they're wrong in front of others.