Your Team Is Underperforming and You Don't Know Why

The results are not where they should be. You know this. The team knows this. And yet when you look for the cause — the specific, addressable thing that is producing the gap between where the team is and where it should be — you cannot find it cleanly.

It is not one person. It is not one project. It is not a single identifiable failure. It is more diffuse than that — a general sense that the team is operating below its potential, that the energy is not quite right, that things that should be getting done are taking longer than they should, that the output is adequate but not what you know these people are capable of.

You have tried the obvious things. You have had conversations. You have set clearer goals. You have checked in more frequently. The numbers have not moved.

And now you are sitting with a problem that resists easy diagnosis — which is, in many ways, the hardest kind to solve.

Why team underperformance is harder to diagnose than it looks

The instinct when a team is underperforming is to look for a cause that matches the scale of the problem. If the team is significantly off target, there must be a significant reason. Find the reason, fix it, and the performance will recover.

This instinct is understandable. It is also, frequently, wrong.

Team underperformance is rarely the product of a single, significant cause. It is usually the product of several smaller causes that interact with each other in ways that make any one of them, in isolation, look insufficient to explain the overall picture. The team that is underperforming because of unclear goals is usually also underperforming because of something in the interpersonal dynamics, and also because of something in the relationship between the team and its resources, and also because of something in the way feedback is being given or not given. None of these things, alone, would produce the gap. Together, they do.

This matters because it means that fixing any one of them, alone, is unlikely to produce the improvement you are looking for. The team that gets clearer goals but still has unresolved interpersonal tension and inadequate feedback is a team with clearer goals — not a team that is performing better.

The three most common underlying causes

While every team's situation is specific, there are three underlying causes that account for the majority of sustained team underperformance, and distinguishing between them changes everything about how you respond.

The first is a direction problem. The team does not have a clear enough understanding of what they are trying to achieve, why it matters, and how their work connects to something that is worth caring about. Direction problems tend to produce a particular kind of underperformance: work that is technically competent but not pointed correctly, effort that is genuine but not well-aligned, output that fills the time available rather than driving toward a specific outcome. The team is not disengaged — they are working without a clear target, and the work reflects it.

The second is a dynamics problem. Something in the interpersonal fabric of the team is getting in the way of the collaboration that effective performance requires. This might be unresolved conflict between team members, a breakdown of trust between the team and the manager, a social hierarchy within the team that is suppressing certain voices, or a culture of self-protection that makes honest conversation about problems feel risky. Dynamics problems tend to produce a different kind of underperformance: one where the individual outputs are reasonable but the collective output is less than the sum of its parts, where there is a notable absence of the spontaneous collaboration and mutual support that characterise high-performing teams.

The third is a capability problem. The team genuinely does not have the skills, knowledge, or experience required to perform at the level that is expected of them. This is the cause that managers most often reach for first — and, paradoxically, the one that is least often actually the primary issue. Most teams that are underperforming are not underperforming because they lack capability. They are underperforming because the capability they have is not being well-directed, or is being undermined by dynamics, or is being applied to a target that is not clearly enough defined.

Distinguishing between these three causes requires a different quality of attention than the one that is typically applied to performance problems. It requires listening to what the team is actually saying — in formal conversations and in the informal signals that are often more accurate — rather than looking for evidence that confirms the diagnosis you have already formed.

What the data is and isn't telling you

Performance data tells you that there is a gap. It does not tell you why the gap exists. This sounds obvious, but it is a distinction that managers frequently collapse in practice — using the performance data as if it were a diagnosis rather than a symptom.

The data that is more useful for diagnosis is qualitative: what the team members themselves say about what is getting in the way, what you observe in the quality of team interactions, what the patterns in the work reveal about where the friction is accumulating. This data is harder to collect, harder to interpret, and harder to act on than the quantitative performance data. It is also much more likely to point toward the actual cause.

The most direct way to collect it is to ask — but to ask in a way that creates the conditions for honest answers. Not "how do you think the team is doing?" — which tends to produce polished, safe responses. But specific, grounded questions about specific, observable things: what is making this harder than it should be? Where do you feel like you are waiting for something? What would you change if you could change one thing about how we work?

These questions will not always produce clean answers. But they will produce information that performance data cannot — and that information is the foundation of any response that is likely to actually work.

The manager's role in the underperformance

This is the question that is most difficult for managers to ask honestly, and the one that is most often avoided: what am I doing, or not doing, that is contributing to this?

Underperforming teams almost always have some contribution from the manager's behaviour or decisions — not as the sole cause, but as a factor. The manager who is unclear about goals has contributed to a direction problem. The manager who avoids difficult conversations has contributed to a dynamics problem. The manager who has not invested in the team's development has contributed to a capability problem.

This is not a comfortable thing to examine. But it is one of the more reliable places to look for leverage, because it is the place where you have the most direct ability to make a change. The team's dynamics, capabilities, and direction are all things you can influence. But the thing you can change most immediately and most completely is your own behaviour.

The question is not whether you are a good manager in the abstract. The question is what, specifically, you are doing or not doing that is making it harder for this team to perform — and what you could change about that.

What you can actually do

The first step is to resist the urge to act before you understand. The pressure to do something when a team is underperforming is real, and acting before diagnosing tends to produce interventions that address the wrong problem. The team that gets a performance improvement plan when what it needed was clearer direction is a team that now has a performance improvement plan and still doesn't have clear direction.

The second step is to invest in the diagnosis. This means making time for individual conversations with each team member — not performance conversations, but genuine inquiry into what they are experiencing, what is getting in the way, what would help. It means observing the team in action, not just reviewing their outputs. It means being honest with yourself about what you are seeing and what it might imply.

The third step is to address what you find, directly and specifically. Not with a general push for more effort or a team-wide performance initiative, but with specific changes to the specific things that are producing the gap. If the problem is direction, provide direction — more specifically, more consistently, with more connection to why it matters. If the problem is dynamics, address the dynamics — directly, with the specific people involved, without the vagueness that makes these conversations feel safe but ineffective. If the problem is capability, invest in the capability — but be honest about whether the investment can produce results in the timeframe that is required.

A different angle on this moment

Here is something that managers in this situation often find useful to remember: a team that is underperforming is almost never a team that does not care.

The teams that produce the worst performance — that are genuinely disengaged, going through the motions, doing the minimum — are actually relatively rare. What is much more common is a team that cares about the work and is being prevented from doing it well by something in the environment: unclear direction, unresolved tension, inadequate support, a manager who is not giving them what they need.

That distinction matters, because it changes what the job is. If the team doesn't care, the job is motivation. If the team cares but is being blocked, the job is removal of obstacles — which is a very different, and in many ways more tractable, problem.

Most underperforming teams are blocked, not checked out. The question is what is blocking them.

MEETONESELF is designed for situations where the problem is real but its source is not immediately visible — where a structured view of the field can surface what the performance data alone cannot.