Your Team Doesn’t Have a Communication Problem. It Has an Operating System Problem.

“We need to improve communication.”

It is one of those team diagnoses that can mean almost anything. People talk too little. They talk too much. Difficult things are not said. They are said in the wrong place. Information gets lost between functions. Decisions remain vague. The manager is copied into every thread. Nobody is quite sure who gets the final call.

Then the development plan says: communication skills.

And everyone goes to a workshop.

What if the communication is behaving exactly as the system trained it to?

Imagine a team where every difficult decision eventually has to go through the manager. People quickly learn not to decide too much on their own. A few months later, the organisation complains that the team lacks ownership.

Or three functions own one shared outcome, but each is measured against a different KPI. Each team optimises its own part, the end-to-end result gets worse, and someone schedules a collaboration workshop.

Or consider a team where challenge is officially encouraged, but the last person who openly questioned a decision became known as “difficult”. Meetings become quieter over time. The silence may even look like improved alignment.

These may not be communication problems. They may be perfectly rational behaviours inside the system the team is operating.

Every team has an operating system

I do not mean Teams, Slack or Jira.

I mean the invisible rules underneath the work.

Who really makes the decision when the official process says “we decide together”? What happens when someone says no? Does asking for help build trust or reduce status? Which mistakes are safe, and which ones become public lessons? Does the person who owns the decision on the slide actually have authority in practice?

Some of these rules are explicit. The most influential ones often are not.

A team can therefore have beautifully documented processes and still operate according to a completely different social logic.

“We have a RACI” does not mean we have clarity

On paper, Anna is Accountable, Marta is Responsible and Peter is Consulted.

In practice, Anna knows the project will not move if Peter disagrees. Marta checks every decision with the manager because the last mistake was handled publicly. Peter may officially be “consulted”, but everyone knows his approval is effectively required.

The roles are clear in the artefact. The social system tells a different story.

Team coaching becomes interested in that second layer. Not just what the team says its rules are, but what patterns it repeatedly creates and what keeps those patterns alive.

A team is not the sum of individual skills

You can have five excellent communicators and a team that cannot discuss the thing that matters most. You can have individually high-performing people who produce a weak collective result. You can also have very different personalities who have built a healthy way to disagree, decide and learn.

That is why team coaching is not several one-to-one coaching sessions happening at the same time.

The client is the team as a whole: its relationships, agreements, patterns, goals, tensions and responses as a system. The International Coaching Federation’s Team Coaching Competencies make this distinction explicit by addressing the unique dynamics of coaching a team rather than simply coaching individuals within it.

The question changes from “Who is the problem?” to “What pattern are we creating together, and what keeps reproducing it?”

Handovers are where the system reveals itself

I have a particular interest in handovers because tech and data environments expose them quickly.

Product hands over to development. Development to testing. Data engineering to BI. Project delivery to support. One market to another.

When tension repeatedly appears at the same boundary, “they need to communicate better” is an easy conclusion.

Maybe they do. But it is worth asking whether both sides share the same definition of done, whether one is optimising for speed while the other is optimising for stability, whether risk travels with the work, and whether the receiving team can say “this is not ready” without triggering a political escalation.

That is more than active listening.

It is the design of collaboration.

Conflict may be part of the job

Some tensions should not be removed. Speed versus quality. Sales versus delivery. Local versus global. Innovation versus governance.

The goal is not to make the tension disappear. It is to build a team capable of using the tension to make better decisions.

If every hard question is escalated to the manager, the manager becomes the team’s central processor. If the highest-status person always wins, other perspectives eventually stop appearing. If conflict is avoided, the decision still gets made — just later, in a private conversation after the meeting.

Team coaching is not an atmosphere repair service

It may improve communication. It may strengthen trust. It may help a team work through conflict.

But I would not start with the assumption that the team simply needs to be nicer to each other.

I would rather look at how decisions are made, where responsibility disappears, which topics cannot be discussed, what happens under pressure and whether the team’s current way of working still supports the outcome it exists to create.

Sometimes a team does not need another communication workshop.

It needs to see its own operating system clearly enough to decide what to change.

You can read more about how I approach this work on the Team Coaching page.

Source

• ICF Team Coaching Competencies