Root Cause Analysis in Lean

5-WHY ROOT CAUSE ANALYSIS (RCA) Problem Statement: A batch of parts was rejected due to an oversized hole diameter. 5-Why Analysis: 1.Why was the batch rejected?→ Because the hole diameter was larger than the specified tolerance. 2.Why was the hole diameter too large?→ Because the drilling machine was not properly adjusted. 3.Why was the machine not properly adjusted?→ Because the operator used an outdated setup sheet. 4.Why did the operator use an outdated setup sheet?→ Because the latest revision was not available at the machine. 5.Why was the latest revision not available at the machine?→ Because there is no system in place to ensure controlled document distribution. Root Cause: No document control system for distributing updated setup sheets. Corrective Actions: •Introduce a document control procedure to issue and display the latest revision only. •Restrict access to outdated setup sheets by removing old versions from machines. •Train machine operators and line leaders on verifying document revision before setup. Preventive Measures: •Digitize all setup sheets with access through a centralized network folder or MES (Manufacturing Execution System). •Implement revision control logs with sign-off for updates and acknowledgments by operators. •Conduct regular audits on setup documents at workstations. •Establish standard work that includes a revision check step before every job setup. •Integrate barcode or QR code scanning to verify correct document versions at machines.

Most manufacturers treat symptoms, not causes. They fix the machine. Retrain the operator. Blame the supplier. Then wonder why problems keep coming back. Root cause analysis isn't about finding someone to blame. It's about finding the system failure that allowed the problem. Here's your toolkit for different scenarios: WHEN EQUIPMENT FAILS UNEXPECTEDLY: → 5 Whys Analysis - Simple questioning technique → Fishbone Diagram - Visual mapping of contributing factors   → Fault Tree Analysis - Logical breakdown of failure sequences → Timeline Analysis - Chronological review of events WHEN QUALITY ISSUES ARISE: → Statistical Analysis - Data-driven investigation → Process Mapping - Visual workflow analysis → Design of Experiments - Systematic testing of variables → Mistake Proofing Review - Error prevention assessment → Supplier Analysis - Investigation of incoming materials WHEN SAFETY INCIDENTS OCCUR: → Incident Reconstruction - Detailed event recreation → Policy Review - Analysis of existing protocols → Human Factors Analysis - Training and procedural review → Witness Interviews - Structured personnel discussions → Equipment Inspection - Thorough machinery examination → Corrective Action Planning - Systematic prevention measures The method matters less than the mindset. Are you asking "Who made the mistake?" Or "What system allowed this mistake to happen?" One question leads to blame. The other leads to solutions. Your choice determines whether problems disappear permanently. Or just hide until next time. Which root cause analysis method does your team use most often?

🔑 Key factor of Why-Why Analysis🎯 Have you ever solved a problem only to see it reoccur weeks later? That’s where Why-Why Analysis proves its worth. By repeatedly asking "Why?", this method digs beyond symptoms to uncover true root causes—helping teams fix issues permanently, not temporarily. ✅ Problem Example: A painted component was delivered to the customer with peeling and uneven coating. -Instead of just blaming the painter or redoing the job, we asked Why multiple times—leading to insights like: -No surface preparation SOP -Spray gun pressure inconsistencies -Expired paint use -Missing coating adhesion checks -No preventive maintenance on equipment 💡 What We Gained: 🔹 Identification of direct, detection, and systemic root causes 🔹 A structured action plan with clear owners and timelines 🔹 Long-term solutions like SOPs, training, audits, and control measures 🛠️ Tools Used: ✔️ Ishikawa (Fishbone) Diagram ✔️ Why-Why Root Cause Matrix ✔️ Action Plan with responsible departments 🐟 Cause and Effect Analysis (Ishikawa Diagram): Categories contributing to the issue: -Machine: Inadequate spray gun pressure -Measurement: No thickness check, missing visual inspection -Man: Operator not trained in spray angle -Materials: Low-grade/expired paint, improper thinner mix -Method: No SOP, no checklist -Environment: Booth humidity 🚀 Benefits of Why-Why Analysis: 🔸 Improves quality and reliability 🔸 Reduces recurring issues and rework 🔸 Builds a culture of continuous improvement 🔸 Enhances team accountability and preventive actions 📌 Key Takeaway: -Fixing the problem is good. -Fixing the cause of the problem is excellence. -Have you applied Why-Why Analysis in your operations? What challenges did you face or overcome? #WhyWhyAnalysis #RootCauseAnalysis #QualityEngineering #ContinuousImprovement #Ishikawa #LeanManufacturing #OperationalExcellence #ProblemSolving #SixSigma #QualityTools #qms #iso9001

