Psychological Safety: What’s Keeping Your Team From Taking Critical Risks?
By Vanessa Douyon and Kiera Vinson
In our six-part blog series, we are exploring cross-cutting themes that surfaced in our DEI In Action Case Studies, themes that we see again and again in our work with organizations across the country. As we delve into the challenges and successes of the DEI efforts at Blue Engine, College Track, and TNTP, we first extend deep gratitude to the many leaders and staff members who were courageously candid with us. Because they were willing to vulnerably pull back the curtain, we all have an opportunity to recognize patterns and build more inclusive, radically human workplaces.
Promise54’s Vanessa Douyon and Kiera Vinson share their experience of how psychological safety within organizations fosters greater risk-taking, effectiveness, and productivity – and how your team can get there.
Imagine yourself sitting in a senior leadership team meeting, sharing performance ratings for your direct reports. You’re discussing one staff member in particular, and the feedback you’re hearing from the team doesn’t quite sit well with you. Something feels… off. You wonder if some of the observations you’re hearing are biased, and rooted in the staff member’s identity. You’re not sure whether to say something, but you can’t ignore this gut feeling and, even if you were to say something, you’re not entirely sure how to voice your objection to the rating. To be honest, it would be easiest to just let the feeling pass, and say nothing.
What happens next in this scenario has a lot to do with the degree of psychological safety felt in the room, and in the organization.
So what is psychological safety? We know, it’s a wonky term. But, it’s crucial to fostering more diverse, inclusive, and equitable organizational cultures because when psychological safety exists, team members feel safe to be more vulnerable in front of peers — and leadership — and to take risks. If people experience trust at the individual level, psychological safety is what’s experienced at the group level in team meetings and all-staff retreats, during PD and design sessions, on conference calls, video chats, and in shared office spaces
The need for psychological safety emerged as a theme in Promise54’s radically human case studies. In one case, staff at Blue Engine recognized how the organization’s size and sense of personal connection was critical in creating high-enough psychological safety for challenging conversations to take place. Blue Engine’s Sarah Fuentes reflected that “I haven’t seen many organizations where people feel comfortable being uncomfortable.” Staff recognized the importance of relationships in order to engage in the hard and messy conversations around DEI. Essentially, the team was able to take on those crucial conversations because those relationships existed in a context where there was a high degree of psychological safety.
Let’s return to the senior leadership team meeting above. In this example, psychological safety would mean you’d face fewer barriers to speaking up. You would feel safe taking the risk to share your thinking, even if it weren’t fully baked, and it would be okay if you weren’t able to fully articulate your objection. You wouldn’t worry later about the implications for your job or future promotions.
Not only is psychological safety beneficial at an individual level, but studies show that the most productive teams have high psychological safety. Teams with high psychological safety are more likely to admit mistakes, contain effective partnerships, take on new responsibilities, and retain employees. Don’t get us wrong, it’s not a panacea; there are always challenges in an organization and room for critical feedback, but psychological safety means the difference between the organization collectively talking about its challenges and people individually talking about the organization’s challenges.
So that story at the beginning? That was me — Vanessa — in the room. And in that room, there was actually very high psychological safety. So I took a risk, and I named my concern about the rating to the group. I thought I would be uncomfortable watching them respond, but within seconds, the CEO thanked me for sharing that perspective. Other members of the senior leadership team followed suit, asking questions and adding more context. I felt safe to continue voicing my in-process thoughts,. Other folks chimed in and built on what I was saying. At some point, I was worried about what I said and tried to walk it back, but they told me not to. I felt affirmed for taking the risk and saying the thing that felt like it must be said.
How did we get there? What did the leadership team do well, and what can your team do to promote a sense of psychological safety?
- Be vulnerable. If you’re a leader and you want your team to take risks, you have to take them first– in front of the group. For example: share the areas of growth you’re actively working on. Or name when you aren’t sure what to do or what decision to make. Be radically human.
In the example, vulnerability was a two-way street. I was vulnerable in sharing what felt off to me. The group of managers with whom I shared my thoughts were open to feedback and reframed how they were thinking.
- Affirm your team when you see them taking a risk. The CEO jumped in immediately to thank me. Whether he agreed or not, he thanked me for the act of sharing and risk-taking.
- Step up to the edge with them. As someone else in the room — particularly one with seniority — if you agree with the person, join them on the edge. Match risk-taking with risk-taking and model it for the rest of the team.
- Follow up. If you’re in the room, you could follow-up in the moment, or later on over Gchat, phone, email or, ideally, in-person. Receiving messages from multiple people can be validating to the person who took the risk.
With psychological safety, the senior leadership team was able to arrive at a final performance rating that felt fair. The rationale was clear and we felt good about the rating as a team. What’s more, our team learned a little more that day about what goes into reflective performance evaluation, and how we could do even better.