Most factories do not have a defect problem. They have a recurrence problem. The same dimension drifts out of tolerance, the same supplier ships bad material, the same weld cracks on final inspection. Each incident gets a fix, and each fix works for a while, until the same failure comes back wearing a different work order number. Root cause analysis is the discipline that breaks this cycle. It is the step between finding a defect and making sure it never comes back, and it is one reason auditors probe it under ISO 9001.
The two most practical root cause analysis tools for small and mid-sized manufacturers are the 5 Whys and the fishbone (Ishikawa) diagram. Neither requires special software or a quality engineering degree. Both work best with real evidence, a cross-functional view, and a way to track the resulting corrective actions.
How do you use the 5 Whys to find a root cause? #
The 5 Whys is deceptively simple: start with the problem, ask why it happened, take the answer, and ask why again, repeating until you reach a cause you can act on. The number five is a guideline, not a rule. Some problems need three whys, others need seven.
A real scenario: A machine shop keeps scrapping brackets because a key dimension drifts out of tolerance during the first hour of every shift.
- Why is the dimension drifting? Because the operator keeps adjusting the tool offsets at the start of each shift.
- Why does the operator adjust the offsets? Because the first parts of the day always measure oversize, then settle in.
- Why do the first parts measure oversize? Because the spindle is thermally expanding as it warms up.
- Why is thermal growth larger than expected? Because the spindle cooling is underperforming.
- Why is the cooling underperforming? Because the coolant filter is clogged and choking flow.
The root cause is not “the operator adjusted the offsets.” It is a clogged coolant filter nobody was checking. The corrective action: add the coolant filter to the preventive maintenance schedule and set a replacement interval. That is why the computerized maintenance management system matters: if the fix does not live in the PM schedule, it will not happen.
Notice what the 5 Whys did here. It started at a symptom (bad dimensions), moved past a tempting wrong answer (blame the operator), and landed on a system-level cause (a missing maintenance task). That shift, from person to system, is the whole point of the exercise.
When do you need a fishbone diagram instead? #
The 5 Whys follow one chain of cause and effect. That is its strength and its weakness: some problems have several possible causes, and picking the wrong chain wastes weeks. A fishbone diagram lays out all the plausible causes first, then you investigate and eliminate.
The classic categories for manufacturing are Man, Machine, Method, Material, Measurement, and Environment. You draw the problem at the head of the fish and branch each category into specific suspected causes.
A real scenario: A pump manufacturer sees rising customer returns for damaged housings arriving at customer sites. Is it the packaging? The carrier? The handling at the warehouse?
- Method: The packaging procedure allows the pump to sit in a single-wall box with minimal foam.
- Material: A recent switch to a cheaper corrugated supplier reduced crush strength.
- Man: New warehouse staff were never trained on the fragile-item packaging standard.
- Environment: The outbound dock gets humid in summer, softening corrugated before it even ships.
One diagram, four categories, and the investigation shows it was not one cause but several compounding ones: weaker boxes, looser wrap, and no outgoing check. The fix touches packaging standards, equipment calibration, and an outgoing inspection step in the quality inspection management system. Without the fishbone, the team would likely have blamed the carrier and changed nothing that mattered.
Why do root cause exercises fail in small factories? #
The tools are simple, so when they fail it is almost never the tool’s fault. Watch for these patterns:
- Stopping at the first answer. One why is not root cause analysis. If the cause you landed on is another symptom (“because the machine was misaligned”), keep going.
- Asking why without evidence. Every answer in the chain should be verifiable. “Because the supplier’s material was bad” is a guess until someone checks the receiving records. The chain is only as strong as the evidence behind each link.
- Fixing the person, not the system. If the conclusion is “the operator should be more careful,” you have not found a root cause. Systems cause recurrence: training gaps, missing maintenance, vague procedures, absent checks.
- Doing it from memory, weeks later. Root cause analysis run weeks after the fact, from one person’s recollection, produces stories, not causes. It has to start close to the event, with data.
- Losing the conclusion in a spreadsheet. The team finds the real cause, agrees on an action, and then the fishbone photo lives on someone’s phone and the action item lives in an email thread. Nothing gets tracked, nothing gets verified.
What changes when root cause analysis lives inside your QMS? #
On paper and in spreadsheets, root cause analysis is an event: a meeting, a diagram, a hope that someone follows up. Inside a quality management system, it becomes a workflow with a memory.
The non-conformance report opens, and the root cause section is part of the record, not a separate document. Evidence from the investigation (inspection results, calibration records, maintenance history) is already in the system, so each “why” can be checked instead of guessed. When it points to a supplier, the finding feeds the supplier assessment scorecard so the next qualification review has the full history.
Most importantly, the loop closes. Corrective actions get owners and due dates, verification checks confirm the fix actually worked, and similar past failures are searchable so patterns surface across months instead of hiding across folders. Auditors see a traceable chain: defect, investigation, root cause, action, verification. That is exactly what ISO 9001 asks for.
Where should a small manufacturer start? #
Pick one real recurring problem, the one everyone in the plant could name without thinking. Run a 5 Whys on it this week with the people closest to the process, and insist on evidence at every step. If the problem resists a single chain, draw the fishbone on a whiteboard and work through the categories together. Either way, write down the root cause and the corrective action somewhere they cannot be lost, with an owner and a due date.
See how Artintech connects non-conformances, corrective actions, maintenance, and supplier data in one system, so root causes are found with evidence and fixed with follow-through: start a free trial of Artintech.
