Organisations · Cohesion

Team cohesion: how to build it for real

It has become the word everyone uses in leadership meetings. You organise an off-site, an escape room, a monthly breakfast. And six months later the same people still aren't saying the real things to each other. Cohesion is not manufactured through activities — it is built elsewhere, and that is good news.

By Quentin de Pret · Organisations & Cohesion

A note from Quentin

People often call me with a request phrased like this: « we should do something about team cohesion ». Almost always, when I dig, there is a specific conflict nobody dares name, or a decision taken two years ago that never landed. A request for cohesion is very often the polite form of a request for truth. So my first question is never « which activity? », but « what is not being said here? »

What we call « cohesion » — and what it actually is

Definition

Team cohesion is the force that holds a group together and moves it in one direction. It rests on three distinct components: shared commitment to the task, the quality of the bond between people, and pride in belonging to the group. It is not a pleasant atmosphere: it is a collective's capacity to hold together precisely when things get hard.

There are two very different things going by the same name.

The first is surface cohesion. Everyone gets on. Meetings are pleasant. Nobody raises their voice. It is comfortable — and it is often the sign that something is being avoided. A team with no disagreement is not a close team: it is a team where disagreement carries too high a price.

The second is real cohesion. It is recognisable by one simple test: what the group can go through without falling apart. A hard trade-off. A costly mistake. A fundamental disagreement between two key people. Genuinely cohesive teams are not the ones that avoid those moments — they are the ones that come out of them stronger.

« A team where nobody ever contradicts anybody is not close-knit. It is careful. That is not the same thing, and it does not produce the same results. »

Surface cohesionReal cohesion
Difficult subjects get avoidedThey are put on the table early
Disagreements are settled in corridorsDisagreements are handled in the room
The relationship is protected by silenceThe relationship is protected by candour
Good atmosphere, decisions dragDemanding exchanges, decisions hold
It collapses at the first crisisIt strengthens in a crisis
It depends on personal affinityIt depends on the frame the group has given itself

← Swipe the table to see all columns

What the research says — and what it doesn't

Cohesion is one of the most studied subjects in organisational psychology, and two findings are worth knowing before investing in anything.

Cohesion is not one thing. The meta-analysis by Beal and colleagues, published in 2003 in the Journal of Applied Psychology, shows that its three components — commitment to the task, interpersonal attraction and group pride — relate to performance independently of each other. In other words: improving the atmosphere without touching commitment to the shared work delivers a third of the possible effect. Which is exactly what a stand-alone cohesion off-site does.

The link is stronger the more people genuinely depend on each other. The same meta-analysis shows the cohesion-performance relationship strengthens markedly as workflow becomes intensely interdependent. A very concrete conclusion: before working on cohesion, check that the team has real reasons to work together. Many « cohesion problems » are in fact organisational design problems — people brought together whose work never actually intersects.

And the number one factor is not the one you'd expect. Google's Project Aristotle analysed more than 180 teams, ran over 200 interviews and examined 250 team attributes. The factor that most sharply separated the best teams from the rest was neither talent, nor seniority, nor size: it was psychological safety — the shared belief that you can take an interpersonal risk without being humiliated.

3
distinct components of cohesion, each independently linked to performance (Beal et al., 2003)
180+
teams analysed by Google's Project Aristotle to identify what makes a team effective
#1
psychological safety, ahead of talent, seniority and team size

One honest caveat about this data: the correlation runs both ways. Cohesive teams perform better, but teams that succeed also become more cohesive. Which means a shared win often does more for cohesion than a day of activities — and a collective that achieves nothing will not be re-bonded over a barbecue.

« A request for cohesion is very often the polite form of a request for truth. »

The levers

Six levers that genuinely build cohesion.

None of them requires leaving the office. All of them require courage.

01

Role clarity

A large share of the tensions attributed to « relationship problems » are grey zones: two people who each think they decide the same thing, or nobody who thinks they decide. Clarifying who decides what defuses more conflict than any workshop.

02

Psychological safety

Being able to say « I disagree », « I was wrong », « I don't understand » without it costing you. It cannot be decreed: it is built by what the leader does the first time someone contradicts them in a meeting.

03

A real decision process

When nobody knows how a decision gets made, everyone develops their own influence strategy — and that is where internal politics is born. An explicit process, known to all, turns competition into contribution.

04

Processing tensions

An unaddressed tension does not disappear: it moves and grows. Cohesive teams are not the ones with few tensions, they are the ones with a designated place to put them — and the habit of using it.

05

Mutual understanding

Understanding how a colleague works — what motivates them, what blocks them, what they do naturally well — changes how you read their behaviour. This is where tools like the Enneagram or Gallup's talents earn their place.

06

A shared purpose

The strongest cohesion does not come from the bond between people, but from what they are looking at together. A team that knows precisely why it exists can carry disagreements nobody would otherwise tolerate.

Why team building fails — and when it works

I am not against off-sites. I run them. But it is worth being clear about what they do and don't do.

An off-site does not create cohesion: it reveals it. Take a team out of its setting for two days and you will see exactly the same dynamics as at the office — the same people speaking, the same people silent, the same subjects skirted. If nothing is done with what surfaces, everyone returns on Monday unchanged, with the added sense of having lost two days.

A fun activity displaces the problem without touching it. An escape room measures your ability to solve a puzzle under pressure, not your ability to tell each other that the strategy agreed in January isn't working. Those are two different competences, and only the second changes anything on Monday morning.

Cohesion imposed from above produces the opposite effect. When leadership announces a cohesion plan without having addressed what teams are actually living, the message people hear is: « your discomfort bothers us, please feel better ». Trust goes down, not up.

Conversely, collective time works remarkably well under three conditions: it addresses a real work subject, it is facilitated by someone with no stake in the decision, and what is said there produces concrete decisions that get revisited a month later. That is no longer team building. That is work — and it is precisely what bonds people.

« An off-site does not create cohesion. It reveals it. What you do with what surfaces — that is the real work. »

Where to start, concretely

If you sense your team lacks cohesion, this is the order I work in, and it is not negotiable.

  • Listen before proposing. Short, confidential one-to-one conversations with each member. Within a few hours you almost always know what is actually stuck — and it is almost never what the original request described.
  • Check the interdependence. Do these people genuinely need each other to do their work? If not, the problem is not cohesion, it is the organisation. No workshop will fix that.
  • Clarify roles and decisions. Before working on the relationship, remove the ambiguity. Many tensions simply disappear because they no longer have a reason to exist.
  • Open a space where tensions can be said. Facilitated, framed, with clear rules. This is the uncomfortable moment — and the one that changes everything.
  • Install a rhythm. Cohesion is not a project with an end date, it is a practice. A short, regular ritual beats one large annual off-site.

This path is less spectacular than a day in the forest. It produces results that hold — and it often costs less.

Does this describe your team? A 30-minute conversation is usually enough to tell apart what belongs to cohesion, to roles, and to governance.

Next step

Does your team really hold together?

A conversation to look at what is actually happening in your collective — and what would make it more solid, durably.