Your team just sat through a strategy meeting. Everyone nodded. No one disagreed. The plan was “approved” unanimously.
And you just made a $2 million mistake.
Not because the strategy was wrong. But because the silence was louder than any dissent could have been. Your team saw the problems. They just didn’t feel safe enough to say them out loud.
Here’s what most leaders get wrong about psychological safety: they think it’s a nice-to-have. A soft skill. Something for the “people team” to worry about while the grown-ups focus on revenue and growth.
They’re dead wrong.
Psychological safety isn’t HR fluff. It’s the difference between a team that executes brilliantly and one that executes blindly. It’s the competitive advantage hiding in plain sight.
The $50 Million Silence
Let me introduce you to Marcus, a VP of Product at a Series B SaaS company. Smart guy. Demanding leader. High standards. His team delivered—always on time, always within scope, always as specified.
They also delivered three consecutive product launches that customers didn’t want.
In our first conversation, Marcus was baffled. “I have weekly check-ins. I ask for feedback. I tell them my door is always open.”
So I sat in on his next product review.
Designer: “I think we should consider—” Marcus: “We tested that approach last quarter. Didn’t work.”
Engineer: “What if we—” Marcus: “We don’t have the bandwidth for scope creep.”
PM: “The customer interviews suggest—” Marcus: “Our customers don’t always know what they need. That’s why we’re the experts.”
Meeting ends. Marcus: “Great session, team. Any concerns?”
Silence.
Marcus’s door wasn’t open. It was a revolving door where ideas went in and got spun back out. His team had learned the most important survival skill: don’t bring problems, don’t challenge assumptions, don’t make Marcus defend his thinking.
The cost? Engineers building features they knew were wrong. Designers compromising on UX they knew would fail. PMs watching customers churn while sitting on data that explained why.
Psychological safety wasn’t a soft skill problem. It was a strategic blindness problem. And it was costing them everything.
Role-Play: The Room Where Safety Dies
Let’s do something different. I’m going to role-play a real conversation. You’re going to watch psychological safety die in real-time. Then we’ll replay it differently.
Scene: Product team meeting. Sarah, a junior designer, has noticed something.
Version 1: Where Safety Dies
Sarah: “Hey team, I was looking at the user testing data from last week, and I’m seeing something concerning. Seventy percent of users couldn’t complete the checkout flow we’re about to launch.”
Marcus (Team Lead): glances up from laptop “Seventy percent? That seems high. Did you check the parameters? Make sure you filtered correctly?”
Sarah: “Yeah, I triple-checked. The friction point is the—”
Marcus: “Here’s the thing, Sarah. User testing always shows friction. That’s why we test. But we’ve validated this flow with stakeholders. Engineering’s already committed the code. We launch in two weeks.”
Sarah: “I understand, but if we just moved the payment options above the—”
Marcus: “Sarah, I appreciate the diligence, but let’s not confuse motion with progress. We’ve all been in launch mode before. There’s always something that could be better. Perfect is the enemy of shipped.”
Sarah: “Right. Of course. Just wanted to flag it.”
Marcus: “And I appreciate that. That’s why we’re a team. Anything else?”
Silence. Meeting continues.
What just happened?
Sarah brought data. Marcus brought dismissal disguised as leadership wisdom. And every person in that room just learned: don’t bring problems close to launch. Don’t challenge the plan. Don’t make Marcus slow down.
The 70% failure rate? Shipped. Launched. Became customer complaints. Became churn. Became a three-month scramble to fix what Sarah could have prevented with a two-hour design change.
But here’s what really happened: Sarah stopped bringing data. Why would she? The last time she did, she was subtly told she was being precious, that she lacked execution mindset, that she was confusing motion with progress.
The team didn’t just lose a checkout flow fix. They lost Sarah’s brain. Multiply that by every team member, every ignored insight, every “let’s not rock the boat” moment.
That’s the real cost of psychological safety failure. Not one bad launch. One thousand unshared insights.
Role-Play: Where Safety Lives
Let’s replay that scene. Same data. Same timeline pressure. Different leader.
Version 2: Where Safety Lives
Sarah: “Hey team, I was looking at the user testing data from last week, and I’m seeing something concerning. Seventy percent of users couldn’t complete the checkout flow we’re about to launch.”
Marcus: closes laptop, full attention “Seventy percent? Walk me through what you’re seeing.”
Sarah: “The friction point is the payment options. They’re below the fold on mobile, and users are assuming they need to create an account first. So they’re bouncing.”
Marcus: “Okay. That’s… significant. And we’re two weeks from launch.” pause “Tell me what I’m missing here. We validated this flow with stakeholders. Why didn’t this surface earlier?”
Sarah: “The stakeholder demos were on desktop. The testing was mobile-heavy because that’s where 80% of our traffic is.”
Marcus: “So we validated the wrong thing.” turns to team “That’s on me. I should have caught the device mix. Alright, options. Sarah, what’s your recommendation?”
Sarah: “If we move payment options above the fold and add a guest checkout button, I think we solve it. It’s not a rewrite—it’s a layout shift.”
Marcus: turns to engineering “David, real talk. What’s the cost of that change at this stage?”
David: “Four hours of dev. Two hours of QA. Manageable.”
Marcus: “Okay. Here’s my thinking out loud: We can ship on time with a 70% failure rate and fix it later. Or we can delay by one day, ship it right, and not burn credibility with customers. Sarah, you brought data. David, you gave me honest timeline. We’re moving payment options. Launch moves to Wednesday. Sarah, you just saved us three months of customer complaints. Thank you for the diligence.”
What just happened?
Same problem. Different leader. Marcus didn’t defend his ego. He defended the outcome. He asked questions instead of providing answers. He made Sarah’s courage worth it.
But notice the subtle things:
- He closed his laptop. Full attention signals “this matters.”
- He asked Sarah to walk him through it. Respect for her expertise.
- He admitted his mistake publicly. “That’s on me.”
- He processed his thinking out loud. “Here’s what I’m weighing.”
- He named Sarah’s contribution explicitly. “You just saved us.”
Those aren’t soft skills. Those are strategic behaviors that buy you access to every insight your team has but isn’t sharing.
The Four Pillars of Strategic Safety
Psychological safety isn’t a feeling. It’s a framework. Here’s the architecture:
Pillar 1: Reward Messengers, Not Messages
Most leaders say they want honesty. Then they shoot the messenger.
The test: What happened the last time someone brought you bad news?
If your response was problem-solving (“How do we fix this?”), you might be okay.
If your response was interrogation (“Why didn’t you catch this sooner?”), you’re training silence.
Your team is always watching. They don’t listen to what you say you value. They watch what you reward and what you punish.
Your exercise: Think of the last three times someone brought you a problem. How did you respond in the first 30 seconds? Before you got to solutions, what was your immediate reaction? That reaction is what they’ll remember. That reaction determines if they’ll come back.
Role-play practice:
Team member: “The client just called. They’re unhappy with the deliverable.”
Response A (Kills safety): “Unhappy? We’ve been working on this for six weeks. What did we miss? Who was point on this?”
Response B (Builds safety): “Okay. Thanks for telling me immediately. What specifically are they unhappy about? Let’s figure this out together.”
The difference? Response A makes them regret telling you. Response B makes them trust you with harder truths next time.
Pillar 2: Model Fallibility Publicly
You’re not fooling anyone. Your team knows you make mistakes. The question is: do you?
When you pretend to be infallible, you teach them to pretend too. When you admit mistakes publicly, you give them permission to be human.
I watched a CEO do this brilliantly. In an all-hands, she said: “I pushed for the redesign. It was my call. I was wrong. Here’s what I learned and what we’re doing differently.”
Twelve words: “It was my call. I was wrong.”
She didn’t over-explain. Didn’t deflect. Didn’t blame market conditions or bad luck. She owned it. And in that moment, she bought herself a thousand moments where her team would admit when they were wrong too.
Your exercise: In your next team meeting, admit one thing you got wrong this week. Not a humblebrag (“I worked too hard”). A real mistake. Watch what happens.
Role-play practice:
In 1-on-1: “I realized I cut you off in yesterday’s meeting when you were making a point about the budget. That was wrong. I want to hear what you were going to say.”
That’s it. No justification. No “I was stressed” or “We were running long.” Just: I did something wrong. I’m acknowledging it. Tell me what I missed.
Pillar 3: Ask Questions You Don’t Know the Answer To
Most leaders ask questions as disguised instructions.
“Don’t you think we should focus on enterprise customers?” isn’t a question. It’s a statement wearing a question mark costume.
Your team knows the difference. And they learn: you’re not actually curious. You’re just testing if they agree with you.
Real questions create psychological safety because they signal: I don’t have all the answers, and I’m genuinely interested in yours.
The test: In your next meeting, ask a question you genuinely don’t know the answer to. Then—and this is the hard part—shut up. Count to ten in your head before you speak again. Let the silence do the work.
Role-play practice:
Fake question (kills safety): “Given the market conditions, don’t we think we should double down on our enterprise pipeline?”
Translation: I’ve already decided. Agree with me.
Real question (builds safety): “I’m torn on where to focus resources—enterprise pipeline vs. product-led growth. What am I not seeing from your vantage point?”
Translation: I’m genuinely uncertain. Your perspective matters.
The real question makes you vulnerable. That vulnerability is the price of honest input.
Pillar 4: Disagree and Commit—Visibly
Psychological safety doesn’t mean consensus. It means the best idea wins, even if it’s not yours.
The most dangerous phrase in business: “Well, I still think X, but we’ll try Y.”
You just told your team: I’m humoring you. I don’t really believe this. And when it goes wrong, I’ll remind everyone I had doubts.
Instead: “I was advocating for X. Sarah made a compelling case for Y. I’m convinced. We’re going with Y. If it works, Sarah was right. If it doesn’t, it’s on me for green-lighting it. Either way, we learn.”
Role-play practice:
Scenario: Your team wants to try a new project management tool. You think it’s unnecessary overhead.
Response A (kills safety): “Fine, we can try it, but I’m skeptical. Let’s not spend too much time on setup.”
Message received: This will fail, and I’ll say I told you so.
Response B (builds safety): “I’ll be honest—I had concerns about switching tools mid-quarter. But Alex showed me data on time savings, and I’m convinced the upfront cost is worth it. Let’s commit to 30 days and measure impact. If Alex is right, we scale it. If I’m right, we revert. Either way, we’ll know.”
You disagreed. You committed anyway. You made it safe for the next person to advocate for an idea you don’t immediately love.
The Safety Audit: What Your Team Isn’t Telling You
Here’s an uncomfortable exercise. Answer honestly:
1. When was the last time someone on your team disagreed with you in a meeting?
- If you can’t remember: You don’t have psychological safety. You have compliance.
2. When was the last time someone told you about a problem before it became a crisis?
- If most problems arrive as fires: They’re not telling you about the smoke because they don’t trust what happens when they do.
3. When was the last time you changed your mind because of something your team said?
- If you’re always right: You’re not always right. You’re just surrounded by people who stopped trying to convince you otherwise.
4. When was the last time someone admitted a mistake without you discovering it first?
- If you’re always the detective: They’re hiding mistakes because admission feels dangerous.
5. When was the last time a meeting ended with unresolved tension?
- If every meeting ends with agreement: You’re not getting healthy conflict. You’re getting performance art.
If you failed more than two of these, you have a psychological safety problem. Which means you have a strategic blindness problem.
Building Safety: The 30-Day Practice
You can’t fix culture overnight. But you can start building safety this week.
Week 1: The Listening Reset
- In every meeting, speak last. Not because you don’t have opinions. Because you want to hear theirs first, unfiltered by your position.
- When someone brings a problem, say this exact phrase: “Thank you for bringing this to me.” Before you say anything else.
Week 2: The Mistake Share
- Start your team meeting by sharing one thing you got wrong this week and what you learned.
- Ask one team member to do the same each week. Rotate. Normalize fallibility.
Week 3: The Genuine Question
- Identify one decision where you’re genuinely uncertain. Ask your team for input before you’ve decided.
- In the meeting, say: “I’m genuinely torn here. I don’t have the answer yet. What am I missing?”
Week 4: The Public Commit
- Disagree with someone’s recommendation, then get convinced. Say publicly: “I was wrong. [Name]’s approach is better. Here’s why I changed my mind.”
- Watch how many more people start advocating for ideas.
Do this for 30 days. You won’t transform your culture. But you’ll start thawing the silence.
The ROI of Safety
Still think psychological safety is soft? Let’s talk numbers.
Google’s Project Aristotle studied 180 teams. The highest-performing teams weren’t the ones with the smartest people or the biggest budgets. They were the teams with the highest psychological safety.
Amy Edmondson’s research at Harvard found that teams with high psychological safety:
- Report 27% more mistakes (not because they make more mistakes—because they admit them early enough to fix them)
- Show 19% higher innovation output
- Have 12% higher performance ratings
But here’s the metric that should terrify you: low psychological safety teams cost you what you never measure—all the ideas, warnings, and insights that die in your team’s heads because they don’t feel safe bringing them to you.
Marcus’s team knew the product launches wouldn’t work. They just didn’t tell him. That’s not a people problem. That’s a profit problem.
The Hard Truth About Safety
Building psychological safety requires you to get comfortable with discomfort.
Comfortable with being wrong publicly. Comfortable with being challenged by people you outrank. Comfortable with not having the answer. Comfortable with tension that doesn’t immediately resolve.
Most leaders can’t do this. Their ego won’t let them.
They want loyalty that looks like agreement. Teams that defer. Rooms where they’re the smartest person. They want psychological safety as long as it doesn’t require them to be psychologically vulnerable.
But here’s the paradox: the moment you need to be right more than you need to be effective, you’ve already lost.
The question isn’t whether your team trusts you. The question is whether you trust them enough to be wrong in front of them.
Your Safety Litmus Test
Monday morning, try this:
Walk into your next team meeting and say: “I’m working on creating more psychological safety in our team. What’s one thing I do that makes you hesitant to speak up?”
Then shut up. Don’t defend. Don’t explain. Don’t minimize. Just listen.
If they say “nothing,” you’ve proven you don’t have psychological safety—because they just gave you the safe answer instead of the true one.
If they say something uncomfortable, and you can receive it without defensiveness, you’ve just taken the first step toward a team that tells you the truth.
That truth is worth more than any strategy deck. Because the best strategy in the world is useless if your team is too afraid to tell you it won’t work.
Psychological safety isn’t soft. It’s the hardest work you’ll do as a leader. And it’s the only way you’ll know what your team actually knows.
What’s one behavior you’re doing that’s killing psychological safety in your team? Drop it in the comments. I read every one.
If this shifted something for you, share it with a leader who mistakes silence for agreement.
🔁 Share This Insight
If this resonated with you, share it with a leader, manager, or team builder who values growth over ego.
Let’s make psychological safety the new strategy advantage.
Share on:
☕ Support My Work
Enjoyed this insight? Support my work and help me continue creating leadership resources and tools that inspire growth.