Root Cause Analysis — 5 WHYs in Action 🔍 When a failure occurs, knowing what happened is not enough — understanding why it happened is the key to preventing recurrence. Here’s a practical example of applying the 5 WHY Analysis to a real shop-floor issue. --- 📍 Case: A Hydraulic Pressing Machine suddenly stopped, disrupting the entire assembly line and causing production loss. --- 🧠 Applying the 5 WHYs 1️⃣ Why did the machine stop? → Due to overheating 2️⃣ Why overheating? → Insufficient lubrication 3️⃣ Why insufficient lubrication? → Oil flow blocked 4️⃣ Why blocked? → Oil filter clogged 5️⃣ Why was the filter clogged? → Not cleaned or replaced regularly 👉 ROOT CAUSE: Unscheduled and poor maintenance of the oil filter --- 📌 Data-Driven Evidence Machine logs showed temperature spikes before the shutdown Maintenance history confirmed delayed filter replacement Inspection validated a clogged filter and lack of lubrication --- 🧩 Corrective Actions Implement maintenance scheduling and checklists Train staff on lubrication standards Upgrade to higher-quality oil pumps and filters Install temperature sensors for early detection --- 🔐 Preventive Measures Documented maintenance calendar Regular audits and inspections Reliable and certified suppliers --- 🎯 Key Learning The issue appeared mechanical — but the real problem was procedural. A small overlooked task caused a major downtime event. Root Cause Analysis isn’t blame. It’s clarity, learning, and continuous improvement. #quality #qualityassurance #qualitycontrol #qualitymanagementsystem #qualityjobs #qualityengineer #qualityeducation #qualityaudit #qualitytraining #qualityinspection #qms #qaqc #7qctools #qualityengineering #pdca #sixsigma #capa #qualitymanagement #management #training #productivity #engineering #careers #projectmanagement #lean #excellence #engineers #waste #iso #tutorial #kanban #kaizen #iso9001 #leansixsigma #leanmanufacturing #5s #mechanicalengineering #msa #oee #industrialengineering #smed #ishikawa #jidoka #pokayoke #andon #histogram #qcc #sop #timwood #takttime #pullsystem #kpi #coretools #automotiveindustry #controlchart #iatf16949 #jobinterviews #checksheet #fishbone #linebalancing #fmea #vsmstudy #flowchart #histograms #smartgoal #dmaic #5why #blackbelt #greenbelt #yellowbelt

Root Cause Analysis (RCA) – A Structured Path to Sustainable Solutions In today’s complex business environment, solving problems at the surface level often leads to recurrence. True organizational resilience requires digging deeper—not just treating symptoms, but identifying and eliminating the real root causes. The Root Cause Analysis Flowchart provides a systematic framework for doing exactly that: List Possible Causes – Capture all potential triggers. Why Chain – Repeatedly ask “Why?” (3–5 times) until you uncover the base cause. Verify Root Cause – Use data tools (control charts, fishbone diagrams, process maps) to validate findings. Solutions – Design corrective actions that directly prevent recurrence. Key Takeaways: • A possible cause ≠ root cause; verification is essential. • RCA is iterative; multiple root causes may exist for a single problem. • Sustainable performance improvement comes only when the real root causes are addressed. This structured approach aligns with Lean Six Sigma and Continuous Improvement methodologies, ensuring organizations move from reactive firefighting to proactive problem prevention. #RootCauseAnalysis #ContinuousImprovement #LeanSixSigma #BusinessExcellence #ProblemSolving

