Building AI Workflows with Claude Cowork Skills
Brock Mesarich | AI for Non Techies
YouTube creator
Christian Loyer
Partner at Exceedium
Let’s delve into the intricacies of the fishbone diagram, also known as the Ishikawa diagram, named after its creator, Kaoru Ishikawa. This visual tool, developed in the 1960s, gained global prominence in the '70s and '80s as one of the seven fundamental quality tools. Originally employed in Japan to address issues, it became a Six Sigma staple in the 1990s, integral to the measure and analyze phase of projects.
To initiate a fishbone diagram, you start by identifying the six main categories, often referred to as the '6Ms.' These include Manpower, Methods, Money, Machines, Metrics, and Mother Nature. While these are the classic categories, customization is possible based on the specific problem at hand. Manpower involves the people in the process, Methods pertain to processes, Money relates to financial aspects, Machines consider technology, Metrics involve measurements, and Mother Nature encompasses the overall environment and company culture.
Let's walk through the process with an operational example: "Service levels are too low." Placing this issue at the head of the fishbone, we proceed to brainstorm with a team, identifying potential causes under each 'M' category. For instance, under Manpower, causes might include a lack of training or low workforce engagement. Methods could involve poorly defined processes, while Money might highlight budget constraints. Machines could involve outdated equipment, and Metrics might lack clear targets. Mother Nature might include high customer expectations or a lack of recognition.
It's crucial to note that this phase is not a root cause analysis but a primary cause analysis. The goal is to identify the primary reasons behind the problem. The Pareto principle comes into play, suggesting that 20% of the causes generate 80% of the problem. Facilitators can guide teams in identifying the top causes through techniques like multi-voting, allowing team members to allocate votes to the most critical reasons. This process streamlines the focus on the most impactful issues.
The selected primary causes are then taken into a root cause analysis phase. Utilizing tools like the five whys, teams delve deeper into understanding why these issues exist. By asking "why" repeatedly, the analysis breaks down complex problems into manageable levels, revealing the root causes that need attention.
Now, let's flip the narrative with the reverse fishbone diagram. Instead of uncovering causes, we're identifying elements crucial for project success. Utilizing the same '6Ms,' we explore how to make a project successful. For example, under Manpower, elements like project sponsor support and communication plans are critical. Each 'M' category contributes specific success elements, providing a holistic view.
Similar to the traditional fishbone, teams use multi-voting to determine the most important success elements. This democratic process allows team members to allocate votes to elements they deem most critical. The result guides teams to focus on key success factors.
With identified success elements, teams can now break down these factors further, just like in root cause analysis. This detailed analysis enables the formulation of actionable strategies and plans to ensure project success.
In conclusion, the fishbone diagram, with its dual approach of issue resolution and success element identification, remains a powerful tool for project management. Whether resolving complex problems or strategizing for success, mastering the fishbone diagram proves invaluable in navigating the intricacies of various challenges. We encourage you to incorporate this versatile tool into your everyday problem-solving arsenal.
Free plan, no credit card. Watching opens this session in the Triple Session app.
Brock Mesarich | AI for Non Techies
YouTube creator
Eric Nowoslawski
YouTube creator
Oleg Melnikov
YouTube creator
How Triple Session works
Coaching fails when it is an event. Triple Session turns it into a loop: measure the gap, train against it, and check whether the next call moved.
01
Every call is recorded and scored against your own playbook, so the distance between what your team says and what the playbook asks for stops being a guess.
02
Patterns roll up across reps, deals, and objections. You see which behavior is costing pipeline, not just which rep is behind.
03
Training is assigned against that specific gap: short, expert-led sessions tied to the behavior you just measured.
04
Managers coach from evidence instead of memory. A scorecard, the moment in the transcript, and the one thing to practice next.
Start with the free plan and run the loop on your own playbook. No credit card, no procurement conversation.