Google began with a reasonable theory about great teams: start with great people, then find the right mix.
Project Aristotle tested that instinct across 180 Google teams. The researchers searched for patterns in team composition, including experience, seniority, personality, and skills. Within the teams they studied, no particular roster reliably separated the effective teams from the rest.
The useful finding was not that people are interchangeable. It was that Google's strongest internal signals described how a team worked: whether people could speak up, follow through, understand the work, find meaning in it, and see its impact.
That changed the question. Instead of asking only who belonged on the team, managers had to ask what happened once those people were together.
An org chart makes the roster and formal structure legible. It cannot reveal the norms operating inside the boxes. Project Aristotle matters because it exposed how much a roster-centered view of a team leaves out.
Key takeaways
- Project Aristotle studied 180 Google teams and found no consistent combination of people that explained which teams were most effective in its data.
- Google identified psychological safety as the most important of 5 team dynamics in its internal analysis.
- The other 4 dynamics were dependability, structure and clarity, meaning, and impact.
- This was internal corporate research, not a peer-reviewed universal model. Wider team research suggests composition can matter, depending on the people, task, and setting.
- An org chart can support formal clarity. It cannot show whether a team speaks honestly, follows through, or finds the work meaningful.
What was Google's Project Aristotle?
Project Aristotle was a research effort Google launched in 2012 to understand what made its teams effective. It was named for the line usually attributed to Aristotle, "the whole is greater than the sum of its parts."
Led by Google's People Analytics group, the project studied 180 teams: 115 project teams in engineering and 65 sales pods. The researchers combined team surveys and interviews with 4 measures of effectiveness, including executive, team-leader, and team-member evaluations, plus sales performance against quota. Google later published the framework and its limitations in a re:Work guide on team effectiveness.
The starting hypothesis was the intuitive one, the same one most of us carry around: build the best team by collecting the best people. Get the mix right. A brilliant individual contributor here, a seasoned manager there, the right blend of extroverts and introverts, the right seniority spread. Assemble talent, get performance.
Google's analysis did not uncover a dependable composition pattern. As Abeer Dubey, the manager who led the work, told The New York Times, no specific mix of personality types, skills, or backgrounds consistently explained effectiveness in their data.
The analysis turned instead toward group norms: the repeated behaviors that told team members how conversation, disagreement, risk, and responsibility worked there.
What 5 team dynamics did Google identify?
Google's researchers identified 5 dynamics associated with its effective teams. They are listed here in the order Google presented them, with psychological safety described as the most important.
1. Psychological safety. Can you take a risk on this team without feeling insecure or embarrassed? Google treated this as the most important dynamic.
2. Dependability. Do people reliably do what they said they'd do, to the standard the work needs? Google's actual survey item was blunt: when teammates say they'll do something, they follow through.
3. Structure and clarity. Are roles, plans, and goals clear? Does the team have an effective way to make decisions? (This is the one an org chart gestures at and, on its own, mostly fails to deliver. More on that below.)
4. Meaning. Is the work personally important to the people doing it?
5. Impact. Do people believe their work matters and changes something?
Of those 5, only structure and clarity is partly visible on an org chart. The other 4 live in behavior and interpretation. You cannot draw psychological safety. You cannot export dependability to PowerPoint. The list widened the manager's field of view: formal structure mattered, but so did conditions no diagram could display.
What is psychological safety, really?
Psychological safety is the shared belief that a team is safe for interpersonal risk-taking. It's the freedom to ask the question you're worried sounds dumb, admit the mistake before it metastasizes, and disagree with the senior person in the room without quietly updating your résumé that night.
The concept predates Google. The researchers did not invent it. Amy Edmondson's 1999 study of 51 work teams defined team psychological safety and connected it with learning behaviors such as seeking feedback, discussing errors, asking for help, and experimenting.
The revealing origin of that work was a hospital finding: better-functioning units sometimes reported more medication errors, raising the possibility that stronger teams were not making more mistakes but surfacing more of them. Our next article follows that evidence and explains why psychological safety is not about being nice.
Psychological safety is not niceness. It is not everyone agreeing, keeping the peace, and lowering the bar so no one feels bad. A team where nobody disagrees isn't safe; it's anesthetized. Edmondson's whole point is that safety exists in service of high standards, not instead of them. The goal isn't comfort. The goal is a team that can tell each other hard truths and get better because of it.
The mistake is treating "safe" and "demanding" as opposites you trade off. They're independent dials. Low on both, you get apathy. High demands but no safety, you get anxiety, where people hide problems to avoid blame. High safety but no demands, you get a pleasant team that ships nothing. You want both turned up: a team that holds a high bar and feels safe enough to be honest about whether they're clearing it.
Psychological safety can vary from team to team inside the same company. Company policy matters, but local reactions teach people whether candor is safe. A manager does not need to wait for a culture program before responding well to the next person who admits they are behind or challenges a plan.
What does this have to do with your org chart?
Everything, and almost nothing, which is exactly the point.
An org chart is a clear record of the formal "who." It shows reporting lines, titles, headcount, and where roles sit. When someone is new, a team has grown beyond memory, or a reorganization changes relationships, a current chart does real work.
Four of the 5 dynamics Google identified do not appear on an org chart. The chart can support structure and clarity, then goes silent on safety, dependability, meaning, and impact. You can have a flawless org chart, every box aligned, every line crisp, sitting on top of a team where nobody trusts anyone and half the commitments quietly slip. The diagram will look great. The team will not be fine.
This is the trap the chart sets, and it is easy to fall into. Redrawing the boxes feels like fixing the team. It is visible, satisfying, and produces an artifact you can point to in a meeting. But moving names around a diagram does not create trust or make people follow through. If the real problem is that the team cannot be honest, a new diagram alone will not solve it.
Use the chart for the questions it can answer. Keep it accurate. Make reporting lines and team boundaries easy to read. Then use other conversations and records to understand who owns the work between those lines, whether risks surface early, and whether commitments hold.
Is Project Aristotle actually settled science?
No, and you should be a little suspicious of anyone who presents it as gospel, including the dozens of leadership blogs that have spent a decade citing it as proof of whatever they were already selling.
Two caveats keep the finding useful.
First, it was never peer-reviewed. Project Aristotle was internal Google research, popularized for the rest of us by journalist Charles Duhigg in a 2016 New York Times Magazine piece. That does not make it wrong. It does make it different from a replicated, peer-reviewed study. Treat it as a substantial finding inside Google, not settled science for every team.
Second, team composition has its own evidence base. A 2024 meta-analysis of 45 studies, 3,331 teams, and 14,549 people found weak relationships between several team-level personality traits and performance, with results changing by context and the way performance was measured. Earlier meta-analyses have also found composition effects in some settings. The evidence does not support either extreme: personality is destiny, or people do not matter.
The fair synthesis is less dramatic than the viral retelling. Project Aristotle did not prove that talent and composition are irrelevant. It found that no particular roster explained effectiveness within Google's sample, while team norms gave managers a useful way to understand the differences they saw.
That distinction is actionable. Managers cannot always choose the team. They can often influence how the team handles risk, commitments, clarity, meaning, and impact.
What can a manager actually do on Monday?
Across the research and practical guidance, a few unglamorous actions recur. None of them require a reorg.
Treat the chart as a starting point, not the finish line. Keep the formal structure clear and current, then check whether people also understand decision rights, ownership, goals, and the route for raising a problem. A clean chart can support clarity. It cannot complete it.
Make your reaction to bad news useful. When someone says a commitment slipped, ask what happened, what is at risk, and what help or decision is needed before passing judgment. One reaction does not transform a team. Repeated reactions teach people whether candor creates progress or punishment.
Frame the work as something you're all still figuring out. Edmondson's advice for building safety is almost suspiciously simple: treat the work as a learning problem rather than a pure execution problem, admit your own fallibility out loud, and ask a lot of questions. Managers who act like they have all the answers get teams that stop offering theirs.
Watch dependability, not just talent. Google's second dynamic was whether teammates completed quality work on time. Notice whether commitments have clear owners, whether risks surface early, and whether the same person repeatedly rescues the work. Our article on team dependability follows the stronger evidence behind those patterns.
The org chart will tell you none of this. It will tell you who reports to whom, which is worth knowing and worth getting right. The team's reactions determine whether important information can travel through those lines.
Related guides
- Why psychological safety is not about being nice
- Why team dependability quietly breaks down
- Why ownership gets lost between reporting lines
Frequently asked questions
What is Project Aristotle in simple terms?
It was Google's internal research project, started in 2012, that studied 180 of its teams to understand effectiveness. In its sample, no particular team composition explained success. Google instead identified 5 team dynamics, led by psychological safety.
What are the five keys to a successful team according to Google?
Google presented psychological safety, dependability, structure and clarity, meaning, and impact. It described psychological safety, the freedom to take interpersonal risks without fear, as the most important dynamic in its internal analysis.
Is psychological safety the same as being nice?
No. Psychological safety is the freedom to speak up, disagree, and admit mistakes. It exists to support high standards, not replace them. A team where everyone agrees to keep the peace is not psychologically safe; it's just quiet, and it tends to hide problems until they're expensive.
Does an org chart show team health?
No. An org chart shows formal structure: reporting lines, titles, and headcount. Four of Google's five effectiveness factors, including trust and follow-through, don't appear on it at all. A chart is useful for clarity, but it can't tell you whether a team actually works well together.
Was Project Aristotle a peer-reviewed study?
No. It was internal corporate research, popularized by journalist Charles Duhigg in 2016. The findings are compelling and data-rich, but they were never published as peer-reviewed academic work, and some psychologists argue it understated how much team composition and personality matter.