The Real Failure: It's Not Courage; It’s Structure
I have spent years walking manufacturing floors and watching how information—or the lack of it—travels from the operator at a machine to the manager in the office. One of the most common mistakes leadership makes is assuming that when an employee fails to report a safety hazard or a quality skip, it’s because they lack "courage" or are simply not part of a "culture of safety."
This is a fundamental misdiagnosis.
A failure to report isn't usually a character flaw; it is a structural design failure. When an operator notices a tool is vibrating outside of spec but chooses to stay silent, they aren't necessarily being "brave" or "cowardly." They are often making a calculated decision based on the system you have built for them. If reporting that issue requires them to stop the line, deal with a supervisor who prioritizes volume over precision, or fill out paperwork that will eventually be ignored by someone three levels up, then silence is the most logical choice they can make.
We need to stop treating these moments as moral failures and start seeing them as signal failures. If your "speak-up" program relies on an employee’s willingness to overcome a broken system just to do the right thing, you haven't built a safety culture; you’ve built a hurdle course. We must move away from trying to "train" more courage into people and start designing structures that make reporting the path of least resistance.
Naming the Problem: The Conflict-of-Interest Trap
The primary reason these systems fail is what I call The Conflict-of-Interest Trap. This happens when the person responsible for investigating a problem is also the same person—or belongs to the same department—that is incentivized by the metrics of that production.
Look at cases like Boeing or Wells Fargo. These weren't just "bad apples" making poor choices; they were systems where the people tasked with oversight had an inherent, built-in reason to look the other way. In a manufacturing context, this happens every day on the shop floor. If a shift lead is responsible for both hitting their production numbers and ensuring all safety protocols are followed, they will—almost every time—prioritize the number when things get difficult.
When we ask a supervisor to "investigate" an incident that happened on their own line during their own shift, we are asking them to be both the judge and the defendant. They cannot objectively weigh the cost of a safety violation against the benefit of keeping the machines running if they are the ones who will get blamed for a production dip. The trap is not just in the person’s heart; it is in their job description. If you want an honest look at why a process failed, the investigator cannot be someone whose primary goal is to keep that specific process moving without interruption.
Why It Persists: When Ownership and Investigation Live Together
The reason these flawed structures persist is that they are easier to manage on paper. It is simpler to have one manager oversee both production and safety reporting than it is to create a truly independent oversight channel. This leads to a situation where the "official" process exists, but the "actual" process is governed by unspoken rules of convenience.
We can see this clearly when we look at what people say versus what is actually happening on the floor:
| The Comfortable Rationalization | The Underlying Reality |
|---|---|
| "Our door policy is always open." | The manager only listens to reports that don't require stopping production. |
| "We have a robust reporting system." | Reports are filed in a binder that nobody opens until an audit occurs. |
| "The team feels empowered to speak up." | Workers know that speaking up results in more work for their peers, not less. |
| "Safety is our first priority." | Safety is the first priority only when it doesn't conflict with the daily quota. |
When investigation and ownership live together, the organization chooses the path of least resistance every time. The fear of a production hit creates a silent pressure to ignore "minor" deviations until those deviations compound into a major failure. It is not a conspiracy; it is just how human beings respond to conflicting incentives. If you give someone two reasons to do something—one that makes their life easier today and one that makes the company safer tomorrow—they will choose the easy one every time unless the structure forces them otherwise.
What This Really Costs You (The Stakes)
When we allow these structural conflicts to remain, the costs are not just potential fines or occasional safety incidents. The cost is a steady erosion of your operational integrity.
First, there is the Cost of Hidden Risk. When people realize that reporting a problem leads to no change—or worse, leads to friction with their peers—they stop reporting altogether. They learn to "work around" the problem. A cracked seal is patched; a faulty sensor is ignored; a shortcut becomes the new standard work. These issues don't go away; they just hide until they cause a catastrophic failure that forces an unplanned shutdown or, worse, injures someone on your line.
Second, there is the Cost of Lost Trust. When an employee sees a peer get in trouble for speaking up—or see nothing happen when they do—the social contract of the team breaks. You lose the ability to lead through influence because you have to lead by enforcement.
Finally, there is the Cost of Stagnation. If your "improvement" reports are only coming from people who aren't afraid to be seen, you will never see the real waste in your processes. You will only ever hear what management wants to hear, leaving the actual bottlenecks and inefficiencies buried under a layer of polite silence.
A Fix That Works: Separating the Roles
To fix this, we must move toward Structural Separation. We need to decouple the reporting mechanism from the production hierarchy entirely. This is not about adding more "awareness" training; it is about redesigning the flow of information so that a worker doesn't have to compromise their values or their standing with their peers to do the right thing.
A robust system requires three distinct, separated roles:
- The Reporting Channel: A way for an operator to flag a concern (a "near miss," a tool failure, or a process deviation) that goes directly into a tracking system without passing through their immediate supervisor first.
- The Independent Investigation: The investigation of that report should be handled by a team whose performance is not tied to the output of that specific production line. This could be an internal safety team from a different plant or an independent ombursman function.
- The Action Review: Once the issue is identified, it is handed back to management for correction.
By separating these three steps, you remove the incentive for "convenient" ignoring of problems. The person reporting isn't afraid of their boss; the investigator isn't worried about production numbers; and the manager who eventually fixes the problem is presented with a clear, documented fact that they cannot ignore without taking personal responsibility. You move from a system based on trust in individuals to a system based on reliability of the process.
Practical Takeaways for Your Next Gemba Walk
You don't have to overhaul your entire corporate structure by Monday morning, but you can begin auditing where your current "leaks" are occurring. On your next walk through the facility, look for these three indicators:
- The Reporting Path Audit: Ask an operator on a non-critical task: "If this machine were making a noise that suggested it was about to fail, who is the first person you would tell?" If their answer leads directly to a supervisor whose primary job is keeping that line running today, your reporting structure has a conflict of interest.
- The "Near Miss" Log Check: Look at your recent safety or quality logs. If you haven't had a "near miss" reported in months, it doesn't mean the floor is perfect; it likely means the barrier to reporting is too high. A healthy system has plenty of small reports that prevent large disasters.
- The Resolution Verification: Pick three recent issues that were reported and fixed. Trace them back. Did they go through a "filter" where someone tried to minimize their importance? If you find instances where a problem was "managed away" rather than solved, your current reporting chain is too short or lacks the necessary independence.
Start by identifying one area—perhaps just one specific cell or process—where you can implement a direct-to-reporting line that bypasses the immediate supervisor for safety and quality issues. Build trust in small segments before trying to overhaul the whole plant at once.
Download and Share This Issue
Call to Action
What is one unwritten rule about escalation in your plant that you suspect is actively undermining compliance? Share this with a colleague who needs to rethink how 'speak-up' actually works.
Newsletter replies and questions: [email protected]
Follow updates on X.com: @kaizen_6sigma
References
https://www.leanblog.org/2026/08/why-speak-up-programs-fail-boeing-wells-fargo/