High Performing Teams Frameworks: 6 Models Reviewed

The most effective high performing teams frameworks are Hackman's 6 Conditions (explains 80% of team effectiveness), Google's Project Aristotle (identified psychological safety as the #1 factor), Edmondson's Psychological Safety research (18,921+ citations), Woolley's Collective Intelligence model, and Mathieu's Shared Mental Models. Lencioni's 5 Dysfunctions is widely used but lacks peer-reviewed validation.

This guide breaks down each framework: what it says, the evidence behind it, and when to use it.

Here's the comparison:

Hackman's 6 Conditions — Harvard research, 80% variance explained — Best for designing teams from scratch

Google's Project Aristotle — 180 teams, validates Edmondson — Best for identifying what matters most

Edmondson's Psychological Safety — 18,921+ citations, peer-reviewed — Best for building learning culture

Woolley's Collective Intelligence — Published in Science, 3,844+ citations — Best for team composition decisions

Mathieu's Shared Mental Models — Journal of Applied Psychology, 4,190+ citations — Best for improving coordination

Lencioni's 5 Dysfunctions — Popular but no peer-reviewed validation — Use as conversation starter (with caution)

The rest of this article breaks down each framework in detail.

1. Hackman's 6 Conditions for Team Effectiveness

J. Richard Hackman spent decades at Harvard studying what makes teams work. His research identified six conditions that predict team effectiveness — and they account for up to 80% of variance in team performance. That's an extraordinary finding: get these six things right, and you've addressed most of what determines whether a team succeeds or fails.

What the research says

Hackman's framework divides into two categories: three essential conditions (without these, teams rarely succeed) and three enabling conditions (which allow successful teams to excel).

Essential conditions:
• Real team — stable membership with clear boundaries, not a team in name only
• Compelling direction — clear, challenging purpose that energises and aligns
• Enabling structure — right people, sound task design, core norms of conduct

Enabling conditions:
• Supportive context — rewards recognise team performance, access to information and resources
• Expert coaching — available when needed, focused on improving team processes
• Adequate resources — material, financial, and human resources required to execute

The key insight: team effectiveness depends more on deliberate design choices than on individual characteristics. Organisations should focus on getting team design right rather than attempting to fix poorly designed teams through leadership development or process interventions alone.

What leaders experience

When we ask leaders to reflect on teams that struggled, the patterns often trace back to Hackman's conditions — even when leaders don't know the framework by name.

That's a "real team" problem — one of Hackman's essential conditions. Without genuine interdependence, you have a collection of individuals, not a team. And no amount of trust-building exercises will change that.

Where leaders get stuck

Here's the uncomfortable truth: most of what determines team effectiveness isn't within the team's control. Reward systems, reporting structures, resource allocation — these are organisational decisions. A team leader can build trust and improve communication, but they often can't redesign the incentive structure that's working against them.

This is where leaders get frustrated. They read about Hackman's conditions and think, "I can't change any of this." And sometimes that's true. But knowing the real problem — even when you can't fix it immediately — is better than blaming the team for a structural failure.

Read our step-by-step guide on how to build a high performing team →

2. Google's Project Aristotle

Google's People Analytics team spent two years studying 180 of their own teams. They analysed over 250 attributes and conducted 200+ interviews. The researchers expected team composition — the caliber of individual performers — to matter most. They were wrong.

What the research says

Project Aristotle identified five key dynamics that predict team effectiveness, in order of importance:

1. Psychological safety — team members feel safe taking risks and being vulnerable
2. Dependability — members reliably complete quality work on time
3. Structure and clarity — clear goals, roles, and execution plans
4. Meaning — work is personally important to team members
5. Impact — the team believes their work matters

The surprise wasn't just that psychological safety topped the list. Individual attributes — intelligence, personality type, seniority, even technical expertise — had far less predictive power than these team-level social dynamics. Who is on a team matters less than how team members interact.

What leaders experience

Project Aristotle's findings align with what leaders describe when reflecting on their best and worst teams. The best teams weren't necessarily the most talented — they were the ones where people felt comfortable being themselves.

That difference — between pretending and admitting — is psychological safety in action. It's not about being nice. It's about being able to take interpersonal risks without fear.

Where leaders get stuck

Most leaders think they're approachable. Most teams would disagree.

The gap exists because leaders judge themselves by their intentions ("I want people to speak up") while teams judge them by their reactions. One dismissive response to a question. One sigh when someone raises a concern. One "let's take that offline" that never gets followed up. These small moments — often invisible to the leader — accumulate into silence.

The leaders who build psychological safety aren't the ones who announce it. They're the ones who respond well when someone actually takes a risk. They say "I don't know" first. They thank people for raising problems instead of shooting the messenger. It's not a policy. It's a pattern of behaviour, repeated hundreds of times.

Read our deep dive on the characteristics of high performing teams →

3. Edmondson's Psychological Safety Research

Amy Edmondson's research on psychological safety has been cited over 18,921 times — making it one of the most influential findings in organisational psychology. Her work established psychological safety as the foundational condition for team learning and performance.

What the research says

Edmondson's 1999 study in Administrative Science Quarterly introduced the construct of team psychological safety: "a shared belief held by members of a team that the team is safe for interpersonal risk taking."

Her most counterintuitive finding came from research in hospital medical teams: high-performing teams reported MORE errors than low-performing teams, not fewer. Better teams weren't making more mistakes — they were more willing to discuss them openly, creating learning opportunities that lower-performing teams systematically suppressed.

The theoretical model shows that psychological safety doesn't directly improve performance. It enables learning behaviours — asking questions, seeking feedback, experimenting, discussing errors — which in turn drive team performance.

What leaders experience

Edmondson's research explains something leaders often sense but struggle to articulate: why some teams learn from mistakes while others repeat them.

That's what happens without psychological safety. Errors get buried. Problems get hidden until they're too big to ignore. The team looks functional on the surface while learning nothing underneath.

Where leaders get stuck

Here's the paradox: the leaders who most need to build psychological safety are often the least aware it's missing. If you're senior, confident, and quick to respond, people may have learned to stay quiet around you — and you may never know.

Only 26% of employees currently work in psychologically safe environments. That's a 74% gap. The challenge is that building safety requires vulnerability from the leader first. You have to admit mistakes before others will. You have to ask for feedback before others will offer it. And you have to respond well when someone tells you something uncomfortable — because they're watching to see if it's actually safe.

4. Woolley's Collective Intelligence Research

Anita Williams Woolley at Carnegie Mellon discovered something that contradicts how most organisations build teams: assembling the smartest individuals doesn't reliably produce the smartest team.

What the research says

Woolley's research, published in Science in 2010, identified a "c factor" for collective intelligence — analogous to the "g factor" for individual intelligence. This single factor predicts a group's performance across diverse tasks, from brainstorming to problem-solving to execution.

The surprising finding: collective intelligence is NOT strongly correlated with the average or maximum individual intelligence of group members.

What DOES predict collective intelligence:
• Social sensitivity — teams whose members score higher on reading emotions and understanding others
• Equal turn-taking — teams where conversation isn't dominated by a few members
• Proportion of women — mediated by social sensitivity (women on average score higher on social perceptiveness)

A 2021 meta-analysis of 22 studies (5,279 individuals, 1,356 groups) confirmed these findings. Group collaboration process is the strongest predictor of collective intelligence, followed by individual skill and group composition.

What leaders experience

Leaders often build teams by selecting high performers. It makes intuitive sense: get the best people and you'll get the best results. But Woolley's research suggests this strategy is incomplete — and sometimes counterproductive.

The "why" usually comes down to dynamics. In this case, two senior people dominated every conversation. Others deferred to them — or disengaged entirely. The collective intelligence of the group was limited to what two people could see.

Where leaders get stuck

Most hiring processes optimise for individual capability. Most meeting cultures reward the people who speak most confidently. Most promotion decisions favour technical expertise over collaborative skill. Everything about how organisations work pushes against what Woolley's research shows actually matters.

The shift requires paying attention to how people work together, not just what they know individually. It means noticing who dominates meetings — and creating space for those who don't. It means valuing the person who asks good questions as much as the person who gives confident answers. For most leaders, this is harder than it sounds.

Learn what defines a high performing team →

5. Mathieu's Shared Mental Models

Shared mental models explain how high performing teams coordinate without constant communication. When team members share understanding of the task and each other, they can anticipate needs and adapt rapidly.

What the research says

John Mathieu's research demonstrates that both team-based mental models (knowledge about roles, responsibilities, interactions) and task-based mental models (knowledge about procedures, strategies, requirements) relate positively to team processes and performance.

The critical finding: team processes FULLY MEDIATE the relationship between mental model convergence and team effectiveness. Having shared mental models doesn't directly improve performance — it improves how teams coordinate their actions, which in turn improves performance.

When team members share mental models, they:
• Anticipate each other's actions and needs
• Coordinate implicitly without explicit communication
• Adapt rapidly to changing conditions
• Reduce misunderstandings and coordination errors

What leaders experience

Leaders describe high performing teams as "in sync" or "on the same page." These intuitive descriptions map directly to the concept of shared mental models. When a team has them, coordination feels effortless. When they don't, everything takes longer than it should.

That "clicking" doesn't happen by accident. It's built through repeated interaction, explicit conversation about roles, and deliberate attention to how work flows between people.

Where leaders get stuck

Building shared mental models takes time — time that teams under pressure rarely feel they have. So they skip the "slow" work of clarifying roles, mapping processes, and discussing who knows what. Then they pay for it later in miscommunication, rework, and frustration.

The other trap is assuming that onboarding someone new means sharing documents. It doesn't. Documents transfer information. Shared mental models require interaction — watching how people work, asking questions, building intuition about each other. There's no shortcut.

6. Lencioni's 5 Dysfunctions of a Team

Patrick Lencioni's The Five Dysfunctions of a Team (2002) is one of the most popular business books on teamwork. It's sold over 3 million copies, been translated into 30+ languages, and is widely used in corporate training. But there's something leaders should know: the model has no peer-reviewed empirical validation.

What the model proposes

Lencioni presents five dysfunctions as a hierarchical pyramid:

1. Absence of Trust (foundation) — unwilling to be vulnerable within the group
2. Fear of Conflict — seeking artificial harmony over constructive debate
3. Lack of Commitment — feigning buy-in creates ambiguity
4. Avoidance of Accountability — ducking responsibility to call peers on counterproductive behaviour
5. Inattention to Results (top) — focusing on personal success over team success

The causal claim: each level depends on the one below. Without trust, teams can't have healthy conflict. Without conflict, they can't commit. And so on.

What the evidence says

To be clear: the individual constructs (trust, conflict, commitment, accountability, results) are supported by independent research. What lacks validation is Lencioni's specific hierarchical structure and causal claims. There's no peer-reviewed evidence that trust must come first, or that the pyramid sequence is accurate.

Academic critics, including organisational psychologists Gordon Curphy and Robert Hogan, note the model's lack of evidence-based validity and oversimplification of real-world team dynamics.

What leaders experience

Despite the evidence gap, Lencioni's model resonates. Leaders recognise the dysfunctions in their own teams. The pyramid gives them language to describe what they're seeing — and that's genuinely useful.

That's the tension with Lencioni: it's helpful as a lens, but misleading as a map. Real teams don't move neatly from trust to conflict to commitment. Sometimes accountability comes first — because external pressure forces it — and trust develops later.

Where the model falls short

The hierarchy may simply be wrong. Research by Stewart et al. (2021) found that accountability doesn't necessarily flow from trust in a linear sequence. Once teams get going, "trust is established and the strongest predictor of future trust is trust itself." The bidirectional, non-linear relationships between these constructs don't fit Lencioni's neat pyramid.

The bigger problem: Lencioni treats team dysfunction as an internal issue — as if the five dysfunctions exist inside the team and can be fixed by the team. Hackman's research shows this is often wrong. Many team problems are actually structural — reward systems, reporting lines, resource constraints — and no amount of trust-building will fix a broken design.

How to use it appropriately

Use Lencioni to start conversations, not to diagnose problems. If your team recognises itself in the five dysfunctions, that's useful — it creates shared language. But don't assume the pyramid sequence is correct, and don't ignore the possibility that your team's problems are structural rather than interpersonal. Sometimes the dysfunction is in the system, not the people.

Read our guide on how to build a high performing team →

Which Framework Should You Use?

Different frameworks serve different purposes. Here's a decision guide:

If you need to design a team from scratch → Hackman's 6 Conditions

If you need to identify what matters most for effectiveness → Google's Project Aristotle

If you need to build a learning culture where mistakes can be discussed → Edmondson's Psychological Safety

If you need to make better decisions about team composition → Woolley's Collective Intelligence

If you need to improve coordination and reduce handoff failures → Mathieu's Shared Mental Models

If you need to start a conversation about team dynamics → Lencioni (with caveats)

Most organisations know multiple frameworks. The challenge isn't framework knowledge — it's implementation.

The Limitation of Frameworks

Every framework in this guide describes what high performing teams look like. None of them explains how to build one.

That's not a criticism — it's just what frameworks do. They give you a map, not the territory. Knowing Hackman's six conditions doesn't create them. Understanding psychological safety doesn't make your team feel safe. Reading about shared mental models doesn't build them.

If you've read this far, you probably already knew most of this. The characteristics of high performing teams aren't secret. What's hard is the daily work of building them: responding well when someone challenges you, admitting when you're wrong, following through on small commitments, creating space for others to speak.

That work doesn't happen in a workshop. It happens in moments — thousands of them — over months and years. Frameworks can point you in the right direction. But they can't do the walking for you.

Learn more about what makes a high performing team →

Explore our full high performing teams resource hub →