Psychological Safety
… my team is a safe place for interpersonal risk taking
Early this decade Google was focused on building the perfect team. Even earlier, the company had endeavored to capture large quantities of data about employees and how they worked. They knew, for example, how frequently particular people ate together (more productive people had larger networks of dining partners) and were able to identify key traits shared by the very best managers (good communication and avoidance of micromanaging).
In 2012 the company launched a new initiative, Project Aristotle, to analyze this data and develop an understanding of what really made the best teams. This study is the subject of an article by Charles Duhigg published in the New York Times: “What Google Learned from its Quest to Build the Perfect Team.1” Google’s website re:Work2 provides access to a broad set of information about the study as well as guides for all phases of a team’s work.
Project Aristotle identified five key “dynamics” that set successful teams apart from other teams at Google:
- Psychological safety: Can this team’s members take risks without feeling insecure or embarrassed?
- Dependability: Can this team’s members count on each other to do high quality work on time?
- Structure and clarity: Are the 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?
Of these five key dynamics, the study clearly showed that the first, psychological safety, was far more important than the other four key dynamics and, in fact, it provided the underpinning for the other four. John Katzenbach, noted writer on organizational culture, leadership, and learning, put it this way: [The study demonstrated] “…that the purely functional aspects of a team’s performance – the members’ professional backgrounds, experience, drive, or intelligence, for example – were not as relevant to success as this safe-space facility.3” Said differently, what really mattered was less about who was on the team and more about how the team worked together.
This leads us to two questions: How might this concept of “psychological safety” be defined? And, “What is needed to make my team psychologically safe?”
Amy Edmondson, the Novartis Professor of Leadership and Management at the Harvard Business School, was first to identify the concept of “psychological safety.” In a 2014 TEDxTalk HGSE talk, Professor Edmondson said that “Psychological safety is a belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes4.” The term describes a team climate characterized by interpersonal trust and mutual respect in which people are comfortable being themselves and speaking openly. However, this is not an environment where there is no accountability. Edmondson sees psychological safety and accountability as separate qualities. Low psychological safety and low accountability are indicators of apathy. High psychological safety combined with high accountability result in learning, the state a team strives for so that it will be seen as both continuously learning and successful.
So, how do we build such a team? Start small. Getting to “full-on” psychological safety for your team will take time. Perhaps, by first taking a small step at a team meeting and doing a go-around where each person talks about one thing he or she brings to the team. Others might speak on the value they experience from that individual’s work before continuing to the next team member for what he or she brings. Repeated over time, this could naturally evolve to people talking about life events that impact their work on the team. Some teams make a “go-around” to talk about what’s going on in each individual’s life a regular part of every team meeting. This would build stronger relationships, including trust and mutual respect, between all team members. Without strong bonds the trust that is required for the team’s psychological safety cannot exist5.
Beyond this, Edmondson4 suggests three paths that must be taken for a team to have psychology safety:
- Frame the work as a set of learning opportunities rather than as execution problems. No matter the task, there is always some uncertainty. Recognize this, be open to and seek input from others, set the pattern of a willingness to hear the ideas of others.
- Acknowledge that you don’t have all the answers. Be open to input because “you just may miss something.” Even though you really believe that you know the answer, be willing to admit that you might have incomplete knowledge of the total situation.
- Model curiosity. Ask lots of questions. If you ask the questions, then your colleagues on the team will have to answer, adding their voice to the overall discussion. Every time we don’t ask questions we deprive ourselves and our colleagues of some amount of learning.
Making work assigned to each team member really the team’s work is key to team learning and having a team that will deliver its very best work. That is a worthy objective for every team leader and every team member.
Make time this week to stop and think about the team you lead or are a member of. What can you do to increase psychological safety so that the team can do it’s very best work? And, as you make progress on psychological safety for the team, begin to work on the other four dynamics – dependability, structure and clarity, the work’s meaning, and its impact – of highly successful teams.
Make it a great week. . . . jim
Jim Bruce is a Senior Fellow and Executive Coach at MOR Associates, and Professor of Electrical Engineering, Emeritus, and CIO, Emeritus, at the Massachusetts Institute of Technology, Cambridge, MA.
References and Notes:
- Charles Duhigg, What Google Learned From Its Quest to Build the Perfect Team, New York Times, February 25, 2016.
- Google’s website re:work is a library of learning and informational materials on work. You may find its collection Guide: Care Professionally and Personally for your Team and Guide: Understand Team Effectiveness to be particularly helpful.
- John Katzenbach, Great Teams Build Great Cultures, Strategy+Business, May 17, 2016.
- Amy Edmondson, “Building a Psychologically Safe Workplace,” TEDxHGSE, May 4, 2014.
- Duhigg, in the NYTimes article referenced earlier, related a very special moment in the life of Sakaguchi’s team: “He [Sakaguchi] began by asking everyone to share something personal about themselves. He went first: ‘’I think one of the things most people don’t know about me,’ he told the group, ‘is that I have Stage 4 cancer.’ In 2001, he said, a doctor discovered a tumor in his kidney. By the time the cancer was detected, it had spread to his spine. For nearly half a decade, it had grown slowly as he underwent treatment while working at Google. Recently, however, doctors had found a new, worrisome spot on a scan of his liver. That was far more serious, he explained. No one knew what to say. The team had been working with Sakaguchi for 10 months. They all liked him, just as they all liked one another. No one suspected that he was dealing with anything like this. ” ’’To have Matt stand there and tell us that he’s sick and he’s not going to get better and, you know, what that means,’ Laurent said. ‘It was a really hard, really special moment.’” And, that is the type of bonds that colleagues on a well-functioning team have and an example of things, very difficult things, they can share to strengthen the interpersonal bonds between them and to support each other.
- December 2024 (3)
- November 2024 (4)
- October 2024 (5)
- September 2024 (4)
- August 2024 (4)
- July 2024 (5)
- June 2024 (4)
- May 2024 (4)
- April 2024 (5)
- March 2024 (4)
- February 2024 (4)
- January 2024 (5)
- December 2023 (3)
- November 2023 (4)
- October 2023 (5)
- September 2023 (4)
- August 2023 (4)
- July 2023 (4)
- June 2023 (4)
- May 2023 (5)
- April 2023 (4)
- March 2023 (1)
- January 2023 (4)
- December 2022 (3)
- November 2022 (5)
- October 2022 (4)
- September 2022 (4)
- August 2022 (5)
- July 2022 (4)
- June 2022 (4)
- May 2022 (5)
- April 2022 (4)
- March 2022 (5)
- February 2022 (4)
- January 2022 (4)
- December 2021 (3)
- November 2021 (4)
- October 2021 (3)
- September 2021 (4)
- August 2021 (4)
- July 2021 (4)
- June 2021 (5)
- May 2021 (4)
- April 2021 (4)
- March 2021 (5)
- February 2021 (4)
- January 2021 (4)
- December 2020 (4)
- November 2020 (4)
- October 2020 (6)
- September 2020 (5)
- August 2020 (4)
- July 2020 (7)
- June 2020 (7)
- May 2020 (5)
- April 2020 (4)
- March 2020 (5)
- February 2020 (4)
- January 2020 (4)
- December 2019 (2)
- November 2019 (4)
- October 2019 (4)
- September 2019 (3)
- August 2019 (3)
- July 2019 (2)
- June 2019 (4)
- May 2019 (3)
- April 2019 (5)
- March 2019 (4)
- February 2019 (3)
- January 2019 (5)
- December 2018 (2)
- November 2018 (4)
- October 2018 (5)
- September 2018 (3)
- August 2018 (3)
- July 2018 (4)
- June 2018 (4)
- May 2018 (5)
- April 2018 (4)
- March 2018 (5)
- February 2018 (5)
- January 2018 (3)
- December 2017 (3)
- November 2017 (4)
- October 2017 (5)
- September 2017 (3)
- August 2017 (5)
- July 2017 (3)
- June 2017 (8)
- May 2017 (5)
- April 2017 (4)
- March 2017 (4)
- February 2017 (4)
- January 2017 (4)
- December 2016 (2)
- November 2016 (7)
- October 2016 (5)
- September 2016 (8)
- August 2016 (5)
- July 2016 (4)
- June 2016 (12)
- May 2016 (5)
- April 2016 (4)
- March 2016 (7)
- February 2016 (4)
- January 2016 (10)
- December 2015 (4)
- November 2015 (6)
- October 2015 (4)
- September 2015 (7)
- August 2015 (5)
- July 2015 (6)
- June 2015 (12)
- May 2015 (4)
- April 2015 (6)
- March 2015 (10)
- February 2015 (4)
- January 2015 (4)
- December 2014 (3)
- November 2014 (5)
- October 2014 (4)
- September 2014 (6)
- August 2014 (4)
- July 2014 (4)
- June 2014 (4)
- May 2014 (5)
- April 2014 (5)
- March 2014 (5)
- February 2014 (4)
- January 2014 (5)
- December 2013 (5)
- November 2013 (5)
- October 2013 (10)
- September 2013 (4)
- August 2013 (5)
- July 2013 (8)
- June 2013 (6)
- May 2013 (4)
- April 2013 (5)
- March 2013 (4)
- February 2013 (4)
- January 2013 (5)
- December 2012 (3)
- November 2012 (4)
- October 2012 (5)
- September 2012 (4)
- August 2012 (4)
- July 2012 (5)
- June 2012 (4)
- May 2012 (5)
- April 2012 (4)
- March 2012 (4)
- February 2012 (4)
- January 2012 (4)
- December 2011 (3)
- November 2011 (5)
- October 2011 (4)
- September 2011 (4)
- August 2011 (4)
- July 2011 (4)
- June 2011 (5)
- May 2011 (5)
- April 2011 (3)
- March 2011 (4)
- February 2011 (4)
- January 2011 (4)
- December 2010 (3)
- November 2010 (4)
- October 2010 (4)
- September 2010 (3)
- August 2010 (5)
- July 2010 (4)
- June 2010 (5)
- May 2010 (4)
- April 2010 (3)
- March 2010 (2)
- February 2010 (4)
- January 2010 (4)
- December 2009 (4)
- November 2009 (4)
- October 2009 (4)
- September 2009 (4)
- August 2009 (3)
- July 2009 (3)
- June 2009 (3)
- May 2009 (4)
- April 2009 (4)
- March 2009 (2)
- February 2009 (3)
- January 2009 (3)
- December 2008 (3)
- November 2008 (3)
- October 2008 (3)
- August 2008 (3)
- July 2008 (4)
- May 2008 (2)
- April 2008 (2)
- March 2008 (2)
- February 2008 (1)
- January 2008 (1)
- December 2007 (3)
- November 2007 (3)
- October 2007 (3)
- September 2007 (1)
- August 2007 (2)
- July 2007 (4)
- June 2007 (2)
- May 2007 (3)
- April 2007 (1)
- March 2007 (2)
- February 2007 (2)
- January 2007 (3)
- December 2006 (1)
- November 2006 (1)
- October 2006 (1)
- September 2006 (3)
- August 2006 (1)
- June 2006 (2)
- April 2006 (1)
- March 2006 (1)
- February 2006 (1)
- January 2006 (1)
- December 2005 (1)
- November 2005 (2)
- October 2005 (1)
- August 2005 (1)
- July 2005 (1)
- April 2005 (2)
- March 2005 (4)
- February 2005 (2)
- December 2004 (1)