# Poor Teamwork: The Five Root Causes and What You Can Do Canonical URL: https://headwayskills.com/knowledge/teamwork/poor-teamwork/ Markdown URL: https://headwayskills.com/knowledge/teamwork/poor-teamwork.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving teamwork at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Poor teamwork stacks up from five root causes, starting with trust. How to tell which one your team is stuck on, and what you can change from where you sit. ## Key facts - Title: Poor Teamwork: The Five Root Causes and What You Can Do - Category: Teamwork - Primary skill: Teamwork - Related skills: Communication, Building Resilience - Primary keyword: poor teamwork - Source page: https://headwayskills.com/knowledge/teamwork/poor-teamwork/ ## What this page covers - Poor teamwork stacks up from five root causes, starting with trust. How to tell which one your team is stuck on, and what you can change from where you sit. - Practical guidance for poor teamwork - How this topic connects to Teamwork ## Detailed explanation Poor teamwork is what happens when a group loses the conditions that make collaboration possible: trust between members, honest disagreement, real commitment to the decisions made, mutual accountability, and a shared result everyone is actually aiming at. Take one away and the others fall in sequence, which is why a struggling team feels vaguely broken rather than specifically wrong. That vagueness is the exhausting part. You can usually tell your team isn't working long before you can say what is missing, and in the meantime it is tempting to conclude that the problem is simply the people. It almost never is. These failures stack in a fixed order, and knowing the order tells you where yours started. ## What poor teamwork actually costs The frustration is proportionate to the damage. In survey data gathered across collaboration-statistics roundups, 86% of respondents attribute workplace failures to poor teamwork or ineffective communication, and 97% say a lack of team alignment shows up directly in how tasks and projects turn out. The research firm i4cp puts the average productivity loss on teams that collaborate badly at 39%. Around one in two knowledge workers reports that different teams end up working on the same things because nobody communicated — the duplicated effort you have probably already watched happen. The human cost is where this stops being abstract. A third of HR professionals report that poor collaboration drags morale down, and 26% of employees say poor relationships between teams contributed to their decision to leave a job. That is worth holding onto if you have been wondering whether you are overreacting: people leave over this often enough that it gets measured. The causes, though, are structural rather than personal. Some of the clearest evidence comes from healthcare, where teamwork failures get studied closely because they are dangerous. In a mixed-methods study of poor teamwork between junior doctors and nurses, 63.6% of the situations were attributed to poor quality of collaboration, 48.5% to a lack of coordination, and 42.4% to poor leadership. Not to bad people. To collaboration, coordination, and leadership as processes — and processes can be repaired. ## The five root causes of poor teamwork The most durable map of how a team gets here comes from Patrick Lencioni's *The Five Dysfunctions of a Team*, published in 2002 and still the model most team consultants reach for. Its useful claim is not the list but the shape: the five failures stack in a pyramid, each one resting on the one below it. Trust sits at the bottom, because it is close to impossible to argue productively with someone you fundamentally don't trust. Work upward from there and you can usually find the floor your own team is standing on. ### Absence of trust The starting failure is a fear of being vulnerable with the people you work with. It looks unremarkable from outside: nobody admits a mistake, nobody says "I don't actually know how to do this," and every status update is fine. What distinguishes it from an ordinary reserved team is the total absence of exposure — no one is ever willing to be seen struggling, so no one finds out that the others would have helped. [Trust at work](/knowledge/teamwork/building-trust-in-a-team/) is built out of smaller things than confession, which is what makes this rung available to you. Meaning what you say. Doing what you committed to, on the day you said. Being recognizably the same person in every room. One person behaving that way gives a team a floor to stand on, and it needs nobody else's cooperation to start. ### Fear of conflict When trust is thin, disagreement becomes too expensive to voice, and the team settles for artificial harmony instead: the meeting where everyone agrees, and the corridor afterward where three people tell you they don't. The distinguishing feature is that gap — what gets said in the room differs from what gets said outside it. Notice what is actually being avoided. Not personal conflict, which is worth avoiding, but the productive kind: [honest argument](/knowledge/teamwork/how-to-disagree-respectfully/) about the work itself. Teams that never have it are not peaceful, they are deferring the disagreement and paying for it later as quiet resistance to whatever was decided. The available move here is deliberately small. Say one version of the corridor sentence in the room, on something low-stakes, and find out whether the room can hold it. ### Lack of commitment Without open debate, people don't buy into decisions — they simply stop objecting, which is a different thing. The team leaves the meeting with a plan that several members have privately not agreed to, and the plan then fails to happen for reasons nobody can name. It is usually diagnosed as a follow-through or project-management problem. It is not. The distinguishing signal is ambiguity after the decision: a week later, people give you different accounts of what was decided. The principle that fixes it is "disagree and commit," and it only works as both halves. Voice the objection while the decision is still open, then implement the outcome loyally whether or not it went your way. Either half alone is exactly what a struggling team already does. ### Avoidance of accountability Once commitment is soft, nobody wants to point out that a commitment was missed, because the discomfort of raising it feels worse than the cost of absorbing it. Deadlines slip silently. The same person is late with the same handover for the third time and it goes unmentioned — until weeks later it surfaces as a complaint about them as a person. That is the distinction worth keeping: accountability and blame feel similar to do and are opposites. Accountability is prompt, specific, and about a commitment. Blame is delayed, vague, and about a personality. Most teams slide from the first into the second purely through timing. [Raising a missed commitment](/knowledge/teamwork/peer-accountability/) within a day or two, naming the commitment rather than the pattern, and letting it go once it is addressed is most of the skill — and it is not reserved for whoever runs the team. ### Inattention to results At the top of the stack, individual goals quietly displace collective ones. People protect their own metrics, their own visibility, their own area, and the team's actual result becomes nobody's job. The tell is diagnostic: everyone can describe how their own week went, but nobody can say whether the team hit anything. This is the rung where poor teamwork stops being uncomfortable and starts being expensive, and where the duplication in the survey data comes from. The counterweight is unglamorous: coordinating instead of assuming, sharing what you know, doing the work the team needs rather than only the work assigned to you, and giving credit to the group when it lands. Those behaviors are visible, and they get copied. ## Where to start when the team isn't yours to fix Almost everything written about poor teamwork is addressed to whoever can change the structure: redefine the roles, run the workshop, replace the leader. If that is not you — and early in a career it usually is not — the pyramid is still useful, because it tells you which rung is realistically within reach. Look again at the healthcare numbers. Leadership, at 42.4%, and coordination, at 48.5%, are largely outside your control. The quality of collaboration, at 63.6%, is the largest factor and the one made almost entirely of behaviors, several of which take one person to perform. Following through. [Saying the thing in the room](/knowledge/professional-behaviors/how-to-speak-up/). Raising the miss early. Passing on what you know. Which leaves one question worth answering honestly before you decide the team is beyond saving: which of those do you already do reliably, and which do you avoid? A clear read on [your strongest collaboration habits](https://assessment.headwayskills.com/) is what tells you how much of this you can genuinely shift from an ordinary seat on the team. ## What stays in your hands on a team like this Read back down the five rungs and the fixes have something in common. Not one of them is a policy. Each is a behavior, and the same short list of behaviors keeps reappearing under different names. **Teamwork** carries most of it. Every rung above maps onto a specific piece of it having gone missing: silent meetings are necessary disagreement being ducked, plans that never happen are "disagree and commit" broken in half, unmentioned misses are the accountability habit absent, and protected metrics are "me" beating "we." Working out which piece has failed is what converts a vague bad feeling into something you can act on — in your own behavior first, then carefully with a teammate. **Communication** is where most of those repairs actually get made, in a much narrower sense than "communicate more." It is choosing a conversation over a message when the subject is sensitive, leading with the main point, speaking up rather than assuming someone else will, and handling the specific hard cases a struggling team is made of: expressing disagreement without making it personal, dealing with someone who is angry, apologizing cleanly when the miss was yours. **Building Resilience** is the one people skip, and on a team like this it is what keeps the other two usable. Working inside dysfunction generates a steady supply of automatic thoughts — they don't respect me, this is hopeless, I'm the only one who cares — and left unchallenged those calcify into self-blame or contempt for your colleagues, which end the same way. Separating what you can influence from what you can't, checking a conclusion before acting on it, and talking to someone you trust instead of running it privately in a loop is what keeps you in a position to change anything at all. None of the three is a temperament. They are learnable behaviors, which means a gap is simply something not yet practiced — and it is measurable. Seven minutes of free assessment will show you [where the real gap is](https://assessment.headwayskills.com/), placing these three inside a full profile of twelve work skills rather than in isolation. Seeing them side by side is usually what relocates the problem to somewhere you weren't looking. ## The part of this that is yours Some of those five rungs almost certainly read as a description of your team. One or two may have read as a description of you: the objection you didn't raise, the missed commitment you let slide because saying something felt worse than absorbing it. That isn't a verdict. Skills like these go unlearned for the ordinary reason that nobody teaches them, and they change through practice rather than through becoming a different person at work — you can stay exactly as reserved, or as blunt, as you already are and still do every behavior above. The pull does grow. The further along you get, the more of your work runs through other people, and a team's dysfunction turns into something you navigate rather than something somebody else is supposed to fix. That makes now — on a team where the stakes are still fairly small — the cheapest possible moment to find out which rung is your weakest. You have already done the part most people skip. Reading five descriptions of a failing team and checking yourself against them, rather than only your colleagues, is not the usual response to this feeling. ## Check where your own skills stand The only thing left is finding out which rung is actually yours. The Job Skills Test is a **free** self-assessment of the work skills this article has been circling. It takes about seven minutes and gives you a profile across all twelve — teamwork, communication, and resilience among them — so you can see which ones are already holding steady, which one is quietly costing you on the team you are on now, and which single skill would change the most next. ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? Poor teamwork stacks up from five root causes, starting with trust. How to tell which one your team is stuck on, and what you can change from where you sit. ### Which Headway skill does this connect to? This guide connects primarily to Teamwork. It also relates to Communication, Building Resilience. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/teamwork.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/resilience.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/teamwork/poor-teamwork/ Preferred summary: "Poor teamwork stacks up from five root causes, starting with trust. How to tell which one your team is stuck on, and what you can change from where you sit." ## Change log - 2026-07-07: Content collection version published.