# Bad Teamwork: 9 Examples and What You Can Do About Them Canonical URL: https://headwayskills.com/knowledge/teamwork/bad-teamwork/ Markdown URL: https://headwayskills.com/knowledge/teamwork/bad-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 Bad teamwork follows recognizable patterns: free riding, unclear roles, silent meetings, blame. Nine examples, and what you can do without any authority. ## Key facts - Title: Bad Teamwork: 9 Examples and What You Can Do About Them - Category: Teamwork - Primary skill: Teamwork - Related skills: Professional Behaviors, Communication - Primary keyword: bad teamwork - Source page: https://headwayskills.com/knowledge/teamwork/bad-teamwork/ ## What this page covers - Bad teamwork follows recognizable patterns: free riding, unclear roles, silent meetings, blame. Nine examples, and what you can do without any authority. - Practical guidance for bad teamwork - How this topic connects to Teamwork ## Detailed explanation The status meeting ends, everyone says the plan is fine, and then in the hallway three people tell you it isn't. Bad teamwork is what happens when a group's shared purpose gets displaced by unclear roles, unspoken disagreement, and uneven effort. It shows up as duplicated work, missed deadlines, hoarded information, and quiet resentment — and the causes are usually structural rather than a matter of lazy people. You are almost certainly not imagining it. And the pattern is more specific than it currently feels. ## What bad teamwork looks like from the inside Nearly every article on this topic is written for whoever can fix it structurally — redefine roles, set ground rules, run a workshop. If that isn't you, the advice describes a door you can't open. So each of the nine patterns below comes with the part that stays available from an ordinary seat on the team. One thing to hold onto first. Across the sources that catalog this, including Quire's breakdown of poor teamwork, the agreed root causes are unrealistic expectations, misaligned goals, unclear roles, and unmanaged conflict — explicitly not laziness. In most cases the people around you are responding sensibly to a badly shaped situation. ### 1. Someone isn't pulling their weight — and that's two different problems The most-reported example of bad teamwork hides a distinction that changes what you should do about it. Asana and Leadership IQ both separate two behaviors that look identical from outside: free riding is a deliberate calculation that your effort isn't needed for the group to succeed, while social loafing is an unconscious slackening caused by responsibility being spread thin across a group. Free riders choose not to contribute. Social loafers don't realize they're doing less. Approach a social loafer as though they made a choice and the conversation turns defensive over something they never intended. **What you can do:** work out which one you're looking at before you say anything. The documented conditions that produce loafing are structural — anonymity, group size, and contributions nobody can tell apart — so making one specific piece of work visibly theirs often solves it without a confrontation at all. ### 2. The people who were pulling their weight quietly stop What happens next is documented and predictable. Rather than absorb the extra load indefinitely, the reliable members reduce their own effort to match. Behavioral researchers call it the sucker effect, and it is the mechanism by which one person's non-contribution degrades an entire team. Nobody announces it; effort just reprices itself downward. **What you can do:** notice whether you're already in that slide. Covering for someone is not the neutral, generous act it feels like — it's an unstable position that usually ends with the coverer withdrawing rather than the loafer stepping up. Treat your own resentment as information about the team's design, not as a character flaw. ### 3. Nobody is quite sure who owns what [Unclear role definition](/knowledge/teamwork/role-clarity/) is the most cited root cause in the research, and it's peculiar because it produces two opposite failures simultaneously: the same task done twice by two people, and a task nobody did because each assumed the other had it. The visible symptom is missed deadlines, which is why teams typically respond by adding status meetings — a fix aimed at effort when the defect is in allocation. **What you can do:** write down what you believe you own and what you believe others own, and send it to the team as a question rather than a statement. Being wrong in writing is cheap and fast. Being wrong silently costs weeks. ### 4. The meeting where nobody says the real thing Contributions are limited, the time goes on restating rules or reading updates aloud, and the actual conversation happens afterward in a hallway or a private message thread. Ineffective meetings appear on nearly every diagnostic list of poor teamwork, but the useful signal is narrower than "that meeting was bad." It's the gap: when what people say after the meeting differs from what they said in it, disagreement is being avoided rather than being absent. Avoided disagreement doesn't evaporate — it returns later as passive resistance to whatever got decided. **What you can do:** be the person who says the hallway sentence in the room. Once, on something small, to find out whether the room can hold it. ### 5. Everything routes through one person The "Knowledge Hog," as one guide to bad team members labels the archetype, holds the information, access, or context everyone else needs, so work queues behind a single person and moves at their pace. Sometimes it's deliberate job protection. More often nobody ever asked them to write anything down. This one is hard to raise because the bottleneck looks like the most valuable person on the team — heavy demand for someone reads as competence rather than as a single point of failure. It's also the symptom most likely to be misread as your own incompetence, since being blocked repeatedly feels like not knowing enough. **What you can do:** document what you learn each time you get unblocked, so the next person doesn't have to stand in the same queue. ### 6. Cliques form and gossip goes up Accounts of failed teams converge on the same language: factions form, lines get drawn, communication stops, suspicion rises, and past that point collaboration is close to impossible. What's worth noticing is that cliques and [a rise in gossip](/knowledge/professional-behaviors/workplace-gossip/) are listed as early warning signs, not late-stage ones. That reframes what gossip actually is. It's frustration that has gone underground, appearing precisely where people have grievances and no safe route to raise them directly — a signal about the team's structure rather than about the character of the people talking. **What you can do:** speak about absent colleagues the way you would if they were standing there. It's unglamorous and it works, because it makes you the person others can be candid with at no cost to themselves. ### 7. One person is carrying far too much Some people are perpetually working late while others visibly have time. It's a standard entry on every diagnostic list, and the cause is usually unremarkable: the reliable person is the easiest person to ask, so they keep getting asked. Every top article frames this as something to escalate to a manager, and none of them address the overloaded person's own contribution to it — that they have never said no, so nothing in the team's feedback loop indicates a problem exists. If you recognize yourself there, it's worth getting an honest read on [where your own habits sit](https://assessment.headwayskills.com/), because this is one of the few patterns on the list you can change unilaterally. **What you can do:** decline one thing this week, with a reason and an alternative attached. ### 8. Everyone agrees, and then nothing happens A decision gets made, nobody objects, and implementation quietly fails to occur. This is usually diagnosed as a follow-through or project-management problem, and it isn't. It's a breakdown at both ends of "disagree and commit": the [disagreement was never voiced](/knowledge/teamwork/how-to-disagree-respectfully/), so the commitment was never real. People who stayed silent about their objection don't carry out what was decided, because privately they never agreed to it. **What you can do:** say it before the decision, then implement the decision loyally whether or not it went your way. Doing both is the whole skill — either half on its own is what a struggling team already does. ### 9. Blame arrives instead of accountability When something breaks, the conversation is about who is at fault rather than what failed. Missed commitments go unmentioned for weeks, then surface as personal criticism long after the moment has passed. [Holding each other accountable](/knowledge/teamwork/how-to-hold-someone-accountable/) and blaming each other feel similar to do, which is how teams slide from one into the other without noticing, but they are opposites: accountability is specific, prompt, and about a commitment, while blame is vague, delayed, and about a person. **What you can do:** raise the missed commitment within a day or two, name the commitment rather than the pattern, and let it go once it's addressed. Speed is most of what keeps it from turning personal. ## The skills that make a difficult team easier to handle Read back over those nine and something is hard to miss: almost none of the available fixes are organizational. They're behavioral, and it's the same short list of behaviors recurring under different names. **Teamwork** carries most of the weight here. Every symptom above maps onto a specific part of it having gone missing — duplicated effort is complementary roles left unsorted, hoarded information and grabbed credit are "me" beating "we", unnamed missed commitments are the accountability habit absent, silent meetings are necessary disagreement being ducked. Working out which part has failed converts a vague bad feeling into something you can act on: in yourself first, then carefully with a teammate. **Professional Behaviors** covers what the research describes at team level but you experience one person at a time. There's a usable taxonomy of what goes wrong — passive (not contributing), aggressive (making it personal), arrogant, manipulative (indirect communication and rumors), and negative (complaint as a default register). Identifying which of the five you're actually facing beats concluding that the team is toxic, and honestly checking which one you slip into under pressure is more useful still. **Communication** is where most of these get repaired, in a much narrower sense than "communicate more." It's choosing a conversation over a written message when the subject is sensitive or complex, leading with the main point, speaking up instead of assuming someone else will, and handling the specific hard cases that define a bad team: expressing disagreement, defusing someone who's angry, apologizing when the miss was yours. None of these is a temperament you either have or don't. The fastest way to find out [which ones you're strongest in](https://assessment.headwayskills.com/) is the free test — seven minutes, and it maps a full set of twelve work skills, so teamwork and the two above arrive with context instead of in isolation. Most people are surprised by which one turns out to be the real gap. ## Where that leaves you Some of this probably already describes how you work. Most people reading nine descriptions of a failing team find that a few point back at their own habits as well as at everyone else's — the covering, the silence in the meeting, the thing they meant to say and didn't. That isn't a verdict. Gaps in this kind of skill are the ordinary result of never having been taught them, they're changeable, and closing them doesn't require becoming a different person at work. The pull does grow, though: the more your work depends on other people, the more a team's dysfunction becomes yours to navigate rather than someone else's to solve — which is exactly why it's worth knowing which of these behaviors is your weakest now, while the stakes are still small. You've already done the part most people skip. You checked yourself against the list, not only your colleagues. ## See where your own skills stand The only thing left is finding out which of these are already working for you, and which one is quietly costing you in a team like this. The Work Skills Test is a **free** self-assessment of your work skills. It takes about seven minutes and gives you a profile across all twelve — teamwork, communication, and professional behavior among them — so you can see where you're strong, where the real gap is, and which single skill would make the most difference to the team you're 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? Bad teamwork follows recognizable patterns: free riding, unclear roles, silent meetings, blame. Nine examples, and what you can do without any authority. ### Which Headway skill does this connect to? This guide connects primarily to Teamwork. It also relates to Professional Behaviors, Communication. ### 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/professional-behaviors.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/teamwork/bad-teamwork/ Preferred summary: "Bad teamwork follows recognizable patterns: free riding, unclear roles, silent meetings, blame. Nine examples, and what you can do without any authority." ## Change log - 2026-07-07: Content collection version published.