Anyone waiting? Yes, can I have, um, like a black coffee? Large or small? Um, large.
Okay, take a seat. Okay, oh, I didn't really mean large. What was I thinking? Sorry, I made a mistake.
Sorry, I was distracted. My fault. Could I, could I have a small one? Yes, I'll bring it over.
Okay, thank you. Sometimes it's really difficult to get it wrong, isn't it? Oh, well, completely fit for today's topic, psychological safety. Right, let's find a table.
What do you fancy? How about that one over there by the window? Yeah? Let's go over there, then.
Hello and welcome to Management Café. If we haven't met before, I'm Pilar Orti, Director of Virtual Not Distant, where we help you transition to a remote setup with your team. You can check out our podcasts, blog posts, and information on our services on virtualnotdistant.com. And if you prefer to just subscribe to this podcast, then make sure you subscribe now on your smartphone or your podcast app, or you can sign up via email on managementcafepodcast.com.
Today I thought we could talk about psychological safety. How about that? It's the one commonality that Google found all the high-performing team shared during the Project Aristotle, and they in turn have come across this concept when looking at the research carried out by Amy Edmondson. And today I'll be mainly looking at what I've taken from one of her books, The Teaming for Innovation.
Now, if you're like me and scout the internet and literature for ways of making teens as strong as they can be, you will have come across the concept of psychological safety before. But just to make sure we're all talking about the same thing, here's a handy definition by Edmondson herself. She says it's an interpersonal climate where people feel able to express ideas, ask questions, quickly acknowledge mistakes, and raise concerns, and where they feel responsible for doing so. That's a nice list, isn't it?
Here's your coffee. Thank you. Okay, where were we? Yes, psychological safety sounds all very well and utopian, but how do we get there?
What can we do in our team to nurture this wonderful atmosphere itself where we can express ideas, as Amy Edmondson says, ask questions, quickly acknowledge mistakes, and raise concerns? Well, for a start, we need to recognize that we're not actually looking for a wonderful atmosphere. Because where there is psychological safety, there will be uncomfortable conversations. There will probably be conflict at some point.
Part of this safety is being able to own up to mistakes, which is really uncomfortable, and to bring up concerns, which might well refer to work that's being done by other people, hence the conflict bit. But do remember that some conflict is healthy as long as it's helping us improve our work or our process. So although psychological safety sounds like the best thing to strive for in theory, yes, it is, but it can be quite difficult to get there. But worth it.
Right, let's see whether we can look at how to get this healthy, productive state in our team, whether we're sharing the same office space or not, because psychological safety should not be the domain of only co-located teams. Those teams where people work away from base, or where people work in different locations, cities, countries, can also look at how they can build psychological safety in the team, because we still need to work together, we still need to raise concerns, we still need to be able to ask questions. So there are certain behaviors that will help psychological safety in groups. And when we are in an official position of leadership, or sometimes even if we are an emergent leader, if we see that we have certain influence, it helps to role model these behaviors, like with everything.
People will still look to us if we're in an official position of leadership. They still look up to us to see what is acceptable or isn't acceptable in the team. And people will look at what others are doing, of course. And if you're interested in this, you might want to check out episode 7 of this podcast, Management Cafe, on team norms.
So looking specifically at leadership behaviors, in a team to innovate, a book by Amy Edmondson, she talks about certain behaviors that build psychological safety in a team. I'll list them now, I'll do that first, and then we'll think through them one by one. And when I say think through them, I really encourage you to do so. What would it mean for you to be role modeling in that behavior?
How would you do it? It might, for example, give a very obvious example of whether it would be different, it would be different in a co-located team or in a virtual team, because the nature of communication might be very different. And it might even look different depending on your profession. And also think to yourself, how comfortable would you be with role modeling certain behaviors?
They might go against how we've been behaving for a very long time. So how aware are we of whether we are already behaving in this way or not? At the same time, as well as role modeling, you might also think of highlighting these behaviors if they're already occurring in your team. Because, of course, these things might be happening already, especially if you've got a team where people work very well together, where there's a lot of healthy debate going on.
Some people are probably already exhibiting some of these behaviors, and it's always good to thank them for it, especially when they're uncomfortable, or even just giving room for them to repeat the kind of helpful behavior. So here's the list. So quite a list. And again, these are behaviors that you need to think about whether you are in the same physical space or whether you are communicating mainly by a written communication or even video or audio meetings, because the principles are the same, but the actions we carry out to reinforce them will be different.
So let's take the first point. Let's go through all of them. Be accessible. In an office, this might mean giving someone their full attention when they're talking to you, for example, by looking away from your computer or your phone.
It might also mean letting people know when and how they can contact you if they need you. And this will go for all kinds of setups. And I'm sure you can think of other examples relevant to your own situation of what being accessible means. But let me be clear.
This does not mean that you end up just being there for other people and never get on with your own work or that you don't set any boundaries. Of course, set boundaries is one of the actions that Edmanson recommends. But it's about being clear when you are and when you're not accessible and when you're ready to interrupt with others. And this is crucial to building an environment where people feel free to reach out.
If I'm afraid of interrupting you when you'd really not like to be disturbed, well, I might just not interrupt you at all in the first place. So it's good to know when you really don't want to be interrupted. Building on this point, in the article Collaborative Overload by Rob Cross, in the January-February 2016 issue of the Harvard Business Review, the authors mentioned that, and I'm going to quote directly, and many companies, the proportion of people doing work with others in collaboration is around 80%, leaving employees little time for all the critical work they must complete on their own. Performance suffers as they are buried under an avalanche of requests for input or advice, access to resources or attendance at a meeting.
They take assignments home, and soon, according to a large body of evidence on stress, burnout and turnover become real risks. If we are always available to our team members, when do we find the time to reflect, to check in with ourselves, or to concentrate on our work? So being accessible might also mean setting boundaries. So let's look at that aspect of building psychological safety.
There are always boundaries in a team and organization around what's acceptable or not. When we talk about a team, we tend to refer to these unwritten rules as norms. When we talk about an organization, we refer to its culture. If somebody always makes sarcastic remarks when other people try to raise concerns, the atmosphere will not feel that safe.
So in addition to role modeling behavior, we might also want to reward behavior that contributes to a prolific team atmosphere, and maybe even call out those behaviors that aren't. And if we can create an atmosphere where other team members call out these behaviors also that we're onto a winner, we don't always want it to be us, because then we end up being completely in charge of the team, and the team stops to be accountable for their own behavior. So notice that when I was talking about prolific team atmosphere, that's what I use. I use the word prolific and not positive.
And I'm very weary of people that talk about the need to be positive, because this might start to deter people from bringing up concerns, from admitting to mistakes, from pointing out threats. Positive has a connotation that we are capable of success, which we obviously need to believe in. But I always feel it also suggests that if we point out those things we need to improve on, then we might be seen as negative. And nobody likes that label.
So yeah, it's not that easy, is it? Okay, let's move on. Another difficult one to follow, unless you're used to it, is acknowledge your limits. Basically admitting that you don't know everything.
So this one can feel very hard if we tend towards perfectionism, but this can do wonders when building trust. And by the way, there's a whole other episode in this podcast about trust, so check that one out. Part of the power of admitting that you don't know everything is that you role model transparency. And you also role modeling admitting when you might need someone else's input to cover your missing knowledge or your skills gap.
So it also makes it feel okay for others to ask for help when they might need it. And that's what you want, especially in a team where members don't see each other very often. You really want people to ask for help when they need it. You don't want to feel like they're waiting for you to ask for help.
And you definitely don't want to feel like if they reach out for help, they're going to be undervalued. So this one is very important. Now, 20 years ago, I would probably need to pause here and add that admitting we don't know something is sometimes more difficult to do if we're communicating in writing with someone else, because there is a longevity of our message. If we're in an organization with a blame culture or a very competitive culture, then we might feel that admitting our limits in writing might come back to bite us.
And also, if the levels of trust are low, the message I don't know might be taken for I don't want to help you. So this is especially important in writing. So if your team relies heavily on written communication, it's really worth picking the times when you share your limitations if this is making you uncomfortable. We do so much communication now by writing that you have to stop thinking about it in this way, but I really don't know your situation, your company, your team, your culture.
So again, think about, right back to what I was talking about at the beginning, think about where this sits with you. So once more, when looking at this advice, think about what you're comfortable with doing. And if thinking of showing your limits makes you a little uneasy, then first of all, think of why. Why is it making me uneasy?
I think it's really important to understand that. Is it something within ourselves or is it about the environment? We're both. And then see what kind of behavior within that might be helpful to both you and your team members.
It's really worth looking into. So I think in a similar line to this is another behavior in building psychological safety, display fallibility. So when those were the previous point it was this one as well. In-person meetings or video calls, sorry, in-person meetings or video calls, or even in audio, these are probably the best to show yourself as a human person that you are.
So real-time conversations, you can explain your points, you can pinpoint where your weaknesses are, and there are also great places to communicate where you might need help and also to invite questions. So invite questions leads me to the next point, invite participation. Now, when we're talking about inviting participation, we're not just talking meetings. We're talking about inviting participation in making decisions for the team, in getting feedback, in innovating, in designing how you all work together.
And to do that, ask thoughtful, insightful questions, especially questions that you don't know the answer to. So there's nothing, and this is quite personal again, there's nothing that makes me more uncomfortable than being asked a question by someone who thinks they already know the answer. So why are you asking me? Ask questions when you want to find out what someone else thinks, not when you want to prove a point.
And another personal point on this, and definitely not when you've been sneaky about people buying into your decisions. So yeah, quite personal points, let's move on. Another one, use direct language. Well, that followed quite nicely from the previous point about asking needing questions.
But again, you have to trust your common sense on this one, because some people have difficulty with direct language. They might not be used to it. It might be perceived as threatening or even accusatory. So I would say, make sure that your message is clear when you communicate.
It builds trust, and it avoids people being left thinking, whoa, whoa, whoa, what did she really mean when she said that? Oh, is he really sharing what he's thinking? So yeah, use direct language. Finally, one of the most difficult ones, I think, because it touches on lots of things we might not be used to doing, which is frame failures as learning opportunities.
Failures. We don't like failing. I definitely don't like being wrong, and I really don't like doing things wrong. However, worse than doing something wrong is being so paralyzed by the thought of it that we continue doing things that no longer work, just because we don't want to go into the unknown and take the wrong step.
So if your team members, if you try stuff out and mistakes follow, let's see what we can learn from that. And this might need quite a lot of self-awareness, as the last thing we want to do is to show any signs of disapproval when people point out something that didn't work for them or when they own up to a mistake. But framing the failure as a learning opportunity doesn't just mean, oh, we can learn, it didn't work, and we can move on. Once more, I come back to asking questions.
Or even further, think back to Kolb's cycle of learning through experience. Something happens, we reflect on it, we think through why it was like that, what conditions contributed to it, how our actions contributed to it, and we start then to think about how we could have done it differently, and the next time a similar situation turns up, we do something different. That's learning, in this case, learning from mistakes. So it's a whole cycle of hypothesizing and theorizing and reflecting and actioning that constitutes learning, not just, oh, well, let's learn from that, and then we won't make it really uncomfortable to talk about it.
So yeah, it can be painful because sometimes we just want to sweep something that went wrong under the carpet and we don't want to talk about it. But if we have a process for it, if we prepare in advance before failures or mistakes happen, or even better, if we get used to reviewing our work together consistently, then it's easier. These conversations become a little bit easier. So whether your team is together in the office all the time or whether you're all spread all over the city or in the world, get used to reviewing your work so that you can all learn from each other and your process and your work and so that you can get used to getting things wrong as part of innovating and improving how you work.
Right, well, my coffee's getting cold. I didn't drink much. I was talking too much. But before I go, shall we recap?
Here are the behaviors that Amy Edmondson recommends for creating psychological safety in your team. Be accessible. Acknowledge limits. Display fallibility.
Invite participation. Frame failures as learning opportunities. Use direct language. Set boundaries.
Finally, let me recommend her book. It's called Teaming to Innovate. It's quite a short read and it has some great examples of how to build psychological safety. The ones in one of the hospitals, in a clinic, they're beautiful.
They're examples of how to work across cultures, working through conflict and how to deal with unused failure. And this is my favorite quote. Recognize that teaming up is interpersonally challenging as well as rewarding. Who said any of this was easy?
Don't forget to subscribe to this podcast, Management Cafe. I'm Pilar Orti and I'm sure I'll be back with a new topic soon. You can subscribe to your podcast application or if you want to be notified by email, head over to managementcafepodcast.com and you can find me on virtualnotdistant.com. Have a lovely day.
Thank you.