How to Intervene When One Team Member Is Being Scapegoated

You’re in the weekly project meeting, and it’s happening again. The new feature shipped with a critical bug, and the conversation is slowly, inexorably circling back to one person. Mark is explaining the technical debt, but he ends with, “…and Sarah’s team was running behind, so we had to cut some corners on QA.” Then Priya adds, “I did flag the capacity issue, but Sarah was confident they could handle it.” You watch as Sarah’s shoulders tighten. You want to step in and say, “This isn’t just on her,” but you know it will sound defensive. You’re the manager, you’re supposed to fix this, but you’re stuck wondering, “how do I handle it when my team keeps blaming one person for everything?”

This dynamic isn’t just a communication problem; it’s a form of systemic self-preservation. When a group is under pressure or facing failure, it’s incredibly difficult to tolerate the complexity and shared responsibility of what went wrong. It’s much simpler, and psychologically easier, to locate the problem in a single person. The team isn’t just blaming an individual; it’s unconsciously outsourcing its collective anxiety, failure, and frustration onto a single colleague. By making one person the container for the problem, everyone else gets to feel competent, cohesive, and safe. This is what makes the pattern so sticky and so resistant to simple fixes.

What’s Actually Going On Here

When a project fails, the real cause is almost always a tangled mess: an unrealistic timeline from leadership, a key person quitting mid-project, a misinterpretation of client needs, and a dozen small, individual missteps. To confront that complexity is to admit the team, and you as its leader, have limited control. The human brain resists this. It searches for a simpler story. Scapegoating provides one: “It’s not that our entire process is flawed; it’s that one person didn’t pull their weight.”

Once that story takes hold, a powerful filter snaps into place. Everything the targeted person does is interpreted through the lens of their perceived failure. If Sarah speaks up in a meeting, she’s being “defensive.” If she stays quiet, she’s “disengaged” or “sulking.” She is placed in a classic double bind: any action she takes will be used as further evidence of the original accusation. The team’s story about her becomes a self-fulfilling prophecy.

This pattern is also incredibly stable. For the group, it works. It reduces anxiety and provides a clear, if false, path forward: fix or remove the “problem person.” Even you, as the manager, can get drawn into this. Your attention becomes consumed by managing Sarah, trying to coach her, or defending her. In doing so, you inadvertently agree with the team’s core premise: that the problem is, in fact, located in Sarah. The system has successfully organized itself around the scapegoat, and everyone, including you, is now playing their part to keep it that way.

What People Usually Try (and Why It Backfires)

When you feel the pressure to intervene, the most obvious moves are often the ones that reinforce the dynamic. You’ve likely tried some of these, because they seem like the right thing to do.

• The Direct Defence. You step in and say, “Let’s be fair, Sarah was working with limited resources and she flagged that early on.” This makes you Sarah’s sole protector, isolating the two of you and casting the rest of the team as unreasonable accusers. It turns the dynamic into you-and-her against them.

• The Vague Appeal to Professionalism. You try to lift the conversation to a higher plane: “Okay, let’s keep the feedback constructive and not make this personal.” This is a request to change behaviour without changing the underlying belief. The team will just find more “professional-sounding” ways to imply blame, leaving you to manage a problem that has become less visible but no less toxic.

• The Forensic Investigation. You take the bait and try to prove or disprove the accusations. “Mark, can you pull up the project plan? I want to see the exact date Sarah’s deliverable was due.” This is the biggest trap. By agreeing to investigate the individual’s culpability, you validate the entire frame. You’ve become the judge in a trial where the verdict has already been decided, and the focus remains squarely on the scapegoat.

A Different Position to Take

The way out is not to get better at playing referee in the blame game. It’s to stop being the referee altogether. Your job is not to determine who is right or wrong. Your responsibility is to the health of the team as a whole, and the current dynamic is unhealthy for everyone, not just the person being targeted.

Let go of trying to defend the individual. Let go of trying to find the “true cause” of the problem in the heat of the moment. Your new position is that of a facilitator whose primary focus is on the team’s process. You are no longer managing a person; you are interrupting a dysfunctional pattern.

This means you stop reacting to the content of the accusations and start addressing the way the conversation itself is unfolding. Your goal is to make the system look at itself. You are holding up a mirror to the group’s behaviour and asking, “Is this how we want to solve problems?” This shift is subtle but profound. It moves you from being a participant in the drama to being an observer and shaper of the system.

Moves That Fit This Position

These aren’t lines from a script to be memorized, but illustrations of how to act from this new position. The goal is to redirect the focus from the person to the problem and from the accusation to the process.

• Zoom out from the person to the system. When the conversation narrows onto the individual, widen the aperture.

  Instead of: “Did Sarah get you the report on time?” Try: “Let’s map this out. What was the original request, when did it come in, who needed to sign off, and where were the other dependencies? I want to see the whole chain of events, not just the final step.” This move refuses to accept the simplified story and forces the group to confront the real-world complexity they are trying to avoid.

• Name the pattern, not the people. Make the dynamic itself the topic of conversation, without assigning blame for it.

  “I’m noticing that we’re spending a lot of time discussing Sarah’s role in this. I’m concerned that if we focus only on one person’s actions, we might miss a bigger, systemic issue in our workflow that could burn someone else out next quarter. I want to pause on this and ask: what else was going on that made this project so difficult?” This labels the pattern gently and provides a forward-looking, team-oriented reason to change course.

• Translate vague labels into concrete data. Scapegoating thrives on abstract, unprovable accusations like “being uncooperative” or “lacking ownership.” Don’t let them stand.

  When someone says: “The problem is a lack of commitment from her team.” You respond: “Can you walk me through a specific instance? I need to understand what you asked for, and what you got back. The details matter here.” This forces the speaker out of vague judgment and into observable facts. Often, the concrete example is far less damning than the label applied to it, or it reveals a simple miscommunication.

• Re-route the conversation physically. When the group keeps defaulting to blaming one person, explicitly ask someone else to contribute on a different topic.

  “Thanks for that perspective, Mark. I want to make sure we cover all the bases. Priya, you were managing the client relationship. Can you walk us through the feedback you were getting in the final two weeks?” This is a structural edit of the conversation. It creates a new focal point and gives the rest of the team a productive way to contribute, breaking the repetitive loop.