Psychological Safety and Change: Why Your Team’s Brains Are Wired to Resist
The new process goes live on Monday. At the end of the kickoff you ask, "Any questions?" Nobody has one. Two weeks later, half the team is still working the old way, and you hear about the problems from someone in another department.
It's natural to read that quiet as agreement. You explained the change clearly, you asked for input, and nobody raised a concern. But quiet during a change often means people are still deciding whether it's safe to say what they think. That's a psychological safety question, and it's one you can do something about this week.
Key takeaways
Psychological safety is Amy Edmondson's term for a team's shared belief that it's safe to take interpersonal risks, like asking a question or admitting a mistake.
During a change, people often stay quiet because they're watching what happens to the first person who speaks up. Your response to that person teaches the whole team.
Safety without clear standards turns into comfort. Standards without safety turn into anxiety. Change needs both.
Your own read of the silence is worth questioning. "If they had a concern, they'd tell me" is a belief, and you can test it.
Keep asking after launch. The question that gets an answer is the one people hear in the middle of real work, again and again.
What psychological safety means during a change
Harvard's Amy Edmondson defined psychological safety as "a shared belief held by members of a team that the team is safe for interpersonal risk taking" (Edmondson, 1999). Interpersonal risk is anything that could make you look uninformed, incompetent or difficult in front of your colleagues: asking what a new term means, saying you haven't figured out the new system, or telling your manager the rollout date won't work.
A change creates a lot of these moments at once. Everyone is a beginner again. The people who were the experts last month are now learning alongside everyone else. Questions that would have been easy to ask about the old way feel riskier about the new one, because the answer might show that you're behind.
Psychological safety doesn't mean comfort or constant agreement. People on a psychologically safe team still get direct feedback and still have to meet the standard. The difference is that they can say what's getting in the way before it becomes a missed deadline.
Why teams go quiet when things change
Here's what your team's brains are actually doing. Every person on your team has a history of what happened when someone raised a problem. Maybe a concern was welcomed and acted on. Maybe it was brushed aside, or the person who raised it was quietly seen as "not on board." People remember those moments, and they use them to decide what to do next.
Under pressure, the practiced response is faster. If staying quiet has been the safer choice before, it's the choice people make on a busy Tuesday when the new tool does something unexpected. They work around it, go back to the old way, or ask a trusted colleague instead of you. None of that means they're against the change. It means the old pattern of keeping your head down is still familiar.
Feeling alone makes this harder. I spent 18 years leading learning and development inside a Fortune 500 company. When I sponsored the change program for a 2019 system rollout, one concern we heard from title staff was: "Why do I feel like I am the only one learning?" When everyone keeps their struggles to themselves, each person assumes they're the one who's behind. So they stay quiet and hope to catch up before anyone notices.
One response we built was simple: ask people to share successes and challenges in their office meetings. When one person says what's been hard, the others can see they aren't the only one, and it gets easier for the next person to say it too.
One small shift: In your next team meeting, name one part of the change you're still learning yourself. Then ask each person for one thing that's working and one thing that's been hard.
Safety without standards turns into comfort
Some leaders worry that psychological safety means lowering the bar. Edmondson's answer is that safety and accountability are two separate dimensions, and teams need both. In a conversation with David Rock at the NeuroLeadership Institute, she described four combinations (NeuroLeadership Institute, 2024):
Low safety, low accountability: the apathy zone, where "people don't really care about their work."
High safety, low accountability: the comfort zone, where "people feel safe to express their ideas but don't take ownership."
Low safety, high accountability: the anxiety zone, where people "are reluctant to take risks or offer new ideas."
High safety, high accountability: the learning zone, where "people collaborate and learn from each other's mistakes."
The comfort zone is easy to mistake for a healthy team. Early in my career, new to a company and over-prepared for everything, I supported a leadership meeting where everyone was nice and agreed to everything. Weeks later, nothing had happened, and nobody said a word about it. It wasn't fear, threat or politics. These were very successful people who were used to success coming readily, and they had no motivation to change.
That's why safety alone doesn't fix a quiet team. Someone also has to own the next step, with a date.
The anxiety zone looks different from the outside. People follow the new process while you're watching and drift back to the old one when you're not. They report good news and hold back bad news until it's too late to fix cheaply.
During a change, you want the learning zone: a clear standard for what "done" looks like, and a team that can tell you early when something is in the way of it.
What you do after someone speaks up matters most
Your team learns what's safe mostly from what happens the first time someone disagrees, admits a mistake or says the new process isn't working.
When that moment comes, you're usually busy, and the concern may feel like a setback. You're trying to keep the change moving, so the natural reaction is to reassure, explain again or move on. Your team may read that as "we don't want to hear it."
A better response takes about a minute. Thank the person for raising it. Ask what they're seeing and where it shows up in their work. Say back what you heard, so they know it landed. Then be clear about what happens next, even if the decision doesn't change. People can usually accept a "no" when they can see their concern was taken seriously.
Treat small experiments the same way. Edmondson calls some failures intelligent. HBR's summary of her 2011 article describes these as the ones "at the frontier, where 'good' failures occur quickly and on a small scale, providing the most valuable information" (Harvard Business Review, 2011). When someone tries a new step and it doesn't work, ask what they expected, what happened and what they'd try next. Keep the standard clear, and treat what they learned as useful to the whole team.
One small shift: The next time someone raises a concern about the change, ask one follow-up question before you respond. "Where did you run into that?" works well.
Question your own read of the silence
The belief that often keeps leaders from asking is a reasonable one: "If they had a concern, they'd tell me." You would tell your manager, so it's easy to assume your team would too.
The Shift Method is how I work through a belief like that. Applied to a quiet team, the five steps look like this:
Identify the belief. Write down what you're assuming the silence means. For example: "Nobody raised a problem, so the rollout is going fine."
Question the evidence. Think about the last time someone on your team raised a problem with a decision you'd already made. What happened next? Did you hear about the issue from them, or from someone else first?
Reframe it. Replace the belief with one the evidence supports. "The team hasn't raised a problem yet" is more accurate, and it leaves space for you to go and look.
Picture the vision in detail. Describe what a good team meeting looks like three weeks from now. Who is speaking? What kinds of problems are people bringing up? What do you say when they do?
Act. Choose one conversation this week that moves you toward that meeting, and have it.
When your team starts talking
The first answers you get may be small or cautious. That's a good sign, because it means someone tested the water. How you handle those first small concerns matters a lot for whether bigger ones follow.
If your organization is working through a change and the quiet is starting to worry you, Feed Your Brain | Consulting helps leaders find out what their teams haven't said yet and build the habits that keep people talking.
Frequently asked questions
Is psychological safety just another word for being nice to employees?
No. Psychological safety means people can raise concerns, ask questions or admit mistakes without being humiliated or punished for it. You can still be direct about a missed expectation. The test is whether people can tell you what happened and help solve it, rather than hiding information to protect themselves.
How can I tell if my team lacks psychological safety during a change?
Look for concerns that reach you secondhand, meetings where nobody asks a question about something new, and problems that surface only after they're expensive. One quiet meeting doesn't tell you much. A pattern of hearing about problems late does.
Can you have psychological safety in a high-pressure, high-performance team?
Yes. Edmondson describes safety and accountability as two separate dimensions, and high-performing teams are high on both. Make the outcome and each person's part in it clear, and give people a regular place to flag a risk before it grows.
What's the fastest way to build psychological safety in a new team?
Say what you expect about questions, disagreement, and mistakes, then show it in how you respond. A new team watches what happens after the first person speaks up. Consistent follow-through tells them more than any promise you make at the start.
Why do people resist a change that's good for the company?
A change that helps the organization can still leave someone unsure about their own work: which steps to follow, how they'll be judged, or what to do when the new way doesn't work. When time is short, people reach for the way they know. Clear next steps and a safe place to ask questions make the new way easier to reach for.
What if I'm the one making people hesitant to speak up?
Start with specific behaviors, like interrupting, answering a concern with a defense, or moving on before someone finishes. Ask one person you trust what they notice, listen without arguing, and choose one response to change. When you get it wrong, say so and keep the conversation going.
How does psychological safety affect AI adoption at work?
People are more likely to practice unfamiliar AI tasks when they don't have to pretend they already understand them. Be clear about which uses are appropriate and what's still undecided, give people time to try relevant tasks, and ask what they learned. Confidence grows through supported use.
About this article. Tiffany Whitney is a NeuroLeadership-trained brain-based coach with 18 years of Fortune 500 Learning & Development leadership, and Amazon bestselling co-author of Strength with Kathy Ireland. Statistics are cited to primary sources; where a figure comes from an organization's internal data rather than independent research, that is noted in the text. This article is for educational purposes and is not medical, psychological, or clinical advice.