Brutal truth: Most organizations think they’re doing problem-solving… …but they’re really just treating symptoms. And that’s why most “continuous improvement” efforts quietly fail within 6 months. Here’s the pattern: ↓ A problem emerges ↓ Teams jump into action ↓ They brainstorm fixes ↓ Something sort of works ↓ Everyone gets busy ↳ The problem returns—sometimes worse What’s missing? A disciplined system for understanding what's really going on. that's where Root Cause Analysis comes in. Without true Root Cause Analysis (RCA), all improvement becomes guesswork. RCA is the operating system of real improvement Effective problem-solving is not a single method. It’s a system of thinking supported by tools that reveal what's going on beneath the surface. here are 3 RCA tools: 1/ Fishbone Diagram Purpose: Organize possible causes into categories so patterns emerge. The Fishbone works because it forces teams to externalize assumptions. Instead of blaming individuals or latching onto the first explanation, it broadens the search. 2/ The 5 Whys Purpose: Drill down from surface symptoms to deeper causes through structured questioning. This is the simplest and most used RCA tool. When done well: You follow a single causal chain You validate each “why” with evidence You avoid speculation You keep going until the answer becomes systemic (not human error) When done poorly, it becomes a rapid-fire guessing exercise that leads nowhere. 3/ Fault Tree Analysis (FTA) Purpose: Map how multiple causes combine into failures. FTA is a branching model that shows how different conditions must align for a failure to occur. It is the most rigerous of the RCA tools and my personal favorite. FTA exposes: ➡️conditions for failure ➡️hidden interdependencies ➡️missing safeguards In high-performing organizations, RCA is embedded into: + Total Quality Management + Standardized Work + Just-In-Time and Flow Design + Policy Deployment + Daily Management & Suggestion Systems Organizations don’t fail because problems are too complex. They fail because they don’t build a system for revealing and understanding causes. So start simple: Pick one tool Use it consistently Train people on the thinking behind it Validate causes with data Improve the surrounding systems that make RCA possible Then connect that tool to others—just like Kaizen. Sustainable improvement isn’t an event. It’s a capability. Built patiently. Strengthened daily. Powered by clarity about why things happen. And that starts with Root Cause Analysis.

4P Ishikawa Diagram (Transactional Lean Context) The Ishikawa diagram (also called a fishbone or cause-and-effect diagram) helps teams identify root causes of problems. In manufacturing, it’s often structured around the 6Ms (Man, Machine, Material, Method, Measurement, Mother Nature). For transactional/office environments, the 4Ps framework is often more effective because it reflects the drivers of service and knowledge work. The 4Ps in Transactional Lean People: Skills, training, role clarity, workload, motivation. Example: Finance staff miscode invoices due to lack of training. Process: Workflow design, standardization, handoffs, bottlenecks. Example: HR approvals pass through five managers, delaying onboarding. Policies: Rules, compliance requirements, approval matrices, decision rights. Example: Outdated expense policies create excessive exception handling. Place (Technology/Environment): Systems, tools, workspace, digital platforms. Example: ERP system downtime causing backlog. Why It’s Better for Transactional Lean Language fit: Office teams often struggle to relate to “Machine” or “Material.” The 4Ps use terms that make sense for service work. Focus on knowledge work: Captures the true sources of variation in transactional processes, rules, systems and workflows, rather than physical production factors. Improves adoption: Employees in HR, IT, Finance, and Customer Service can contribute more meaningfully when categories match their reality. Simpler alignment: Easier to use in workshops and daily management for transactional teams. Summary: The 4P Ishikawa (People, Process, Policies, Place) reframes root cause analysis for transactional Lean, making it more relatable, actionable and effective than the traditional 6M manufacturing-based approach.

Is “Operator Error” the Real Root Cause in Manufacturing? When a defect, breakdown, or safety incident happens on the shop floor, many investigations quickly settle on one conclusion: “operator error.” It’s simple, fast, and seems to explain everything. But in modern manufacturing, this label is often a symptom of deeper issues, not the real cause. Behind every so-called “human error” there is usually a chain of factors: 1.Inadequate or unclear work instructions 2.Poor workstation ergonomics or excessive fatigue 3.Gaps in training or skill development 4.Lack of mistake-proofing (Poka-Yoke) in process design 5.Equipment not calibrated, or preventive maintenance overdue 6.Material inconsistency, environment fluctuations, or unrealistic production targets Blaming people may give temporary closure but blocks true continuous improvement. A blame culture discourages operators from reporting near misses or improvement ideas — leading to recurring failures, higher costs, and low morale. The best manufacturing organizations take a systemic approach: • Use structured root-cause tools (5 Why, Fishbone/Ishikawa, FMEA) • Build strong SOPs and visual standards • Error-proof high-risk activities wherever possible • Create an open environment where operators, engineers, and leaders solve problems together When teams stop asking “Who messed up?” and start asking “What in our process allowed this to happen?”, quality, safety, and productivity all improve. #ManufacturingExcellence #RootCauseAnalysis #LeanManufacturing #Qualitycircle

