# Problem in Teamwork: 10 Reasons Teams Stop Working Well Canonical URL: https://headwayskills.com/knowledge/teamwork/problem-in-teamwork/ Markdown URL: https://headwayskills.com/knowledge/teamwork/problem-in-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 Stuck on a team that is not working? Here are 10 common problems in teamwork, what each one actually looks like, and what you can do without being the boss. ## Key facts - Title: Problem in Teamwork: 10 Reasons Teams Stop Working Well - Category: Teamwork - Primary skill: Teamwork - Related skills: Communication, Influence - Primary keyword: problem in teamwork - Source page: https://headwayskills.com/knowledge/teamwork/problem-in-teamwork/ ## What this page covers - Stuck on a team that is not working? Here are 10 common problems in teamwork, what each one actually looks like, and what you can do without being the boss. - Practical guidance for problem in teamwork - How this topic connects to Teamwork ## Detailed explanation You can usually feel it before you can name it: the deadline slips again, two people did the same task, someone has gone quiet for a week, and nobody mentions any of it in the meeting. Almost every problem in teamwork traces back to a small set of recognizable failures — unclear roles, uneven contribution, silent disagreement, broken commitments, lost trust, information that never crosses a boundary, or a disagreement that turned personal. Naming which one you actually have is what makes it fixable. The frustrating part is not that these problems are exotic. It is that nearly every guide to fixing them is written for whoever runs the team. Most people reading this are sitting inside the problem with no power to reassign anyone, which changes what is actually available to them. ## The 10 most common problems in teamwork The list below deliberately separates problems that usually get lumped together, because the wrong diagnosis costs weeks. You cannot fix a silo by communicating more clearly into it, and you cannot fix a deliberate free rider by making effort more visible. Each entry describes what it looks like from inside the team, and what [one person without authority](/knowledge/influence/influence-without-authority/) can do about it. Much of the advice you will find online borrows its vocabulary from Patrick Lencioni's *The Five Dysfunctions of a Team* — absence of trust, fear of conflict, lack of commitment, avoidance of accountability, inattention to results. It is a genuinely useful vocabulary, but a peer-reviewed study of the model, published in ScienceDirect, points out that Lencioni's book is explicitly a work of fiction rather than research. Treat it as language, not as evidence. ### 1. Nobody says what they actually think The tell is a meeting where everyone agrees quickly and then nothing happens. Sources on team dysfunction describe members withholding ideas because they fear ridicule or backlash, so objections travel by private message instead of surfacing where they could change the plan. This is not conflict; it is the absence of conflict, and it is more expensive. The move available to you is small: ask one person directly, one on one, what they would change about the plan. Private disagreement is nearly always easier to collect than public disagreement. ### 2. One or two people carry all the work The research literature separates two things the word "lazy" collapses. Social loafing is effort that quietly drops because individual contribution is pooled and less visible. Free riding is a deliberate step back in the expectation that someone else will compensate. Group size, fatigue and pooled evaluation are the factors most often named as drivers. The distinction matters because the fixes differ: loafing responds to making individual contributions visible, free riding does not. And teams often permit it knowingly — the study of Lencioni's model notes that teams put up with a free ride to avoid a confrontation, or out of a genuine impulse to help someone who seems to be struggling. ### 3. Nobody knows who owns what Two people build the same thing while a third task falls off entirely, and each person assumed the other had it. Role ambiguity is reported as a major predictor of job performance, with employees who lack [role clarity](/knowledge/teamwork/role-clarity/) showing lower engagement, higher stress, and less willingness to contribute beyond their basic duties. This is one of the few problems on this list a junior member can largely solve alone: write down who owns what, circulate it, and ask people to correct it. Nobody has to grant you permission to keep a list. ### 4. Everyone is busy on the wrong thing Effort is high and alignment is zero. Research at Edith Cowan University on project teams found that the unsuccessful members were concentrating on their own assigned tasks rather than contributing to the group's outcome — they were not idle, they were busy on the wrong thing. That reframe matters if you have been quietly assuming your teammates are coasting. The countermove is to start every update with the shared outcome rather than your own progress, which tends to pull other people's updates into the same frame. ### 5. Information stops at the edge of each person's job Silo working is genuinely distinct from poor communication, and confusing the two wastes effort. In a silo the information exists and simply does not cross a boundary, either because nobody thought to send it or because holding it is convenient. Sources consistently name it as one of the heaviest drags on team productivity. Because the transmission is not the problem, communicating more clearly into the silo changes nothing. What works is changing what crosses the boundary by default — a shared running note that everyone can read without asking. ### 6. Commitments get broken and nobody mentions it A deadline passes without comment, the team silently reroutes around it, and the resentment goes into a private ledger instead of a conversation. Sources tie the failure to establish clear [norms of accountability](/knowledge/teamwork/peer-accountability/) directly to that resentment, which then degrades the team further. Raising it is uncomfortable, which is exactly why it gets delayed until it is a grievance rather than a correction. Say it early, keep it specific, and keep it about the commitment rather than the person: what was agreed, what happened, what you need next time. ### 7. Trust is gone and everyone is checking everyone Once people stop believing colleagues will deliver, they start monitoring, duplicating and hedging, and the team pays for the same work twice. The peer-reviewed study of Lencioni's model describes the mechanism in reverse: cognitive trust reduces the need for monitoring, and reduced monitoring in turn reduces loafing, because members feel a professional obligation to people who are visibly counting on them. That means the trust problem and the uneven-workload problem are frequently the same loop observed at different points — and the only end of it you control is [your own reliability](/knowledge/teamwork/build-trust-at-work/). ### 8. A disagreement became personal Teams need disagreement; what they cannot absorb is disagreement that migrates from the topic to the person. Once it does, sources describe it escalating into a genuinely toxic environment, with absenteeism, falling productivity and turnover downstream. The signal to watch for is a shift in language from "that approach won't work" to "he never thinks these things through." If you notice it in yourself, name the topic again out loud. If you notice it between two others, the useful intervention is not mediation but restating the actual question they were arguing about. ### 9. Somebody has checked out A member is present and contributing nothing, and everyone quietly reads it as laziness. It is more often lost purpose — they cannot see how their piece matters, or they concluded some time ago that nobody would notice either way. This is where the standard advice is least usable: the top-ranking guides recommend regular one-on-ones and clearer conditions for pay raises and promotion, none of which a peer can offer. What a peer can do is ask, privately and without an agenda, what changed. It is a low-cost question and it is asked surprisingly rarely. ### 10. Distance makes every other problem worse Remote and hybrid work is less a standalone problem than a multiplier. Sources report that team members who are not physically present feel excluded, that emotional tone is lost in writing, that reactions arrive late, and that written messages get read in the worst plausible register. None of that is new dysfunction; it is one of the nine problems above, amplified and harder to spot early. So treat distance as a diagnostic question rather than a cause: which of the nine is it making invisible? Read down that list and most people recognize two or three at once — and notice that the countermove for each is a behavior rather than a policy. Some of those behaviors you will already have; others you have simply never had a reason to practice. Knowing which is which is worth having before the next project rather than after it, and a short [read on your working habits](https://assessment.headwayskills.com/) is a quick way to get it. ## The skills that make a stuck team easier to handle Look back at those countermoves and they share something: not one of them requires authority, and every one of them is a behavior that improves with practice. Three of them carry most of the weight here. **Teamwork** is the diagnostic itself. Trust is not a mood; it is built by being sincere, being reliable, and doing what you said you would do — which is why the reliability problem and the trust problem keep turning out to be the same problem. The same skill covers engaging necessary disagreements without making them personal, committing to decisions you argued against, and addressing a teammate's missed commitment promptly and specifically rather than storing it up. Those are the four moves that most often unstick a team from the inside. **Communication** is what turns "we have a communication problem" into something you can actually do on Tuesday. Leading with your main point so updates stop getting lost, choosing a conversation rather than a message when the subject is sensitive or complicated, and having a repertoire for the awkward moments — voicing disagreement, giving a peer feedback, handling someone who has lost their temper, apologizing properly. It is the difference between naming the symptom and treating it. **Influence** is what you use when you can see the problem clearly and cannot order anybody to fix it. It builds from reliably delivering your own part first, then taking responsibility for a bit more than your job description, then setting the agenda by volunteering to organize, write up or track the thing nobody owns. Prepare by working out what each teammate actually gets out of the change, keep the ask small, and follow up on what people committed to. That sequence is how one junior person restarts a stalled team without a title. The free Job Skills Test measures **twelve work skills** of exactly this kind, these three among them, and it is usually the combination rather than any single one that decides how a team goes. If your team is currently in one of the states above, it is worth a few minutes to [see where you stand](https://assessment.headwayskills.com/) across all twelve — the weakest link is the one where practice will change the most, and it is rarely the one you would have guessed. ## Where this leaves you Some of this may already describe how you work. If you have been the one keeping the list, restating the goal, or asking the quiet person what they think, you have been practicing several of these behaviors without labeling them. The ones you have not practiced are not fixed limits — they are simply things nobody taught you yet, and they are learnable without becoming a different person at work. They also tend to count for more as your responsibilities grow, because the number of people whose work depends on yours only goes up. That is worth knowing now rather than later. And you have already done the part most people skip: instead of waiting for the problem to resolve itself, you went looking for its name. ## Seven minutes to see where your skills stand The only thing left is to find out which of these you already do well and which one is quietly costing your team the most. The Job Skills Test is a **free** self-assessment of your own work skills: it takes about seven minutes, scores you across all twelve, and shows you which ones would make the biggest difference to the team you are on right now. ## 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? Stuck on a team that is not working? Here are 10 common problems in teamwork, what each one actually looks like, and what you can do without being the boss. ### Which Headway skill does this connect to? This guide connects primarily to Teamwork. It also relates to Communication, Influence. ### 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/influence.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/teamwork/problem-in-teamwork/ Preferred summary: "Stuck on a team that is not working? Here are 10 common problems in teamwork, what each one actually looks like, and what you can do without being the boss." ## Change log - 2026-07-07: Content collection version published.