Psychological Safety on the Production Floor
Practical ways to measure and build it
About fourteen months into my role as a department manager, I noticed something in our near-miss reporting data that I initially read as good news.
The numbers were dropping. Fewer near-misses being reported week over week. My first instinct was to feel good about it; the floor was running better, people were being more careful, the safety culture was improving.
A more experienced operations manager (one of the best I’ve ever worked with) set me straight. He looked at the data and said something I’ve never forgotten: “When near-miss reports go down, it usually means one of two things. Either your floor got dramatically safer, or your people stopped feeling safe enough to report. Which one do you think it is?”
I knew the honest answer. We hadn’t changed anything operationally that would explain a dramatic safety improvement. What had changed was that I’d responded to a couple of recent reports with more visible frustration than I’d intended. Not at the reporters, but at the situations they’d described. But that distinction, from my team’s perspective, was invisible. The signal that had landed was: reporting problems creates a reaction from the manager that feels unpleasant. So people started reporting fewer problems.
That’s when I understood what psychological safety actually costs when it’s missing. Not just engagement. Not just morale. Near-miss reports. The early warning system that stands between a manageable situation and something that puts someone in the hospital.
What the Term Actually Means Here
“Psychological safety” has become one of those phrases that gets used so frequently in management writing that it starts to lose its edges. In office environments, it often gets translated as: people feel comfortable sharing ideas in meetings, giving honest feedback upward, and taking creative risks without fear of ridicule.
That’s real and it matters. But on a production floor, the stakes are different and the translation has to be more specific.
On the floor, psychological safety means one concrete thing: your team brings you problems before they become crises.
The associate who notices something wrong with the equipment at the start of shift and says something rather than assuming it’ll be fine and not wanting to slow the line. The team lead who flags a quality concern even though it might delay shipment, rather than hoping the next shift catches it. The new hire who admits she doesn’t understand a procedure rather than guessing and potentially creating a safety issue because asking doesn’t cost her anything.
Psychological safety on the floor isn’t about feelings. It’s about whether problems surface before they become crises.
None of those moments require a particularly brave person. They require an environment where speaking up doesn’t carry a cost. Where the manager’s response to a problem being surfaced is curiosity and action, not frustration. Where the last person who raised a concern isn’t being talked about in ways that discourage the next person from doing the same.
When that environment exists, your floor becomes what I describe in Leading From the Floor as an early warning system. Problems get addressed during planned downtime rather than becoming emergency shutdowns. Quality concerns get investigated before defects reach customers. Near-misses get documented and fixed before they become incidents.
When it doesn’t, problems go underground. They keep happening. They just do it quietly.
How It Gets Destroyed (Usually Accidentally)
Most psychological safety damage on the floor isn’t caused by managers who berate people or create genuinely hostile environments. It’s caused by managers who respond to problems in ways that make problems feel slightly costly to surface. Not dramatically, not obviously, just enough that the calculation shifts over time.
A team lead reports an issue and the manager’s first response is “why didn’t you catch this earlier?” A near-miss gets documented and the manager spends the debrief focused on what went wrong rather than on what was learned. An associate raises a concern during a pre-shift and the manager moves past it quickly, visibly preoccupied with something else.
None of these responses is villainous, but all of them send a signal. And that signal, compounded over dozens of interactions, builds a floor culture where people have learned that raising problems is more trouble than it’s worth.
I wrote about this in The Culture You’re Building Without Knowing It. Culture isn’t what you intend, it’s what you consistently do and allow. The same mechanism that builds a culture of development or accountability builds or erodes psychological safety, one small response at a time.
The other common mechanism is what happened to an associate I inherited when I took over another team. His previous supervisor had publicly criticized a decision he’d made—a decision that turned out to be correct, but had an unexpected outcome he hadn’t anticipated. This associate was competent, experienced, and well-regarded by his peers. But he was consistently escalating quality decisions to me that he had the authority and judgment to make himself, because the cost of independent judgment, in his recent experience, was being publicly wrong in front of his team even when he was right.
No amount of reassurance fixed it immediately. What rebuilt it was a deliberate pattern of small, low-risk moments where I explicitly supported his judgment regardless of outcome, debriefed what went right rather than what could have gone better, and made it clear through repeated behavior—not just words—that his judgment was trusted here.
The High-Confidence Problem
There’s a version of psychological safety damage that doesn’t come from the manager at all. It comes from the floor itself. Specifically, from the highest-confidence voices on it.
In When Your Best Player Makes Your Team Worse, I wrote about the ways star performers can unintentionally block the development of the people around them. The same dynamic operates here. When the most experienced, most confident person on the floor reacts to a newer associate’s concern with visible impatience,“That’s not an issue, we’ve always done it this way,” she may not be wrong about the specific situation. But the signal that lands isn’t about the specific situation. It’s about whether raising concerns is worth the social cost.
Your highest-confidence team members are some of the biggest determinants of psychological safety on your floor but most managers don’t treat them that way. How they respond when someone surfaces a problem in front of them matters enormously. Whether they ask questions or dismiss them, model curiosity or signal boredom, encourage or roll their eyes.
This is one reason the conversation I described in the previous article, about reframing what excellence looks like for your star performers, has direct psychological safety implications. A team lead who understands that her job includes creating conditions where people around her feel safe to speak up is doing something qualitatively different from one whose standard is simply handling everything herself.
What Building It Actually Looks Like
It’s built the same way culture is built: through small, repeated, consistent behaviors that accumulate into a pattern your team can rely on.
The most important habit is how you respond to bad news first. Before you ask what went wrong or who missed something, get in the habit of acknowledging the act of surfacing it. Saying “I’m glad you told me” (and meaning it) is the single most powerful sentence you can say in response to a problem being raised. It’s not about being soft on standards. It’s about separating the act of speaking up from the content of what was spoken. People need to know that surfacing a problem is always the right call, even when the problem itself reflects a mistake.
Closely related is what happens after someone raises something and turns out to be wrong. This is the test most managers fail without realizing it. If an associate raises a concern and it turns out not to be an actual problem, how do you respond? If the response—even subtly—communicates that she wasted your time or should have figured it out himself before saying anything, you’ve just made the next concern marginally less likely to surface. The right response to a false alarm is: “Good catch. Better to check and find nothing than to miss something.” The behavior gets reinforced regardless of the outcome.
Follow-through matters just as much as the initial response. People track what happens to the concerns they raise, even when they don’t discuss it. When something gets surfaced and nothing visibly happens with it, the implicit message is that raising it didn’t matter. You don’t need to give a status update on every minor report. But for anything significant, closing the loop tells the floor that surfacing problems leads somewhere. That knowledge is what sustains the reporting behavior over time.
Finally, watch your visible reaction to near-misses specifically. Near-miss reporting rate is one of the most useful indirect measures of psychological safety on a floor. When it drops without a corresponding operational change, it almost always means people have learned that reporting isn’t cost-free. Review it deliberately. Not as a target to manage, but as a diagnostic. If the number is trending the wrong way, the question to ask isn’t “how do we get more reports?” It’s “what has happened recently that made reporting feel less safe?”
These aren’t complex interventions. They’re habits. And like the accountability habits I covered in Creating Accountability Without Constant Oversight and the recognition habits in Why Positive Feedback Comes First, they work through consistency rather than intensity. One good response to bad news doesn’t build psychological safety. Fifty of them, over months, does.
The Operational Payoff
Psychological safety is often discussed in ways that make it sound like a culture amenity; nice to have, important for morale, relevant when you have space for it. It isn’t.
When near-miss reporting is healthy, safety incidents go down. Not because people are being more careful in some abstract sense, but because the floor’s early warning system is working and small problems get addressed before they become large ones. In my time tracking the correlation between near-miss reporting rates and incident rates, the relationship was consistent: healthy reporting, fewer incidents. The causation runs directly through psychological safety.
Quality works the same way. A team that feels safe to flag concerns catches defects at the source. One that doesn’t ships them downstream. The customer complaint, the return, the re-work; these aren’t quality system failures in the first instance. They’re psychological safety failures that look like quality system failures by the time anyone traces them back.
The cost of a floor where problems go underground isn’t visible in the daily metrics until suddenly it is, in a way that’s hard to ignore. The near-miss that wasn’t reported. The quality concern that nobody raised. The equipment issue that turned into a shutdown because nobody wanted to be the one to slow the line.
Building psychological safety is operational risk management, not just people management. The managers who treat it as the former build floors that are genuinely safer, genuinely higher quality, and genuinely more resilient because their team is working for them, not around them.
From Theory to Action
Pull your near-miss reporting data for the last three months. Is it trending up, flat, or down? If it’s down and nothing operationally explains why the floor became dramatically safer, that’s a culture signal worth investigating. Don’t try to reverse-engineer the cause from the data. Ask. A direct, genuinely curious question to a team lead you trust (”Have you noticed any change in how people feel about reporting issues?”) will tell you more than the numbers will.
Audit your last five responses to bad news. Not your intended responses—your actual ones. Think back to the last five times a team lead or associate surfaced a problem. What was your first reaction, and what signal did it send about the act of surfacing it versus the content of what was raised? If you can’t remember, that’s useful information too.
Practice “I’m glad you told me” this week. Not as a script, as a genuine reframe. The next time someone brings you a problem, before you do anything else, acknowledge that they brought it. Then address the problem. The order matters. The problem gets addressed either way; the acknowledgement is what shapes the next decision about whether to surface something.
Watch how your highest-confidence team members respond to concerns. Your stars set the social norms on your floor as much as you do. If your most respected team lead visibly dismisses concerns from newer associates, that behavior is doing more damage to your early warning system than your management responses are building. Address it directly, as a development conversation, not a performance one.
Close the loop on something that was raised. Pick one concern from the past two weeks that someone surfaced, formally or informally, and go back to that person with a brief update on what happened with it. Not because one update changes the culture, but because the habit of closing loops, practiced consistently, tells your floor that raising concerns leads somewhere. That knowledge accumulates.
Protect the person who’s wrong. The next time someone raises a concern that turns out to be unfounded, pay attention to how you respond and how the people nearby respond. Reinforce the behavior publicly and specifically: “That was the right call. Better to check and be wrong than to stay quiet and miss something.” That sentence, said genuinely in front of the team, does more to protect future reporting than a month of safety training.
Use your one-on-ones to surface what you can’t see from the floor. The concerns that never make it to a report almost always exist somewhere in your team leads’ awareness. A direct question like “What are people hesitant to raise with me?” when asked in a context that feels genuinely safe, will surface things you’d never find another way. The fact that you asked is itself a psychological safety signal.
This post concludes the Building High-Performance Teams arc, which began with The Culture You’re Building Without Knowing It, continued through How to Raise the Floor, Not Just the Ceiling and When Your Best Player Makes Your Team Worse, and ends here.
Next: The Conversation You Keep Postponing. This will be the first article in the Performance Management arc, looking at the feeling of knowing you need to have a difficult conversation and finding seventeen reasons to wait.