A plant is producing defective parts. The quality team investigates. The root cause is a worn fixture. The corrective action replaces the fixture. Three months later, a different fixture on the same line wears out, and a different defect reaches the customer. The quality team investigates again. Another root cause, another corrective action, another cycle.

This is the pattern I have seen in every company I have worked for and every plant I have audited. Quality problems are treated as technical problems with technical solutions. Find the root cause. Fix it. Close the 8D. Move on. And the problems keep coming, because the technical root cause is never the actual root cause.

The actual root cause is almost always a leadership decision.

The leadership decisions behind every quality problem

Let me trace a few "quality problems" back to their actual origin:

The worn fixture. Why was the fixture worn? Because the preventive maintenance schedule was extended from three months to six months. Why was it extended? Because the maintenance budget was cut by 20 percent to meet a quarterly cost target. That is not a quality problem. That is a leadership decision.

The untrained operator. Why was the operator untrained? Because the training period was reduced from four weeks to two weeks. Why was it reduced? Because the plant was short-staffed and production needed bodies on the line. Why was the plant short-staffed? Because hiring was frozen to control costs. That is not a quality problem. That is a leadership decision.

The supplier defect. Why did the supplier ship nonconforming parts? Because they changed their process without notification. Why did they change their process? Because the buyer negotiated a 12 percent price reduction that forced the supplier to cut corners. Why was the price reduction demanded? Because procurement was incentivised on cost savings, not on total cost of ownership. That is not a quality problem. That is a leadership decision.

Quality does not fail in the factory. Quality fails in the meeting room where the trade-offs are made.

The cost-down spiral

The most common pattern I see across manufacturing is the cost-down spiral. Leadership sets aggressive cost reduction targets. Procurement squeezes suppliers. Maintenance defers preventive work. Training is shortened. Inspection is reduced. Quality is eroded, one decision at a time, each decision rational in isolation and destructive in aggregate.

And then the defects start. And the cost of dealing with them — sorting, rework, line downtime, customer returns, 8D investigations, expedited freight, crisis meetings — exceeds the cost that was saved by a factor of five to ten. But the cost of poor quality is not visible on the P&L in the same line as the cost savings, so leadership does not see the connection. They see a quality problem. They do not see their own decisions reflected in it.

The conversation nobody wants

I had this conversation with an executive team once. I presented the data: over twelve months, cost reduction initiatives had saved €1.8 million. Over the same period, the cost of poor quality — the sorting, rework, customer credits, expedited freight, and quality team overtime directly attributable to the system degradation caused by those initiatives — had increased by €3.4 million. The net effect of the cost reduction was a €1.6 million loss.

The CFO disputed the numbers. The COO said the quality costs were inflated. The CEO asked whether I was suggesting they should stop pursuing cost reductions. I said no — I was suggesting they should pursue cost reductions that accounted for the total cost, not just the savings. The conversation did not go well. It never does, because the implication is uncomfortable: the people responsible for fixing the quality problem are the people who created it.

What changes when you call it a leadership problem

The language matters. When you call something a "quality problem," the responsibility falls to the quality department. The quality department investigates, writes corrective actions, and tries to fix a system they do not control. The leadership team reviews the results and asks why quality has not improved. The cycle continues.

When you call it a leadership problem, the conversation changes. The question is no longer "how do we fix this defect?" The question is "what decision did we make that created the conditions for this defect, and what decision do we need to make to prevent it from recurring?" That is a question leadership can actually answer, because leadership controls the system conditions — budgets, resources, priorities, incentives — that produce quality outcomes.

I have seen this shift happen exactly once, at a plant where the plant manager was willing to hear it. He looked at the data and said "you are telling me that my cost pressures are creating quality problems." I said yes. He said "what do I need to change?" We rewrote the preventive maintenance budget. We reinstated the full training period. We revised the procurement incentive to include total cost of ownership, not just piece price. Within nine months, the defect rate had dropped by 60 percent, and the total cost — including the reinstated investments — had decreased.

The uncomfortable truth

Quality is not a department. Quality is not a system. Quality is a set of decisions made by leaders, every day, about what they are willing to invest, what they are willing to tolerate, and what they are willing to prioritise. The quality department can measure the consequences of those decisions. They cannot change the decisions.

If your quality problems are recurring, if your defect rate is flat, if your corrective actions keep addressing the same types of failures, stop looking at the shop floor. Look at the meeting room. The root cause is there.