Latest / Lead With Clarity: Practical Insight for Senior Leaders / Safe Isn't Nice: What Psychological Safety Actually Means for Leaders
Transcript
- Blake Holman: Welcome to Lead with Clarity. This is a space for leaders who want to grow without losing themselves in the process. Each episode is a short reflection on leadership, influence, and the inner work that shapes how we show up for others. It's not hype, not noise, just clear thinking for the journey of leading well. Today's episode is entitled Safe Isn't Nice: What Psychological Safety Actually Means for Leaders. Here we go. I want to start with a scene a lot of you may recognize. A team is in a meeting. Project is clearly off track, and everyone in the room can feel it. Nobody says anything. The meeting ends, people go back to their desks, and the problem stays exactly where it was. That scene is why I come back to a line from Amy Edmondson, the researcher who has spent her career studying what makes teams actually perform. She said Psychological safety is not about being nice. It's about giving candid feedback, openly admitting mistakes, and learning from one another. Let's sit with that for a moment because it cuts against how most of us were taught to think about safety at work. A lot of leaders hear psychological safety and picture something soft, a comfortable culture, a place where nobody gets their feelings hurt. That's a misread, and it is a costly one. Here's the piece that gets missed. Nice and safe are not the same thing. Nice is agreeable. Nice avoids friction. Nice lets a bad plan. Sail through a meeting because nobody wants to be the person who raises their hand. Safe is different. Safe means a junior analyst can tell a senior partner that the numbers don't add up. Safe means someone can say, I made a mistake here, out loud, in the room, instead of quietly trying to fix it before anyone notices. Edmondson's research on hospital teams found something counterintuitive. The teams that reported more errors were not the worst performing teams, they were often the best. Not because they made more mistakes, but because they were safe enough to talk about the mistakes they made. The worst teams were not making fewer errors. They were just staying quiet about them. That's the leadership lesson underneath all of this. If your team never disagrees with you, that's not alignment, that's silence. And silence hides the exact problems you need to catch early while they are still small and still fixable. So, how do you build the real thing instead of the comfortable imitation? It starts with what you reward. The next time someone on your team admits a mistake in front of the group, don't let that moment pass quietly. Thank them for it, visibly. What gets rewarded gets repeated, and what gets punished, even subtly, through a raised eyebrow or an awkward silence, goes underground and stays there. It also starts with you going first. If you want people to admit their mistakes, they need to see you admit yours. Not a vague, general, nobody is perfect comment, but a specific real accounting of a call you got wrong. Leaders who model that are giving their team permission to do the same. I'll add one more layer to this because it is increasingly relevant. As more of the routine analysis in our work gets handed off to AI tools, this question of safety does not go away. It changes shape. A tool can draft the report, flag the anomaly, summarize the meeting notes. What it cannot do is decide whether the room is safe enough for a person to stand up and say the anomaly actually matters, or that the recommendation feels wrong, even though the model produced it cleanly. That judgment call, the one about whether it is to safe to push back on something polished and confident sounding, is still entirely human. It is still yours to build. So as you move through this week, here's what I would carry forward: separate the word nice from the word safe in your own thinking. And be honest with yourself about which one your team actually has. Ask one person on your team what they have been hesitant to tell you. And the next time a mistake surfaces in a meeting, whether it came from a person or from a tool your team relied on, treat that moment as the win that it actually is. One last thought before I let you go. Building this kind of team does not happen in one dramatic meeting. It happens in a hundred small moments. The way you react in the first five seconds after someone tells you something went wrong. That reaction is what people remember, and it's what they calibrate against the next time they are deciding whether to speak up or stay quiet. A team that can disagree well will always outperform a team that just agrees quickly.