Three months into my first management role, I asked my team in a meeting: “Any concerns about the new process?” Dead silence. Five nodding heads. “Great, sounds like we’re all aligned.”
Two weeks later, the process blew up. Turns out everyone had concerns. Nobody felt safe enough to say them out loud.
That was the moment I realized something uncomfortable: silence isn’t agreement. Silence is fear. And I was the one creating it — not intentionally, not maliciously, but through a hundred small signals I didn’t even know I was sending.
If you’re a new manager and your meetings are quiet, your team never pushes back, and nobody ever admits a mistake — you don’t have a compliant team. You have a scared one. And scared teams don’t innovate, don’t improve, and don’t stick around.
This article is about fixing that. Not with posters about “safe spaces” or corporate training modules, but with specific behaviors you can start practicing today.
What Psychological Safety Actually Is (And Isn’t)
Let’s get the definition straight, because this term gets thrown around a lot.
Based on Amy Edmondson’s foundational research on psychological safety at Harvard, psychological safety means people on your team believe they can speak up, ask questions, admit mistakes, and challenge ideas — without being punished, embarrassed, or dismissed. The Amy Edmondson psychological safety framework has become the gold standard for understanding how teams function at their best.
It does NOT mean:
- Everyone is always comfortable
- Nobody ever gets critical feedback
- There’s no accountability
- Every idea gets implemented
- People can say whatever they want without consequences
Google’s Project Aristotle study looked at 180+ teams to figure out what made some teams wildly more effective than others. They tested everything — team composition, skills, personalities, management styles. The number one factor? Psychological safety. Not talent. Not experience. Not strategy. Whether people felt safe enough to take interpersonal risks.
Think about what “interpersonal risk” means in a work context. It’s saying “I don’t understand” when everyone else seems to get it. It’s admitting “I made a mistake” before anyone discovers it. It’s pushing back on your manager’s idea because you see a problem. It’s proposing something creative that might sound stupid.
Every single one of those actions requires courage. And the amount of courage required is directly proportional to how unsafe the environment feels.
Your job as a manager is to lower the courage threshold. Make it easy — not hard — for people to be honest. Building a speaking up culture at work starts with reducing the personal cost of honesty.
Signs Your Team Doesn’t Feel Safe
These are subtle. You won’t find a team member walking up to you saying “I don’t feel psychologically safe.” Instead, watch for patterns:
In meetings:
- The same two people do all the talking
- Questions are met with silence
- Nobody disagrees with you — ever
- People only share polished, safe ideas
- Heads nod but nothing changes after the meeting
In daily work:
- Mistakes get hidden or blamed on external factors
- Nobody asks for help until a problem becomes a crisis
- People CC everyone on emails to “cover themselves”
- Information hoarding — people protect their knowledge instead of sharing it
- New ideas only surface through back-channels, never in group settings
In your one-on-ones:
- Conversations stay surface level
- People tell you what they think you want to hear
- Nobody gives you feedback on your management
- Career conversations feel rehearsed, not real
- People agree to things they later don’t follow through on
The hardest truth: If you’re a new manager and you think your team already feels safe — you’re probably wrong. The transition from peer to boss automatically creates a power distance that didn’t exist before. Even if you were friends last month, the dynamic changed the day you got the title. I wrote about navigating that shift in my piece on going from colleague to boss, and it’s directly connected to this.
How You React to Mistakes Changes Everything
Here’s the single most important thing I can tell you about psychological safety: it’s built or destroyed in the moments after someone screws up.
Not in your speeches about how “mistakes are learning opportunities.” Not in your team charter. In the actual, real-time, visible way you respond when something goes wrong.
Your team is watching. Always.
Scenario: A team member pushes a change that breaks something in production.
Trust-destroying response: “How did this happen? Didn’t you test it? We talked about this process. Who reviewed this?”
Even if those are legitimate questions, the timing matters. When your first reaction to a mistake is interrogation, you’re training your team to hide mistakes.
Trust-building response: “Okay, first priority — let’s fix it. [Name], what do you need from me to get this resolved? … Great. Once it’s stable, let’s do a blameless review so we can figure out what happened and prevent it next time.”
What’s different: You led with support, not blame. You focused on fixing, not fault-finding. You signaled that the post-mortem would be about learning, not punishment. This kind of blame-free post-mortem process is what separates teams that learn from failure from teams that hide it.
The script for when someone admits a mistake:
- Thank them: “Thanks for flagging this. I appreciate you telling me.”
- Focus forward: “What do we need to do right now?”
- Learn together: “What can we change so this is less likely to happen?”
- Normalize it: “I’ve made similar mistakes. This is how we get better.”
That last part matters. If you’ve never admitted your own mistakes, your team won’t admit theirs. Period.
The “First Failure” Test
Here’s a concept I think about constantly: the first time someone on your team fails, messes up, or takes a risk that doesn’t pan out — how you handle it sets the tone for everything that follows.
I call it the First Failure Test, and most new managers fail it without realizing.
The test works like this: Your team member tries something new and it doesn’t work. Maybe they proposed an approach that fell flat. Maybe they took initiative on something and it went sideways. Maybe they spoke up in a meeting with a concern that turned out to be unfounded.
If you respond with frustration, dismissal, or “I told you so” — congratulations, you just taught your entire team (not just that person) that taking risks is punished. They will play it safe forever.
If you respond with curiosity and support — “That didn’t work out, but I’m glad you tried. What did we learn?” — you’ve just taught your entire team that experimentation is valued. They’ll take smarter risks, surface problems earlier, and bring you better ideas.
The first failure is a gift. Treat it like one.
Practical framework for handling failures:
| Step | What to do | What to say |
|---|---|---|
| 1. Acknowledge | Recognize the effort, not just the result | ”I appreciate you taking that on” |
| 2. Separate | Distinguish the person from the outcome | ”The approach didn’t work — that’s different from you not being good at this” |
| 3. Explore | Investigate together without blame | ”Walk me through your thinking. What did you see that I might have missed?“ |
| 4. Extract | Pull out the learning | ”What would you do differently? What did this teach us?“ |
| 5. Encourage | Reinforce that risk-taking is valued | ”I’d rather you try things and sometimes miss than play it safe every time” |
How to Handle Disagreement (Without Shutting It Down)
Disagreement is the canary in the coal mine. If nobody ever disagrees with you, your psychological safety is broken.
But handling disagreement well is harder than it sounds, especially when you’re new and still establishing credibility. Your instinct might be to defend your position or shut down debate to appear decisive. Resist that instinct.
When someone pushes back on your idea:
Don’t say: “I hear you, but we’re going with my approach.” Do say: “Tell me more about your concern. What am I not seeing?”
Don’t say: “Let’s take this offline” (the corporate equivalent of “shut up”). Do say: “This is a good discussion. Let’s dig into it. [Name], can you walk us through the specifics?”
Don’t say: “I’ve already decided.” Do say: “I’m leaning toward X, but I want to stress-test it. What could go wrong?”
Create structured disagreement:
In meetings, before making a decision, try: “I want to hear the strongest argument against this. Who wants to make the case?”
This technique — sometimes called a “pre-mortem” — gives people explicit permission to disagree. It removes the social risk because you literally asked for it.
Another approach: assign someone the role of “devil’s advocate” on a rotating basis. When disagreement is a job, not a rebellion, people are more willing to voice it.
The hardest version: When someone disagrees with you publicly and they’re right, say so. Out loud. “You know what, you’re right. I hadn’t considered that. Let’s go with your approach.” This costs you nothing and buys you enormous trust.
Making It Safe to Say “I Don’t Know”
One of the most powerful things you can do as a manager is model three words: “I don’t know.”
New managers often feel pressure to have all the answers. So they fake it. They give vague non-answers. They redirect. They Google things under the table during meetings.
Your team sees through all of it.
When you pretend to know things you don’t, you create an environment where everyone pretends. Questions don’t get asked. Assumptions don’t get challenged. Problems don’t get surfaced until they’re crises.
Model “I don’t know” regularly:
- “I don’t know the answer to that, but it’s a great question. Let me find out.”
- “I’m not sure about the technical details here. [Name], you’re closer to this — can you walk us through it?”
- “Honestly, I don’t know what the right call is. Let me think about it and get back to you tomorrow.”
Then follow through. Actually come back with the answer. This builds trust on two levels — you were honest about not knowing, and you were reliable about finding out. This is exactly the kind of follow-through I discuss in building trust with your team.
Create “I don’t know” moments for your team:
In your one-on-ones, ask questions that are genuinely open-ended. Not “Is there anything I should know?” (which invites “nope”), but “What’s one thing that’s confusing or unclear about our current project?” This normalizes uncertainty.
Asking for Feedback on YOUR Work
This is the ultimate psychological safety accelerator, and almost no new managers do it.
Ask your team to give you feedback. On your management. Regularly.
Yes, this is terrifying. Do it anyway.
How to start (because “any feedback for me?” won’t work):
Be specific in your ask:
- “I tried a new format for our team meeting. What worked? What didn’t?”
- “I gave you feedback on your presentation yesterday. Was it helpful? Was there a better way I could have delivered it?”
- “I’ve been doing more check-ins this week. Is that helpful or does it feel like micromanaging?”
Make it safe to be honest:
- Ask in private first (one-on-ones, not team meetings)
- Don’t get defensive when you get an answer
- Thank them for the feedback, even if it stings
- Visibly act on it: “You mentioned my check-ins felt too frequent. I’m going to pull back to twice a week. Let me know if that’s better.”
The critical part: what you do after you receive feedback.
If someone gives you honest feedback and nothing changes, they’ll never do it again. If someone gives you honest feedback and you get defensive, they’ll never do it again. If someone gives you honest feedback and you punish them (even subtly, like being colder in the next meeting), they’ll never do it again — and they’ll tell everyone.
But if someone gives you honest feedback, you thank them, and you visibly change? They’ll trust you more than ever. And others will see it and follow.
The Daily Behaviors That Create Safety
Psychological safety isn’t built in workshops or team offsites. It’s built in the tiny, daily interactions that most managers don’t think about.
In meetings:
- When someone shares an idea, your first response should be curiosity, not evaluation. “Tell me more” before “Here’s what I think.”
- Call on quiet people by name (gently): “Alex, I’d value your perspective on this. No pressure if you’d rather think on it.”
- When someone is interrupted, circle back: “Hey, Sam was making a point. Sam, can you finish your thought?”
- End meetings with: “Is there anything we didn’t discuss that we should have?”
In Slack/email:
- Respond to questions without judgment. Never “As I already mentioned…” or “Per my last email…”
- When someone asks a “basic” question, answer it straightforwardly. Never make someone feel stupid for asking.
- Share your own learning publicly: “TIL that [something you didn’t know]. Pretty useful.”
In one-on-ones:
- Start with a genuine check-in: “How are you actually doing?”
- Ask about blockers without making people feel incompetent for having them
- Share your own challenges: “I’m struggling with [thing]. Working through it.”
- When giving feedback, frame it as investment: “I’m telling you this because I think you can be great at this, and I don’t want this one thing to hold you back.”
After someone takes a risk:
- Acknowledge the courage it took, separate from the outcome
- Celebrate good thinking even when the result wasn’t perfect
- Share what you learned from their attempt with the broader team (with their permission)
When You’ve Inherited an Unsafe Team
Sometimes you walk into a team that’s already been burned. A previous manager punished honesty. A company culture rewards blame. Years of layoffs made everyone protective.
This is harder. The walls are up and they won’t come down quickly.
What to expect:
- Progress will be slow (months, not weeks)
- People will test you with small disclosures before risking bigger ones
- Old habits will resurface under stress
- Some people may never fully trust, and that’s okay
What to do:
- Acknowledge the history without badmouthing the past. “I know this team has been through some changes. I don’t know all the details, and I don’t need to. What I want you to know is how I plan to operate.”
- Be explicit about your values. Use inclusive team environment strategies from day one: “I want honest disagreement. I want to hear about problems early. I will never punish someone for bringing me bad news.”
- Then prove it with actions. Words mean nothing to a team that’s been burned by words before. Every action that matches your stated values is a brick in the foundation. Every contradiction is a demolition.
- Be patient. You’re essentially asking people to unlearn survival behaviors. That takes time.
The Measurement Problem
How do you know if psychological safety is improving? You can’t exactly run a survey that says “Are you scared of me?”
Proxy signals to watch for:
Improving:
- More questions in meetings
- People bringing you bad news earlier
- Hearing “I messed up” without having to investigate
- Disagreement in group settings (healthy kind)
- New ideas being floated, even half-baked ones
- People asking for help before problems become emergencies
Not improving:
- Continued silence in meetings
- Finding out about problems late
- CYA behavior (excessive documentation, CC-ing everyone)
- People only engaging one-on-one, never in groups
- High turnover or disengagement
One simple question you can add to quarterly check-ins: “On a scale of 1-10, how comfortable do you feel bringing up problems or disagreeing with me?” Don’t ask for a number in person — use an anonymous form. The number itself matters less than the trend.
This Is a Long Game
Here’s what I wish someone had told me when I first started managing: creating psychological safety is the slowest, most important thing you’ll ever do.
It’s slow because trust is slow. Every time you respond well to a mistake, that’s one data point. Your team needs dozens — maybe hundreds — of data points before they really believe you mean it.
It’s important because everything else depends on it. Learning from failure in teams is impossible without it. You can’t have real feedback conversations if people don’t feel safe being honest. You can’t innovate if people don’t feel safe proposing wild ideas. You can’t improve processes if people don’t feel safe pointing out what’s broken. You can’t build a great team if people don’t feel safe being themselves.
The managers I respect most aren’t the ones with the best strategies or the most impressive results. They’re the ones whose teams would follow them anywhere — because those teams know, from hundreds of small moments, that their manager made it safe to be human.
You can be that manager. Start with how you react to the next mistake. Start with saying “I don’t know” in your next meeting. Start with asking your team what you could do better.
It won’t feel like much. It will matter more than anything else you do.