It bears repeating: "Lack of" isn't a root cause. During a recent conversation with an executive about a vexing quality problem his operation was experiencing, the "lack of" well-defined, well-documented, and well-managed standard work came up. As did the "lack of" proper training. As we address directly with clients—and in our Mistake Proofing, Problem Solving, and Root Cause Analysis courses, there are typically TWO factors at play with quality problems: contributing factors and direct root causes. For example, let's consider quality problems in four very different types of work: 1) hemolyzed blood draws that require redrawing blood; 2) cracks in manufactured parts that have to be scrapped, 3) wrong reason codes for an outcome, which causes dirty data; 4) missing critical notations on construction blueprints, which create construction defects and increases warranty expenses. In all four cases, quality can most certainly be improved with clearer, documented standards; excellent training; and better work oversight. But true root causes (and there are often multiple root causes for a problem) rear their heads DURING THE WORK ITSELF. 🔸 Hemolyzed blood is often due to shaking the tube of blood too vigorously. 🔸 Cracks can be caused by poor equipment, improper part handling, or improper temperatures. 🔸 Wrong reason codes are often the result of too many codes to choose from, or missing prompts in software to help someone discern between two similar-sounding codes. 🔸 Missing blueprint notations can be caused by distraction, rushing, or incorrect AutoCad settings. To help people conduct more robust root cause analyses that get to the process or work system issue that creates the specific cause and effect, it's helpful to differentiate between contributing factors and true root causes. Oh and while I'm at it . . . fishbone diagrams (aka cause-and-effect and Ishikawa diagrams) are brainstorming tools. While the true root cause(s) may make their way to a fishbone diagram, you have to dig more deeply. Definitive root causes can only be discovered via data, direct observation of the work, equipment and code testing, etc. Brainstorming can be a powerful first step and great way to get a team engaged in problem solving. But it's only the first step. VALIDATION is necessary. So the next time your head (or someone else's) lands on "lack of" root causes, acknowledge them as possible "contributing factors," but dig more deeply for true root causes. Remember: they exist in the work itself. #rootcause #quality #causeandeffect

ROOT CAUSE ANALYSIS (RCA) "5 Whys" Method In operational management, addressing a "near-miss" involves moving beyond immediate fixes to uncover the systemic flaws that allowed the issue to occur. This process is known as Root Cause Analysis (RCA). Using the example from the provided video, we can break down how a single drop of oil led to a company-wide change in quality standards. The "5 Whys" of the Incident A common RCA technique is the "5 Whys" method, which forces an investigator to look past symptoms and find the origin of a problem. 1. Why was there oil on the floor? Symptom: A bolt on the overhead pipe was leaking. 2. Why was the bolt leaking? Immediate Cause: The rubber gasket inside the bolt had deteriorated. 3. Why did the gasket deteriorate while others nearby were intact? Direct Cause: This specific gasket was sourced from a different supplier than the others, despite being installed at the same time and in the same environment. 4. Why was a gasket from a different (and inferior) supplier used? Systemic Cause: Procurement standards or quality control checks failed to identify that the supplier was providing substandard parts. 5. Why were the procurement standards insufficient? Root Cause: A lack of rigorous supplier vetting and quality assurance protocols within the procurement department. Impacts of the Analysis By performing this deep dive rather than simply wiping up the oil, the factory achieved several high-level operational improvements: 1. Systemic Prevention: The company reviewed its supplier standards and strengthened quality control procedures. 2. Preventing Future Failures: The findings prevented similar gasket failures across the entire system, potentially avoiding massive leaks or equipment fires. 3. Financial Efficiency: Investigating the root cause is more cost-effective than repeatedly fixing the same recurring "symptom". Key Takeaway for the Incident This incident perfectly illustrates why under-reporting is dangerous. If the worker had simply wiped the floor, the defective gaskets from that supplier would have remained in the system, eventually leading to a catastrophic failure. "If you only fix what you see, you're treating symptoms. If you keep asking why, you uncover the truth."