Project Aristotle was Google's internal study of what makes teams effective. It examined 180 teams over two years with quantitative and qualitative methods, and is notable for what it failed to find as much as for what it found.

Evidence: Moderate. A large, well-resourced internal study of 180 teams, but correlational, largely self-report, conducted in a single company, and never peer reviewed. Its null results may reflect restricted range, since every employee studied was already selected for high ability. Its value is convergent: the top finding independently reproduces the external psychological-safety literature, which is strong. Do not cite it as a universal law.

Use when: countering the belief that team effectiveness comes from assembling the best individuals, or from personality mix.

Do not use when: treating it as universal law. It is one organization, one sector, one era — strong internal validity, uncertain external validity.

What did not predict effectiveness

  • Individual ability or seniority of members.
  • Personality mix, introvert/extrovert balance, or type profiles.
  • Colocation vs. distribution.
  • Tenure, team size, or team age.
  • Whether members socialized outside work.

This null result is the most useful part of the study. A great deal of team intervention money is spent on factors that showed no effect.

The five factors that did

In descending order of importance as reported:

  1. Psychological safety — by a wide margin the most important. Can we take risks on this team without feeling insecure or embarrassed? See psychological-safety.

  2. Dependability — can we count on each other to do high-quality work on time? The second factor, and the one most often neglected in favor of the first. Safety without dependability produces comfort, not performance.

  3. Structure and clarity — are goals, roles, and execution plans clear? Google linked this to clear goals at individual and team level.

  4. Meaning — is the work personally important to each member? Note: personally, not organizationally. What counts as meaningful differs by person.

  5. Impact — do we believe the work matters and creates change? Distinct from meaning: this is about consequence in the world, not personal significance.

How the factors interact

The ordering is not a menu. Psychological safety is enabling: without it, the other four cannot be honestly assessed, because people will not say the goals are unclear or that a teammate is unreliable.

But safety alone is insufficient, and this is where the finding is most often misused. Teams that invest only in safety and neglect dependability and clarity end up pleasant and ineffective — precisely the criticism leveled at the concept. Edmondson's own 2x2 makes the same point. See psychological-safety.

Examples by audience

  • Health care: factor 3 (structure and clarity) is frequently the binding constraint in multidisciplinary teams, where role boundaries are contested and nobody wants to name it. Factors 4 and 5 are usually strong — health care work is meaningful and consequential — which is why erosion of 1 and 3 is so demoralizing.

  • Software: hiring processes optimize hard for individual ability, which the study found irrelevant to team effectiveness. That does not mean ability does not matter; it means the variance between teams was explained by group norms, not by individual talent. Reallocating some hiring investment into team norms is the implication.

  • Executive: dependability is the executive team factor most often broken — commitments made in the room and not delivered, with no consequence. Structure and clarity is second: overlapping remits nobody will renegotiate.

Limitations

  • Single company; a well-resourced technology firm with unusually able staff. The null result on individual ability may reflect restricted range — everyone hired was already strong.
  • Correlational, and largely self-report.
  • Popular retellings compress it to "psychological safety is all that matters", dropping four of the five factors and most of the nuance.

See also

Organizational Development — a comprehensive practitioner's guide to OD for health care professionals, software engineers, and senior executives. Every framework says what the evidence is, and where it is weak.

Source and contributions: github.com/organizational-development. Built with the Lily Design System™.