How to Conduct Root Cause Analysis

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.

💡Using Fishbone Diagram & 5 Whys for Health & Safety Root Cause Analysis When investigating workplace incidents, it’s crucial to find the true root cause—not just the immediate hazard. Two powerful techniques for this are the Fishbone Diagram and the 5 Whys. 1️⃣ Problem Statement (Effect) In HSE, the problem statement is the incident or near-miss you are analyzing. Examples: “Employee slipped in warehouse” “Chemical spill in lab” This becomes the head of the fish in your diagram, with all analysis flowing backward along the spine. 2️⃣ Categorization (Primary Causes) Diagonal branches (bones) represent primary categories of causes. Common HSE-focused categories include: ✅Man / Mind Power – Worker behavior, training, fatigue, or human error ✅Method – Procedures, work instructions, permits, or safe systems of work ✅Machines / Equipment – Tools, machinery, maintenance, or safety devices ✅Materials / Substances – Chemicals, PPE quality, flammable materials ✅Measurements / Policies – Risk assessments, inspections, compliance audits ✅Environment – Lighting, floor conditions, weather, temperature 3️⃣ Major Contributing Factors Smaller branches under each category represent specific causes. Example for “Man / Mind Power”: Lack of training Fatigue Unsafe behavior Like a doctor examining symptoms, you drill down each factor to discover why the incident occurred. 4️⃣ Integrating the 5 Whys Ask “Why?” repeatedly for each contributing factor to reach the root cause. Example (Slipped in warehouse – Materials / Floor condition): Why did the employee slip? → Wet floor Why was the floor wet? → Cleaning in progress Why was it wet without warning signs? → No signage placed Why was no signage placed? → Staff unaware of procedure Why were staff unaware? → Training not provided ✅ Root Cause: Lack of training and procedural awareness 5️⃣ Benefits in Health & Safety Provides a structured, visual approach to investigate incidents. Helps identify systemic issues instead of blaming individuals. Supports corrective actions to prevent recurrence. Encourages continuous learning in safety culture. 💡In Health & Safety, using Fishbone Diagrams + 5 Whys ensures incidents are fully analyzed, underlying causes are identified, and preventive measures are implemented — turning every incident into a learning opportunity. #HealthAndSafety #IncidentInvestigation #RootCauseAnalysis #FishboneDiagram #5Whys #SafetyCulture #WorkplaceSafety #ContinuousImprovement

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."

🧠 Root Cause Analysis using Fishbone Diagram – CUT INJURY CASE STUDY In workplace safety, understanding why an incident occurs is more valuable than simply knowing what happened. One of the most effective and structured tools for uncovering the root cause is the Fishbone Diagram, also known as the Ishikawa Diagram or Cause-and-Effect Diagram. ⸻ 🎯 Purpose of the Fishbone Diagram The Fishbone Diagram helps in: • Identifying all possible causes of a problem • Organizing contributing factors into logical categories • Focusing on root causes rather than surface symptoms • Encouraging teamwork and analytical thinking during investigations ⸻ 🧩 Categories of Causes A typical Fishbone Diagram for safety uses the 6M Model: 1. Man (People) 2. Machine (Equipment) 3. Method (Process) 4. Material (Tools/Substances) 5. Measurement (Inspection/Monitoring) 6. Environment (Workplace Conditions) ⸻ ⚠️ Case Study: Cut Injury at Workplace Problem Identified: Frequent cut injuries in fabrication and maintenance areas. Root Cause Exploration: 👷♂️ Man (People) • Lack of skill-based training • Ignoring safety protocols • Not wearing protective gloves • Fatigue or carelessness ⚙️ Machine (Equipment) • Faulty cutting tools or dull blades • Missing guards or improper tool design • Inadequate maintenance schedule 🧾 Method (Process) • Unsafe cutting techniques • Absence of standard operating procedures (SOPs) • Rushing work to meet production targets 🧱 Material • Sharp edges on materials • Improper storage causing unexpected cuts 📏 Measurement • No proper tracking of near-miss incidents • Lack of inspection records for tools 🌤️ Environment • Poor lighting conditions • Cluttered or slippery workspace ⸻ 🛠️ Corrective & Preventive Actions ✅ Conduct regular hands-on safety training for operators ✅ Inspect and maintain cutting tools periodically ✅ Enforce PPE usage (especially gloves and safety glasses) ✅ Implement standardized procedures and supervision ✅ Maintain proper lighting and housekeeping standards ⸻ 💡 Conclusion The Fishbone Diagram is a simple yet powerful tool that transforms incident analysis into actionable insights. By systematically identifying and addressing each possible cause, we can move from reactive correction to proactive prevention, ensuring a safer workplace for everyone. ⸻ 🔗 #SafetyFirst #RootCauseAnalysis #IshikawaDiagram #WorkplaceSafety #CutInjuryPrevention #HSE #OccupationalSafety #ContinuousImprovement #RiskManagement #SafetyCulture

