The U.S. FDA recently issued Medline another warning letter over quality control lapses, making it the company’s second FDA warning in two months. The latest warning, dated May 28, 2026, involved issues including inadequate investigation of microbial contamination, cleaning practices, and disinfection procedures at a facility in Waukegan, Illinois. Reuters also reported that the FDA pointed to repeated failures across multiple sites and concerns around management oversight and control.
This is not just a regulatory story. It is a useful reminder for any organisation: when quality problems repeat, the issue is rarely only the individual incident. The deeper question is whether the process, governance, corrective-action system, and management review are strong enough to stop the same problems from returning.
Repeated Problems Are Signals
Every organisation experiences problems. Errors happen, processes break, people miss things, suppliers create variation, systems fail, and conditions change. A single issue does not automatically mean the whole system is weak.
Repeated issues are different.
When the same type of problem appears again, or when similar problems appear across different teams, sites, products, or processes, the organisation should treat it as a signal. It may be a sign that the real cause has not been understood. It may also show that previous corrective actions did not go deep enough.
Many organisations unintentionally treat recurring problems as isolated events. They investigate the latest incident, correct the immediate issue, close the action, and move on. That may solve the visible problem, but it does not always strengthen the process behind it.
If the same problem keeps returning, the problem is probably not only the incident. It is the system that allows the incident to return.
Corrective Action Must Go Beyond Correction
There is a major difference between correcting a problem and improving the process.
Correction deals with what has already happened. It fixes the defective item, updates the record, cleans the area, reworks the order, replaces the product, or responds to the complaint. Correction is necessary, but it is not enough.
Corrective action should address why the problem happened and what needs to change so it is less likely to happen again. That may require changes to procedures, training, ownership, checks, equipment, handoffs, controls, escalation routes, or management review.
This is where many organisations struggle. They close actions too quickly because the immediate issue has been handled. The visible problem disappears, but the weakness remains. Later, the problem returns in the same place or appears somewhere else in a slightly different form.
This is why quality problems often feel frustrating. People may say, “We already fixed this.” In reality, they may have fixed the outcome, not the process.
Quality Control Is Not Just Inspection
Quality control is often misunderstood as checking work at the end. Inspection is important, but it is only one part of quality. Strong quality depends on process discipline throughout the work.
A well-managed process makes quality easier to achieve. The steps are clear. The standards are understood. Responsibilities are defined. Critical controls are visible. Deviations are recorded and reviewed. People know when to stop, escalate, or ask for support.
Management has enough visibility to spot patterns before they become serious.
A weak process pushes quality problems downstream. People find issues late. Teams rely on rework. Decisions depend on individual judgment. Records become inconsistent.
Problems are corrected after they happen instead of being prevented earlier.
In this situation, inspection may catch some issues, but it cannot compensate for poor process discipline. If the process is unclear, unstable, or poorly controlled, quality will always depend too much on individual effort.
Quality is not created at the final check. It is built into the process.
Management Oversight Matters
Recurring quality issues should also make leaders ask whether oversight is working as intended. Management oversight is not simply receiving reports or attending review meetings. It means having the right visibility, asking the right questions, and acting before weak signals become major problems.
If the same issue keeps appearing, leaders should ask whether the organisation is seeing the pattern early enough. Are deviations reviewed properly? Are corrective actions tested for effectiveness? Are repeat issues escalated? Are process owners accountable for sustained improvement? Are different sites or teams learning from each other’s failures?
These questions matter because weak oversight allows process problems to become normal. A recurring issue may be known locally, tolerated informally, and only escalated when it becomes too serious to ignore. By that point, the cost is much higher.
Good management systems do not wait for failure to become obvious. They create routines that make weak signals visible early.
The Operational Excellence Lesson
The Operational Excellence lesson is simple: do not treat repeat problems as bad luck.
If a problem happens once, investigate it. If it happens again, look at the process. If it appears across multiple areas, look at the management system.
This does not mean blaming people. In many cases, people are doing their best inside a process that has become unclear, overloaded, poorly controlled, or insufficiently reviewed. The goal is not to find someone to fault. The goal is to understand why the process allowed the problem to occur and why the system did not prevent it from returning.
Strong organisations build the discipline to learn from problems. They do not just close corrective actions; they check whether those actions worked. They do not just document procedures; they make sure procedures are practical and followed. They do not just collect performance data; they use it to identify patterns, risks, and improvement priorities.
This is how organisations move from reactive problem-solving to managed improvement.
Stop Solving the Same Problem Twice
Every repeated issue carries a message. It tells the organisation that something has not been properly understood, controlled, or sustained. The longer that message is ignored, the more expensive it becomes.
The cost may appear as rework, customer dissatisfaction, regulatory findings, employee frustration, operational delays, or loss of trust. In regulated environments, the consequences can be especially serious. But the principle applies everywhere. Whether the organisation is in healthcare, manufacturing, logistics, services, or administration, repeated problems are rarely random.
They are usually signals of process weakness.
The right response is not panic. It is discipline. Understand the pattern, find the root cause, strengthen the process, test the corrective action, and review whether the improvement holds over time.
Operational Excellence is not about having no problems. It is about building the capability to learn from problems properly and stop the same ones from returning.
For organisations and professionals that want to strengthen this kind of discipline, PATH OEMS™ provides a structured Operational Excellence Management System to help deploy, manage, and sustain improvement across operations. The Operational Excellence Deployment Training supports this by helping professionals understand how to apply structured improvement, corrective action, and process management in practice. Explore PATH OEMS™ to strengthen your organisation’s improvement system, and enrol in the Operational Excellence Deployment Training to build the practical capability to deploy it effectively.
Leave a Reply