Pat Schneider, Chief People Officer at Chevron Federal Credit Union, has spent his career inside industries where pressure and risk are constant: hospitality, security, and financial services. His view on innovation is grounded in that reality. People do not bring new ideas to work when they expect to be punished for being wrong; they wait, hedge, or leave.
The wider issue is that many leaders ask for innovation and stability at the same time without recognizing the trade-off. Innovation requires speaking up about problems, questioning assumptions, and admitting when something failed. Without psychological safety, those behaviors get filtered out before they reach a leader's desk.
HR leaders who care about both innovation and retention have to treat psychological safety as core infrastructure. The work is concrete and measurable, not philosophical.
Why psychological safety drives both innovation and retention
Teams with high psychological safety bring more ideas forward and lose fewer people. HBR's foundational explainer makes the case clearly; HBR's piece on what psychological safety is walks through the research on team performance and openness to disagreement. Teams that feel safe disagree better, learn faster, and stick together longer.
For HR leaders, the practical move is to build safety into manager development, listening systems, and ER processes, not just culture decks. AllVoices' employee survey tool gives people leaders a direct read on whether employees feel safe raising concerns.
Safety also depends on follow-through. Employee feedback programs that ask for input and produce no visible action teach people to stop offering it. The behavior becomes self-reinforcing in either direction.
Building psychological safety across an organization
What signals tell you a team has psychological safety?
Look for disagreement in meetings, frequent admissions of mistakes, questions from junior staff in front of senior staff, and willingness to revisit decisions. The absence of those signals is rarely a sign of consensus; it is more often a sign that people have learned to stay quiet.
McKinsey's research on the topic walks through the leadership behaviors that change those dynamics; you can read more in McKinsey's explainer on psychological safety.
How do you build safety on a struggling team?
Start with the manager. Train them to invite dissent explicitly, to model admitting mistakes, and to respond to bad news without punishing the messenger. Over time, the rest of the team takes its cues from those behaviors.
Pair manager work with anonymous channels. AllVoices' anonymous reporting tool gives team members a way to raise concerns they are not yet ready to put their name on, which is often where the most important signals live.
What actually works
Make admitting mistakes a leadership behavior
The most underused tool for building safety is leaders admitting their own mistakes in front of the team. When senior leaders model the behavior, junior staff start to do it too, and the team's collective intelligence rises. Hide your mistakes and the team will hide theirs.
Use coaching to help leaders who struggle with this. For some, it is the hardest behavior to learn.
Separate ideas from identity
Innovation requires people to share half-formed ideas. That cannot happen if every idea attaches to the contributor's reputation. Train teams to evaluate ideas on their merits, separately from who proposed them, and protect that norm in meetings.
The same principle applies to dissent. People should be able to push back on a senior leader's idea without fear that the disagreement will follow them into a performance review.
Treat retaliation as the safety killer
Nothing damages psychological safety faster than retaliation, real or perceived. HR leaders who want safety to last have to build clear anti-retaliation policies and respond visibly when boundaries get crossed. AllVoices' whistleblower hotline gives employees a structured channel for the most sensitive cases.
Make the anti-retaliation commitment visible across onboarding, manager training, and ER documentation. The visibility itself signals what the company will protect.
Where Employee Relations Fits
Psychological safety and ER work are linked at the foundation. AllVoices' employee relations function support gives HR teams a structured way to handle the moments when safety has been broken, and our HR case management system keeps the trail of every concern in one place. Strong ER infrastructure is one of the clearest signals that an organization takes safety seriously.
How does ER reinforce psychological safety?
When concerns get heard, investigated, and resolved, employees learn that the system can be trusted. When concerns disappear, the lesson is that speaking up is a waste of time at best, dangerous at worst.
That dynamic is why ER process design matters as much as ER outcomes. Speed, fairness, and follow-up are the three pillars; missing any of them undoes the safety work elsewhere.
Frequently Asked Questions About Psychological Safety
How is psychological safety different from being nice?
Psychological safety is the ability to take interpersonal risks, including disagreement and admission of error. It often requires direct, even uncomfortable, conversations. Niceness can actually undermine safety by suppressing dissent.
How do you measure psychological safety?
Use survey questions about willingness to raise concerns, comfort admitting mistakes, and confidence that input is heard. Pair survey data with ER case patterns and exit interview themes.
How does psychological safety affect retention?
Significantly. Employees who feel unsafe are more likely to quietly disengage and eventually leave. Safety is one of the strongest predictors of long-term tenure, especially among high performers.
What is the manager's role in building safety?
Central. Managers shape the conditions for safety on their teams every day. No company-wide program can compensate for a manager who routinely punishes bad news.
How do anonymous channels fit a safety strategy?
They give employees a path for concerns they are not yet ready to raise directly. Used well, with consistent follow-up, they reinforce the company's commitment to listening.
What's the first step for HR leaders who want to put this into practice?
Start with one team and one measurable outcome. Pick a function where the issue shows up sharply and a leader who is willing to model the new practice. Map the current state honestly: what is happening, who feels it, and what would good look like in ninety days. Share that picture with the team, ask them what is missing from your read, and adjust before launching anything formal. The goal of step one is alignment, not activity.
Once the picture is shared, pick two or three changes you can make inside one quarter. Resist the urge to launch a full program. Run the changes, measure the response with simple pulse questions, and report back. The combination of a focused team, a clear measure, and a public commitment to learn is what turns a good idea into a practice that spreads. HR leaders who try to launch everywhere at once usually end up launching nowhere.
Iterate from there. The teams that succeed treat the first cycle as a prototype, not a rollout. They keep what worked, drop what did not, and write down what they learned. By the time the practice expands to the next group, it has been pressure-tested by people who have a stake in seeing it work. That is the unglamorous work of putting any people-strategy idea into practice, and it is also the work that compounds.
The Bottom Line for HR Leaders
Pat Schneider's work across financial services and hospitality points to one durable lesson: psychological safety is what makes innovation and retention possible at the same time. Without it, ideas stay hidden and people leave. With it, both compound.
The work is concrete. Manager training, listening systems, ER infrastructure, and anti-retaliation policies are how safety gets built; culture decks alone will not do it.
.avif)
.avif)
.avif)