It's one of the most disorienting things a leader can experience: a team of demonstrably talented individuals that somehow underperforms. Everyone is smart, everyone works hard, and the output is less than the sum of its parts. The instinct is to look harder at the people — who's the weak link, who needs managing out. That instinct is almost always wrong, and acting on it usually makes things worse, because the problem isn't located in any individual. It's located in how they coordinate, and capable individuals can coordinate terribly.
A team's performance isn't the sum of its members' abilities. It's a function of how well those abilities connect — how cleanly work passes between people, how reliably commitments hold, how openly the group can have the conversations it needs to have. Those connections are a kind of infrastructure, mostly invisible, and a team can have brilliant components bolted onto terrible infrastructure. When that's the case, adding more talent does nothing; you're upgrading components on a network that can't carry the load.
This is why the underperformance feels so mysterious from the inside. Every individual, examined alone, checks out. The dysfunction lives in the gaps — in the handoff that was never clear, the commitment that was never really made, the disagreement that never got aired. Gaps don't show up on a performance review of any single person, so they stay invisible while quietly degrading everything.
If you trace a team's underperformance back to its origin, you land on the same spot more often than not: the request. Work in a team moves through requests and commitments, and when the requests are vague, everything downstream wobbles. Picture a capable team where the lead says, in a meeting, “we should really get on top of the onboarding numbers.” Four people nod. Nothing in that sentence specifies who, what exactly, or by when — so each of the four leaves with a different private interpretation, or with the comfortable assumption that someone else has it. Two weeks later the onboarding numbers are exactly where they were, and the lead is privately wondering why such a good team can't execute. The team is fine. The request was never a request.
Capable individuals can coordinate terribly. The dysfunction lives in the gaps, where no performance review ever looks.
Multiply that single vague moment across a week of them and you have the whole phenomenon. Each fuzzy handoff produces a little rework, a little duplicated effort, a little dropped work that everyone assumed someone else was holding. None of it is dramatic. All of it compounds. And because no individual is failing, the team keeps looking for the problem in the wrong place — sharper hires, better tools, more meetings — while the actual fault, the connective tissue, goes untouched.
The other place capable teams quietly fail is in what they won't say to each other. A team that can't disagree openly will agree its way into bad decisions, because the person who saw the problem decided it wasn't worth the friction to raise. A team where trust is thin on one dimension — where, say, people doubt each other's reliability — will hedge, duplicate, and check up on each other in ways that burn enormous energy. These are not talent problems either. They're problems in the relational layer, and they respond to work on that layer, not to a reshuffle of who's on the team.
The reshuffle is the most common response to an underperforming team and one of the least effective. Swap a couple of people, the logic goes, and the chemistry will change. Sometimes it does — but if the real problem was the coordination infrastructure, the new arrivals inherit exactly the same broken handoffs, the same vague requests, the same unsayable topics, and within a couple of months the team performs no better with different faces in it. You've paid the considerable cost of disruption to relocate the problem. The exception is a genuine values or behaviour issue in one person — that does need addressing directly — but the diffuse “this team just doesn’t gel” almost never resolves by changing who’s in it, because the gel was never the issue.
So when a capable team underdelivers, resist the urge to audit the people and audit the connections instead. Are requests landing with real clarity — what, to what standard, by when — or are they vague gestures everyone interprets differently? Are commitments freely made and reliably closed, or are they nods that evaporate? Can the team have its hard conversations, or does it agree on the surface and seethe underneath? Those three questions locate almost all team underperformance, and none of them is about ability.
The encouraging part is that coordination is far more fixable than talent. You can't quickly make people smarter, but you can quickly make requests clearer, commitments firmer, and conversations more honest — and when you do, the talent that was always there finally connects. The team didn't need new people. It needed the space between the people it already had to start working.