top of page

Root Cause Analysis: Why "Fixing It Fast" Is Often a Failure | OEC Insights

  • Feb 23
  • 3 min read

By Allan Ung | Founder & Principal Consultant, Operational Excellence Consulting (OEC)

Updated: 20 July 2026


OEC Implementation Insights 

Implementation is where success or failure happens. At OEC, we go beyond awareness to provide structured, practical guidance on Lean, TPM, ISO, and quality systems. Each article in this series highlights proven steps, common pitfalls, and practical insights — and connects directly to facilitation‑ready training presentations that help teams move from learning to doing.


In most organizations, "problem-solving" is just a high-speed exercise in symptom-chasing. When a failure occurs, the pressure to restore operations is so high that teams reach for the quickest available patch. The result? The problem goes away temporarily, only to reappear weeks later. This isn't problem-solving—it’s just rescheduling the crisis.


As a consultant, I’ve learned that Root Cause Analysis (RCA) is less about tools and more about the discipline to resist the urge to "just fix it." True resolution requires the courage to slow down and look for the underlying systemic failure. Here is the practitioner’s approach to stopping the cycle of recurrence.


TPM implementation roadmap in 6 steps
Root Cause Analysis (RCA) Roadmap in 6 Steps

Step 1: Define the Problem: The "Precise Statement"


Clearly articulate the issue, its scope, and its impact before you even think about solutions.


  • Practitioner’s Insight: If your problem statement contains the word "because," you’ve already started biasing your team. State the facts of the failure, not your theories about what caused it.


Step 2: Collect Data: The "Evidence Base"


Gather process data, timelines, and physical evidence from the moment of impact.


  • Practitioner’s Insight: Never analyze a problem in a conference room. Go to the gemba. The most vital clues are often found in the debris of the failure, not in the spreadsheets back at the office.


Step 3: Identify Possible Causes: The "Wide Net"


Brainstorm potential contributing factors using tools like Fishbone diagrams.


  • Practitioner’s Insight: Avoid tunnel vision. Most teams stop at the first "obvious" factor—usually human error. If your list doesn't include systemic, technical, and management factors, you aren't looking wide enough.


Step 4: Analyze Root Causes: The "Deep Dive"


Apply the 5 Whys or Fault Tree analysis to distinguish between correlation and causation.


  • Practitioner’s Insight: The goal is to find the systemic gap that allowed the error to occur in the first place. If your "root cause" is "the operator made a mistake," you haven't finished—you’ve only just begun.


Step 5: Develop and Implement Solutions: The "Architectural Fix"


Design corrective actions that eliminate the root cause entirely rather than just building a "workaround" buffer.


  • Practitioner’s Insight: A good solution makes it harder to repeat the failure. If your solution relies on "reminding people to be more careful," it is not a solution—it’s a prayer.


Step 6: Verify and Sustain: The "Learning Loop"


Measure outcomes to confirm the failure is gone, then standardize the fix into your process.


  • Practitioner’s Insight: The analysis is only successful if the problem stays solved. If you haven't updated your Standard Work or visual controls, you haven't really solved anything; you’ve just cleared the stage for the next incident.


The Common Pitfalls of Root Cause Analysis


  • The "Speed Trap": Jumping to solutions before the analysis is complete.


  • The Opinion Bias: Letting the "loudest person in the room" dictate the cause instead of following the data.


  • The Surface Barrier: Stopping at the first layer of the problem instead of drilling down to the systemic driver.


  • Sustainability Failure: Implementing a fix but failing to codify it, leading to a slow slide back into old, broken habits.



👉 Ready to stop putting out fires and start preventing them? Implementation is where success is won or lost. To move your team from "quick fixes" to deep, systemic problem-solving, download the facilitation‑ready OEC Root Cause Analysis Training Presentation here for the complete suite of structured slides, group activities, and templates to guide your team through successful resolution.



About the Author


Allan Ung, Founder & Principal Consultant, Operational Excellence Consulting (Singapore)

Allan Ung is the Founder and Principal Consultant at Operational Excellence Consulting (Singapore). A Certified Lean Six Sigma Black Belt and Certified Management Consultant, Allan has led transformation initiatives at Microsoft, IBM, and Underwriters Laboratories (UL). His facilitation‑ready training toolkits and courses are used worldwide to help leaders and teams embed Lean practices, solve problems systematically, and deliver sustainable customer value. Learn more and explore the full catalog at www.oeconsulting.com.sg


This article is part of the OEC Implementation Insights series — practical guides linked to facilitation‑ready training presentations.

bottom of page