When the Human Layer Becomes the Bottleneck

It Usually Starts as Friction

Over the last year, I’ve been working as Product Owner across multiple TYPO3 teams in a cross-company, open-source environment. No clean org charts. No single line of authority. Just shared goals, strong opinions, and a lot of informal dynamics. 

What I learned—the hard way—is that teams rarely break all at once. The breakdown starts much earlier, and much more quietly. Before anything visibly collapses, you start to notice three things: 

Slower decisions: You’re doing more alignment, not less. But somehow things are still getting less clear. 
Recurring debates: The same topics keep coming back. Not because they’re complex, but because they’re never really resolved. 
Fragile delivery: Progress depends more and more on coordination. Trust erodes. Momentum stalls. 

That’s not a technical problem. It’s a social one.

The Challenge Is Socially Organized

As organisations grow more complex, something else grows with them: the number of relationships that need to be coordinated. More teams, more stakeholders, more dependencies, more interfaces.

And with that, ownership often becomes less clear, communication more fragile, and informal power more relevant.

I use the open-source world as a lens here—not as a model to copy, but because it makes certain dynamics more visible. Formal hierarchy is weaker. Informal influence matters more. And people often attach their identity to the product. That combination exposes patterns many organisations face, yet in a more subtle way.

When I described this talk to a friend working in IT for a large company, his reaction was: “Honestly, we see most of these symptoms too.”

It’s Not Just “Men”

The easy answer when you’re in a male-dominated tech environment—and let’s be honest, a lot of us are—is to say: “It’s a gender thing.” And yes, some patterns become very visible in those spaces: status behaviour, gatekeeping or the need to be right.

But that’s still too simple.

The real issue isn’t men. It’s what happens when unmet needs, insecurity, and unclear structures come together. Work becomes more than work. It becomes a place where people seek recognition, belonging, and identity. And when that happens without being named or structured, it gets negotiated informally—through control, correction, and conflict.

I’m borrowing Maslow’s hierarchy here not as a perfect model, but as a useful reminder: beneath most workplace conflict, there are unmet needs. 
Safety (who decides, and does that feel fair?), 
Belonging (am I actually part of this group?), 
Recognition (does my contribution count, or only my status?).

Unmet needs don’t disappear. They just get expressed sideways.

Structure Helps—But Not Enough

Once you see the pattern, the instinct is to add structure. Clearer roles. Better decision rights. More explicit ownership. And that absolutely helps—a lot of conflicts get worse simply because authority stays unclear.

But structure has its limits. It can clarify responsibility and reduce informal power. However, it cannot remove insecurity, stabilise self-worth, or force self-awareness where it’s missing.

You can’t organize away human insecurity. But you can stop it from defining the team.

What Leadership Needs to Add

If structure isn’t enough on its own, then leadership has to do more than organize work. It also has to shape the conditions in which work happens.

Presence means something different. It means staying grounded when the room is tense. Reading what’s actually happening—not just the agenda items, but the emotional temperature. Creating orientation without adding more noise.

We talk a lot about AI these days. But in many teams, the real bottleneck isn’t artificial intelligence. It’s emotional intelligence. The ability to notice tension, read people, create orientation, and respond without escalating.

For me, emotional intelligence in leadership means:

Awareness — noticing what’s actually happening in the room, not just what’s on the agenda.
Regulation — not responding to every tension with more control, speed, or authority.
Presence — staying grounded and creating clarity without adding emotional noise.
Relational skill — combining clarity with connection. Naming things, setting limits, giving feedback, without unnecessarily losing people in the process.

This isn’t about being nice. It’s about staying human and approaching complex situations with clarity.

Four Levers You Can Use

If you only take one practical thing away from this blog post, may it be that leadership under complexity needs four levers. These four levers don’t solve every problem. But they reduce the power dysfunction has over the team.

1. Clarity. Who decides what? Where does ownership sit? How do we escalate? Many conflicts become hard not because people are difficult, but because responsibility stays unclear.
2. Visibility. Not only the loudest voices should count. Good leadership makes the work that actually fosters collaboration visible: coordination, documentation, translation between perspectives, and the enabling work that rarely gets credit.
3. Boundaries. Not every behaviour should become part of team culture. Gatekeeping, dominance, and dismissive communication don’t disappear on their own. If they’re not contained, they eventually define the space.
4. Development. People aren’t static. Create room for feedback and learning—without being naive about the speed at which change actually ends up happening.

Leadership changes the environment

I want to end with something that’s become something of a personal leadership touchstone for me: Ted Lasso.

For those who haven’t seen it—Ted Lasso is an American football coach who ends up leading an English soccer team, despite not being the obvious technical expert for the job. What makes him interesting isn’t tactics. It’s how he leads people.

He sees the person behind the behaviour. He combines care with accountability. He creates belonging on purpose.
What he changes isn’t the people themselves—it’s the environment around them. The tone, the trust, the sense that contributions matter.

That’s the real takeaway: you may not fix the people, but you can change the pattern.

Lead less through control. Lead more through presence—the ability to stay grounded under pressure. Through clarity, so that uncertainty doesn’t automatically turn into conflict. Through trust, so that collaboration doesn’t collapse into control. Through boundaries, so that destructive behaviours don’t set the tone.

Leadership may not solve the whole problem. But it can stop dysfunction from defining the team.