Learn About Teamwork: The 8 Behaviors That Make a Team Work

To learn about teamwork is to learn a set of specific behaviors, not a personality type: doing what you said you would, making it safe to admit mistakes, sharing airtime, getting clear on who owns what, disagreeing without making it personal, and speaking up when a commitment slips. Every one of those is practiced, and none of them asks you to become a more sociable person.

That is a narrower answer than most explanations give. The common ones describe what a good team looks like from the outside — trust, shared purpose, camaraderie — which is accurate and close to useless if you are one member of a group project or a new team trying to work out what you should actually do differently. There is a reason the outside view dominates, and it has to do with how teams have mostly been studied.

What teamwork actually is

Team effectiveness has been researched for over fifty years, and the George Washington University Himmelfarb research guide on the subject reports that the same three dimensions keep surfacing: productivity, participation, and camaraderie. Those are real findings, but notice what they describe — the state of a group, not the actions of a person inside it. That gap is why so much teamwork writing feels unusable to an individual reader.

The exception is worth knowing. Stevens and Campion’s 1994 typology, cited in the National Academies’ review of team effectiveness research, split individual teamwork competence into two dimensions: interpersonal knowledge and self-management knowledge. The first half is what everyone expects. The second is the part almost nobody is taught — that a real share of being good in a team is what you do alone, with your own commitments and your own reactions, before anyone else is involved.

Eight behaviors to learn about teamwork

Each of these has a research finding under it rather than a virtue word. Read them as things to try, not as a description of who you already are.

1. Doing what you said you would

When Google ran Project Aristotle, its study of 180 of its own teams, dependability came out second among the five dynamics separating effective teams from ineffective ones — behind only psychological safety, ahead of structure and clarity, meaning, and impact. It ranks that high because the rest of a team is built on top of it: a group cannot coordinate around someone whose commitments are provisional. The learnable part is not heroic follow-through at the deadline. It is being careful at the moment you accept work — what is actually being asked, when it is genuinely due, what finished looks like — so the commitment is one you can keep.

2. How you react when someone admits a mistake

Project Aristotle put psychological safety first of its five dynamics: whether members believe they can raise a question, float a half-formed idea, or own an error without being embarrassed for it. It is tempting to file that as something managers arrange. The research describes it as a property of shared norms — the way members treat one another — which puts every member inside it. Your share is mostly reactive and mostly small: what your face does when a colleague says they got something wrong, and whether the next thing you say is a question or a joke at their expense.

3. Noticing how much airtime you take

One of Project Aristotle’s more concrete findings was that high-performing teams showed roughly equal conversational turn-taking and high social sensitivity — members were tuned in to each other’s cues. This is the most measurable item on the list. Across a meeting you can notice whether you spoke five times or fifteen, whether anyone has said nothing at all, and whether you finished someone’s sentence for them. Talking less is not the point; the point is that the distribution stops being accidental. Teams lose their quietest members’ contributions silently, and nobody reports it.

4. Asking who owns what, before it matters

Structure and clarity ranked third among Project Aristotle’s dynamics, and the George Washington University guide adds an uncomfortable detail: members frequently lack the clarity about goals and responsibilities that leadership assumes they have. That gap is rarely closed from above, because the person in charge cannot see it. It gets closed by someone asking a question that feels too basic to ask — who is doing this part, by when, and what counts as done. Group projects fail on this far more often than they fail on effort.

5. Treating disagreement as a process

The characteristics that recur in accounts of effective teams include frank and frequent critique and fair decision-making — disagreement as routine rather than rupture. That is one skill with two halves, and the halves usually get separated. The first is raising the objection while it still matters, keeping it on the substance and off the person. The second is what you do once the decision goes the other way: implement it properly regardless. Disagreeing and then quietly under-delivering is the version that damages a team, and it is the more common one.

6. Saying something when a commitment slips

Accountability sits in nearly every description of strong teams — defined roles, accountability, clear and proactive communication is the standard triad — and it is almost always read as accountability for your own work. The harder half is raising it when someone else’s commitment slips. Early on, the options feel like silence, absorbing the extra work, or escalating to a manager. The alternative is smaller and more awkward than any of those: say it directly and soon, and be specific about the commitment and its effect rather than about the person.

