Team cohesion: what it is, how to build it and a 10-question check
Check how well your team holds together in two minutes, then see what to do about it. Ten statements, one result and three next steps. Nothing is saved or sent.
The 10-question team cohesion check
Answer for your team as it is today, not as you’d like it to be.
We would all describe the team's top goal in roughly the same words.
Everyone knows who owns what, and work rarely falls between two people.
When someone falls behind, others step in without being asked.
We celebrate team results at least as much as individual ones.
When we disagree about the work, we settle it and the decision sticks.
People here genuinely enjoy working with each other.
New teammates feel part of the team within their first month.
People talk to each other directly, not only through the manager.
Remote, part-time and newer teammates are as included as everyone else.
Given the choice, most of us would pick this team again for the next project.
0 of 10 answered
Team cohesion is what makes a group of people act as one cohesive unit: they want the same outcome and they want to stay part of the group. The check above gives you a first read. The rest of this guide explains what cohesion is, shows 15 examples of cohesive teams at work, lists the warning signs and gives 10 ways and 12 activities to build it. It ends with how cohesion goes wrong and how to measure it across the whole team.
What is team cohesion?
A simple team cohesion definition: it is the pull that keeps a team together. In 1950, Leon Festinger and his colleagues described cohesiveness as the total field of forces that act on members to remain in a group. Sport psychologist Albert Carron later described it as a group’s tendency to stick together and stay united in pursuit of its goals. The model he and his colleagues built on sports teams separates task cohesion from social cohesion, and that split is how most people talk about cohesion at work today:
Task cohesion
How strongly the team is committed to the same goals and to getting the work done together.
You see it when: Everyone can name the goal, handoffs are clean, people cover for each other near a deadline.
It breaks with: Vague or competing goals, unclear ownership, rewards that pit people against each other.
Social cohesion
How much people like working together and value being part of the team.
You see it when: People talk directly, newcomers are let in fast, the team would choose each other again.
It breaks with: Cliques, constant reshuffling, remote people left out, no time together beyond status updates.
Which matters more for results? When psychologists Brian Mullen and Carolyn Copper pooled dozens of studies in 1994, the link between cohesion and performance was real but modest, and it ran mostly through commitment to the task rather than through liking each other. They also found success builds cohesion at least as much as cohesion builds success. So start with the work: a shared goal and some early wins, then the social side.
Cohesion is related to camaraderie, the day-to-day goodwill between people, which our team camaraderie guide covers with 30 everyday ideas. Cohesion is also one ingredient of high-performing teams, not the whole recipe.
Cohesiveness examples: 15 cohesive teams in action
What a cohesive team looks like in real work, across offices, warehouses, kitchens and remote teams. Each is marked by the kind of cohesion it shows.
- The launch-week cover. A developer gets sick two days before launch. Two teammates split her tickets without being asked, and she comes back to a status note, not a pile.Task
- The goal everyone can say. Ask anyone on a five-person support team what matters this quarter and you get the same answer: a first reply within an hour.Task
- The shared win. A sales team closes a big contract, and the account executive thanks the solutions engineer and the onboarding lead by name in the company channel.Task
- Bad news in ten minutes. A warehouse shift lead spots a labeling error at 7:00 and the whole shift knows by 7:10, because nobody expects to be blamed for raising it.Task
- The decision that sticks. A product team argues hard about a feature. The lead decides, and the people who lost the argument build it as if it were their idea.Task
- The same handover every time. Nurses on a hospital ward hand over at shift change with the same short checklist, so nothing depends on anyone's memory at the end of a long shift.Task
- Jumping on the line. A restaurant kitchen gets slammed. The pastry cook moves to the grill station without a word, and the chef thanks him after service.Task
- Inside jokes with an open door. A design team has its own running jokes, and the newest hire is let in on them in her first week.Social
- The Friday call people choose. A fully remote team keeps an optional 15-minute coffee call on Fridays, and most of the team turns up because they want to.Social
- Asking in the open. A junior analyst asks for help in the team channel instead of struggling quietly, and gets three useful answers in ten minutes.Social
- Arguing, then lunch. Two engineers disagree sharply in a design review, settle it, then grab lunch together.Social
- Celebrating without a reminder. When a teammate passes a certification, the team marks it in the weekly meeting. Nobody had to prompt them.Social
- The volunteer day nobody assigned. A finance team's volunteer day is planned by three people who aren't the manager, simply because they wanted to do it together.Social
- Pulling together in an outage. When a system goes down, a small IT team splits the roles in minutes (one on the fix, one on customer updates, one on the incident log) and debriefs the next day without blame.Task and social
- One team after a merger. After a reorg merges two teams, the new team writes its own working agreement in week one, and by the end of the quarter nobody says old team anymore.Task and social
Signs your team lacks cohesion
Any one of these can happen on a good team. Three or four together, week after week, mean the team is drifting apart:
- Ask five people what the team is for and you get five different answers.
- Each person guards their own numbers, even when it costs the team's.
- Work falls through gaps because everyone assumed someone else had it.
- Meetings are reports to the manager rather than conversations with each other.
- Remote and part-time teammates hear about decisions last.
- Decisions made in the meeting get reopened in side chats afterward.
- When someone leaves, the rest of the team barely notices.
- New hires still feel like outsiders after three months.
A team that recently formed or reorganized will show several of these for a while. That is normal; our guide to the stages of team development explains what to expect at each stage.
How to build team cohesion: 10 ways
The first four build task cohesion, the rest the social side. A manager can start all of them this month.
- Agree on one shared goal. Write it in a sentence everyone can repeat, and check progress against it every week.
- Make ownership clear. Everyone should know what they own, what others own and who decides what.
- Reward the team, not only individuals. Shared targets pull people toward each other; individual leaderboards pull them apart.
- Stack up early wins together. Visible progress on a shared goal builds belief in the team, and that belief makes the next push easier.
- Keep the team stable where you can. Constant reshuffling resets the team to day one before people learn to rely on each other.
- Make room to talk about more than work. Five minutes at the start of a meeting counts, as long as it happens in work hours.
- Bring new people in on purpose. A buddy, introductions and a real task in week one make a newcomer part of the team, not a visitor.
- Invite disagreement about the work. Cohesion that depends on avoiding conflict breaks the first time a real one arrives.
- Mix the subgroups. Rotate pairs and project groups across locations, shifts and tenure so no clique sets hard.
- Mark milestones and endings together. Finish projects with a short retro and a thank-you, and celebrate the team's anniversaries.
12 team cohesion activities
Each lists the time, group size, steps and two debrief questions. Numbered straight through, so a facilitator can say number 7.
Activities for task cohesion
Getting everyone pointed at the same goal and clear on how the work fits together.
1. One-sentence mission
Builds: Finding out whether everyone is pulling toward the same thing.
20 minutes · 3 to 15 people · Sticky notes or a shared board · works on video
- Everyone writes, alone, one sentence that finishes: This team exists to ___.
- Reveal all the sentences at once and read them aloud.
- Circle the words that show up more than once, and mark any sentence that points somewhere different.
- Together, write one sentence everyone can live with and post it where the team works.
Debrief
- How far apart were our first sentences?
- What work do we do that the final sentence doesn't cover?
2. Line of sight
Builds: Connecting each person's work to the team goal.
25 minutes · 3 to 12 people · A whiteboard or shared board · works on video
- Write the team's top goal for the quarter at the top of the board.
- Each person adds their two biggest current tasks underneath and draws a line to the goal, or admits there isn't one.
- Look hard at every task with no line: is it needed, or could it stop?
- Agree on one task to drop or hand off this month.
Debrief
- Which task was hardest to connect to the goal?
- What would you start if the unconnected work went away?
3. Team scoreboard
Builds: Giving the team one score it wins or loses together.
30 minutes · 3 to 15 people · A whiteboard · works on video
- Brainstorm measures the whole team affects, like response time, on-time deliveries or customer ratings.
- Pick no more than three, and drop any that one person controls alone.
- Decide where the scoreboard lives, who updates it and how often.
- Review it at the start of every weekly meeting for a month.
Debrief
- Which measure did people argue about most, and why?
- After a month, has the scoreboard changed how we help each other?
4. Future headline
Builds: Agreeing what a great year would look like.
25 minutes · 4 to 15 people · No materials · works on video
- Ask everyone to imagine a newsletter story about the team a year from now that makes them proud.
- Each person writes the headline and two sentences under it.
- Read them aloud and group the themes.
- Pick the theme most people share and name one step toward it for this quarter.
Debrief
- Which headline would you most like to come true?
- What stands between us and that headline today?
Activities for social cohesion
Helping people value being part of the team, and keeping the circle open to newcomers.
5. Our best day
Builds: Learning what makes this team click, from its own history.
20 minutes · 3 to 15 people · No materials · works on video
- Each person describes, in a minute or less, the best day they have had on this team. On a brand-new team, the best day on any team.
- Listeners note what those days had in common: a shared push, a win, a laugh, a problem solved together.
- List the common ingredients on a board.
- Choose one ingredient to create on purpose in the next month.
Debrief
- What did our best days have in common?
- Which ingredient is missing from a normal week?
7. Invent a team ritual
Builds: Making something that belongs only to this team.
25 minutes · 3 to 15 people · No materials · works on video
- List moments the team goes through regularly: a launch, a big win, a hard week, a goodbye.
- Small groups pick one moment and invent a ritual for it that takes under two minutes and costs nothing.
- Each group pitches its ritual, and the team votes on one to try.
- Use it the next three times that moment comes up, then decide whether to keep it.
Debrief
- What makes a ritual feel like ours rather than forced?
- Which moment do we let pass without marking it?
8. Our welcome guide
Builds: Writing down how the team works, so new people can join it fast.
30 minutes · 3 to 12 people · A shared doc · works on video
- Each person writes the three things they wish someone had told them in their first month on the team.
- Group the answers into a short guide: how we communicate, how we decide, who to ask about what, and our unwritten habits.
- Ask the newest person to check it for anything still missing.
- Give it to every new hire on day one and review it twice a year.
Debrief
- Which unwritten habit surprised the newest person?
- What does the guide say about who we are as a team?
Activities that build both, including for remote teams
Shared work with a social side. Every one of these runs on a video call.
9. Cohesion check debrief
Builds: Talking honestly about how well the team holds together.
30 minutes · 4 to 15 people · The ten statements from the check on this page, sent ahead as an anonymous survey · works on video
- A week ahead, send the ten statements from the cohesion check as an anonymous survey.
- In the meeting, show how many people agreed with each statement, with no names.
- Discuss the two statements with the fewest agrees: what makes them hard here?
- Pick one next step for each, with an owner.
Debrief
- Which statement split the team most, and why?
- What would move that statement from disagree to agree for you?
10. Pass-the-project relay
Builds: Building something together that no one could finish alone.
30 minutes · 4 to 8 people per group · A shared doc or slide deck · works on video
- Pick a small real deliverable, such as a one-page guide to the team's main tool or a customer FAQ.
- Each person gets four minutes to add their part, in their own specialty, then passes it on.
- Nobody may delete another person's work, only add to it or improve it.
- Read the finished piece together and decide whether it is good enough to use.
Debrief
- What did you change about your part because of what came before it?
- Where in our real work do handoffs feel like this relay?
11. How others see us
Builds: Seeing the team from outside, before it turns inward.
30 minutes, plus short interviews beforehand · 3 to 12 people · No materials · works on video
- Before the session, each person interviews someone from a team you work with: what do we do well, what is frustrating about working with us, and what do we not notice about ourselves?
- Bring the answers back without names and read them aloud.
- Group them into strengths and frustrations.
- Pick one frustration to fix, and tell the people you interviewed what you are doing about it.
Debrief
- Which outside view matched how we see ourselves, and which didn't?
- What does it say that other teams noticed it before we did?
12. Backlog blitz hour
Builds: Feeling progress together on work everyone has been putting off.
45 minutes · 3 to 20 people · A list of small overdue tasks · works on video
- Pick a pile of small, overdue tasks anyone can help with, such as stale tickets, outdated docs or untagged files.
- Everyone joins one call or room, cameras optional, and works through the pile for 40 minutes, posting each item as it's done.
- Keep a running count where everyone can see it.
- Use the last five minutes to celebrate the number and set the date of the next blitz.
Debrief
- How did it feel to watch the count go up together?
- Which other chore would be better done as a team?
Want lighter ideas for getting to know each other? See our team bonding activities.
When cohesion goes wrong: groupthink and cliques
Cohesion is good until the team cares more about staying close than about getting things right.
Groupthink
Psychologist Irving Janis developed the idea in the early 1970s to explain why close groups make poor decisions: nobody wants to break the consensus. He described eight warning signs:
- Feeling the team can't fail.
- Explaining away warning signs.
- Taking the team's good intentions for granted, so nobody checks the ethics.
- Writing off critics and competitors as foolish.
- Leaning on anyone who disagrees.
- Keeping your own doubts to yourself.
- Taking silence as agreement.
- Shielding the group from bad news that would upset the consensus.
Cliques
The other risk is a team that is cohesive inside a smaller circle: the founding members, one office, one shift. Everyone else feels it, even if nobody says it. Four guards help with both problems:
- The leader speaks last. On big decisions, hear everyone's view before giving yours.
- Name a skeptic. Rotate one person per decision whose job is to make the case against.
- Ask outsiders. Show plans to someone from another team before they are final.
- Keep the door open. Mix project groups and pair newcomers with long-timers so the team doesn't harden into an in-group.
Our guide to group dynamics covers groupthink, roles and the other forces at work in any group.
How to measure team cohesion
The check at the top of this page is one person's view. For the team's view, ask everyone the same questions, anonymously.
- Send the ten statements as a survey. Agree or disagree for each, no names collected.
- Count, don't average. Look at how many people agreed with each statement. The two with the fewest agrees are where to start.
- Compare the two sides. Statements 1 to 5 are task cohesion, 6 to 10 social cohesion. Fix the weaker side first.
- Repeat every quarter. The trend tells you more than any one result, and it shows the team you acted on what they said.
KraftyLab Intelligence can send it for you: any survey by email, answered in the browser with no account, with AI summaries of the written answers. It also has 20 ready-made templates, from eNPS to burnout, and after every KraftyLab event it sends a short pulse survey to participants with an email.
Want help building a cohesive team?
Supercharge Your Squad is a live workshop for managers on aligning the team’s values with how it works and putting each person’s strengths to use, so the team pulls together without micromanagement. It runs on Zoom by default; book about 2 weeks ahead. See more leadership team building or get a free quote.
The workshop, with its live price:
