Root Cause Analysis in Manufacturing: 5 Whys, Ishikawa, FMEA

Root cause analysis (RCA) is a structured process for finding the fundamental cause of a problem, such as a breakdown, a quality defect or a process interruption, so that it can be eliminated instead of patched. Rather than reacting to the same failure every few weeks, the plant corrects what actually produced it, and the failure stops coming back. Where a small failure can cascade into large losses, that ability is central to a stable operation.

What is root cause analysis?

Root cause analysis is the structured process of identifying the underlying cause of a problem or undesired event in order to prevent it from recurring. In manufacturing, it is used to investigate mechanical failures, quality defects, process interruptions and safety incidents. In pharma and other GMP environments, the same logic sits behind deviation investigations and CAPA (corrective and preventive action).

RCA goes past the visible symptom. It asks why the event happened, looking at the materials, equipment, methods and work practices behind it, as well as human factors. Once the cause is clear, corrective action can be focused, and the rework and losses from that source stop.

A useful test: if the cause you identified had been removed, would the problem have been prevented? If not, keep digging. The same applies to “operator error.” When a trained person makes a mistake, the real question is why the process allowed it: an unclear instruction, a missing check, a setup that depends on memory.

How to run a root cause analysis

The method varies with the problem, but most investigations follow the same sequence:

1. Define the problem precisely. What happened, where, when and how often, backed by data such as a downtime Pareto or defect counts per batch.
2. Contain it. Protect the customer and the product first, for example by placing affected batches on hold.
3. Gather facts. Batch records, machine data, maintenance history, and interviews with the people who were there.
4. Find the root cause with a method suited to the complexity of the problem (see below).
5. Correct and verify. Implement the action and confirm that it worked, which in practice is a PDCA cycle.
6. Standardize and share. Update procedures, training and risk assessments so the same failure cannot recur on another line.

Root cause analysis methods

Several established methods exist, each suited to a different kind of problem. The three most widely used:

Method	Best for	Output
5 Whys	Low to medium complexity problems, often involving procedures or human factors	A single chain from symptom to cause
Ishikawa (fishbone) diagram	Problems with several possible contributing causes	A map of potential causes by category
FMEA	Complex equipment or processes, and prevention	A ranked list of failure modes and their controls

1. The 5 Whys

The 5 Whys asks “why?” repeatedly to trace a failure back to its origin. Each answer becomes the basis for the next question, and the process continues until the fundamental cause is found. Five is a guideline, not a rule: stop when the answer points to something you can fix permanently. Simple as it is, the technique works well for problems of low to medium complexity, especially those linked to human error or inadequate procedures.

Take a cartoner on a packaging line that keeps stopping:

• Why does it stop? The drive motor fails.
• Why does the motor fail? It has not been maintained on schedule.
• Why was maintenance not done on schedule? The preventive maintenance windows were repeatedly skipped.
• Why were they skipped? The windows are not reserved in the production schedule, so they are the first thing dropped when the plan is tight.

The root cause is a planning issue, not the motor. Replacing the motor fixes today’s stop; reserving maintenance time in the schedule prevents the next one. In another plant, the same chain might end in a training gap instead.

2. Ishikawa (fishbone) diagram

The Ishikawa diagram is a visual tool that sorts the potential causes of a problem into categories. The classic categories are the 5Ms: Machine, Method, Material, Manpower (people) and Mother Nature (environment). Many manufacturing teams add Measurement to make it 6M, and other categories can be added as needed.

The diagram helps the team see and explore how different factors interact. Take a batch of tablets that fails its hardness specification. Candidate causes might include punch wear or incorrect compression settings (Machine), granulate moisture out of range (Material), an unclear setup instruction (Method), gaps in operator training (Manpower), high room humidity (Environment) or a hardness tester out of calibration (Measurement). Laying them out side by side makes the investigation broader and more systematic, and keeps the team from settling on the first plausible explanation.

3. Failure Mode and Effects Analysis (FMEA)

FMEA is a more structured and demanding tool. Its main use is proactive: evaluating potential failures before they happen. On an automated filling line, for example, the team lists how sensors, motors and controllers could fail, describes the effect of each failure mode, rates its severity, likelihood of occurrence and detectability, and defines preventive actions for the highest risks. In pharma, FMEA is one of the tools referenced in ICH Q9 for quality risk management.

In an RCA, FMEA works in both directions. After a failure, check whether that failure mode was already in the FMEA and, if so, why the existing controls did not catch it. If it was missing, add it with its cause and new controls, so the investigation also feeds prevention.

Benefits of root cause analysis

1. Recurring problems stop recurring

The main advantage of RCA is that repeat problems go away. By acting on the source of a failure rather than its symptoms, the plant puts permanent solutions in place, which reduces rework, waste and unplanned stops. If a recurring defect is traced to a machine calibration error, the permanent fix is to adjust or replace the equipment and add the check to the calibration plan, not to sort out defective units every time it happens.

2. Higher efficiency and lower costs

Fixing failures at the root means fewer interruptions. That has a direct effect on productivity and profitability, because the plant avoids unplanned downtime and the cost of emergency repairs and lost material. The gain shows up in availability and, with it, in OEE.

3. Better product quality

Attacking root causes improves the quality of the final product. This matters most in sectors where compliance with quality and safety standards is critical, such as pharmaceuticals, automotive and aerospace. A detailed investigation might show, for instance, that a specific supplier is delivering out-of-specification material, which lets the company work with that supplier on corrective action, or change supplier, and keep its quality consistent.

4. A culture of continuous improvement

When investigation and problem solving become routine, people are encouraged to question processes, suggest improvements and look for solutions before problems escalate. That habit is the foundation of operational excellence.

5. Better-informed decisions

RCA grounds decisions in data and facts. That reduces subjectivity and lets management allocate resources and plan on the basis of evidence.

From recurring stops to lasting fixes with Cogtive

Every investigation starts with knowing which problem to attack first. Cogtive captures stops through IoT, sensors, AI Vision cameras and batch entries on the tablet and ranks them in a downtime Pareto, while maintenance indicators such as MTBF and MTTR show whether a corrective action held. Alerts in Teams, Slack and email flag when a known problem returns, and the electronic logbook signed by PIN, with its audit trail, keeps a traceable record of what was done. Through the CAPTA method, Cogtive’s Customer Success team of Operational Excellence professionals from industry helps turn investigations into part of the daily, weekly and monthly routine. Book a demo to see it on your own lines.