# Good Teamwork and Bad Teamwork: The 8 Differences You Can Actually See Canonical URL: https://headwayskills.com/knowledge/teamwork/good-teamwork-and-bad-teamwork/ Markdown URL: https://headwayskills.com/knowledge/teamwork/good-teamwork-and-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 Good teamwork and bad teamwork rarely differ in personality — they differ in eight observable behaviors. Here's what separates them, and what you can change. ## Key facts - Title: Good Teamwork and Bad Teamwork: The 8 Differences You Can Actually See - Category: Teamwork - Primary skill: Teamwork - Related skills: Professional Behaviors, Communication - Primary keyword: good teamwork and bad teamwork - Source page: https://headwayskills.com/knowledge/teamwork/good-teamwork-and-bad-teamwork/ ## What this page covers - Good teamwork and bad teamwork rarely differ in personality — they differ in eight observable behaviors. Here's what separates them, and what you can change. - Practical guidance for good teamwork and bad teamwork - How this topic connects to Teamwork ## Detailed explanation You can usually feel it before you can name it: the meeting where everyone agrees and nothing moves afterward, or the week two people quietly did the same piece of work. The difference between good teamwork and bad teamwork isn't the people involved — it's a set of observable behaviors: whether roles are clear, whether problems get raised in the room or in the corridor, whether commitments hold, and whether disagreement stays about the work rather than the person. That is the useful part. You can't audit a personality, but you can watch what a team does in the week after something goes wrong — and that is exactly where the two versions stop resembling each other. ## 8 differences between good teamwork and bad teamwork None of these are ranked, and no real team sits cleanly on one side of all eight. Read them against your team, then against your own behavior — the half this kind of advice usually skips. Most writing on the subject is aimed at whoever can restructure the team. If that isn't you, the more useful question is which of these you can move on your own. ### 1. Roles are clear — or nobody is quite sure who owns what In the good version, people can say who owns which piece of work and what "finished" looks like for it. Google's Project Aristotle, its internal study of what separated its effective teams, named structure and clarity as one of five dynamics behind them: members know their responsibilities and what they are aiming at. The bad version finds the gaps late — two people have done the same work, or a decision sat for two weeks waiting on an owner who was never appointed. Role confusion is hard to catch because it doesn't feel structural from the inside. It feels like friction between people, so teams diagnose a personality problem and fix the wrong thing. ### 2. Problems get raised in the room — or in the corridor afterward Between 2012 and 2014, Project Aristotle examined roughly 180 Google teams against more than 250 attributes — personality, skill level, seniority, leadership style — looking for the right mix of people. What it found instead was that who was on a team mattered far less than how the team worked together, and the strongest single differentiator was psychological safety: whether members could raise an idea, admit a mistake, or disagree without fear of embarrassment or punishment. That makes this the most checkable line on the list. In a good team the difficult thing gets said while everyone is still in the room. In a bad one the meeting is quiet, and the real objection surfaces afterward in a conversation between two people. ### 3. Commitments hold — or things slip and nobody says anything Dependability sits directly beneath psychological safety among Project Aristotle's five dynamics, and it is the difference most visible from outside: poor teamwork shows up in delays, flat morale, and people leaving long before anyone names teamwork as the cause. But every team misses things. The divide is what happens next. In good teams a dropped handover gets raised directly, early, and specifically, by the person it affected. In bad ones it gets absorbed in silence, discussed with everyone except the person responsible, or escalated straight to a manager — which usually reads as a breach of trust even when the complaint underneath it is completely fair. ### 4. Disagreement is about the work — or about the person, or missing entirely Effective teams don't avoid conflict; they address it directly and close it quickly instead of routing around it. Bad teamwork fails at this in two opposite-looking ways. One is disagreement that turns personal, where the argument stops being about the decision and becomes about who is being difficult. The other is a team where nobody visibly disagrees about anything. The second looks pleasant and is usually the worse sign, because it shares a root with the corridor conversation above: people have worked out that saying the hard thing costs more than staying quiet. ### 5. Decisions get implemented — or quietly relitigated Good teams do their arguing before a decision and their committing after it. Everyone gets to object while it's open; once it closes, everyone implements it, including the people who lost. In bad teamwork the sequence inverts — agreement in the room, dissent afterward, expressed through slow or partial execution rather than words. This is the entry most invisible to the person doing it. Withholding commitment rarely feels like disagreement from the inside; it feels like being busy, or unconvinced, or waiting for more information. Worth checking whether there's a decision you agreed to this month that you haven't actually acted on. ### 6. Information moves to whoever needs it — or sits in silos Failing to share relevant information in time, and failing to coordinate around what other people need, is named across sources as the largest single obstacle to team effectiveness — usually as silos, sometimes as cliques, where an in-group leaves other members outside what's being discussed. Team research points to a specific habit on the good side: closed-loop communication, where whoever receives a message confirms back what they understood instead of both parties assuming. Note the direction of cause, because it changes your response — information usually goes missing because roles are unclear or it isn't safe to speak, not because someone is hoarding it. ### 7. Credit goes to the team — or gets captured Strong teams treat what is good for the team as good for its members, and say so out loud when work goes well. The recurring character on the other side is the opposite: someone who pursues recognition in a way that actively disrupts the team's work, taking the visible half of a joint effort while the rest stays anonymous. The cost runs past the resentment. Credit capture is the quickest way to stop information moving, which loops straight back to the point above — people stop volunteering the half-formed idea or the early warning once they've seen what happens to it. ### 8. People back each other up — or compete internally Backing-up behavior — noticing a teammate is overloaded and stepping in without being asked — is one of the observable markers team researchers use to identify effective teams, alongside monitoring how the work is going and giving each other feedback on it. The bad version is members competing with one another and losing the shared goal in the process. One caveat: internal competition is often structural rather than personal, built into individual targets or how recognition gets handed out, and you can't redesign that from below. What you can do is decline to play it, which is more visible to everyone else than most people expect. Most of the eight can be moved without a title. You can make your own commitments legible, ask the question nobody asked, confirm back what you understood, pass credit across, cover for someone having a bad week. The harder part is seeing your own share of the pattern, since nobody watches themselves in a meeting the way they watch everyone else — which is where an outside read on [how you work with others](https://assessment.headwayskills.com/) beats your own estimate. And none of it is fixed. These are habits, and habits move. ## The skills underneath the good version Read back over the eight and notice how few are about ability. Almost every difference sits in what people do with each other — what gets said when something slips, how a disagreement is handled, where information ends up. Those are habits, and they have names. **Teamwork** is doing most of the work here. It's less about liking your colleagues than about a few concrete commitments: being good at your own role and respecting other people's, putting the team's purpose ahead of your own visibility, being reliable enough that others can plan around you, disagreeing while a decision is open and then implementing it loyally once it's closed, and telling a teammate directly when they've missed something rather than waiting for someone senior to notice. Every entry above is one of those commitments held or dropped. **Professional Behaviors** covers the conduct half — the part of bad teamwork that is one person's behavior rather than the team's design. The failures are a recognizable short list: staying passive and contributing nothing, attacking when challenged, treating your own judgment as obviously superior, working through hints and rumors instead of saying things plainly, and complaining as a default setting. The counterparts are just as concrete: genuine interest in what colleagues are doing, thanking someone who covered for you, speaking about people as though they were in the room. Read that list against yourself before you read it against anyone else. **Communication** is what "poor communication" means once you unpack it — not eloquence, but timing and clarity. Leading with the main point so people can act on it. Choosing a conversation over a message when the topic is sensitive or complicated. Listening with a real intent to understand rather than to reply. Being able to disagree, give feedback, or apologize without the exchange going sideways. More talking isn't the fix; a team can meet constantly and still leave everyone unsure what was decided. Teamwork is a hard one to judge from inside, because your evidence is mostly your intentions while everyone else's is your behavior. A short, free self-assessment gives you a starting read on it — and on the eleven others the framework treats as **learnable rather than fixed** — so you can [see which ones need work](https://assessment.headwayskills.com/) first instead of guessing. Some of those eight probably read as things you already do: the person who says the quiet thing in the meeting, or who checks back that they understood a handover correctly. Others may have landed less comfortably. Both are useful. Either way, you've just spent this article describing a team in behaviors instead of personalities — which is the move most people skip, and the one that makes any of it changeable rather than something you're stuck with. The habits you don't have yet are learnable, and building them doesn't require becoming a different person at work. They also carry more weight as you take on more: the more your work depends on other people, the more of your day runs on which version of a team you're standing in. ## Where to start with your own half of it You know what to look for now; the open question is where your own habits sit. The **free** Job Skills Test is a short self-assessment of your work skills — you answer for yourself, and it shows you where you stand across all twelve, including the teamwork, conduct, and communication habits that decide which version of a team you end up in. It won't tell you what your colleagues think. It will tell you which one or two are worth your attention first, which is usually enough to start with. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, takes about 7 minutes, and your results appear as soon as you finish.* ## 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? Good teamwork and bad teamwork rarely differ in personality — they differ in eight observable behaviors. Here's what separates them, and what you can change. ### 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/good-teamwork-and-bad-teamwork/ Preferred summary: "Good teamwork and bad teamwork rarely differ in personality — they differ in eight observable behaviors. Here's what separates them, and what you can change." ## Change log - 2026-07-07: Content collection version published.