Your Leadership Team Doesn't Have a People Problem. It Has an Operating System Problem.

Dana Campbell, PCC

CEO | Leadership Coach | Advisor | Speaker | Change Leader | Stress Resiliency Expert

Strong teams don't fall apart. They get overtaken by a business that changed faster than they did.

When a leadership team that previously produced results starts struggling, the instinct is to change the team.  Our work with clients has shown that the real issue is that the business evolved and the team never updated how it operates together. The friction shows up as conflict, decision churn, and slow execution — but those are symptoms, not causes. The fix is building explicit agreements in five areas: how conflict gets surfaced, how decisions get made, how priorities realign, who owns what and whether the operating model itself gets revisited.

We’re diving into what good looks like in each area.

___________________________________________________________________________

You notice it before anyone says it out loud.

Two of your leaders have stopped disagreeing in meetings. Not because they've found alignment — but because they've stopped trying. The tension that used to surface in the room now lives in hallways, in Slack messages, in conversations that happen after the meeting ends. Decisions get made, but not really. The same issues keep coming back.

As a C-suite leader this is one of the most frustrating things to solve.  A team that used to deliver and now is lacking the cohesion to function let alone deliver.

Research from Harvard Business Review, based on interviews with more than 100 CEOs and senior executives, found that a dysfunctional leadership team is one of the most underestimated drags on strategy execution — and that the health of a senior team can make or break a CEO's tenure. The same research identified a consistent root cause: not the wrong people, but a lack of clarity — strategic, operational, and behavioral — about how the team is supposed to work together.

Dysfunction is often treated as a people problem.  But treating only the people overlooks a more systemic problem - a broken, outdated or undefined leadership operating system.

Conflict and dysfunction are just symptoms. The underlying infrastructure is the cause.  And until you address it, the same dynamics will keep resurfacing regardless of how many one-on-one conversations you have.

Here is what building that infrastructure actually looks like.

Start where the pain is: conflict surfacing

Most leadership teams handle conflict one of two ways. Either everything gets surfaced in the room — which sounds healthy but often means the loudest voices set the agenda — or disagreement gets suppressed until it becomes unavoidable, by which point it has usually gotten personal.

Neither is what high-functioning teams actually do.

What works is creating explicit agreements around how tension gets raised before it compounds. That means the team decides together: what kinds of disagreements warrant a direct conversation versus a structured discussion in the full team? How do we signal that something is bothering us without it escalating? Who is responsible for calling it when the team is avoiding something important?

These are not complicated agreements. But most teams have never made them. As a result, teams are trying to solve conflict while perspectives are distorted by conflict. That's like trying to fight your way out of a paper bag — lots of energy, zero visibility, and the bag is still winning."

The practical output is simple: a short set of team agreements about how conflict gets surfaced and resolved. Not a values statement — actual behavioral commitments the team revisits when things get hard.

The benefit is that disagreement stops being a sign that something is wrong and starts being a sign that the team is actually working.

Decision-making: the hidden source of churn

Once conflict has somewhere to go, the next most common friction point is decision-making — specifically, the gap between how the team thinks decisions get made and how they actually get made.

In most leadership teams, decision-making authority is implicit. Everyone has a general sense of who owns what, but it has never been tested under pressure. When a decision is easy, the ambiguity doesn't matter. When a decision is hard — when it touches multiple functions, when there's real disagreement, when the outcome affects someone's team or budget — the ambiguity becomes expensive.

A separate HBR study found that 75% of cross-functional teams are dysfunctional, frequently missing deadlines and falling short of expectations — and poor decision-making governance was one of the primary culprits. When it is not clear who owns a decision or how disagreements get resolved, the default is delay, politics, or both.

Think simple, not complex.  Design for clarity on a handful of specific questions: Which decisions does each leader own outright? Which requires input before moving? Which need full team alignment? And critically — when there is genuine disagreement, how does the team resolve it?

Getting explicit about this does not slow things down. It speeds them up. The team stops the relitigating process at the exact moment when speed matters most.

Priority alignment: what changes and what doesn't

When business conditions shift — AI changes how work happens, a key customer churns, a competitor moves, a product bet doesn't land — most leadership teams don't have a shared framework for how to realign. Each leader defaults to protecting their own function's priorities, which is rational from where they sit but pulls the organization in multiple directions at once.

What works is establishing a standing agreement around two things: what the leadership team's top shared priorities are at any given time, and what process the team will use to revisit those priorities when conditions change.

This doesn't mean priorities never change. It means the team has a shared way to change them together rather than each leader making independent adjustments that quietly compound into misalignment.

For a C Suite Leader, this is particularly important — you are often the one absorbing the gap, spending your time realigning leaders who have each drifted in a reasonable direction, but away from each other.

Accountability: what the org chart doesn't tell you

Org charts create structure. They don't create shared and aligned expectations.

Accountability gets genuinely complicated when work is cross-functional — and at most stages of growth, it increasingly is. The gaps that slow execution are rarely the obvious ones. They live in the white space between functions, where everyone assumes someone else has it covered until something falls through.

The most effective approach separates two things most teams conflate: structural accountability, which is about role clarity, and relational accountability, which is about the commitments leaders make to each other.

Structural accountability is relatively easy to define. Relational accountability requires the team to have explicit conversations about what each leader needs from their peers to do their job well — and what they are committing to in return. That conversation, done well, surfaces more about how the team actually operates than any org chart revision.

Revisiting the operating model itself

The final area is the one most teams skip — and the one that prevents the other four from drifting back into ambiguity over time.

The way a leadership team operates is not fixed infrastructure. It needs to evolve as the business evolves. Without a deliberate practice of revisiting it, teams default to doing what they have always done long after it has stopped serving them.

The most effective leadership teams build in a regular checkpoint — quarterly works well for most — to ask a simple question: does the way we operate together still match what the business needs from us?

The cost of assumptions versus agreements

Across all five areas, the pattern is consistent: most leadership teams have assumptions. Very few have actual agreements.

Assumptions are invisible until they conflict. Agreements create a shared foundation the team can actually build on.

For C-suite leaders the leverage here is significant. You can spend your time mediating tensions that should never have reached you — or you can invest in building the operating infrastructure that handles them earlier, and at a lower level.

The teams that move fastest are not always the ones with the most talented leaders, though talent matters. They are the ones where capable leaders have a shared, explicit way to make decisions, surface conflict, align on priorities, and hold each other accountable.

That doesn't happen by accident. It gets built.

About Optimize Corps Optimize Corps partners with executive teams to solve the problems that strategy alone can’t fix—misalignment, leadership friction, and breakdowns in execution.

Through its Cohesion Catalyst model, the firm partners with senior leaders across growth-stage and enterprise organizations to strengthen decision-making, increase alignment, and elevate how leadership teams function day-to-day.

The work targets the real sources of friction—unclear expectations, misaligned priorities, and conversations that never fully happen—so teams can move from stalled execution to ownership and momentum.

Our clients experience faster decision-making, stronger alignment, and meaningful improvements in how their teams execute.