The 5 Conditions of High-Performing Teams: What Google's Project Aristotle Means for L&D

Google's Project Aristotle studied 180 internal teams over two years to find what makes teams effective. The finding: who is on the team matters far less than how the team works together. Five conditions separate high performers from the rest:

1. Psychological safety
2. Dependability
3. Structure and clarity
4. Meaning
5. Impact

Psychological safety is the foundation. Without it, the other four collapse.

What Project Aristotle actually found

In 2012, Google launched a two-year study to answer one question: what makes a team effective?

The starting hypothesis was the obvious one. Smarter people. More experienced managers. Better resources. After 180 teams, none of it held up. Top performers and low performers had similar mixes of seniority, IQ, and tenure.

What separated them was behavioral, not compositional.

This is the most important piece of team research of the last two decades, and most L&D strategies still ignore it. The reflex when a team underperforms is to send people on a course. Project Aristotle is a direct argument against that reflex.

The 5 keys to team effectiveness, explained

1. Psychological safety

Team members feel safe to speak up, disagree, and take risks without fear of judgment.

What it looks like in practice: people admit mistakes early. Junior team members challenge senior ones. Bad news travels up.

What it doesn't look like: meetings where everyone agrees, then the real conversation happens in DMs afterward.

2. Dependability

People do what they said they would do, on time, at the standard required.

Not about working hard. About being predictable. High-performing teams know what they can count on from each other.

3. Structure and clarity

Roles, goals, and expectations are unambiguous. People know what they own, what success looks like, and how decisions get made.

When this is missing, smart people waste time on coordination and politics instead of work.

4. Meaning

The work connects to something personally significant for the person doing it.

Note the word "personally." This is not about company purpose statements. It is about whether each individual finds their own meaning in the work.

5. Impact

People believe their work actually makes a difference. They can see the line between what they do and an outcome that matters.

Without it, motivation erodes regardless of pay or perks.

Why psychological safety is the foundation

Of the five, Google found psychological safety to be the most critical. Not because it sounds nice. Because the other four cannot function without it.

• Without safety, dependability becomes compliance. People hit deadlines but stop flagging risks.
• Without safety, structure becomes control. Clarity turns into rigid hierarchy.
• Without safety, meaning gets self-censored. People stop sharing what actually matters to them.

Psychological safety is the precondition. The other four are the operating system that runs on top of it.

Where most HR and L&D strategies miss the point

The Project Aristotle finding has a hard implication for how HR and L&D operate.

Team performance is rarely a skills problem. It is a conditions problem.

That distinction matters because most L&D demand is filtered through the wrong lens. A manager says "my team is not collaborating" and L&D builds a collaboration workshop. The workshop does not address the actual issue, which is usually that the team has no psychological safety, unclear roles, or both.

‍

‍

4 things HR and L&D leaders can actually do

1. Make psychological safety a deliberate manager practice

Psychological safety is built or destroyed in everyday manager behavior:

• Inviting input before sharing an opinion
• Acknowledging mistakes openly
• Responding to problems with curiosity, not blame

These behaviors are trainable. They are also measurable. Build them into manager feedback cycles and design programs that practise these moments rather than just explain them.

‍

‍

2. Diagnose before you design

Before accepting any L&D brief, ask what is actually blocking performance.

A four-part filter:

• Capability: people don't know how
• Clarity: people don't know what
• Conditions: people don't feel safe to act
• Systems: the structure prevents the behavior

Only capability is a training problem. The other three need different interventions, often outside L&D's traditional remit.

3. Connect learning to personal meaning

Programs framed around business KPIs alone get tolerated. Programs that connect to something personally meaningful get internalised.

‍

‍

4. Measure team conditions, not just learning completions

Course completion rates tell you who clicked through a module. They tell you nothing about whether team performance has changed.

Add a measurement layer for the conditions themselves:

• Pulse surveys on psychological safety (4-6 items, quarterly)
• Clarity scores on roles and goals
• Dependability ratings within teams
• Manager behavior observations tied to the practices above

These give HR and L&D a working baseline and a way to show that interventions are moving the right needle.

‍

‍

From training delivery to performance architecture

Building high-performing teams is a design problem, not a delivery problem.

The shift from delivering content to designing conditions is what the most effective people functions are doing right now. It changes what L&D measures, who L&D partners with, and how L&D justifies its budget.

It also changes what training looks like. Manager development that is divorced from the team conditions it is meant to influence will keep producing the same disappointing results. Manager development designed around the five conditions, practised in real team contexts, and measured against real behavior change is the version that works.

That is the version Lepaya builds.

Frequently Asked Questions

What is Google's Project Aristotle?

Project Aristotle was a two-year Google study, launched in 2012, that analysed 180 internal teams to identify what makes teams effective. The conclusion: team dynamics matter more than individual talent or seniority.

What are the 5 keys to team effectiveness from Project Aristotle?

The five conditions are psychological safety, dependability, structure and clarity, meaning, and impact. Psychological safety was identified as the most critical of the five and acts as the foundation for the other four.

Why is psychological safety important at work?

Psychological safety lets team members speak up, disagree, and admit mistakes without fear. Without it, the other conditions of effective teams cannot function: dependability becomes compliance, structure becomes control, and meaning gets self-censored.

How do you measure psychological safety in a team?

Use short pulse surveys (4-6 items, quarterly) covering whether team members feel safe taking risks, raising concerns, admitting mistakes, and asking for help. Track changes over time and tie the data to manager behavior and team performance metrics.

Is psychological safety the same as comfort?

No. Psychological safety means it is safe to take risks and have hard conversations. Teams with high safety often have more disagreement, not less. Comfort and safety are different things.

What should L&D do differently based on Project Aristotle?

Shift from delivering training in response to skill requests toward designing the team conditions that produce performance. That includes diagnosing whether a problem is actually a training problem, building manager behaviors that create safety, and measuring team conditions alongside learning completions.

Does Project Aristotle still apply in hybrid and remote teams?

Yes, and arguably more so. Hybrid teams have fewer informal moments to build safety and clarity, which means the conditions need to be designed in deliberately rather than left to chance.