Why most attempts to fix a leadership team's performance fail

There is a pattern I encounter regularly in my work with senior leaders who have a leadership team that is underperforming — decisions that don't get made, commitments that don't get delivered, collaboration that never quite works the way it should. They know something needs to change. And they have already tried to change it.

They brought in a leadership coach. They ran an offsite. They had the difficult conversations. They reorganized reporting lines, changed a compensation structure, or replaced someone they thought was the problem. Sometimes they did all of these things. And the patterns they were trying to address are still there, sometimes worse than before.

This is not a story about failure of effort or commitment. Most senior leaders who find themselves in this situation are talented, experienced, and genuinely invested in their teams. The problem is not what they tried. The problem is what they assumed before they tried it.

The assumption that drives most interventions

When a leadership team is underperforming — meaning, not delivering according to expectations — the instinct is to identify what is wrong and fix it. That instinct may be right. The problem is in how "what is wrong" gets determined.

In most cases, the senior leader has a hypothesis about what's happening based on the information they've been able to gather, and the evidence they've seen. That interpretation becomes the basis for the intervention. The training program is designed around it. The offsite agenda is built around it. The difficult conversation is structured around it.

The problem is that if the interpretation is wrong —because the diagnosis is incomplete or inaccurate—, the intervention addresses the wrong cause. Which is why the patterns return. Not because the intervention was badly designed, but because it was aimed at the wrong target.

The most common diagnostic error is confusing symptoms with causes

A leadership team that appears not to collaborate is exhibiting a symptom. 

The cause might be that the team has no shared understanding of priorities — each leader has developed their own working definition of what matters most, because no one has defined it clearly at the team level. In that case, a collaboration workshop will not help. The problem is not collaboration; it is direction. And those two problems require completely different responses.

A leader who appears passive or risk-averse is exhibiting a symptom. 

The cause might be that initiative has been implicitly discouraged — that specific experiences of taking initiative and having it corrected or reversed have produced a rational adaptation. In that case, coaching the leader to be more confident will not help. The problem is not their confidence; it is the conditions that have made confidence costly. And changing those conditions is the senior leader's job, not the coach's.

A team of leaders who are not holding their own people accountable for results is exhibiting a symptom. 

The cause might be that role clarity is insufficient, and that leaders cannot hold their teams accountable for outcomes they do not fully control, with authority they do not fully have, against metrics they did not help define. In that case, accountability training will not help. The problem is structural, not behavioral.

The distinction between symptoms and causes is not trivial. It determines whether the intervention you design will actually work.

Why the right diagnosis is hard to reach

One reason for why senior leaders frequently misdiagnose the patterns they observe is that the people around them manage what they communicate upward.

Not usually through dishonesty. More often it is through the normal human instinct to present things constructively, to avoid surfacing problems that might reflect poorly on them, and to tell the person at the top what they believe that person wants to hear. The result is that the picture the senior leader receives of their own team is systematically filtered. The patterns that are most visible to the team are least visible to the person running it.

The other reason is that most team performance problems do not have a single cause. 

They are produced by the interaction of multiple factors — role clarity, decision rights, meeting structures, reporting relationships, competing priorities, and informal dynamics — none of which is sufficient on its own to explain what is happening. Identifying that kind of root cause requires a systemic lens, not just sharper observation. And it also requires the political will to examine structures, processes, and behaviors that may be deeply entrenched in the organization's culture. It means looking for what the patterns have in common, what conditions are consistently present when performance breaks down, and what structural features are sustaining the problem regardless of who is involved.

What a good diagnosis looks like

A real diagnosis starts with the right question

What conditions are actually producing the patterns we are observing? Not what behaviors need to change, but what organizational, structural, and relational conditions are driving those behaviors.

Answering that question requires going directly to the people who know the answer — the members of the leadership team themselves. Not through a survey, which produces aggregate data that obscures individual experience. Not through a 360 assessment, which measures how people are perceived rather than what conditions they are operating in. Through individual, in-depth conversations designed to surface the specific conditions that are shaping how each leader thinks, decides, and acts.

What those conversations reveal, when analyzed systematically across the full team, is almost always more complex and more actionable than what the senior leader understood going in. Some findings confirm their initial interpretation. Others reframe it significantly. And some surface patterns that were entirely invisible from where they were standing — including, sometimes, findings about how their own behavior is contributing to the conditions they are most concerned about.

That last category is the most important and the most uncomfortable. It is also where the most significant change becomes possible. Because if the senior leader's own practices are contributing to the problem, changing those practices is within their control. It does not require restructuring, or expensive programs, or personnel changes. It requires understanding what is actually happening, and making deliberate choices about what to do differently.

It's important to note also that the conditions that produce performance gaps rarely stay contained to performance. They create an environment where people operate with unnecessary uncertainty, where trust is harder to build and easier to lose, and where the energy that should go into the work goes instead into managing the ambiguity around it. Fixing those conditions does not just improve results — it creates a workplace where people are more likely to thrive and do their best work.

The persistence of the problem is a signal

If you are reading this and recognizing your own situation — a leadership team whose performance problems have persisted despite genuine efforts to address them — that persistence is itself diagnostic information. It is telling you that the root cause has not yet been correctly identified. That the interventions you have tried, however well-designed, were aimed at symptoms rather than causes.

The right response to that signal is not another intervention. It is an investigation.