The Mistake of Treating a Team Problem as an Individual Problem

You’re staring at a blank document, the cursor blinking patiently. It’s the pre-write for your third performance conversation with Mark this quarter. You’ve already had the informal chats, the check-ins, the feedback sessions. The knot in your stomach tells you this one won’t be any different. He’ll get defensive. He’ll argue the details. He’ll agree to the action points and then, a week later, the same friction will reappear with the rest of the team. You find yourself typing into a search bar, “how to get an employee to take feedback,” knowing the articles will tell you to be clear, be specific, be direct, all the things you’ve already tried.

The real problem isn’t that your feedback is bad. It’s that you’re delivering it to the wrong address. The issue you’re trying to manage is presenting as one person’s difficult behaviour, but its source code is located in the team’s dynamics. You’re trying to fix a faulty part, but the machine it’s in is designed to break it. This is the core trap: we locate the problem inside the person we can see, the one causing the most noise, rather than in the invisible patterns between people. Mark isn’t just Mark; he’s become the designated carrier for the team’s unexpressed conflict, its avoidance, or its anxiety. And no amount of feedback directed at him will fix that.

What’s Actually Going On Here

When a team has an issue it can’t or won’t deal with directly, like a flawed process, a fear of disagreeing with a senior member, or a collective anxiety about a deadline, it often outsources the resulting tension to one person. That person becomes the “problem employee.” They might be the one who complains about the broken process while everyone else stays silent. They might be the one who sounds cynical in meetings where everyone else is performing enthusiasm. Their behaviour is disruptive, yes, but it’s also a symptom. It’s the check-engine light for the entire team.

For instance, consider a team that avoids direct conflict. A new project plan has obvious flaws, but no one wants to challenge the director who proposed it. They bite their tongues in the meeting. Mark, however, doesn’t. He pushes back, maybe not skillfully, but he says what others are thinking. The team breathes a silent sigh of relief, the tension is broken, but they also subtly distance themselves from him. In the debrief, you and the other managers discuss “Mark’s negative attitude.” The system works perfectly: the unpopular truth gets aired, and the group gets to pin the resulting discomfort on one person, preserving the illusion of a harmonious team. The group’s conflict avoidance is maintained and reinforced, and Mark is siloed as the problem.

This pattern is cemented by the vague, un-actionable feedback these employees often receive. Phrases like “you need to be more of a team player” or “your attitude needs to improve” create a classic double bind. There is no clear, behavioural path to satisfying the demand. If Mark asks for specific examples, he’s seen as “argumentative.” If he tries to guess what “being a team player” means, he’ll almost certainly guess wrong. This isn’t a request for a change in behaviour; it’s a demand for a change in character, and it’s impossible to comply with. It’s designed to fail, confirming your initial assessment that he is, in fact, the problem.

What People Usually Try (and Why It Backfires)

When faced with this situation, smart, capable managers tend to reach for a standard set of tools. These moves are logical, defensible, and almost guaranteed to make the underlying problem worse.

• Move: Doubling down on individual feedback. You create a detailed document listing specific instances of the problem behaviour, hoping that more data will break through their defensiveness.

  • How it sounds: “Let’s walk through the meeting on Tuesday. At 10:15, when Jane was speaking, you interrupted…”
  • Why it backfires: This frames the conversation as a prosecution, not a diagnosis. You are presenting evidence against them. It forces the employee into a defensive crouch and solidifies the belief that the problem is 100% located within them, making it even harder to see the wider team dynamic.

• Move: Escalating to a formal process. You engage HR and initiate a Performance Improvement Plan (PIP), formalising the consequences and timeline for change.

  • How it sounds: “Because we haven’t seen the necessary changes, we’re going to put a formal plan in place to support you.”
  • Why it backfires: A PIP is a tool for individual skill or will gaps. By deploying it here, you are officially misdiagnosing the problem. It formalises the employee’s role as the scapegoat. The rest of the team sees it, learns that raising issues is dangerous, and becomes even more conflict-averse. The system gets stronger.

• Move: Coaching on tone. You focus on how they say things, rather than what they are saying, because their delivery is alienating others.

  • How it sounds: “I agree with your point, but your tone was too aggressive. You need to be more constructive.”
  • Why it backfires: While delivery matters, focusing on it exclusively is a way to invalidate a legitimate concern. You’re telling them their alarm is ringing too loudly, instead of investigating the fire they’re pointing at. This teaches them that the organisation cares more about comfort than about truth.

The Move That Actually Works

The counter-intuitive and effective move is to stop trying to fix the individual and start investigating the system through them. This requires a fundamental shift in your stance, from a manager trying to correct a performance issue to an analyst trying to understand a team dynamic. You have to treat the “problem” behaviour not as a character flaw, but as a piece of data.

Your primary question changes from “What is wrong with Mark?” to “What is Mark’s behaviour a response to?” or “What function does this behaviour serve in our team?” By asking this, you reposition the employee from being the problem to being the person who is pointing at the problem. This doesn’t absolve them of responsibility for how they act, but it correctly frames their actions as part of a larger picture.

This means your job is no longer to get them to agree with your assessment. Your job is to get curious about theirs. You have to zoom out from the specific incident, the interruption in the meeting, the cynical comment, and look at the context in which it occurred. What was happening right before? Who else was in the room? What was the unspoken tension? The person you’ve labelled the problem is often the most sensitive barometer of the team’s unspoken anxieties. If you can learn to read the barometer instead of trying to fix it, you’ll finally understand the weather.

What This Sounds Like

This isn’t a script, but a set of illustrations for how this shift in stance changes the words you use. The goal of this language is not to be nicer; it’s to be more effective at gathering information about the real problem.

• Instead of focusing on their reaction, ask about their perception.

  • Example: “In the project meeting yesterday, you were the only one to raise concerns about the timeline. I want to understand what you were seeing that others might have missed.”
  • Why it works: This reframes their “negativity” as a unique and potentially valuable perspective. It validates their perception without necessarily agreeing with it, and it turns a monologue (your feedback) into a dialogue (their data).

• Name the dynamic you see in the group.

  • Example: “I’ve noticed a pattern where you often end up being the voice of dissent, and then the rest of the room goes quiet. I’m wondering what you think makes it difficult for others to join that conversation.”
  • Why it works: This explicitly widens the lens from their behaviour to the group’s. It makes the silence of others a topic for discussion. You are signalling that you see the whole picture and holding the entire team accountable for its dynamic.

• Connect their behaviour to a shared team goal.

  • Example: “My sense is that your frustration comes from a deep commitment to getting this project right. I share that commitment. Help me understand which part of our current process you believe is putting that at risk.”
  • Why it works: This move assumes a positive intention behind the difficult behaviour. It aligns you with the employee against a shared problem (the risk to the project), rather than positioning you against them.

• Replace vague labels with concrete, forward-looking requests.

  • Example: “Instead of talking about ‘attitude,’ let’s talk about the next meeting. When we discuss the budget, I need you to let the finance team present all their numbers before you identify problems. Can you commit to that one behavioural change?”
  • Why it works: This scraps the impossible demand to change a personality trait and replaces it with a specific, observable, and achievable behavioural request. It gives them a clear way to succeed.