Root Cause: Beyond 5-Whys

I once watched seven engineers chase a phantom root cause for three weeks because they were married to a linear 5-Why. The problem was an intermittent communication failure between a PLC and a vision system on a high-speed packaging line. The 5-Why chain looked clean on paper: communication dropped because the cable shield was damaged because it was routed too close to a variable-frequency drive. The team confidently replaced the cable, rerouted it along a different cable tray path, updated the wiring SOP, and closed the 8D. The problem came back four days later and the line went down during a critical production run costing the plant over fifty thousand dollars in downtime. The real failure required three simultaneous conditions that no linear 5-Why chain could possibly capture. The first condition was electromagnetic interference from the VFD which was always present but usually benign because the cable shield was intact. The second condition was a ground loop that developed when the maintenance crew replaced a rusty panel door three weeks earlier without bonding the new door to the ground bus. The third condition was a firmware timing bug in the vision system that only triggered when the image processing load...