# Bad Teamwork Examples: The Five Patterns They Fall Into Canonical URL: https://headwayskills.com/knowledge/teamwork/bad-teamwork-examples/ Markdown URL: https://headwayskills.com/knowledge/teamwork/bad-teamwork-examples.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 Most bad teamwork examples fall into five categories that stack on each other. See what each one looks like, and what you can fix from an ordinary team seat. ## Key facts - Title: Bad Teamwork Examples: The Five Patterns They Fall Into - Category: Teamwork - Primary skill: Teamwork - Related skills: Professional Behaviors, Communication - Primary keyword: bad teamwork examples - Source page: https://headwayskills.com/knowledge/teamwork/bad-teamwork-examples/ ## What this page covers - Most bad teamwork examples fall into five categories that stack on each other. See what each one looks like, and what you can fix from an ordinary team seat. - Practical guidance for bad teamwork examples - How this topic connects to Teamwork ## Detailed explanation You email a teammate about something the client needs. They reply "Okay." Four days later nobody has done it, because each of you assumed the other one had. Most bad teamwork examples are that undramatic. They also sort into five categories: broken trust, coordination failures, people putting themselves ahead of the group, disagreement that either never ends or never starts, and commitments nobody addresses. They are not interchangeable. They stack, and the one you can see is rarely the one worth fixing. That last part is what the usual list of warning signs leaves out. ## The five categories behind most bad teamwork examples Search this topic and you get flat lists — nine signs, twelve symptoms, all presented as equals. The one genuinely authoritative structure here is not a list at all. Patrick Lencioni's The Five Dysfunctions of a Team, published in 2002, arranges team failure as a pyramid: absence of trust, fear of conflict, lack of commitment, avoidance of accountability, inattention to results. Each level makes the one above it possible. Trust sits at the bottom because people who do not trust each other cannot argue productively, and a team that cannot argue never commits to anything it can later be held to. That ordering is the practical part. When you recognize your team in one of the categories below, the thing to change is usually a level down from the thing you noticed. ### Trust failures This is the category people describe last and feel first. Commitments get made and quietly missed. Information others need in order to work sits with one person — Quire's breakdown of bad teamwork names the archetype the "Knowledge Hog," someone who amasses and retains what the team needs in order to hold onto power, creating a bottleneck that from outside looks like being indispensable. Concerns about a colleague get raised to everyone except that colleague. What separates trust failures from the rest of this list is that they are usually deliberate rather than accidental, and that no process fixes them. You can add a status meeting to close a coordination gap. There is no meeting that makes people believe each other again. It is also the only category that makes all four below it worse, which is why it sits at the base of the pyramid. ### Coordination and communication failures These produce the story you would actually tell someone: two people who did the same task, or a task nobody did. Chron's account of poor teamwork points at undefined roles — participants unsure of their responsibilities, or unable to identify their place on the team — as a leading cause, alongside the failure to share information in time. The canonical illustration across these sources is the one-word reply. Someone raises a client need, the answer is "Okay," and both parties walk away believing the other is handling it. Nothing in that exchange is careless. It is under-specified, and an under-specified message lets each reader fill the gap with whichever assumption costs them least. That is the useful thing about this category. It happens between people who like each other and are trying, which makes it the most fixable of the five and the most consistently misread as laziness. ### "Me" before "we" Team members who compete against one another rather than toward the shared goal appear on nearly every list of bad teamwork examples, usually described as losing sight of the big picture. In practice it is less dramatic than rivalry. It is credit that quietly attaches to one name, work that stops exactly at the edge of a job description, and someone doing the minimum on the assumption that the group will carry it. The distinguishing feature is the gap between how this looks and how it feels. Almost nobody experiences themselves as putting their own interests first. They experience themselves as ambitious, or efficient, or finished. That makes this the category most worth checking yourself against, because the internal evidence is misleading in a way it is not for the others. ### Disagreement failures This one has two opposite faces. Evolve3's rundown of poor-teamwork signs lists conflict without resolution — the same dispute recurring, never settling, drifting from the issue to the person. Its mirror image is on the same list: ineffective meetings where contributions are limited and nobody raises anything, after which the real objections circulate privately. Both are the same failure. The first is disagreement that stopped being about the work. The second is disagreement that never made it into the room. What defines this category is that too little is as damaging as too much, which is why "we don't have conflict on our team" is rarely the good news it sounds like. Evolve3 notes what follows: a scarcity of new ideas. A team that cannot disagree cannot reach a better answer than the first one proposed. ### Accountability failures The last category is made of things that do not happen. A deadline slips and nobody mentions it. A decision gets made and quietly not implemented. Someone's attitude sours and the mood spreads — attitude on a team is contagious, as Chron puts it, and one person's can permeate the rest — while everyone waits for someone else to name it. Failure by omission is the hardest kind to raise, because there is no incident to point at, only an accumulation. It is also the level furthest from where the repair usually belongs. Teams rarely avoid accountability because they lack nerve. They avoid it because they never committed to the decision in the first place, having never voiced the disagreement that would have made the commitment real. ## What this costs beyond the delays you can see Lateness is the visible price. The costs underneath it are larger and harder to attribute. Articles covering the price of poor teamwork keep returning to the same three: rework after decisions made on bad information, duplicated effort because two people were not talking, and procrastination driven by fear of being judged for getting something wrong. Evolve3 adds low engagement and a shortage of new ideas. None of that appears on a project plan, which is part of why teams tolerate it for years — and part of why the situation feels unfixable when it usually isn't. Every one of the five categories has a move available to an ordinary member of the team. ## What you can do without being the manager Most writing on this topic hands the fix to whoever can redefine roles or run a workshop. The advice aimed at individuals is narrower and more consistent. Youth Employment UK and Forbes both land in the same place: talk to the person directly, and early. Be candid, be courteous, don't circle the point. Escalating first — to a manager, a tutor, a team lead — is slower and reliably worse, because it converts a workable conversation into a formal complaint. If the direct route fails, then you escalate, and you bring specific factual examples rather than a characterization. The second move is less comfortable. There is real search demand behind The Muse's piece on the signs you are not pulling your weight and people know it, which suggests a fair number of people reading about bad teams are quietly wondering about their own part in one. Given how misleading the internal evidence is for the third category, it is worth checking [how your own habits score](https://assessment.headwayskills.com/) before concluding the problem is entirely other people. Being wrong about that is recoverable. Not checking is what makes it expensive. ## The skills that make a bad team easier to handle Look at what those moves actually require and the organizational content thins out fast. Naming a missed commitment, saying the hallway sentence in the room, writing down who you think owns what — none of it is a process change. It is a small set of behaviors, and the same ones keep resurfacing under different category names. **Teamwork** is where the five categories came from in the first place. Each names a piece of it that has gone missing: complementary roles left unassigned, common purpose losing to a personal agenda, reliability that stopped being predictable, disagreement that either turned personal or never surfaced, and the habit of raising a missed commitment promptly and specifically instead of letting it sit. Read that way, "we have a teamwork problem" becomes a question with an answer — which part, and what does the person in your seat do about it. **Professional Behaviors** supplies the vocabulary for what you are facing one person at a time. The behaviors that damage a team sort into five: passive (not contributing), aggressive (making it personal), arrogant, manipulative (indirect communication and rumor), and negative (complaint as the default register). Working out which one is actually in front of you beats concluding the team is toxic, since each calls for a different response — and honestly checking which one you drift into under pressure is more useful still. **Communication** is where most of these get repaired, and not by doing more of it. The moves are narrow: leading with the main point instead of burying it, choosing a conversation over a message when the subject is sensitive or complicated, saying the thing rather than assuming someone else will, and handling the hard cases that define a struggling team — expressing disagreement, defusing someone who has stopped being reasonable, apologizing when the miss was yours. That "Okay" reply is a communication failure wearing a teamwork costume, and so are half the examples you would list. Which of the three you can already lean on matters more than which one your team is short of, because it decides where your leverage is. Seven minutes on the free test that maps them — twelve work skills in total, these three among them — and [finding your strongest one](https://assessment.headwayskills.com/) tells you which move to make first. None of the three is temperament. They are behaviors nobody has taught you yet. ## If some of this sounds like you You may have recognized more than one category on that list, and not only in other people. That is the ordinary result of reading five descriptions of how teams fail — a couple of them point back. None of it is fixed. These behaviors go unlearned because nobody teaches them, which is exactly what keeps them changeable, and closing a gap in one doesn't require becoming a more forceful or less easygoing version of yourself at work. What does shift is the weight. The more your work runs through other people, the more a team's dysfunction stops being something someone else should solve and starts being yours to navigate. Better to know which of these behaviors is your thinnest while you are one voice on a small team than when you are the person everyone is waiting on. You have already done the part most people skip. You read the list against yourself, not only against your colleagues. ## Find out which one is your thinnest The only thing left is working out which of these behaviors is already going for you, and which one is quietly costing you on the team you are on right now. The Job Skills Test is a **free** self-assessment of your work skills. It takes about seven minutes, the results appear immediately, and it gives you a profile across all twelve — teamwork, communication, and professional behavior among them — so you can see where you are strong, where the real gap sits, and which single skill would change the most about the team situation you have been reading this for. ## 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? Most bad teamwork examples fall into five categories that stack on each other. See what each one looks like, and what you can fix from an ordinary team seat. ### 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-examples/ Preferred summary: "Most bad teamwork examples fall into five categories that stack on each other. See what each one looks like, and what you can fix from an ordinary team seat." ## Change log - 2026-07-07: Content collection version published.