How systems drive (or derail) team behavior

Not all workplace drama is personal.

When teams fall apart, we love to blame personalities. But what if the real culprit is invisible and fixable?

In fact, most of it isn’t.

After more than two decades working in tech—leading teams, advising founders, and coaching professionals across industries—I’ve come to a simple conclusion: most team conflicts aren’t rooted in personality clashes or a lack of emotional intelligence.

They’re usually the result of broken or unclear processes.

We tend to assume that if people are arguing or pulling in different directions, there must be a personal issue. Maybe they don’t like each other. Maybe someone is being difficult. But in reality, what’s often going wrong is far less personal and far more structural.

The System Shapes the Behavior

Think back to the last time you saw conflict between two team members or departments. Did they really have opposing values or personalities? Or were they working within a system that made collaboration hard, miscommunication easy, and assumptions inevitable?

Time and again, I’ve seen good people struggle—not because they’re unwilling, but because the system around them doesn’t support alignment. I’ve seen high-performing individuals burn out or turn cynical simply because the processes they rely on are outdated, unclear, or completely missing.

When people aren’t clear on what they’re trying to achieve together, or how their roles connect, tension builds. When deadlines are imposed without context, trust erodes. And when communication is inconsistent or filtered through too many tools, misunderstandings pile up.

These aren’t character flaws. These are system flaws.

A Common Scenario: Engineering Meets Product

One of the clearest examples I see over and over again is the tension between engineering managers and product managers. They’re supposed to be close collaborators—two sides of the same coin. One focuses on customer value and business goals. The other ensures technical excellence and feasibility.

Yet in many companies, especially growing startups or under-structured environments, they operate more like parallel lines than intersecting teams.

There’s no regular one-on-ones. Priorities don’t align. Roadmaps are shared late or not at all. Engineers feel like they’re constantly reacting. Product managers feel like they’re not being heard. The tension builds—not out of disrespect, but out of misalignment.

I’ve sat in retros where the frustration in the room was palpable. But when we paused to map out the process and communication flow, the root problem became obvious: they weren’t speaking the same language, and there were no intentional moments built into the calendar to bridge the gap.

Add to this the pressure of deadlines, limited resourcing, and shifting business needs, and you’ve got a perfect storm.

The False Comfort of Communication Tools

We live in a time of endless communication tools. Slack, Zoom, Teams, Notion, Jira, Trello, Confluence. The list goes on.

And yet, communication has never felt more fragmented.

These tools were supposed to make things easier. In some ways, they do. But too often, they give us the illusion of communication while reducing the actual quality of it. Slack messages replace real conversations. Ticket comments become the battleground for blame. Feedback is delayed or diluted.

What’s worse, asynchronous tools often leave too much room for interpretation—and when there’s a lack of trust or familiarity, people fill in the blanks with their own assumptions. That’s where bias creeps in. That’s when we start thinking, “They just don’t care,” or “They always ignore what we say,” when in reality, no one sat down to clarify expectations in the first place.

I once worked with a set of teams who hadn’t met in real-time for months. They were exchanging dozens of tickets and updates each week, but they were growing more frustrated with each other. It took just one 45-minute sync session to clear up misunderstandings that had been lingering for weeks. After that, they set up recurring check-ins—and the tension dropped dramatically.

Technology should be an aid to communication, not a substitute for it.

Process is Not Bureaucracy

One of the biggest misconceptions is that processes create rigidity or slow things down. But good processes do the opposite—they create clarity, autonomy, and speed.

Processes don’t have to be long documents or flowcharts. They can be simple agreements. For example:

• Every new feature starts with a quick scope review between Product and Engineering.

• Every Friday, each squad shares what’s shipped, what’s blocked, and what’s next.

• Every cross-functional project kicks off with a shared success metric and owner.

These are not rules for the sake of rules. They are agreements that help people operate with less friction and more trust. They create a shared language and structure, especially useful when the pressure is on or when new people join.

Process is how culture scales. And culture is what allows people to collaborate at speed, not chaos.

What to Do Instead

If you're dealing with team conflict—or want to avoid it altogether—start by looking at the environment, not the personalities.

Here are five pragmatic steps you can take right now:

1. Establish recurring cross-functional check-ins
   Don’t wait for conflict. Make space for collaboration before it’s needed. These can be short and regular. Even 15 minutes a week is enough to surface blockers and align.

2. Document your shared processes
   They don’t need to be fancy. Just clear enough that someone new to the team can understand how work moves forward and who is responsible.

3. Clarify ownership early
   Most conflicts arise from confusion about who’s accountable. Create simple RACI models (Responsible, Accountable, Consulted, Informed) or use whatever helps your team understand roles.

4. Measure what matters together
   Align on shared outcomes, not just activities. If Engineering is optimizing for stability and Product for speed, they’ll always feel at odds unless there’s a shared success definition.

5. Create space for reflection
   Build retros, feedback sessions, and postmortems into your culture. But make sure they’re safe, blame-free, and actually lead to action.

A Reality Check: The Data

McKinsey research shows that 75% of cross-functional teams are dysfunctional, with the top problems being unclear roles, lack of accountability, and poor communication. That’s a systems issue.

Not surprisingly, teams that have clear structures and regular communication rituals are far more likely to succeed.

In my coaching work, I’ve found that once a team agrees on how they work—not just what they’re working on—everything else improves: delivery, morale, even innovation.

Final Thought

The next time you sense tension between two people or teams, pause before assigning blame. Instead, ask:

"Is this really a people issue—or is the process failing them?"

In most cases, the process is the problem. And the good news? You can fix that.

With intention, communication, and a willingness to adjust, you can reduce conflict and create an environment where collaboration isn’t just possible—it’s natural.