Root cause analysis
Root cause analysis is a structured way of finding the underlying reason a problem occurred, by tracing it back step by step, so that the fix removes the cause and not just the symptom.
What it means
The first answer to "why did this happen?" is usually a symptom. Asking why again, often about five times, leads to a process, tool, material or instruction that actually failed.
Example
A client rejects a batch of printed cartons for colour variation. Why? The ink mix was off. Why? The operator used an old viscosity chart. Why? The chart was not updated after the ink supplier changed. The root cause is missing document control, so the fix is to version the chart and brief operators, and not merely to scold one person.
Records and checks
- Record the problem, evidence, each why or cause found, the root cause chosen and the actions that follow.
- Verify the cause with facts, such as test results or logs, and not just opinions in a meeting.
- The quality head leads it with the people who did the work, and the owner reviews recurring causes.
Common mistakes
- Stopping at "human error", which rarely explains why the process allowed the error.
- Naming one cause when several combined to produce the failure.
Did not find your answer?Message the lamp team on WhatsApp. Ask about setup, your records, or anything we have not covered here.Ask us on WhatsApp →