You can't order safety into existence

Last week, we defined psychological safety: the shared belief that your team is safe for interpersonal risk-taking. It's the number one driver of team performance, and it's the difference between a team that tells you the truth and one that quietly nods while problems grow. So, the natural next question is the hard one: how do you actually build it?

Here's the uncomfortable truth for leaders: you can't. Not directly. You can't announce "this is a safe space now" and make it so. In fact, declaring it while behaving otherwise makes things worse. Safety isn't something that you install. It's something people infer, over and over, from how you behave in small moments. The good news is that those behaviors are learnable. Amy Edmondson groups them into three key moves.

Move 1: Set the stage

Before people will take a risk, they need to understand why their voice matters and that imperfection is expected. Setting the stage means framing reality honestly. 

Start by framing the work as a learning problem, not just an execution problem. When a leader says, "This is genuinely complex, the ground is shifting, and none of us can see it all, so I need everyone's eyes," they change the math. Now, speaking up isn't insubordination; it's the job. Pair that with a plain admission of your own fallibility: "I will miss things. I'm counting on you to tell me." And connect the work to purpose: who is helped when we get it right, who is hurt when we don't. Purpose is what makes speaking up feel worth the risk. 

Move 2: Invite participation

Setting the stage lowers the perceived risk. Inviting participation actively pulls the input out, because a lifetime of hierarchy has taught most people that silence is safer. 

The most underused leadership tool here is a genuine question followed by silence. "What are we missing?" "What's the risk we're not talking about?" And then wait. Count to ten if you have to do so. Leaders routinely fill the pause and answer their own question; resist it! When someone does speak, listen to understand rather than to reply, which mostly means not immediately explaining why they're wrong.

Individual behavior isn't enough, though. Build structures that make participation the default. Round-robins so the loudest voice doesn't set the agenda, pre-mortums ("imagine this project failed; why?") that make dissent a team sport, anonymous input channels for the things people won't say with their name attached, and skip-level conversations. Structure beats willpower, because it invites the quiet people the extroverts drown out. 

Move 3: Respond productively

This is where safety is won or lost. Everything above is a promise; your response in the moment when someone takes a risk is whether you keep it. Respond badly once, whether it be a sigh, a put-down, or shooting the messenger, and people update instantly. The lesson spreads faster than any policy. You lose. 

Responding productively has three parts. Express appreciation: thank people for speaking up, by name, especially when the news is bad, or the dissent is inconvenient. A simple, "I'm really glad you raised that," is disproportionately powerful. Destigmatize failure: reframe mistakes and near-misses as information. "What can we learn?" instead of "Whose fault is this?" So that problems surface early, while they're still cheap to fix. And, importantly, this does not mean anything goes: you still sanction clear, blameworthy violations. Psychological safety and accountability are not opposites; a fair, consistent line between honest failure and negligence is exactly what makes the safety credible. 

The trap to avoid

The most common failure mode isn't being a tyrant; it's being inconsistent. A leader who invites candor on Monday and punishes it on Thursday is more corrosive than the one who never invited it at all, because they've taught their team that safety is a trap. Consistency, not charisma, is what builds trust. That's why the small moments matter more than the grand gestures. 

Start this week

You don't need a culture initiative to begin. Pick one behavior. In your next meeting, replace "Any questions?" with "What are we missing?" and then hold the silence. The next time someone brings you a problem, make your first words "Thank you for flagging that." Admit one thing you got wrong, out loud, in front of your team. None of these requires permission or budget, only attention. 

Because in the end, your people won't remember your value statements. They'll remember what happened the last time they took a risk in front of you. This week, we'll go deeper on each of these moves.