How to Improve Psychological Safety in Your Team
Improving psychological safety requires consistent leader behaviour, not one-off workshops. Learn the specific tactics that actually move safety scores — and how to measure whether they're working.
Most attempts to improve psychological safety fail for the same reason: they treat it as a culture initiative rather than a behaviour change challenge. A two-hour workshop on psychological safety moves scores by approximately zero. Consistent changes in how a leader responds to questions, feedback, and mistakes — repeated over 8–12 weeks — moves them significantly.
This guide covers the specific behaviours and tactics that reliably improve psychological safety in teams, how to implement them without making the process feel performative, and how to measure whether they're working.
Why is psychological safety hard to improve?
Psychological safety is hard to improve because it is built through accumulated experience, not declared intentions. A single incident where a manager reacts defensively to feedback can undo weeks of positive signals. Improvement requires consistency across time and conditions — including the moments of pressure when reverting to default behaviours is most tempting.
Amy Edmondson's original research on psychological safety found that it forms through repeated interpersonal experiences within a team — specifically through how leaders respond when team members take interpersonal risks (speaking up, admitting mistakes, proposing unconventional ideas). The pattern of responses over time becomes the team's shared belief about how safe it is to take those risks.
This means improvement is necessarily slow and consistency-dependent. It also means regression is fast: one high-visibility incident where speaking up goes badly can reset months of progress.
What leader behaviours most reliably improve psychological safety?
The behaviours with the strongest and most consistent evidence for improving psychological safety are: modelling fallibility by sharing mistakes openly, responding to bad news with curiosity rather than blame, structuring meetings to actively invite dissent, following through visibly on feedback received, and protecting dissenting voices in group settings from social pressure to conform.
-
Model fallibility — go first with a real mistake
In your next team meeting, share something you got wrong recently and what you learned from it. Be specific ("I underestimated how long the API migration would take and didn't communicate the delay early enough — here's what I'd do differently") rather than vague ("I know I don't always get things right"). Specificity signals authentic vulnerability; vagueness signals performative humility. When leaders go first, the implicit message is: admitting error is safe here.
-
Respond to bad news with curiosity, not blame
When a team member brings you a problem — especially one they contributed to — your response in that moment determines whether anyone brings you problems early in the future. Replace "Why did this happen?" (blame signal) with "Walk me through what happened" (curiosity signal). Replace immediate problem-solving with "What do you think we should do next?" Your facial expression and body language matter as much as the words.
-
Structure dissent into every team meeting
Don't wait for people to volunteer disagreement — build space for it into the meeting structure. Before finalizing any significant decision, ask: "What am I missing?" or "Who sees this differently?" Then wait. Silence after these questions is not neutral — it is the moment where people decide whether speaking up is worth the risk. Hold the pause for at least 10–15 seconds before moving on.
-
Follow through visibly on what the team tells you
The fastest way to destroy psychological safety is to ask for feedback and do nothing with it. After every feedback cycle — survey or otherwise — tell the team publicly what you heard and what you're changing because of it. Even if the answer is "I heard this concern and I'm not able to address it right now because of X" — that transparency is safety-building. Silence after feedback is safety-destroying.
-
Protect the person who speaks up in group settings
When someone raises a concern or a dissenting view in a meeting, your public response determines whether anyone else will do the same. Thank them specifically for the challenge. Engage with the substance before responding to the position. Never signal — through tone, dismissal, or moving on immediately — that the challenge was unwelcome. Other team members are watching to calibrate their own risk assessment.
What team-level practices support psychological safety?
Beyond leader behaviour, team-level practices that support psychological safety include regular blameless post-mortems after failures, structured retrospectives that invite all voices equally, peer recognition rituals that reduce status hierarchies, and anonymous feedback channels that lower the interpersonal risk of giving honest input.
- Blameless post-mortems — after any significant failure or near-miss, run a structured debrief that asks "what happened in the system?" rather than "who made the mistake?". This frames errors as information about process gaps rather than evidence of personal failure — the exact reframe needed for psychological safety.
- Structured retrospectives — run regular retrospectives (monthly or after major projects) with explicit equal-voice mechanisms: round-robin input, anonymous sticky notes, or written submissions before the meeting so quieter team members aren't pre-empted by dominant voices.
- Peer appreciation rituals — practices where team members recognize each other's contributions (not just managers recognizing reports) reduce status hierarchy effects that suppress lower-status voices. Brief, regular, and specific beats annual and elaborate.
- Anonymous feedback channels — give the team a way to surface concerns without attribution pressure. Anonymous pulse surveys are the most reliable mechanism; they systematically remove the interpersonal risk from feedback without requiring the team to trust individual relationships enough to speak up directly.
Mirrovo's anonymous surveys are the lowest-friction way to give your team a safe feedback channel.
Sent via tokenized links with no respondent login, Mirrovo surveys remove the interpersonal risk from feedback entirely. After responses arrive, the AI identifies exactly where safety gaps are concentrated — so you're working on the specific driver, not running a generic intervention.
How do you measure whether psychological safety is improving?
Measure psychological safety improvement with two parallel signals: quantitative (safety dimension scores on monthly pulse surveys showing upward trend) and qualitative (observable behaviour changes — more questions asked in meetings, earlier problem escalation, more peer-to-peer feedback). Both signals together give you a reliable picture; either alone can be misleading.
Timeline expectations for consistent leader behaviour change:
- Weeks 1–4 — No measurable score change expected. Team members are observing whether the new behaviours are consistent or performative. Trust is being evaluated, not yet given.
- Weeks 4–8 — Early behavioural signals may appear: slightly more questions in meetings, one or two people speaking up who hadn't before. Survey scores may tick up marginally.
- Weeks 8–16 — If behaviours have been consistent, survey scores should show a measurable improvement (typically 0.3–0.7 points on a 5-point scale). More people participating in retrospectives. Earlier escalation of problems.
- 6+ months — Psychological safety is becoming a team norm, not just a leader behaviour. New team members onboard into a culture where safety is the expected standard rather than the exception.
Written by Simon, Co-founder of Mirrovo
Simon has spent over a decade building and advising software teams across Europe. He co-founded Mirrovo to give team leaders a data-driven way to track whether their psychological safety investments are working — not just to feel like they are.
Frequently asked questions about improving psychological safety
Improving psychological safety is a long-term investment in team behaviour change — not a quick fix. The leaders who make the most progress are those who track it consistently, act on data, and hold themselves accountable to the behaviours that the research shows actually work.
How long does it take to improve psychological safety?
Early improvements are visible in team behaviour within 4–8 weeks of consistent leader behaviour change. Measurable survey score improvement typically takes 8–16 weeks. Deep, durable psychological safety — where it has become a team norm that persists even when the manager is absent — typically takes 6–12 months of sustained effort. The timeline is shorter for teams with a stable history; longer for teams recovering from a specific trust-damaging event.
What is the single most effective action for improving psychological safety?
Based on Edmondson's research and practitioner experience, the single most effective action is changing how a manager responds to problems and mistakes — specifically, responding with curiosity and support rather than blame or defensiveness. This behaviour is highly visible, tested frequently, and its pattern quickly becomes the team's shared belief about what happens when you speak up here. Get this one right, and other safety improvements follow more easily.
Can psychological safety be improved in remote teams?
Yes, but it requires more deliberate effort than in co-located teams. The informal signals that build trust — body language, casual conversation, visible empathy — are harder to convey remotely. Compensate by being more explicit about safety norms ("I want to hear dissent — please push back if you see things differently"), more generous with positive reinforcement of risk-taking, and more consistent about anonymous feedback channels since the interpersonal barrier to direct feedback is higher in remote contexts.
Should you tell the team you're working on psychological safety?
Yes — transparency about the goal accelerates progress. Naming the intention ("I've looked at our survey data and I want to create more space for everyone to speak up") gives team members a frame for the behaviour changes they're about to observe. It also creates accountability: once named, the team can hold the leader to the stated commitment. Avoid corporate jargon ("we're launching a psychological safety initiative") and opt for plain language about the specific change you're making.
Related guides
- What Is Psychological Safety and How Do You Build It? — the foundational guide to understanding what psychological safety is and why it is the strongest predictor of team performance.
- How to Run an Anonymous Team Survey (Step-by-Step) — how to measure psychological safety honestly using anonymous surveys that get around the interpersonal risk of direct feedback.
- 10 Warning Signs Your Team Health Is Declining — silence in meetings and declining survey participation are the top early signals that psychological safety is eroding.
- Team Health KPIs: Which Metrics Actually Matter? — how to track psychological safety as a quantitative KPI alongside the other three team health dimensions.
Ready to improve your team health?
Mirrovo turns anonymous survey feedback into concrete actions in minutes — no spreadsheets, no guesswork.
Start your free trial →