When 'Fine' Is Not Fine: The Real Causes of Team Communication Problems

There is a word that should put any experienced manager on alert. It is a short word, used constantly, and almost never accurate. That word is fine.

I had a client come in not long ago. Before we had even settled into the session, I asked how he was doing. Fine, he said. We started the work, moved through the opening conversation, and about ten minutes in, I stopped. Something was off. The energy in the room did not match what he was telling me. I said to him, listen, what I am picking up is that you are not entirely fine. There is something there that is taking up space. He paused, then told me there was a personal situation at home, nothing he wanted to go into in detail, but it was sitting on him heavily. He had been carrying it into work all week without fully realising how much it was colouring his thinking.

We did not go into the personal matter in depth. That was not what the session was for, and he was not looking for that. But just naming it changed the atmosphere. The session that followed was one of the more productive ones we had. When people are preoccupied, the preoccupation does not stay neatly on one side of the door. It follows them in. And if no one notices, or no one feels it is appropriate to notice, the work suffers quietly and for longer than it needs to.

I tell that story not as a detour but as an entry point into what team communication problems actually are. They are rarely what they appear to be. They are rarely solved by what they are usually met with.

The Symptom Is Usually Not the Problem

When a team identifies that communication is not working, that observation is almost always correct and almost always incomplete. Poor communication is the visible surface. Underneath it, there is usually something else: a manager who assumes silence signals agreement, roles that are not as clear as everyone assumes, a culture where raising concerns feels politically risky, or people who are carrying something privately that is colouring their engagement.

A pattern I see regularly when working with teams is that the response to communication problems tends to address the surface rather than the source. More meetings are added. A new channel or platform is introduced. People are encouraged to speak up more. None of that is wrong in itself, but it rarely lands because the deeper conditions that are making good communication harder have not been examined. A team does not need more talking. It needs clearer thinking, more honest habits, and managers who are paying the right kind of attention.

The useful question to ask is not only how are we communicating? It is also what is making clear communication harder than it should be?

When Assumptions Fill the Space That Clarity Should Occupy

One of the most consistent findings in research on team performance is that assumptions are extraordinarily expensive. The Chartered Management Institute has repeatedly documented that unclear expectations are among the leading causes of team underperformance in UK workplaces, costing organisations time, morale, and avoidable rework. The figure sounds abstract until you start mapping where the hours actually go in a typical working week.

One thing I have noticed working with professionals across different sectors is that assumptions tend to form most readily in environments where clarity feels unnecessary. Teams that have worked together for a while, or teams where the manager has high confidence in their people, often stop stating things explicitly because it seems obvious. It is not always obvious. One person thinks a piece of work is urgent. Another considers it important but not immediate. A manager expects early escalation when problems arise. A team member reads that as a lack of confidence in their ability to problem-solve independently. Nobody has said anything wrong. Nobody has been careless. They simply have not been explicit enough, and the gap between assumption and agreement does its damage slowly.

The fix here is less about communication style and more about discipline. Effective teams make expectations visible. They are specific about who owns what, what good looks like, when something needs to be raised rather than resolved independently, and what the standard is for a finished piece of work. That kind of clarity is not micromanagement. It is respect for people's time.

The Manager Who Assumes People Know

A common challenge in many workplaces is the assumption that team members already understand exactly what is expected of them. The logic feels reasonable: these are capable adults, experienced professionals, people who have been around long enough to read the situation. But capability does not eliminate the need for clear direction. Experience does not make expectations telepathic.

Early in my career, I worked in an organisation where the manager had a habit that, at the time, seemed almost unremarkable. Every week, without fail, he would come round to the team for a ten-minute conversation about what needed to happen that week. Not a formal briefing, not a set-piece review. Just a direct, unhurried conversation that made the priorities visible and gave people the chance to raise anything that might affect their ability to deliver. Once a month, there was a one-to-one. That was it. The structure was simple. But what it produced was something that a lot of teams never quite achieve: everyone knowing what they were actually supposed to be doing and why it mattered.

The contrast, when I have worked in or with environments that do not have this, is striking. People end up guessing, duplicating, or quietly dropping things they assumed someone else had covered. Conflict arises not because people are difficult but because the work itself has become ambiguous. And the wee detail that makes it worse is that people stop asking for clarification because they do not want to look as though they cannot figure it out for themselves. So the gap persists, and the manager never finds out because everyone appears to be getting on with it.

What good looks like in practice

