# Awesome Teamwork Is Made of 8 Ordinary Behaviors, Not a Vibe Canonical URL: https://headwayskills.com/knowledge/teamwork/awesome-teamwork/ Markdown URL: https://headwayskills.com/knowledge/teamwork/awesome-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 Awesome teamwork isn't chemistry or luck. Here are the eight behaviors that produce it, what Google's own team research found, and which ones you can start alone. ## Key facts - Title: Awesome Teamwork Is Made of 8 Ordinary Behaviors, Not a Vibe - Category: Teamwork - Primary skill: Teamwork - Related skills: Communication, Professional Behaviors - Primary keyword: awesome teamwork - Source page: https://headwayskills.com/knowledge/teamwork/awesome-teamwork/ ## What this page covers - Awesome teamwork isn't chemistry or luck. Here are the eight behaviors that produce it, what Google's own team research found, and which ones you can start alone. - Practical guidance for awesome teamwork - How this topic connects to Teamwork ## Detailed explanation Awesome teamwork is not chemistry, luck, or a group of unusually likable people. It is a short list of ordinary behaviors: people say the awkward thing, deliver what they promised, know who owns what, disagree on the record and then back the decision, coordinate on purpose, and hand the credit around. Do those and a group starts being described as great. That is a deflating answer if you came here hoping for the spark that brilliant teams supposedly have. It is also the useful one — because Google spent two years looking for that spark, and what it found instead was a list you can act on tomorrow. ## What awesome teamwork looks like from the inside The most careful study of this question is Google's Project Aristotle, launched in 2012 by the company's People Analytics team. Researchers examined 180 of Google's own teams — 115 in engineering, 65 in sales — and measured around 250 attributes, from personality mixes and demographics to how often teammates socialized outside work. Almost none of it predicted anything. What separated the effective teams was five dynamics, in this order of importance: [psychological safety](/knowledge/teamwork/psychological-safety-in-the-workplace/), dependability, structure and clarity, meaning, and impact. Two things in that finding are worth carrying into your own team. First, who is on the team matters much less than how the members interact — the answer lives in behavior, not in the roster you were handed. Second, a poll of more than 6,000 workers found effective teams turning up remote, hybrid, and in person alike; the setup wasn't the variable. What people did with each other was. Here are the eight behaviors that keep showing up. Most are unremarkable to watch, which is why teams that have them rarely feel special from the inside — they just feel like a place where work moves. ## 1. Someone says the awkward thing first Psychological safety was Project Aristotle's runaway leader: can we take risks on this team without feeling insecure or embarrassed? In practice it is small and unheroic. Someone admits they don't understand the brief. Someone questions the plan the most senior person just proposed. Nothing bad happens, and everyone watching files that away. The trap is that a team without this often looks fine. Nobody argues, meetings end on time, and silence reads as agreement rather than calculation. Safety isn't created by announcing that all questions are welcome — it's created by one person going first and paying no price for it, which lowers the cost for whoever was about to stay quiet. ## 2. Commitments land without anyone chasing them Dependability came second in Google's five: can we count on each other to do high-quality work on time? Of everything on this list it is the most observable, and the fastest to read. Trust builds slowly and is hard to assess from inside a group. Whether people deliver what they said they'd deliver shows up within a week. For a quick diagnosis of a new team, watch what happens to the first small commitment someone makes out loud. Does it land on the day it was promised? Does anyone notice if it doesn't? The behavior itself is narrow — say what you'll do and by when, do it, and flag it early when you can't. Narrow, and almost entirely within one person's control. ## 3. Everyone knows who owns what, and who decides Third on Google's list was structure and clarity: are goals, roles, and execution plans clear? Most struggling teams are not confused about the task. They're confused about the standard — nobody agreed what a good outcome looks like, so there's no yardstick for anyone's contribution. The piece that goes missing most often is [decision rights](/knowledge/teamwork/role-clarity/). Groups spend a whole meeting on a question nobody in the room can actually close, then leave with it still open. Awesome teamwork usually starts with an unglamorous conversation: what are we producing, who owns which part, and who calls it when we disagree. ## 4. The work visibly matters to somebody Meaning and impact were the fourth and fifth dynamics, and they are not the same thing. Meaning is the work being personally important to you. Impact is believing it changes something for someone outside the team. A group can have one without the other — a project you care about that nobody uses, or a critical system you find joyless to maintain. Teams that keep their energy make impact visible on purpose: who used the thing, what changed downstream, what the customer said. It costs one line in a status update. Without it, effort goes out with no evidence coming back, and the group quietly stops trying hard. ## 5. Disagreement gets raised, then the whole team commits WeWork's rundown of great teamwork puts [honest feedback](/knowledge/self-awareness/constructive-feedback/) near the center, on the grounds that teams which never hear it stop improving and start competing quietly. The version most people get wrong is what happens after the argument. Two moves make this work. Disagreements stay on the topic instead of becoming a verdict on a person — you can argue hard about an approach without implying anything about the colleague who proposed it. And once the group decides, the people who argued against it implement it properly, without a running commentary. Losing the argument and backing the decision anyway isn't a betrayal of your position. It's the mechanism that lets a team decide anything at all. ## 6. Coordination is scheduled, not assumed When Ford developed the F-150, parallel teams worked on different parts of the truck and met once a month for 18 months, for the single purpose of making sure the pieces would still assemble into one vehicle. Nobody would call a standing monthly integration meeting inspiring. It is, however, the whole reason the thing came together. Most groups skip this, because coordination feels like overhead when everyone is busy inside their own piece. The failure then shows up late and expensively: two people built the same thing, or built two things that don't fit. Awesome teamwork treats the seams between people's work as somebody's job, not as something that sorts itself out. ## 7. Credit goes to the team, out loud Effective teams are consistently described as sharing ownership rather than sorting individual scores, and the everyday version is simply saying who did what, in front of the people keeping track. Naming a teammate's contribution in a meeting costs you nothing and is remembered for a long time. The opposite is rarely dramatic. It's letting a compliment land on you when it belonged to someone else, or narrating shared work in the first person. Do that a few times and people start protecting their contributions instead of pooling them — the exact moment a good team becomes a group of individuals sitting near each other. ## 8. Setbacks get treated as information Great teams encourage people to learn on the job and treat mistakes as part of that, using setbacks to refine how they work rather than to establish who is at fault. The distinction is between asking what went wrong and asking who was wrong. Only the first question produces anything you can use next time. This one compounds. A team that meets its first failure by looking for the cause has just shown everyone that owning up is survivable, which feeds straight back into the first behavior on this list. A team that looks for a culprit has taught everyone to go quiet — and it will hear about the next problem much later than it needed to. ## Which parts of awesome teamwork are yours to start Notice how much of the standard advice here is addressed to whoever runs the team. Create psychological safety. Define the roles. Build the culture. That is a manager's to-do list, and most people searching this are not the manager — they're one member of a team they didn't pick. So it's worth cutting the same eight behaviors a different way. Some need the group to negotiate: the definition of a good outcome, the split of roles, the standing coordination slot. You can propose those, but not install them alone. The rest you can start doing today, without anyone's permission — going first with the awkward question, delivering on the small commitment, [raising the missed deadline](/knowledge/teamwork/how-to-hold-someone-accountable/) at three days rather than three weeks, backing the decision you lost, saying whose work it actually was. If you're not sure which of those you already do well and which you quietly skip, it's worth [checking your own team habits](https://assessment.headwayskills.com/) before deciding the problem sits with everyone else. ## The skills that make a team worth being on Read back over those eight and something is hard to miss: not one of them is a property of a team. They're things individuals do, which a group is then described as having. That also means they're learnable — and a few of them keep recurring under different names. **Teamwork** is the direct one. It's putting the group's common purpose ahead of your own scoreboard: coordinating rather than optimizing your own piece, sharing what you know, being excellent at your role while respecting other people's. It's where trust actually gets built, in the specific forms of being reliable and meaning what you say. And it covers the two hardest moves above — disagreeing constructively and then committing anyway, and holding a teammate to a commitment without turning it into a grievance. **Communication** is what makes any of it visible to other people. Not writing mechanics, but choices: leading with your main point, being brief and direct, adapting to how the person in front of you takes in information, and picking a conversation over a written thread when the subject is sensitive or needs negotiating. A surprising share of team friction is a difficult thing settled in a group chat that should have been a five-minute call. **Professional Behaviors** are the conduct that decides whether people want you on their team in the first place — showing genuine interest and humility, treating everyone impartially, expressing appreciation, being on time. The inverse is even more diagnostic: the behaviors that reliably damage a group are passivity, aggression, arrogance, manipulation, and constant negativity. If a team feels bad and nobody can name why, it's usually one of those. The free Job Skills Test scores all three, along with the other nine work skills the framework treats as buildable rather than fixed. Since a team pulls on all three at once, seeing [where these three stand](https://assessment.headwayskills.com/) is usually the quickest way to work out which one is costing you the most. ## Where your own habits already sit You may recognize parts of this in how you already work — the instinct to flag a slip before anyone asks, or to name a colleague's contribution without thinking about it. That's the raw material, and the rest is practice rather than personality; none of it requires becoming a different person at work. A gap here is just something not learned yet, and it's worth closing on purpose, because the ability to make a group function tends to count for more as your responsibilities grow. It stops being a pleasant quality and becomes the part of the job everything else runs through. The fact that you've read this far, thinking about what you contribute rather than cataloging what your teammates get wrong, already puts you ahead of most of the room. ## Your next seven minutes The only thing left is finding out where your own habits actually sit. The free Job Skills Test is a quick self-assessment that scores you across all twelve work skills — including the teamwork, communication, and professional behaviors behind every behavior on this page — and shows which of them will make the biggest difference to the team you're on right now. It takes seven minutes, and you finish knowing where to put your effort instead of guessing. Have a look at [where your skills stand](https://assessment.headwayskills.com/) and take it from there. ## 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? Awesome teamwork isn't chemistry or luck. Here are the eight behaviors that produce it, what Google's own team research found, and which ones you can start alone. ### Which Headway skill does this connect to? This guide connects primarily to Teamwork. It also relates to Communication, Professional Behaviors. ### 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/professional-behaviors.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/teamwork/awesome-teamwork/ Preferred summary: "Awesome teamwork isn't chemistry or luck. Here are the eight behaviors that produce it, what Google's own team research found, and which ones you can start alone." ## Change log - 2026-07-07: Content collection version published.