When conflict goes underground

/in , , , , /by

When The Team Doesn’t Disagree In Meetings, There’s a Problem

Two Failure Modes

There are two failure modes when it comes to conflict in leadership teams.

The first is obvious: escalating conflict, openly adversarial peer relationships, meetings that generate more heat than resolution. Most people recognize this as a problem.

The second is more subtle, more common, and often more damaging. Genuine disagreement exists but gets managed rather than resolved. They are discussed openly in hallway conversations but not in the room, separate meetings occur, and functional decisions quietly diverge from what the team appeared to agree on. The goal in the room is to preserve relationships rather than surface real concerns.

This mode produces meetings that look healthy. Calm. Collegial. Efficient. The dysfunction only becomes visible later. I saw this pattern clearly when I worked in a financial services company. Meetings were consistently polite, conflict was rare, and the moment each session ended, executives quietly lined up to get on the president’s calendar to say what they hadn’t said in the room.

Recognizing It

The pattern I look for isn’t whether the team argues. It’s whether what gets raised in the room is the real conversation or a version that’s safe enough to say out loud:

  • Members describe the real conversation as something that happened after the meeting, not during it.
  • The CEO is routinely surprised by concerns raised one-on-one that never surfaced in the room.
  • When disagreement does appear, it resolves quickly, not because the issue was worked through, but because someone backed down to preserve the peace.

The Damage It Does

Conflict that has gone underground is self-perpetuating because its consequences are seldom traceable back to the conflict itself. The feedback loop that would allow the team to learn is broken at exactly the point where the cause was managed out of sight.

Too often, people comply with the decision rather than commit because they don’t feel heard or to avoid any more difficult conversations on the topic. This leads to the deterioration of the relationships among those involved.

Sometimes the team doesn’t learn the cost of compliance, or never recognized the true source of the problem. Post-mortems may blame failure on execution gaps, unclear ownership, insufficient resourcing. What doesn’t surface is that the real disagreement was never resolved.

 

The team that fights openly and well will eventually recognize the true nature of the conflict. A team that manages conflict quietly keeps attributing the consequences to other causes and never reaches the source.

The Fix

The goal isn’t more confrontational meetings. It’s making the room safe enough for real concerns to surface — and building the team’s capacity to work through disagreement without the relationship cost that currently makes avoidance feel like the better option.

 

Accountability Without Blame

/in , , , , /by

Accountability has a reputation problem.

For a lot of people, being held accountable feels like being set up to be blamed. So, they hedge commitments, qualify timelines, and avoid owning outcomes they’re not certain they can control.

The result is a team that’s busy, well-intentioned, and too often vague about who is responsible for what.

That’s not an accountability problem. It’s a safety problem.

When people experience accountability as punitive, they learn to protect themselves from it. They underpromise. They blame circumstances. They point to dependencies. None of this is laziness. It’s rational behavior in response to the environment they’re in.

I worked at a large consulting firm where accountability and blame were synonymous. During a performance review, I told one of our staff consultants that the partner wanted him to share more of his ideas. He said he didn’t know that was ‘allowed’. He had seen too many staff consultants blamed for ‘not following the plan’ when they tried to add a different way of thinking to a project or plan. The message was don’t add anything to the process. Just do what you’re told. The project managers thought they were creating accountability. What they were really doing was creating an atmosphere of fear.

Real accountability is built on clarity, not pressure.

It starts with commitments specific enough to be meaningful. Not “we’ll make progress on this” but “we’ll have a decision by the 15th.” Vague commitments can’t be held — they can only be argued about.

It also requires that when something goes wrong, the first question is “what do we need to do differently?” rather than “whose fault is this?” These may sound a bit similar. But they produce completely different conversations.

The leader’s role

The tone of accountability on a team usually traces back to how the leader handles their own misses. When a leader acknowledges openly that something didn’t go as planned — without deflection — they give everyone else permission to do the same. I’ve seen this happen in real time in executive teams. The power of acknowledgement was the productive conversation it created.

That modeling is quiet and powerful. It signals that honesty about what’s not working is valued more than the appearance of having everything under control.

How does your team handle accountability when things don’t go to plan? Reply and let me know.

E.Onderick-Harvey@NextBridgeConsulting.com