Google Spent Years Researching What Makes Teams Work. Belbin Knew the Answer Decades Earlier.

In 2012, Google set out to answer a question Belbin had investigated in the 1970s. The answer would not have surprised Belbin.

In 2012, Google launched Project Aristotle to answer a question that Dr Meredith Belbin had already investigated in the 1970s: why do some teams succeed while others — with equally talented people — fail?

Google had the resources to study this at scale. They analysed hundreds of teams, tracked dozens of variables, and eventually arrived at a conclusion that surprised them but would not have surprised anyone who has worked seriously with team dynamics: the difference between high-performing and dysfunctional teams was not intelligence, experience, or technical skill. It was how team members treated one another.

Belbin's research at Henley Management College had reached the same finding decades earlier. He called them "Apollo teams" — groups assembled from the highest-intellect individuals available. These teams consistently underperformed. They spent their time in debate rather than collaboration. As Belbin wrote: the lack of coherent teamwork nullified the gains of individual effort or brilliance.

Five Factors — and One That Sits Underneath the Others

Google's researchers identified five conditions that separated effective teams from the rest: psychological safety, dependability, structure and clarity, meaning, and impact. All five are important. But the research was clear about which one sits underneath the others.

Psychological safety — the belief that you can take risks, voice concerns, and make mistakes without fear of punishment — was the foundation. Without it, the other four conditions do not hold. A team without psychological safety does not argue. That sounds peaceful. It is not. It means people have stopped trying.

I have observed this in hundreds of teams over 28 years. One recent example: a team where the leader thought silence in meetings meant alignment. It meant the opposite. People had learned that disagreement led to consequences, so they stopped disagreeing. The decisions got worse. Nobody said anything. Trust was gone, but it took months before anyone named it.

For more on how trust is built through decisions, not time, read *Trust Is a Decision. Everything Else Follows.*

Dependability means the team delivers what it promises — on time, to standard. In behavioural terms, this requires people who turn plans into action and people who check the details before the work goes out. Many teams overvalue creativity and initiative at the start of a project, then wonder why the finish is poor. The finish is poor because nobody was responsible for it.

Structure and clarity means each person understands their role, the plan, and the goals. Not their job title — their actual contribution. What do they bring? Who do they consult? Where do they lead and where do they support?

Meaning is personal. People perform at their best when the work connects to something they care about. Gallup's research shows that employees who use their strengths every day are six times more likely to be engaged. Six times. That is not a marginal improvement — it is a different category of performance.

Impact means knowing that your work creates change. Not in the abstract. Specifically: does what I did today make a difference that I can see?

What Belbin Adds to the Google Finding

Google's research identified the conditions. Belbin provides the method for creating them.

Psychological safety grows when a team has shared language for strengths and weaknesses. In Belbin terms, weakness is not a problem — it is the predictable flipside of a strength. When a team can discuss weaknesses openly, using behavioural language rather than personal judgement, the fear that normally surrounds these conversations drops.

Dependability becomes visible when a team maps its behavioural contributions. Who drives action? Who checks quality? If both are missing, the team knows exactly where it is exposed — before the deadline arrives.

Structure and clarity sharpen when people understand not just what needs to be done, but who is best suited to do it. Matching work to behavioural strengths is more effective than matching work to job descriptions.

Meaning and impact connect directly to strengths. People who spend most of their working time on tasks that suit their natural behavioural preferences are more engaged, more motivated, and produce better results. People who spend most of their time compensating for their weaknesses burn out.

This is the demotivation trap most leaders miss. Read *Before You Motivate, Remove What Demotivates*.

Data Gets You to the Door. Conversations Get You Through It.

Google's own reflection on Project Aristotle was honest: their intensive data collection led them to the same conclusions that experienced managers have always known. In the best teams, members listen to one another and show sensitivity to feelings and needs.

This is where behavioural assessment earns its value. Not as a test. Not as a label. As the starting point for the conversations that teams avoid but always need.

For the full Belbin framework, read *Belbin Team Roles: The Practitioner's Guide to What Teams Actually Need*. Weakness is where those conversations usually start. Read *Let's Talk About Weakness*.

When you are ready to put the behavioural language into your team, *start with the assessment*.

Google ran the most expensive study on team performance in modern history and arrived where Belbin started in the 1970s. The conditions for high-performing teams are knowable, and they begin with how people behave together — not what they know individually. Start with *your own Belbin profile →*. Then put the language into your team's hands. Project Aristotle named the conditions; Belbin gives you the method to build them.

Photo by Mats Soomre · #MomentsBySoomre · moments.soomre.com