# The Characteristics of a Good Team — and Which Ones Are Yours to Supply Canonical URL: https://headwayskills.com/knowledge/teamwork/characteristics-of-a-good-team/ Markdown URL: https://headwayskills.com/knowledge/teamwork/characteristics-of-a-good-team.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 The characteristics of a good team, grouped into five dimensions backed by Google's own team research — and which of them any member can supply alone. ## Key facts - Title: The Characteristics of a Good Team — and Which Ones Are Yours to Supply - Category: Teamwork - Primary skill: Teamwork - Related skills: Communication, Professional Behaviors - Primary keyword: characteristics of a good team - Source page: https://headwayskills.com/knowledge/teamwork/characteristics-of-a-good-team/ ## What this page covers - The characteristics of a good team, grouped into five dimensions backed by Google's own team research — and which of them any member can supply alone. - Practical guidance for characteristics of a good team - How this topic connects to Teamwork ## Detailed explanation The characteristics of a good team are a shared goal everyone actually agrees on, enough trust that people can speak up without weighing the risk first, clear roles and reliable follow-through, disagreement that gets raised rather than avoided, and members who hold each other to what they promised. That much is close to consensus. What the consensus leaves out is the part you probably came for. If you're reading this because your own group has some of that and not the rest — the deadline everyone nodded at and nobody owns, the person who goes quiet instead of objecting — a list of desirable states doesn't help much. The useful question isn't which characteristics a good team has. It's which of them you can supply yourself, starting Monday. ## What actually separates a good team from a bad one The most careful answer to this question came from Google's Project Aristotle, a study launched in 2012 that examined 180 of the company's own teams across roughly 250 attributes, led by Abeer Dubey with researcher Julia Rozovsky. It looked at team composition, personality mixes, seniority, skills, meeting patterns — and its central conclusion is the one worth carrying into your own situation: who is on a team matters much less than how the members interact. That is a genuinely useful finding, because the instinct when a team is struggling is almost always to blame the roster. The people are wrong; the group got unlucky. Project Aristotle points somewhere else — at behaviors, which are changeable, rather than at personalities, which mostly aren't. It identified five dynamics of effective teams: [psychological safety](/knowledge/teamwork/how-to-create-psychological-safety/), dependability, structure and clarity, meaning, and impact, with psychological safety the most important by a clear margin. Read across the trait lists that dominate this topic — Indeed, WeWork, SkillPath, IMD and the rest — and their eight or ten items sort into five recognizable groups. Here is what each one actually consists of, and how to tell whether your team has it. ## A shared goal, not just an assigned task Almost every source agrees that effective teams share a common goal, whether the aim is landing deals, fixing problems faster, or integrating a new system. It sounds like the easiest characteristic to have, which is why it's so often missing. Most struggling student and junior teams have an assigned task — nobody is confused about the brief — but have never agreed on what a good outcome would look like. Those are not the same thing, and the gap between them is where most of the friction later comes from. Project Aristotle splits this into two parts worth keeping separate: meaning, which is the work mattering to you personally, and impact, which is the work mattering to somebody outside the team. A group can have one without the other. The reason this dimension comes first is structural: without an agreed goal, there is no standard against which anyone's reliability or contribution can be judged. Every other characteristic on this list is measured against it. ## Trust and psychological safety Trust is the single most repeated item on this topic, and also the most vaguely described — usually as a climate that a good team somehow has. Psychological safety is the sharper version of the same idea. In Amy Edmondson's construct, as reported through the Project Aristotle work, it means members feel safe taking interpersonal risks with each other: admitting a mistake, asking the obvious question, disagreeing with the loudest person in the room. That definition matters because it isn't the same as comfort or niceness, and top results routinely blur the two. A team where nobody argues can look harmonious and still be failing — which is exactly the situation many group projects are in. Patrick Lencioni's Five Dysfunctions of a Team places absence of trust at the base of its model for the same reason Project Aristotle ranked safety first: everything else is built on it. The part the trait lists underdescribe is how trust is actually produced. Not by team-building events, but by two ordinary behaviors: reliability, meaning you do what you said by when you said, and sincerity, meaning you mean what you say and your actions match it. Both are things one person can do without anybody's permission. ## Clear roles and dependability WeWork and HBS Online both treat role clarity less as one item among ten and more as a precondition for the others: if nobody knows who owns what, accountability and dependability have nothing to attach to. Paired with it is the diversity of skills and perspectives that stops members from duplicating each other's work or quietly competing over the same territory. Dependability was second in Project Aristotle's five, and it's the most testable characteristic on this page. Trust accumulates slowly and is hard to assess from inside; whether people deliver what they committed to can be observed within a week. If you want a fast read on a new team, watch what happens to the first small commitment somebody makes. ## Disagreement that gets raised, then settled IMD names regular, [constructive feedback](/knowledge/self-awareness/constructive-feedback/) as one of the defining traits of high-performing teams, on the grounds that it strengthens accountability and keeps a team improving rather than drifting. This is the item most often mistaken for a defect. Quiet teams read as healthy, but silence is usually a symptom of missing psychological safety rather than evidence that everyone agrees. A good team [disagrees on purpose](/knowledge/teamwork/how-to-disagree-respectfully/). The disagreements stay on the topic instead of becoming personal, and they end in a decision that the whole group then implements — including the people who argued against it. Being on the losing side of a team decision and backing it anyway is not a compromise of principle; it's the mechanism that lets a team decide anything at all. ## Accountability, feedback, and adaptability The last group is the one that operates on the team itself rather than on the work. Sources consistently describe accountability on good teams as collective rather than individual — members accept mistakes together instead of isolating whoever slipped. What they rarely mention is the timing. Saying something early and specifically, while the [missed commitment](/knowledge/teamwork/how-to-hold-someone-accountable/) is still small and unloaded, is what stops it from becoming the resentment that ends the project. "You said Thursday and it's Monday, what happened?" is a different conversation at three days than at three weeks. Adaptability belongs here too: the willingness to change how the team works when conditions change, rather than defending a process that stopped fitting. Together, these are the repair mechanism. When purpose drifts, trust erodes, or roles blur, this is the group of behaviors that catches it. ## Which of these are yours to supply Here is the thing worth noticing about almost every article on this topic: it is written to the person who can change the team's conditions. Create psychological safety. Define the roles. Build the culture. That is advice for a manager, and most people searching this are not one — they're a member of a team they didn't pick, which makes the standard advice quietly unusable. So it's worth cutting the same characteristics a different way. Some of them require the whole group to negotiate: the shared definition of a good outcome, the split of roles, the decision to run things differently. You can propose those, but you can't install them alone. The rest you can simply start doing. Delivering what you said, when you said. Saying the thing you were going to keep quiet about, which is usually the single move that makes it safer for the next person to speak. Raising a missed commitment at three days instead of three weeks. Backing a decision you argued against. Crediting a teammate in front of whoever is keeping score. None of these needs authority, and each of them measurably changes how the group functions — which is precisely what Project Aristotle found when it concluded that interaction outweighs composition. If your team is stuck and you're not sure which of those you already do well and which you skip, it's worth [checking your own collaboration habits](https://assessment.headwayskills.com/) before concluding the problem sits with everyone else. ## The skills behind a team that works Look back over those five groups and something becomes hard to miss: almost none of them is a property of the team at all. They're behaviors, performed by individuals, that add up to something the group then gets described as having. Which means they're learnable — and a few of them recur so often across the list that they're worth naming. **Teamwork** is the most direct. It's the habit of putting the team'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 also where trust actually lives, in the specific form of being sincere and reliable, staying authentic, and forgiving mistakes rather than filing them. And it covers the two hardest moves on this page — disagreeing constructively and then committing to the decision anyway, and holding a teammate to a commitment without making an enemy. **Communication** is what makes any of that visible to other people. Not the mechanics of writing things down, but the choices: stating your main point first, being brief and direct, adapting to how the person in front of you actually takes in information, and choosing a conversation over a written thread when the subject is sensitive or needs negotiating. Half of what goes wrong on stalled teams is a difficult thing settled in a group chat that should have been a five-minute call. It also covers the moments a good team runs on — expressing disagreement, giving feedback, apologizing cleanly when you've dropped something. **Professional Behaviors** are the conduct that decides whether people want you on their team at all. Showing genuine interest and humility, treating everyone impartially, expressing appreciation, being on time. The mirror image is more diagnostic still: the five behaviors that reliably damage a group are passivity, aggression, arrogance, manipulation, and constant negativity. If your team feels bad and you can't name why, it's often one of those, and it's often not the person you'd expect. The free Work Skills Test scores all three of these — alongside nine others that shape almost any job — and takes about seven minutes. Because a team pulls on all three at once, finding [which skill to strengthen](https://assessment.headwayskills.com/) is usually the quickest way to work out where a little practice will change the most. ## Where your own habits stand You may recognize some of this in how you already work — the instinct to flag a slip before anyone asks, or to say the awkward thing in the meeting rather than after it. Those are the raw material, and the rest is practice rather than personality; none of it asks you to become a different person at work. Gaps here are simply things not learned yet, and they're worth closing deliberately, because the ability to make a group function tends to count for more as your responsibilities grow — it stops being a nice quality and starts being the thing the job runs on. The fact that you've read this far, thinking about what you contribute rather than cataloguing what your teammates get wrong, already puts you ahead of most people in the room. So the only thing left is to find out where your own habits actually sit. The free Work Skills Test is a quick self-assessment that scores you across all twelve work skills — including the teamwork, communication, and professional behaviors behind everything above — and shows which ones will make the biggest difference to the team you're on now. Seven minutes, and you'll finish knowing where to put your effort instead of guessing. You can [see where yours stand](https://assessment.headwayskills.com/) 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? The characteristics of a good team, grouped into five dimensions backed by Google's own team research — and which of them any member can supply 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/characteristics-of-a-good-team/ Preferred summary: "The characteristics of a good team, grouped into five dimensions backed by Google's own team research — and which of them any member can supply alone." ## Change log - 2026-07-07: Content collection version published.