7. Working with people whose methods aren’t yours

The National Academies’ review reports a pattern worth expecting: teams with heterogeneous members take longer to begin working together effectively, but performance generally improves as members grow familiar with one another. The friction is the normal early phase, not evidence that the team is broken. Knowing that changes what you do in week two of a group project, when someone’s approach looks inefficient and the temptation is to route around them. Assuming competence and asking how they work is usually faster than the workaround.

8. Managing yourself, not just the group

This is the half of Stevens and Campion’s typology that rarely makes any list: self-management knowledge, standing alongside interpersonal knowledge as its own dimension of individual teamwork competence. In practice it covers how you plan your own portion, how you keep track of what you owe other people, and how you handle yourself when the work goes badly. It is invisible from the outside, which is exactly why it gets dropped — and why someone can be warm, well-liked, and still hard to work with.

The fastest way to learn teamwork

You cannot learn eight behaviors at once, and you cannot learn any of them by reading. All eight are practiced in the same place: a real group with real stakes — a class project, a part-time job, a first team. What reading gives you is names for things you would otherwise experience as vague friction, and that is worth something, because a behavior you can name is one you can catch yourself doing.

So the honest first move is narrower than “get better at teamwork.” Most people already do three or four of these without thinking about it and quietly steer around one or two — usually number six. Working out which is which is worth doing deliberately rather than by guesswork, so it is worth seeing where your teamwork stands before you pick something to practice.

The skills that make a team easier to work in

Read back over the eight and something becomes hard to miss: hardly any of them is about teams as such. They are a few underlying capabilities that happen to be most visible when other people are in the room.

Teamwork is where most of the list lives, and as a skill it is more specific than the word suggests. It covers the trust-building behaviors — meaning what you say, doing what you committed to, forgiving people rather than keeping a record — and the moves that introductions to the topic skip: raising a necessary disagreement without making it personal, committing to a decision you argued against, telling a teammate directly that something slipped. Held that way it stops being a quality you either have and turns into something you practice on a particular team in a particular week.

Communication is what makes several of these behaviors visible to anyone else. Giving someone your full attention instead of composing your reply, moderating how long you talk, managing interruptions, stating your main point first so people can act on it — that is what “good communicator” resolves into once you look closely. It also carries the moments that decide how a disagreement lands: how you voice one, how you give a colleague feedback, and how you apologize when the mistake was yours.

Professional Behaviors are the ordinary conduct that makes a group workable in the first place — treating people impartially, showing genuine interest and humility, expressing appreciation, staying open when plans change. They also name the five patterns that quietly wreck collaboration: being passive and not contributing, aggressive and personal, arrogant about your own judgment, manipulative, or persistently negative. Having names for those is what lets you catch one in yourself before a teammate has to raise it.

The useful question is not whether you have all three but which one is costing you most right now — and that is what the Job Skills Test answers. It is free, and it scores all twelve of the work skills this framework treats as learnable rather than fixed, so it also flags the ones you were not looking for. You finish knowing which skills need attention first.

Where you stand with this already

Some of the eight probably read as things you already do. That is the ordinary result rather than a low bar: most people reach a first team having picked up several of these from group work, sport, or a part-time job without ever having had them named. The ones that felt unfamiliar are not fixed features of how you are wired — they are behaviors you have not yet had a reason to practice, and you can build them without turning into a different person in meetings. They also tend to count for more rather than less over time, as more of your work starts running through other people instead of sitting on your own desk. By reading past the definition to what teamwork actually asks of you, you have already done the part most people skip.

So the only thing left is finding out where you stand. The Job Skills Test is a free self-assessment of your work skills — about seven minutes, no preparation, scored across all twelve: the three above and the nine this article did not touch. It ends with the ones that will make the biggest difference to how you work with the people around you right now. That turns eight behaviors and no obvious starting point into one place to begin, which is the whole difference between learning about teamwork and getting better at it.