Few concepts in management have been discussed more — or acted on less — than psychological safety. Most managers have heard the term. Far fewer have thought carefully about what it actually requires of them on a daily basis, or taken the specific steps that build it in practice. This article skips the theory and focuses on the five things new managers can do, starting immediately, to create a team environment where people feel genuinely safe to contribute, challenge and be honest.
What psychological safety actually means
Amy Edmondson, the Harvard Business School researcher whose work on psychological safety is most widely cited, defines it as a shared belief among team members that the team is safe for interpersonal risk-taking — that you can speak up, ask questions, admit mistakes or disagree with a view without fearing embarrassment, punishment or rejection.
The reason it matters in practice is straightforward: teams with high psychological safety perform better. They surface problems earlier, generate more diverse ideas, learn faster from mistakes and make better decisions because more relevant information reaches the people who need it. Teams with low psychological safety do the opposite: they hide problems, agree when they disagree, avoid risks and optimise for not being criticised rather than for being effective.
For new managers, the significance is particular: you are the single most powerful influence on whether your team feels psychologically safe. The culture of a team is set largely by its manager, and it is set early. The patterns you establish in your first three months — how you respond to mistakes, whether you genuinely listen, how you handle disagreement — will shape your team's behaviour long after you have moved on from the active work of building it.
Strategy 1 Model vulnerability before you expect it from others
The fastest signal you can send that your team is safe for honest, imperfect communication is to demonstrate it yourself. When you admit that you were wrong, that you do not know something, or that an approach you tried did not work, you make it significantly easier for others to do the same. This is not weakness — it is one of the most trust-building things a leader can do, precisely because most people expect leaders to project certainty and control.
The specific form this takes matters. Vague humility ("I'm still learning too") is less powerful than specific, genuine disclosure: naming something you got wrong, explaining what you learned and inviting others' experience. The latter opens a real conversation; the former can feel performative.
In your next team meeting, briefly share a specific learning from something that did not go as planned recently. Be concrete: what you tried, what happened, what you would do differently. Then ask if anyone else has had similar experiences or a different perspective on the challenge. You will likely find that it opens the room in ways that a standard agenda item never would.
Strategy 2 Listen in a way that actually changes the conversation
Most managers believe they listen well. Most teams, if asked privately, would describe a different experience. The gap is not usually dishonesty — it is that the habits that look like listening (nodding, making eye contact, not interrupting) are not the same as the practices that signal to the speaker that they have genuinely been heard.
Practices that actually build psychological safety through listening: asking follow-up questions that demonstrate you heard the content, not just the topic ("You mentioned the timeline concern — can you say more about what specifically worries you there?"); allowing silence after someone speaks rather than filling it immediately; reflecting back what you heard before responding to it; and visibly acting on or returning to input that was offered. The last one is particularly important — people stop sharing when they observe that what they share has no effect.
Introduce a simple norm in your team discussions: before anyone responds to a point that has just been made, they briefly acknowledge what they heard. "What I'm taking from that is X — is that right?" takes ten seconds and fundamentally changes the quality of conversation. It reduces the experience of being talked past, which is one of the most common reasons people stop contributing in team settings.
Psychological safety is one of the core pillars of the LeadWise Emerging Leaders Program — covered in depth in Week 6, with practical exercises you apply directly with your team.
Explore the program — €299Strategy 3 Treat mistakes as learning events, not verdict moments
How a manager responds to mistakes is one of the clearest and most watched signals of whether the team is genuinely safe. A response that focuses on blame — who is responsible, why it should not have happened — teaches people to hide problems and deflect responsibility. A response that focuses on understanding — what happened, why it happened, what the team can learn — teaches people to surface problems early and engage honestly with failure.
This does not mean that performance issues are ignored or that there are no consequences for repeated poor judgement. It means that the primary frame for errors is inquiry, not prosecution. "Let's understand what went wrong and how we prevent it" is both more useful and more trust-building than "who is responsible for this?"
For significant failures, the blameless post-mortem is a useful structure: a team-level review of what happened, focused entirely on process and system factors rather than individual fault. The goal is not absolution — it is learning. Teams that do this consistently make fewer of the same mistakes twice and are significantly more likely to surface emerging problems before they become serious ones.
When a significant mistake occurs, call a brief team review within a few days. Open it with a clear statement of intent: "We're here to understand what happened and learn from it — not to assign blame." Then ask three questions: What happened? What factors contributed to it? What can we do differently? Document the answers. Return to them in a month to see whether the changes were implemented.
Strategy 4 Actively include — not just passively welcome — different voices
Psychological safety is unevenly distributed in most teams. Some people feel very safe; others — often those who are newer, quieter, less senior, or from different backgrounds — feel significantly less so. A manager who waits for all voices to naturally contribute will see the same voices dominating every discussion. Building genuine inclusion requires active facilitation: deliberately inviting quieter members into conversations, rotating who leads discussions, ensuring that ideas from less dominant voices get acknowledged and engaged with rather than passed over.
The dynamic to watch most carefully is interruption and idea attribution. Who gets interrupted? Whose ideas are built on, and whose are allowed to disappear? These patterns, left unaddressed, teach the less-heard members of your team that their contribution has less value. Addressing them — naming the pattern, re-inviting the voice, attributing the idea correctly — has the opposite effect.
In your next team meeting, pay specific attention to who has not spoken in the first half. Before the meeting ends, invite each person who has been quiet by name — not to put them on the spot, but to specifically ask for their perspective on something they are well placed to contribute to: "You've been working closest to this — what's your read on it?" The specificity of the invitation matters; "does anyone else have thoughts?" rarely draws out the quieter members.
Strategy 5 Reduce ambiguity about roles, expectations and norms
Uncertainty is a significant, underappreciated source of psychological unsafety. When team members are unclear about their role, uncertain what success looks like, or unsure what the norms are for how the team operates, they tend to default to caution — doing less, saying less, risking less. Reducing that uncertainty through clear role definitions, explicit expectations and agreed team norms creates the predictability that allows people to engage more confidently.
This is particularly important at the start of a new team or project, when ambiguity is highest. A clear kickoff that defines who is responsible for what, what the expected outputs are, how decisions will be made and what the communication expectations are is not bureaucratic overhead — it is one of the most direct investments you can make in your team's psychological safety.
At the start of your next project or quarter, hold a brief "working norms" conversation with your team: how do we prefer to communicate? How do we handle disagreement? What do we do when something goes wrong? The questions themselves are as valuable as the answers — they signal that you think the team's working culture matters enough to discuss explicitly, which itself builds psychological safety.
The bottom line
Psychological safety is built or eroded in small moments: how you responded when someone shared a half-formed idea, whether you followed up on the concern that was raised in last week's one-to-one, how you behaved in the meeting where things went wrong. No single action creates it; no single lapse destroys it. What matters is the consistent pattern over time.
As a new manager you have an advantage: you are setting the pattern now, before habits are entrenched. The team is watching carefully and forming impressions that will be hard to shift later. Use that window deliberately. The investment in psychological safety made in your first three months will compound — in performance, in trust, in your team's ability to navigate challenges together — for years after that window has closed.