Psychological safety: how to build a team that speaks up before problems get worse 

Home > Insights > Psychological safety: how to build a team that speaks up before problems get worse

3 Things that must change for psychological safety to thrive

To keep this practical, I've broken it down into three things that have to change and five steps to get you there. 

5 steps to help you make the 3 necessary changes

1. Model vulnerability

Vulnerability here doesn't mean oversharing, lowering your standards, or pretending you have no expertise. What I mean is that you should be honest about your mistakes, your uncertainty, your limitations, and your need for other people's input.

In practice, this means:

• Admitting your own mistakes and sharing what you learned from them.

• Opening up when you don't have the answer and asking for help. "I don't have the answer to this yet. What are you thinking?"

• Sharing an idea while it's still half-formed and inviting your people to poke holes in it. "Here's an early thought I have: what risks, gaps, or unintended consequences do you see?"

This tells to your team that the truth matters more than looking flawless, and over time, they'll start adjusting their behavior.

2. Reinforce vulnerability consistently

When someone on your team asks a question they're worried is basic, admits an error, raises a concern, or has a different view from you, what you do in that moment can either increase psychological safety or lower it.

One thing that has really helped me in this regard is what I call the ACPF rule. 

• A- Appreciate them, explicitly. "Thanks for raising that."

• C- Show curiosity, please don't be defensive. "Tell me more. What else are you seeing?"

• P- Protect the person who opens up; if others react badly. "Calm down everybody, let's hear Maxwell out."

• F- Follow through: show them how their input changed a decision or triggered action.

3. Run blame-free reviews after projects or incidents

A blame-free review, sometimes called a blameless post-mortem, is a structured conversation held after something goes wrong, a failure, a mistake, a bottleneck. Instead of asking who made the mistake, you investigate how and why the system, process, or workflow allowed that mistake to happen in the first place.

Start by setting the tone clearly: "This is a learning conversation, not a fault-finding exercise. Our goal is to understand the work and make it better next time." Then ask three questions:

• What went well?

• What didn't go as planned? (Follow this with the 5 Whys to get to the root cause.)

• What will we do differently next time?

Example: following question 2 with the 5 Whys

What didn't go as planned? A customer’s claim was not resolved within the promised 10 working days, it took 25 working days.

Why did the claim take 25 working days?the claims officer did not receive the required supporting document until late in the process.

Why was the document received late? The customer was not clearly informed about every document required when they first submitted the claim.

Why was the customer not clearly informed? The claims officer used an old checklist that did not include the new documentation requirement.

Why was the officer using an outdated checklist? Because the updated checklist had been shared by email but was not added to the claims-management system or the team’s standard workflow.

Why was the updated checklist not added to the workflow? There was no formal process or assigned owner for updating frontline tools and communicating policy changes across the claims team.

You see that the issue is not simply that “the claims officer was slow.” The root problem is a missing change-management process: no one was assigned to ensure that policy changes become part of the tools and workflows employees used every day.

So the third review question (What will we do differently next time?) will focus on resolving the root cause not blaming or shaming anyone.

This approach protects psychological safety because it shifts the conversation from “Who failed?” to “What allowed this to happen, and what do we need to improve?” To be clear, the aim of blameless reviews is not to excuse or ignore people's misconduct or dodge accountability. They allow everyone to learn from human errors and system weaknesses, so each review must result in clear ownership and follow-through on what must change.

4. Treat conflict and disagreement as collaboration

When someone disagrees with you, what they're really saying is that their background and experience gave them a different perspective, not that they're trying to undermine you. Collaborate with them to work through it. That said, don't mistake collaboration for automatically agreeing with everything, use your judgement, and take time to think something through if you need to. There's really no such thing as losing here. You either win, or you learn.

I also won't skip the fact that in organisations with unhealthy politics, some people may use this as a means to oppose your initiative just to climb the ladder. So again, use your judgement to discern the intent of the person disagreeing and the substance of their disagreement. Not everyone raising a concern is doing so in good faith.

If the basis of the disagreement does not align with the goal at hand, and you have explained this to the person but they keep returning to the issue or discussing it with others, then you have a different problem to address.

5. Change your own beliefs and assumptions about the workplace

We've all encountered people who genuinely mean what they say in the moment, but revert to their old behaviour anyway, because the underlying mindset behind that old behaviour never changed. This is exactly why this step matters. Without it, you risk installing the language of psychological safety in your company, "we value honesty here!", but your team still stays quiet, because your reactions, decisions, and systems have not changed.

Here are the specific mental models worth examining.

1. As the leader, I should have all the answers

Your job as the leader is to create the conditions for the best answers to surface and come to you. To make this work, ask questions when you need clarity. Ask for help sometimes, even when you already know what to do. Speak last in meetings, so people don't defer to whatever you think and skip sharing their own view.

2. Dissent is disrespect

Respectful disagreement is a contribution to better decisions. Every member of your team carries experience and knowledge you don't have. Hearing them out can quickly sharpen what you're already proposing, or catch a fail you didn't see coming. When someone disagrees, ask them why. They may be right, wrong, or somewhere in between. If they're wrong, help them understand why, often you'll find they're pushing back simply because they don't yet fully understand the scope of what's being proposed, which is really just an opportunity to bring them along. Either way, thank them for raising it.

An easy way to encourage dissent is to ask questions like,

• Do you have a different perspective on this?

• Do you see things differently based on your background and experience?

3. If I invite input, I lose authority

In reality, asking for input strengthens your decisions by helping you refine it from multiple angles, moreover, you still own the final call.

4. If I show uncertainty, people will lose confidence in me

