Why the Fishbone Diagram Triumphs Over 5 Whys
1 The 5xWhy: A Path to Simplicity or a Trail to Blame?
Many praise the simplicity of the 5xWhy method, rooted in the principles of lean manufacturing. It involves asking “Why?”. People repeat the question until they find the problem’s root cause.
However, this apparent simplicity can be deceptive. Often the root cause is human error or a decision-making error, done by humans. This singular focus, while useful in pinpointing individual causes, can inadvertently cultivate a culture of blame and finger-pointing.
The issue with this approach is multifold. First, it oversimplifies complex problems. In the intricate web of corporate operations, issues are seldom the result of a single cause. Second, the spotlight on individuals rather than processes can lead to a defensive atmosphere. Employees may feel targeted and stressed, fearing that each session of 5xWhy could turn into a fault-finding mission.
As a result, nobody will cooperate.
2 The Fishbone Diagram: Casting a Wider Net
Enter the Fishbone Diagram, also known as the Ishikawa Diagram. This method takes a distinctly different approach. It’s a tool that encourages teams to explore multiple potential causes of problems, categorized into various ‘bones’ like Methods, Machines, People, Materials, Measurements, and Environment.
The beauty of the Fishbone Diagram lies in its collaborative and holistic nature. By involving team members across different functions and perspectives, it fosters a sense of collective problem-solving. The focus shifts from individual blame to system-wide inefficiencies and process improvements.
This approach promotes a positive atmosphere where team members feel encouraged to contribute. The visual nature of the diagram aids in this. The teams can see at a glance how various factors interplay.
3 Towards learning organizations
The Fishbone Diagram, with its emphasis on systems and processes, aligns well with the objectives of creating a learning culture within organizations. It steers the conversation towards constructive feedback and improvement rather than pointing fingers.
In contrast, the 5xWhy, though effective in certain scenarios, can fall short in fostering this positive environment, especially when dealing with complex, multifaceted issues.
So if it clearly is a technical problem: 5xWhy. Otherwise, Fishbone.