How to Do Root Cause Analysis Like a Senior Analyst? Don't stop at “what happened.” Senior analysts ask, “why did it happen?” That’s the difference. Anyone can say: 📉 “Sales dropped by 18% in January.” But a senior analyst will break it down like this 👇 𝗦𝘁𝗲𝗽 𝟭: 𝗗𝗲𝗳𝗶𝗻𝗲 𝘁𝗵𝗲 𝗣𝗿𝗼𝗯𝗹𝗲𝗺 𝗖𝗹𝗲𝗮𝗿𝗹𝘆 Not “sales are down.” Instead: “Revenue dropped 18% MoM in North Region, mainly in Category B.” Be specific. Vague problems create vague analysis. 𝗦𝘁𝗲𝗽 𝟮: 𝗦𝗹𝗶𝗰𝗲 𝗕𝗲𝗳𝗼𝗿𝗲 𝗬𝗼𝘂 𝗚𝘂𝗲𝘀𝘀 Break the data by: ↳Region ↳Product ↳Channel ↳Customer segment ↳Time period Patterns remove assumptions. 𝗦𝘁𝗲𝗽 𝟯: 𝗨𝘀𝗲 𝘁𝗵𝗲 𝟱 𝗪𝗵𝘆 𝗠𝗲𝘁𝗵𝗼𝗱 Sales dropped. Why? → Fewer orders. Why fewer orders? → Website traffic dropped. Why did traffic drop? → Paid ads budget reduced. Why was budget reduced? → ROAS looked low last month. Why was ROAS low? → Tracking issue misreported conversions. Now we’re talking about the real problem. 𝗦𝘁𝗲𝗽 𝟰: 𝗩𝗮𝗹𝗶𝗱𝗮𝘁𝗲 𝗪𝗶𝘁𝗵 𝗗𝗮𝘁𝗮 Don’t assume. Check: ↳Conversion rates ↳Customer churn ↳Pricing changes ↳Operational delays ↳Campaign changes Data should confirm your hypothesis. 𝗦𝘁𝗲𝗽 𝟱: 𝗥𝗲𝗰𝗼𝗺𝗺𝗲𝗻𝗱 𝗔𝗰𝘁𝗶𝗼𝗻 A senior analyst doesn’t stop at insights. They say: 👉 “If we fix tracking and restore optimized ad spend, revenue can recover 12–15%.” Insight + Action = Influence. Root Cause Analysis is not about showing more charts. It’s about: • Structured thinking • Business understanding • Asking uncomfortable questions • Connecting numbers to decisions That’s how you move from “dashboard builder” → “business partner.” If you’re an early-career analyst, practice this: Next time you find an issue, don’t report it immediately. Ask “Why?” five times first. That’s how seniors think.

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.

