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.

 

Profiled. Workshopped. Still Stuck.

/in , , , , /by

Personality profiles don’t explain why you’re not executing

We’ve all experienced personality profiles as part of our leadership team experiences. DISC, Myers-Briggs,Insights Discovery, an enneagram workshop, They can tell you who’s a driver, who’s a stabilizer, who needs more processing time before a decision. They are great for breaking the ice and breaking down interpersonal issues.

What they usually can’t tell you is the complete story about why the team is stuck.

That’s not a flaw in tools. They were built to describe individual style, not to diagnose how a team functions as a leadership system.

Knowing that someone is a driver doesn’t tell you whether the team has a working process for converting decisions into action. Or whether authority and accountability line up. Or where alignment quietly breaks down between the meeting room and the next quarter.

Those are systemic questions, and they require a systemic answer — one built from how the team actually behaves under real conditions not personality preferences in isolation.

Style and system aren’t in competition. But they answer different questions, and treating a systemic problem with a style-based tool is one of the more common reasons executive team work fails to produce lasting change.

If a team already knows its personality types and is still stuck, that’s often the clearest sign the next layer of the problem is systemic, not stylistic.

Our research-based Executive Team Assessment analyzes the team systemically across 8 dimensions. If your team is stuck, let’s chat.

The Combined Leadership Team

/in , , , , , , , /by

Last to integrate. Most expensive to ignore.

Merged on Paper. Not in the Room.

We’ve all heard stories of the teams, that years after the acquisition is done, introduce each other by their previous company’s name. “I’m from Citi” “I’m from Chase.” I know I’ve experienced it post merger.

Integration plans after a merger are usually thorough on systems, processes, and org charts. They are almost never thorough on whether the combined leadership team can actually operate as one team.

The Combined Team Gap

The gap between a truly combined team and two factions that are working together, tends to begin to surface three to six months after the deal closes. The initial goodwill has worn off and real decisions like budget tradeoffs, aligning conflicting priorities, and decisions about whose process becomes the standard need to be made. The leadership groups need to function as a single unit rather than two groups sharing a company name.

A few things tend to be true of combined teams that are struggling, even when the org chart looks clean:

  • Decisions quietly default to “our side” and “their side” rather than a shared standard, even months after the deal closed.
  • Trust that took years to build on each legacy team has to be rebuilt from zero across the combined group, and nothing in the integration plan accounts for that timeline.
  • Disagreements that would have been resolved directly within one legacy team get escalated instead, because the norms for how this new team handles conflict haven’t been established yet.

None of this shows up in an integration checklist.

It shows up in how the combined team actually makes decisions together, resolves conflict, has honest conversations, and tackles tough issues. How do you identify it? With a systemic read of the new team rather than an assumption that good people will sort it out.

The cost of leaving this question unasked isn’t a single bad quarter.

It’s a leadership team that never fully integrates, well after the systems did. And the longer that gap persists, the more the organization learns to work around the team rather than through it — building informal workarounds, duplicate processes, and shadow coordination structures that quietly drain capacity and compound the original cost of the deal.

How much has an unintegrated leadership team cost your merger or acquisition?

E.Onderick-Harvey@NextBridgeConsulting.com

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

cracked concrete wall showing past stresses

The Organizational Scar Tissue Problem

/in , , , , , /by

Every organization carries history.

Hopefully a lot of it is good, sometimes a lot of it is bad. The restructuring that blindsided people. The leader who played favorites. The initiative that consumed enormous energy and went nowhere.

New leaders don’t always know the details. But they feel the effects every day.

Scar tissue is invisible on an org chart but visible everywhere else.

It shows up in the room that goes quiet when a new idea surfaces. In the team that nods enthusiastically and then does nothing differently. In the manager who learned that raising concerns leads nowhere good.

It’s not resistance. It’s memory.

The mistake most leaders make

They treat skepticism as a communication problem. More emails, more town halls, more slides. But scar tissue isn’t a communication problem. It’s a trust problem. And trust isn’t built by talking. It’s built by doing, consistently, in ways people can actually feel.

What actually helps

Name it. Acknowledging that history exists — “I know there have been changes here that didn’t go the way people hoped” — signals that you’re paying attention to something real.

Let actions outpace promises. Make small, visible commitments and keep them. Repeatedly. Until the pattern becomes undeniable.

Give it more time than you think you have. Trust rebuilds on its own timeline, not the leader’s.

An organization’s history doesn’t disappear when new leadership arrives. However, it can be rewritten by what happens next.

The leaders who understand that earn something more valuable than compliance. They earn commitment.

What’s the history on your team that’s still shaping how people show up today? Reply and let me know.

  E.Onderick-Harvey@NextBridgeConsulting.com