This belief is one of those that push leaders to overstate their certainty and hide doubts, and employees begin to copy that, presenting overly polished updates instead of flagging concerns. In practice, you don't need to overshare every anxiety. Just say: "Here's my current thinking. What am I missing? What should we be testing or questioning?"

5. My people should bring me solutions, not problems

This sounds reasonable on the surface, but it tells your team they need a fully-formed solution before they're even allowed to flag a risk. By the time they figure out a solution and come to you, the problem may be bigger, harder, and more expensive to fix. A helpful belief to hold can be: it's okay for someone to flag an issue without having any idea how to solve it. Early visibility matters more. 

When someone flags an issue, respond with: "Thank you for raising this early. What do you know so far? What help do you need? Who else should be in this conversation?" Or be like Alan Mulally when Mark Fields flagged one of his slides red, Mulally said, “Mark, that’s great visibility. Who can help Mark with this?”

6. Hierarchy exists for a reason, people should respect it

To be clear, hierarchy itself isn't the problem. The danger is assuming seniority automatically translates to superior insight, or that junior staff need permission before contributing. Hierarchy clarifies accountability, it should never block information from moving upward. For example, your frontline staff often see customer friction, operational failures, and emerging risks long before you do as an executives. But you also hold strategic context the rest of the team doesn't have, so you need both perspectives to see the full picture.

7. I already have an open-door policy

An open door isn't proof anyone actually feels safe walking through it. You might believe you're approachable simply because you're willing to listen when someone shows up, meanwhile your team has learned, from watching how you react, that coming forward is risky. It's helpful to know that safety isn't measured by your availability but by how people perceive the idea of coming forward to speak. Will they be welcomed and protected.

To make this work, don't wait for people to come to you. Actively ask for input, make the ask specific, and always remind them that they're safe opening up to you.

8. If no one objects, everyone agrees

Silence gets read as consensus far too often. In an organization without psychological safety, silence can just as easily mean fear, exhaustion, a belief the decision's already made, or a sense that disagreeing will cost them something later. Silence is ambiguous, you must make it easy for people to speak up. Lower the social risk of speaking up with questions like:

• What could make this plan fail?

• What concern hasn't been voiced yet?

• If you were advising a competitor, how would you tell them to beat this plan?

• Whose perspective is missing from this room?

• What would someone junior to us be reluctant to say out loud right now?

Status, politics, and the fear of looking incompetent can undermine psychological safety even in a room full of executives.

Common pitfalls to avoid

• Don't mistake psychological safety for excusing weakness. There's nothing weak about it, we're talking about candid, hard conversations here.

• Don't run a single one-off training and call it done, with no follow-through in how you actually behave day to day.

• People speaking up doesn't obligate you to act on everything they say. Make it clear upfront that not every idea or flagged risk gets acted on immediately, and when something doesn't move forward, give the person a brief reason why. You don't owe them every strategic trade-off behind the decision, just enough feedback to not leave them wondering if they were heard at all.

• Admitting a mistake, uncertainty, or half-formed idea does not require you to sound defeated or apologetic. You do not need to pretend you have all the answers, but you should communicate with steadiness. Use a calm tone, an upright and open posture, and direct language.

A simple starter playbook you can use tomorrow 

1. Name it: In your next team meeting or a one-on-one, briefly explain what psychological safety is, and why it matters for how your team actually works.

2. Model one vulnerability: Share a recent mistake of your own, and what you learned from it.

3. Invite one challenge: Ask, "What's one thing about our current plan that worries you?", and genuinely thank the first person who answers.

4. Set one norm: Agree on a single rule as a team, for example: we thank people before we critique their idea, or we ask questions the moment we're unsure about something.

5. Repeat it: for every conversation be it a meeting or just a casual work chat.

Frequently asked questions

What is psychological safety?

Psychological safety is a shared belief within a team that it's safe to speak up, ask questions, admit mistakes, or disagree, without fear of punishment, humiliation, or retaliation. The term was coined by Harvard Business School professor Amy Edmondson.

Why does psychological safety matter for a business?

Without it, problems stay hidden until they become expensive. Employees who don't feel safe speaking up will hide mistakes, withhold concerns, and present overly positive updates, meaning leadership often only discovers issues once they've already grown much harder and costlier to fix.

How do you build psychological safety on a team?

It requires change in three areas: the beliefs leaders hold about control, error, and status; how leaders behave daily in how they listen, react, and follow up; and what the organisation's systems actually reward, measure, and investigate. Five practical starting points are modelling vulnerability, rewarding honesty, running blame-free reviews, treating disagreement as collaboration, and actively replacing unhelpful leadership beliefs.

What is a blame-free review?

A blame-free review, or blameless post-mortem, is a structured discussion held after a mistake or failure that focuses on how and why a system or process allowed the error to happen, rather than on who is personally at fault. It typically uses a technique like the 5 Whys to trace a problem back to its true root cause.

Does psychological safety mean avoiding accountability?

No, psychological safety is about responding to mistakes and uncertainty with a learning mindset, not about excusing misconduct. Deliberate dishonesty, harassment, or reckless disregard still warrants investigation and fair consequences, the distinction is between human error in a flawed system and intentional misconduct. 

Let's talk

If this topic resonates with you and you'd like to talk more about it, reach out so we can schedule a time to chat.

When you reach out, let me know which of these you're looking for:

• An open conversation about the topic itself. No strategy or brand talk required, just an open discussion

• A conversation about your brand or business specifically

• Hands-on consulting or support: working together to realign things internally for your business

I welcome all three, and I'm happy to have these conversations with executives, team members, and team leads. Just let me know upfront which one you're after, so we can make the most of our time together.