I spent the early part of my career believing that team effectiveness was mostly about talent. Get the best engineers, give them interesting problems, and get out of the way. It’s an appealing theory, and it’s wrong, or at least, it’s missing the most important part.

Google’s Project Aristotle studied 180 teams and ran 35 statistical models to find what made some teams effective and others not. The finding that surprised everyone, including Google, was that who was on the team mattered far less than how the team worked together. Individual talent, seniority, even team size, none of these were the primary drivers.

What mattered were five dynamics, in a specific order of importance.

The Five Dynamics

1. Psychological safety. I’ve written about this at length in an earlier article, so I won’t repeat the full case here. But it bears restating: this was the single most important factor. Teams where people felt safe to take risks, admit mistakes, and challenge each other outperformed teams where they didn’t, regardless of how talented the individuals were.

2. Dependability. Can team members rely on each other to deliver quality work on time? This isn’t about heroics, it’s about consistency. The qualities that make someone dependable are straightforward: genuine intentions, accountability, sound thinking, and consistent contribution. What I found interesting is that dependability is as much about trust as it is about skill. You can be highly skilled but undependable if people can’t predict whether you’ll follow through.

3. Structure and clarity. Does everyone understand the goals, their role, and what’s expected of them? This sounds obvious, but the number of teams I’ve seen where people are working hard on things that don’t align with the actual priorities is staggering. Google uses OKRs to create this alignment, and the research backs it up, teams at Sears that consistently used OKRs were 11.5% more likely to move to the higher performance category.

4. Meaning. Do team members feel their work has purpose? This isn’t about grand mission statements, it’s about whether people can connect their daily work to something they care about. Managers can help by providing positive feedback, strong support, and helping people see how their contributions fit into the bigger picture.

5. Impact. Does the team believe their work makes a difference? This is related to meaning but distinct, it’s about the tangible effect of the work on users, the organisation, or the world. Teams with a strong sense of impact are more committed and more resilient.

The Order Matters

The ordering isn’t arbitrary. Psychological safety is the foundation because without it, the other four can’t function properly. A team that doesn’t feel safe won’t hold each other accountable (dependability suffers). They won’t ask clarifying questions about goals (structure and clarity suffers). They won’t voice concerns about whether the work matters (meaning and impact suffer).

I’ve seen this cascade in practice. I once inherited a team that had excellent structure, clear OKRs, well-defined roles, regular planning cadences, but terrible psychological safety. On paper, everything looked fine. In practice, people were hitting their metrics by gaming them, nobody was raising concerns about the product direction, and the team was slowly building something nobody wanted. The structure was there, but it was hollow because people didn’t feel safe enough to challenge it.

The Gap Between Knowing and Doing

Here’s the uncomfortable truth: knowing these five dynamics doesn’t automatically help you build a team that has them. I’ve read the research, I’ve internalised the framework, and I’ve still led teams that struggled with one or more of these dimensions.

The gap is in the daily work. Psychological safety isn’t built by announcing “we have psychological safety now.” It’s built through hundreds of small interactions, how you respond when someone admits a mistake, whether you follow through on commitments, how you handle disagreement in meetings. The same is true for all five dynamics.

Google created a tool called the gTeams exercise to help bridge this gap. Team members take a 10-minute survey on how the team is doing across the five areas, then hold an in-person conversation to discuss the results. Teams that adopted even simple new norms, like starting meetings with informal conversation, improved by 6% on psychological safety and 10% on structure and clarity.

The lesson I take from this is that awareness plus intentional small changes produces real results. You don’t need a transformation programme. You need consistent attention to the dynamics that matter.

Diagnosing Your Team

If you’re trying to figure out which dynamics your team is missing, here are the signals I look for:

Low psychological safety: People don’t ask questions in meetings. Mistakes get hidden until they’re crises. Nobody pushes back on decisions, even bad ones. New ideas only come from the most senior people.

Low dependability: Deadlines slip without warning. People don’t follow through on commitments from retrospectives. There’s a pattern of last-minute heroics rather than steady delivery.

Low structure and clarity: People are working on different things than what was agreed in planning. There’s confusion about who owns what. The same questions about priorities keep coming up.

Low meaning: The team is going through the motions. There’s no energy in discussions about the product. People talk about their work in purely mechanical terms rather than connecting it to outcomes.

Low impact: The team doesn’t know whether their work is being used. There’s no connection to user feedback. Shipped features disappear into a void with no follow-up on whether they made a difference.

Building It Takes Time

The teams I’ve led that genuinely had all five dynamics didn’t get there quickly. It took months of consistent behaviour, deliberate attention, and willingness to address problems when they surfaced. And it was fragile, a single bad hire, a poorly handled incident, or a period of organisational chaos could set things back.

But the difference between a team that has these dynamics and one that doesn’t is night and day. The effective teams shipped more, learned faster, handled crises better, and retained people longer. Google’s own data showed that teams with high psychological safety were less likely to leave the company, more likely to harness diverse ideas, brought in more revenue, and were rated as more effective by leadership.

If you’re going to invest your energy in one thing as a technical leader, invest it in these five dynamics. Everything else you build sits on top of them.