Google's five keys to building a successful team
Pod, Work group, Committee, Autonomous collective. Whatever you call it, you’re part of one at Google and probably wherever you work: a team. So if we know what makes managers great, why don’t we know what makes a team great?
A group in Google’s People Operations (what we call HR) set out to answer this question using data and rigorous analysis: What makes a Google team effective? They shared their research with the Associated Press, and we’re sharing the findings here, as well.
Over two years Google conducted 200+ interviews with Googlers (their employees) and looked at more than 250 attributes of 180+ active Google teams. They were pretty confident that they'd find the perfect mix of individual traits and skills necessary for a stellar team -- take one Rhodes Scholar, two extroverts, one engineer who rocks at AngularJS, and a PhD. Voila. Dream team assembled, right?
They were dead wrong. Who is on a team matters less than how the team members interact, structure their work, and view their contributions. So much for that magical algorithm.
They learned that there are five key questions that set successful teams apart from other teams at Google:
- Psychological safety: Can we take risks on this team without feeling insecure or embarrassed?
- Dependability: Can we count on each other to do high quality work on time?
- Structure & clarity: Are goals, roles, and execution plans on our team clear?
- Meaning of work: Are we working on something that is personally important for each of us?
- Impact of work: Do we fundamentally believe that the work we’re doing matters?
If you answered “yes” to the five questions above, congrats! You’re probably on a high-performing team. And if not, not all hope is lost. This is a shortcut to help you figure out where to focus, how to get better, and a way to talk about this concept with your teammates in a structured way.
Psychological safety was far and away the most important of the five dynamics we found -- it’s the underpinning of the other four. How could that be? Taking a risk around your team members seems simple. But remember the last time you were working on a project. Did you feel like you could ask what the goal was without the risk of sounding like you’re the only one out of the loop? Or did you opt for continuing without clarifying anything, in order to avoid being perceived as someone who is unaware?
Turns out, we’re all reluctant to engage in behaviors that could negatively influence how others perceive our competence, awareness, and positivity. Although this kind of self-protection is a natural strategy in the workplace, it is detrimental to effective teamwork. On the flip side, the safer team members feel with one another, the more likely they are to admit mistakes, to partner, and to take on new roles. And it affects pretty much every important dimension we look at for employees. Individuals on teams with higher psychological safety are less likely to leave Google, they’re more likely to harness the power of diverse ideas from their teammates, they bring in more revenue, and they’re rated as effective twice as often by executives.
Googlers love data. But they don’t want to sit idle with it. They want to act. So we created a tool called the gTeams exercise: a 10-minute pulse-check on the five dynamics, a report that summarizes how the team is doing, a live in-person conversation to discuss the results, and tailored developmental resources to help teams improve. Over the past year, more than 3,000 Googlers across 300 teams have used this tool. Of those Google teams, the ones that adopted a new group norm -- like kicking off every team meeting by sharing a risk taken in the previous week -- improved 6% on psychological safety ratings and 10% on structure and clarity ratings. Teams said that having a framework around team effectiveness and a forcing function to talk about these dynamics was missing previously and by far the most impactful part of the experience.
From sales teams in Dublin to engineering teams in Mountain View, we’ve seen that focusing on this framework helps all types of teams improve.
What our customers think