It does not require elaborate systems. It requires a manager who is consistent. Regular, brief check-ins on priorities. Explicit ownership of tasks and projects, particularly when multiple people are involved and overlap is possible. Clear goals for what needs to be achieved, not just activity. And an environment where asking a clarifying question is treated as good professional practice rather than a sign of inadequacy.

Feedback That Arrives Too Late or Says Too Little

In healthy teams, feedback is a live current. It flows early, it is specific, and it gives people the information they need to adjust before the stakes are high. In struggling teams, it tends to arrive in one of two unhelpful forms: either so softened that it produces no real change, or so delayed that frustration has already calcified into something harder to resolve.

Vague feedback is a particular problem because it masquerades as kindness. Be more proactive. Tighten that up. Take more ownership. These phrases feel honest to the person delivering them and mean almost nothing to the person receiving them. In my experience advising professionals who have been on the receiving end of this kind of feedback, the most common response is not indignation. It is genuine bafflement. They are trying to act on the feedback and simply do not have enough information to know what acting on it would look like.

Strong feedback is anchored in the work, not the person. It describes what was observed, explains why it matters, and is specific about what needs to happen differently next time. That is not harsh. It is actually more respectful than the alternative, which leaves people managing impressions instead of improving performance.

Conflict That Gets Smoothed Over Rather Than Addressed

Many capable professionals are genuinely uncomfortable with conflict. They have good instincts about collaboration, they care about working relationships, and they have usually learned at some point that challenging a colleague or naming a tension carries social risk. So instead, they smooth things over. They lower their standards quietly. They work around a dynamic rather than addressing it. They tell themselves it is fine.

The cost of this accumulates. Resentment builds slowly and then all at once. Trust erodes without anyone making a decision to let it erode. And by the time the issue surfaces, it has become heavier than it needed to be because it has been carried for too long by too many people without being named.

Organisations frequently overlook the extent to which conflict avoidance is a cultural norm rather than an individual failing. If people have learned that direct challenge is unwelcome, that raising concerns leads to being seen as difficult, or that managers do not deal with tension well when it is brought to them, they adapt accordingly. The team looks calm. The undercurrent is anything but. Managers need to do more than handle conflict when it surfaces. They need to model the habit of naming things early, without drama, as a standard part of how the team works together.

The Strengths Gap Most Teams Have Not Named

One area that is often overlooked in conversations about team communication is the role of individual strengths in how people engage at work. People do not communicate differently because some are better at it than others. They communicate differently because they think differently, process information differently, and bring different natural orientations to the way they interact.

One person will process quickly out loud and push the conversation forward with pace and energy. Another will need time to think before responding and will do their clearest thinking away from the group. A third will challenge ideas instinctively, not out of antagonism but out of a genuine drive to stress-test thinking. When those differences are understood within a team, they become assets. When they are not understood, they tend to get misread. The person who pushes pace is labelled impulsive. The person who needs time to think is labelled passive. The natural challenger is labelled difficult.

Working with professionals through a strengths-led process has shown me consistently that many team communication problems are not communication problems at all. They are misunderstanding problems. The friction is not coming from bad intentions or incompetence. It is coming from differences in how people work that have never been named clearly enough to work with. When teams understand how their people are wired, at least some of what looked like conflict reveals itself as something far more manageable.

Where to Start If Team Communication Problems Have Started to Affect Performance

If you are a manager or a professional looking at a team where communication has started to cost you something real, the useful starting point is diagnosis rather than intervention. Look for patterns rather than incidents. Where does confusion show up most consistently? Which conversations are being delayed or avoided? What do people repeatedly have to chase, clarify, or apologise for?

Then narrow the focus. Trying to fix everything at once almost always produces another initiative that the team observes with weary recognition and waits out. It is more effective to improve a small number of high-friction habits consistently. Clearer outcomes from meetings. Earlier feedback. Explicit ownership on projects. Better judgement about when a conversation needs to happen properly rather than over a message. More direct engagement when expectations have slipped.

Managers should also be willing to look honestly at their own contribution to the conditions. Team communication problems are not always caused by leadership. But leadership sets the tone. If priorities are unclear, if feedback is inconsistent, if people have learned that raising concerns is more trouble than it is worth, the team will build its habits around that reality. The fix starts there.

The word fine should always prompt a second look. In a team, as in a session with a client, the surface answer rarely captures what is actually happening. The teams that communicate well are not the ones with the best tools or the most structured processes. They are the ones where the manager has created enough safety, clarity, and consistency that people do not need to pretend.

By Paula Donnan

Strength-Led Career Consultant

www.pauladonnanadvisory.com

Strength at Work  |  Better judgement. Stronger leadership. Higher performance.