How to Perform Root Cause Analysis (RCA) for Industrial Maintenance Root Cause Analysis (RCA) is a structured method used to identify the underlying reasons for equipment failures, recurring breakdowns, or performance issues (bad actors). The goal is to find the true cause (not just symptoms) and implement long-term solutions.    Step-by-Step RCA Process for Maintenance Teams  1. Define the Problem - Clearly describe the issue (e.g., "Pump bearing fails every 3 months"). - Gather data: - Failure history (MTBF - Mean Time Between Failures) - Maintenance logs - Operational conditions (load, temperature, vibration)  2. Collect Evidence - Inspect the failed component (photos, measurements). - Check maintenance records (was lubrication missed?). - Interview operators (any unusual sounds/behaviors before failure?). - Use condition monitoring data (vibration analysis, thermography, oil analysis).  3. Identify Possible Causes (5 Whys or Fishbone Diagram) - 5 Whys Method (Ask "Why?" repeatedly until reaching the root cause): - Why did the bearing fail? → Overheating - Why was it overheating? → Insufficient lubrication - Why was lubrication insufficient? → Automatic greaser was clogged - Why was it clogged? → No scheduled inspection - Why no inspection? → Missing from PM checklist - → Root Cause: Preventive maintenance program lacks bearing lubrication checks. - Fishbone (Ishikawa) Diagram (Categories: Man, Machine, Method, Material, Environment, Measurement): - Helps visualize all possible contributing factors.  4. Determine the Root Cause - Verify which cause(s) directly led to the failure. - Rule out unlikely factors (e.g., "Operator error" vs. "Defective seal design").  5. Develop & Implement Corrective Actions - Short-term fix (replace the bearing). - Long-term solution (update PM schedule, install better lubrication system).  6. Monitor Effectiveness - Track KPIs (downtime reduction, extended component life). - Adjust if the problem persists.    Example: RCA on a Hydraulic Pump Failure 1. Problem: Hydraulic pump leaks oil weekly. 2. Evidence: Seal wear, oil contamination found. 3. 5 Whys: - Why leak? → Seal damaged - Why damaged? → Contaminated oil - Why is it contaminated? → Filter not replaced - Why not replace? → No scheduled filter change - Why no schedule? → Missing from a maintenance plan 4. Root Cause: Lack of scheduled filter replacement. 5. Solution: Update PM checklist, train technicians.    Key Takeaways - RCA prevents recurring failures, saving time & money. - Use structured methods (5 Whys, Fishbone, FMEA). 

Five Whys: One of the powerful lessons I learned at Amazon is how to ask the “Five Whys” behind incidents. A well-written COE drives root cause analysis through a blameless, customer obsessed process that helps continuous improvement, knowledge sharing, and actionable outcomes to prevent the recurrence of issues. A sample COE typically looks like this: Issue: Customer orders for Product X were delayed by 48 hours due to failure in the fulfillment workflow. Five Whys: Why was the customer order delayed? Because the order did not move from “Packed” to “Shipped” in the fulfillment system. Why did the order not move from “Packed” to “Shipped”? Because the handoff job that updates shipment status failed and did not retry. Why did the handoff job fail and not retry? Because a dependency API (Carrier Service API) returned a malformed response, and the job had no error-handling logic for this case. Why was there no error-handling logic for malformed API responses? Because the API schema validation was assumed to be consistent, and test coverage did not include schema variations. Why was test coverage incomplete? Because the ownership boundary between the fulfillment team and the carrier integration team was unclear, and no single team was accountable for schema validation. Root Cause: Lack of clear ownership for API schema validation resulted in missing error handling, which caused the fulfillment job to fail silently and delay shipments. Corrective Actions: Add schema validation and retry logic in fulfillment job (owner: Fulfillment team, ETA: 2 weeks). Establish single-threaded owner for carrier API contract validation (owner: Carrier Integration team, ETA: 1 week). Add malformed API responses to integration test suite (owner: QA team, ETA: 2 weeks). As you can see, this helps you get to the root of the issue without assigning blame and focuses on fixing the process. Side note: I’ve applied the Five Whys in my personal life as well—it’s a great framework.

Are you treating the symptoms of bad data OR addressing the root causes? Too often, data teams focus on cleaning the data. But if you don’t dig into why the data is bad, you’ll keep spinning your wheels. Enter: The Fishbone Diagram Also known as the Ishikawa or cause-and-effect diagram, it’s one of the most effective tools for identifying the real reasons behind a data quality issue. 🧠 Use it to: • Map out all possible root causes • Group them into logical categories • Spark team collaboration and critical thinking • Present findings in a way that's clear and visual 🔧 Here's how to build one: 1. State the data quality issue (e.g. incorrect customer addresses) — this goes at the “head” of the fish. 2. Determine the main categories — like Tools, Employees, Processes, Standards, Data Sources. 3. Add root causes — what factors contribute to the issue? Connect each to the relevant category. 4. Add sub-causes — ask “why?” to dig deeper and reveal underlying causes. 💡 Pro tip: Apply the “5 Whys” technique for each cause to get to the core issue. If you want a practical example, I've included a free Fishbone Diagram template focused on poor quality address data on my website. What’s one recurring data issue you've seen that deserves a root cause analysis? __ Follow me here for more hands-on insights for the data professional. – George Firican #dataquality #datamanagement