# What Makes a Good Team Work — Nine Behaviors You Can Actually Do Canonical URL: https://headwayskills.com/knowledge/teamwork/a-good-team-work/ Markdown URL: https://headwayskills.com/knowledge/teamwork/a-good-team-work.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 What makes a good team work is behavior, not the mix of people. Nine concrete things a team member does - including the three most advice skips. ## Key facts - Title: What Makes a Good Team Work — Nine Behaviors You Can Actually Do - Category: Teamwork - Primary skill: Teamwork - Related skills: Communication, Professional Behaviors - Primary keyword: a good team work - Source page: https://headwayskills.com/knowledge/teamwork/a-good-team-work/ ## What this page covers - What makes a good team work is behavior, not the mix of people. Nine concrete things a team member does - including the three most advice skips. - Practical guidance for a good team work - How this topic connects to Teamwork ## Detailed explanation What makes a good team work is not the mix of people on it but the way those people behave: doing your own part properly, keeping the commitments you make, saying clearly where things stand, making it safe for others to admit mistakes, disagreeing about the work rather than the person, and backing decisions you argued against. If you have ever sat in a group where everyone was capable and the work still went badly, that gap is why. Teams are not good or bad because of who ended up in the room. They are good or bad because of a set of ordinary things members do or skip, most of which have names — and all of which can be practiced. ## What makes a good team work: nine behaviors The most careful research on this points the same way. Google ran a study called Project Aristotle from 2012 to 2014, examining more than 180 of its own teams, and its central conclusion was that who is on a team matters far less than how the members work together. Talent, seniority, tenure and team size all mattered less than behavior. That finding is the reason a list like this is worth reading: if good teamwork came down to composition, there would be nothing for you to do about it. Project Aristotle named five dynamics behind effective teams — [psychological safety](/knowledge/teamwork/how-to-create-psychological-safety/), dependability, structure and clarity, meaning, and impact — with psychological safety by far the most important. The nine behaviors below are what those dynamics look like from the inside, at the level of a single member rather than a manager building the team. The order runs roughly from easiest to hardest. ### 1. Be genuinely good at your own part of the work Almost every article on this topic opens with communication. Start one step earlier. The peer-reviewed work on interdisciplinary teams names an appropriate skill mix as a founding principle: teams function when the roles differ and each one is properly covered, not when everyone contributes a little of everything. Your first contribution to any team is competence in the slice you own. A group of excellent communicators who cannot deliver their own piece is not a good team. Being excellent at your role — and respecting that other people's roles are different from yours, not lesser — is where the rest of this list becomes possible. ### 2. Put the team's result ahead of your own credit The shift here is small in wording and large in practice: from "me" to "we." It means coordinating with people rather than working in parallel next to them. It means doing whatever work the team actually needs, not only the tasks on your own list. It means sharing what you know instead of holding it, and describing outcomes as the team's rather than yours. There is a simple test. When something goes well, listen to which pronoun you reach for first. And ask whether you have ever passed on information that made a colleague look good rather than you. ### 3. Communicate so nobody has to guess where things stand Every top-ranking article on teamwork leads with communication, but few say what team communication actually consists of. Four things, mostly. State your main point first, so people are not decoding you. Give full attention and [listen properly](/knowledge/communication/active-listening-in-communication/) rather than waiting for your turn. Moderate how long you talk, so the quieter members have room to contribute. And choose an actual conversation over a written message whenever the subject is sensitive, complex, or needs negotiating. The most common failure on a struggling team is not rudeness — it is silent divergence, where two people proceed for a week on different assumptions that nobody ever said out loud. ### 4. Do what you said you would do Project Aristotle defines dependability precisely: can we count on each other to do high-quality work on time. Of the five dynamics, it is the one an individual member controls most directly, and the fastest to demonstrate, since delivery shows up within a week. Psychology Today's summary of good team members pairs it with doing your fair share — a matter of plain equity in how the load is carried — and adds the part people underrate: being straightforward, telling others what's what whether the news is good or bad. That includes flagging early when something will be late. A deadline you warn about three days ahead is a scheduling problem the team can absorb. The same deadline missed in silence is a trust problem, and those take much longer to repair. ### 5. Make it safe for people to admit things Psychological safety is the perception that you can be yourself, ask the obvious question, admit a mistake, or challenge someone without it being held against you. Project Aristotle found it the single most important of the five dynamics, and the foundation the other four rest on. Nearly every article treats it as something a leader builds. That is only half true. Psychological safety is produced from the bottom up, by how ordinary members react in the small moments — what happens in the three seconds after someone says they got it wrong, or asks the question everyone else was too embarrassed to ask. React well and the next person speaks up. React badly, even once, and the room quietly closes. You do not need any authority to affect this. ### 6. Disagree openly, without making it personal Good teams do not have less conflict. They have more disagreement about the work and less friction between the people, and the two are easy to confuse. The discipline is to argue about the decision while making it obvious you still respect the person — staying on the topic, not reaching for anything about their character or history. The signal to watch for in yourself is the moment you stop defending your argument and start defending your position. Most advice on this subject stops at "resolve conflict quickly and constructively," which misses the useful half: suppressing honest task disagreement is one of the main things that produces [personal friction](/knowledge/teamwork/conflict-handling/) later. A team where nobody objects is usually not a team that agrees. ### 7. Commit to decisions you argued against Say your piece fully while the decision is still open. Once the team has decided, implement the decision properly — including when it went against you. No quiet foot-dragging, no half-effort, no "I told you so" kept in reserve for later. This is probably the behavior that most cleanly separates a genuinely good team member from a merely pleasant one, and it appears in almost none of the standard characteristics lists, which stop at having a positive attitude. It is also the mechanism that lets a team decide anything at all. Without it, every decision stays permanently open, and the group relitigates the same question for weeks. ### 8. Raise a missed commitment early When someone does not deliver what they promised, say so — directly, specifically, and soon. Not by escalating to a manager first, and not by silently absorbing the extra work and resenting it. This is the hardest item here for anyone early in their career, and the one general advice most consistently avoids. Timing does most of the work. Raised at three days, [a missed commitment](/knowledge/teamwork/peer-accountability/) is a factual question about what happened. Left for three weeks, it reads as a pattern, the conversation carries accumulated frustration, and the other person hears an accusation rather than a question. Be specific about what was agreed and what did not happen, and leave their motives out of it. ### 9. Bring the ordinary behaviors that make you easy to work with The baseline: showing respect to everyone regardless of their role or seniority, showing humility, being genuinely interested in what colleagues are working on, expressing appreciation, being on time, and speaking about absent colleagues exactly as you would if they were in the room. The mirror image is more diagnostic. The behaviors that quietly damage teams are passive non-contribution, chronic negativity, and indirect or manipulative communication — none of which announce themselves as sabotage, and all of which are usually invisible to the person doing them. Nine behaviors is also too many to work on at once, and the ones you skip are rarely the ones you would guess. If you want a read on which of these is actually your weak spot, it is worth [finding your real gap first](https://assessment.headwayskills.com/) rather than trying to improve everywhere. ## The skills underneath a list like this Read back over the nine and notice how few of them are properties of a team at all. Every one is something a single person does, which is also why the same underlying abilities keep surfacing when you sort them into groups. **Teamwork** covers most of the list directly. It is the habit of putting the group's common purpose ahead of your own scoreboard, of being excellent in your own role while respecting other people's, and of building trust by being sincere and reliable rather than by trying to be liked. It also carries the two hardest behaviors above: disagreeing while keeping the disagreement about the work, then committing loyally to whatever the team decides — and holding someone to a commitment without turning it into a grievance. **Communication** is what makes any of that visible to the people around you. Not formatting or etiquette, but the choices that decide whether a team knows where it stands: leading with your main point, listening properly instead of queuing your reply, giving quieter people room, and picking up the phone when a written thread has started going in circles. **Professional Behaviors** decides whether people want you on their team in the first place. Treating everyone impartially, showing humility, saying thank you, arriving when you said you would, not discussing colleagues in terms you would not use in front of them. It is also the skill that names the five patterns that reliably corrode a group — passivity, aggression, arrogance, manipulation, and constant negativity — which is useful precisely because they are hard to spot in yourself. Those three come from different corners of a larger set: the framework tracks twelve workplace skills of this kind in total, and the free Work Skills Test scores you on all of them. That breadth is the practical point here, because a team that is not working often traces back to something filed outside teamwork altogether — which is why it helps to [see the whole picture](https://assessment.headwayskills.com/) rather than assuming the problem is where you first looked. ## Where you already do some of this Some of the nine probably describe you already — the instinct to flag a slip before anyone chases you, or to say the awkward thing in the meeting instead of in the corridor afterward. That is the raw material, and the rest is practice rather than personality. Nothing on this list asks you to become more outgoing, more assertive, or a different person at work, and a gap here is simply something not learned yet. It is worth closing those gaps deliberately, because the ability to make a group function counts for more as your responsibilities grow. And you have already done the step most people skip: you went looking for what a good team is made of rather than for a way to describe the teammate who is annoying you. ## Find out where your own habits sit The only thing left is to see which of these you actually do well and which you skip. The Work Skills Test is a **free** self-assessment of your work skills: it takes about seven minutes, scores you across all twelve, and shows you which ones will make the most difference to the team you are on right now. You finish with a clear answer instead of a guess about where your effort should go. You can [check your own habits](https://assessment.headwayskills.com/) 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? What makes a good team work is behavior, not the mix of people. Nine concrete things a team member does - including the three most advice skips. ### 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/a-good-team-work/ Preferred summary: "What makes a good team work is behavior, not the mix of people. Nine concrete things a team member does - including the three most advice skips." ## Change log - 2026-07-07: Content collection version published.