A senior VP at a technology company once described a pattern she had noticed after about six months in her role. Every major cross-functional initiative launched the same way: the leadership team met, the strategy got presented, the room came to apparent consensus, and people dispersed. Then, within two weeks, each function would begin executing on a slightly different version of what had been agreed. Not wrong versions exactly. Just different enough that coordination became expensive and the initiative gradually lost definition until it either got quietly relaunched with a new framing or got absorbed into individual team OKRs and effectively died.

She asked the CEO about it once. He told her the team was aligned. He was right that they had agreed. He was wrong that this was the same thing.

What Boards See and What Executives Know

In November 2025, HBR published findings from a study examining C-suite cohesion. One data point worth sitting with: 100% of board directors surveyed believed their senior leadership team operated cohesively. Among the C-suite executives themselves, only 66% agreed. That 34% gap is not a rounding error. It represents the distance between what a board can observe across four meetings a year and what an executive experiences as operational reality every week.

The board sees polished presentations, unified messaging when it matters, smooth consensus in formal settings. The C-suite executives see which decisions have been sitting unresolved for six weeks because nobody wants to own the call. They know which peer relationships are quietly adversarial. They know who will show up to joint planning sessions with real numbers and who will show up with talking points and a pre-negotiated position.

Neither group is lying. They are observing the same team from completely different vantage points, through completely different information. The board's confidence is genuine. The executives' frustration is also genuine. And the organization below both of them runs on the gap between those two realities.

Why Functional Excellence Does Not Build Teams

Most C-suites are assembled by function. A CFO is hired for financial discipline. A CPO for product judgment. A CHRO for people strategy. Each was probably evaluated as an individual leader with a strong track record in their domain. Nobody assessed whether this specific combination of people could make decisions together under sustained pressure, or whether they shared enough of a working model to surface disagreement before it became organizational drag.

What holds the team together, in most cases, is proximity and an org chart. Those things produce coordination, occasionally. They do not produce a team. A team requires shared decision-making norms, explicit ownership of cross-functional questions that fall between domains, and some mechanism for resolving conflict when it arises rather than letting it calcify into positional negotiation.

The organization does not experience C-suite dysfunction as a leadership team problem. It experiences it as a strategy problem. As an execution problem. As the specific frustration of being asked to prioritize five things simultaneously without any indication of which one actually matters most.

Research from LHH's 2026 C-Suite study found that decision-making gaps have become the defining characteristic of the current leadership agenda — not AI, not restructuring, but the inability to make clear, coordinated decisions at the top. Nearly half of executives report they were not successful at aligning others around their initial objectives in a new role. That failure rate does not come from a deficit of intelligence or capability. It comes from the absence of the structural conditions that would make alignment possible.

Where the Drag Actually Lands

The cost does not accumulate at the top. It falls on the layer below: the directors and VPs who receive misaligned signals and have to decide, without explicit authority, which one to act on. They compensate by waiting. By convening more alignment meetings. By building informal intelligence networks that tell them whose signal is actually reliable this quarter. Over time, those workarounds become the real operating model.

Organizations read this as a middle management problem. As excessive meeting culture. As an execution deficit. The source is one layer up.

There is a particular quality to working inside a genuinely cohesive senior team that is difficult to describe until you have experienced it. Decisions move at a different speed. Real disagreement surfaces in the room where it can be resolved, rather than in bilateral conversations afterward. The team can say — before the initiative launches, not six weeks into it — that something is misaligned and needs to be resolved. Once you have seen it work, you can diagnose its absence in a single cross-functional planning session. The tells are specific: the absence of real challenge in formal settings, the volume of off-line conversations required to close anything, the pattern of agreed strategies that produce divergent executions inside a fortnight.

A Design Problem, Not a Chemistry Problem

The 34% of C-suite executives who say their leadership team does not work well together are not describing a personality conflict or a cultural deficiency. They are describing a design problem. The team was never built. It was populated.

Fixing it does not start with team-building events or leadership assessments, though both have their uses. It starts with building explicit mechanisms for surfacing disagreement early, when it is cheap to resolve, rather than letting it accumulate until it costs the organization months of misaligned execution. It requires clear ownership of the cross-functional decisions that fall between domains, because those are precisely the decisions that tend to stay unresolved the longest.

The question worth sitting with is not whether your leadership team agrees on the strategy. It is whether they have ever been required to demonstrate how they disagree — and whether the mechanism for resolving that disagreement actually exists.

What does that look like in your organization?