Six Sigma Overview | Fishbone Diagram | Green Belt 2.0® Lean Six Sigma | fkiQuality HD

(Timestamps below)
The mind-expanding tool! The Fishbone diagram helps us think beyond the person when looking for the reasons for problems.
Ask "why?" instead of "who?"
One of many ways to get us to think about the system of production, not just special causes or easy targets.
Actually, ask "why?" several times to get to the true causes.
Timestamps:
0:28 - Fishbone Diagram Intoduction
0:47 - Fishbone Diagram Sample
1:21 - Visible Vs. Invisible Causes
2:45 - Fishbone Diagram Summary Slide
2:55 - How to use the Fishbone Diagram (5 Why's)
3:36 - How to use Summary Slide
3:44 - Ishikawa's Suggested Six Categories:
4:21 - Materials
4:42 - Person
5:04 - Machines
5:21 - Procedures
6:00 - Measurements
6:48 - Environment
7:08 - Ishikawa's Six Categories Summary Slides
7:38 - Beginner Vs. Experienced Approach to Fishbone Diagrams
8:34 - Experienced Fishbone Diagram Example
9:18 - Beginner Vs. Experienced Summary Slide
9:25 - Fishbone Diagram Summary
10:20 - Fishbone Diagram Summary Slide

[@mattmack8103]

Asking "why" multiple times is a terrific way to get to the get to the cause and effect. I've used this method with customers, and never knew it originated from the fishbone diagram.

[@JamesBehn-pl4li]

Very informative video on the Fishbone Diagram. The Fishbone Diagram is a useful tool to break down complex problems or processes. Using the Fishbone Diagram, we can brainstorm and identify what changes to test, to improve a problem or process.

[@BeatriceDosu]

Another very informative video. The fishbone diagram visually helps to uncover the problems and their root causes. It can help in brainstorming to find the causes of problems; the ones that are not usually visible or likely obvious.

[@cjtrumpeter]

Nice demonstration of fishbone. I've used this type of diagram/logic for several projects in the past but never put a name to it.

[@musicotriste69]

Homero Cardoso: This is a very useful tool to brainstorm problems and their causes. Visualizing in the diagram all of the problems and secondary problems give us a clear picture of what path to take to solve the issues.

[@Student-uo1fn]

I've used this method for safety, quality and general process improvements ... always a good starting point

[@dustinclarke6607]

I like how this diagram is a simple way of brainstorming a list of problems to have a good idea of where to start looking for solutions

[@Student-ws8wg]

A superior thinking exercise to empower brainstorming. The Fishbone diagram ensures teamwork to document and identify multiple causes of a process breakdown.

[@ChristopherStefan]

Nice overview of the fishbone diagram. This tool is regularly used to troubleshoot processes and non-conformances in the manufacturing industry. It's helpful in finding the root cause of a potential issue.

[@rafaelhernandez1981]

Fishbone diagrams seem like a very useful tool for troubleshooting any kind of complicated problem. Doing it all in your head on such issues can have you spinning your wheels very quickly.

[@fkiQuality]

Good point, and keep in mind that the fishbone diagram should always be done with the participation of the team who knows how the work is done.

[@EricBennionDiaryDad]

This seems like a great way to identify “low hanging fruit” opportunities for improvement while you work on solutions to the main problem.

[@jasonglatz232]

Fishbone diagrams are a great starting point to identify the next steps of a charter. Outline People, Method, Material, Machine Equipment, Measurement, Environment. This setups a solution for quick wins and gets the group to identify the problems of the process.

[@williamhansen4837]

i have used the 5 way method both internally and externally from a customer request, i like the fishbone method because its not only a visual tool that every one can see but it encourages a natural collaboration that can be a lot more effective than a email with a PDF back and forth between peers who are not fully engaged with it anyways.

[@colleendriscoll6934]

I like the reminder to always ask why, or remember your why(s). Also, I feel like nearly anyone could make a couple of these for their business or place of employment, as there is always room for improvement. There's always a challenge. A suggestion. I'm big on analyzing and getting into the weeds to figure out the bottom line, so I can see myself using this quite a lot in my workplace.

[@Bittersweetdstny]

This reminds me of the Pros/Cons list we were taught as children. It's a logical approach to solving problems and finding the root cause to brainstorm solutions. Just keeping analyzing and asking why.

[@ernestbroom9995]

I like how the Fishbone diagram gives a focused way to brainstorm. It gives 6 categories of focus on when narrowing down ways to find our solution. Awesome!!

[@ryannew907]

The fish bone diagram is an excellent tool to use when trying to find the why not The Who. This helps us get down to the root causes and then make a fix.

[@Ganjagoddessgrower]

The fishbone diagram is really helpful to provide structure to brainstorming sessions-which can be too random and get off track. I like that it is fast and easy to explain to others.

[@vaniavargasjimenez2358]

I understand that is a brainstorming session with stakeholders, but after doing the fishbone by myself I realized that you have to have different points of view in order to do this activity successful.

[@scotttyler1986]

While I have used fishbone diagrams, I never looked at them as a tool for exploring the teams mental map. I found this a very powerful interpretation.

[@GregBenz-de7nt]

Very interesting concept to look at different categories of causes. I'm familiar with the "5 Whys" but didn't know that this was the origin.

[@ryananderson8130]

I think it is important to remember we are still not trying to solve the process breakdown we are trying to identify it. Another good tool to locate issue within the 6 categories.

[@brigittedickey3298]

This is a great way to start solving problems. You can start to see the causes of issues. I see how it is important to keep asking why

[@jeffmaes5892]

This is a great visual tool to find a problem in an existing process or identifying potential problems when building a new process.

[@rebekkaherrington4509]

I can see how this tool can help guide deeper exploration of the problem and help avoid clinging onto the first assumed cause as the sole area needing fixed.

[@Jaguzma2]

The fishbone diagram is so simple, yet such an effective tool in getting to the root cause.

[@mitchellhoem2003]

This is a great tool to use with your employees. Those performing the work know the ins and outs of each of the categories of a Fishbone Diagram better than anyone. Sitting them down and working through one of these diagrams will help to educate management and find ways to improve processes.

[@jenniferb5322]

i appreciated this explanation of the Fishbone diagram. During the in class activity we kept forgetting to ask, "Why". However, I do think this has practical applications within my current job role to help identify our issues and their root cause. Thank you!

[@JacobReuter28]

a great description on how to build a fishbone diagram and how useful it can be in finding different reasons for a specific problem. I have used the fishbone diagram a couple of times in my job and it seems to always find a few reasons for a problem than no one really thought of before.

[@tedkozelka203]

This is an excellent tool for unlocking tribal knowledge to help find underlying causes.

[@sherisezynel5048]

Thank you for explaining the value of the fish bone diagram. It is such a useful tool to not only uncover problems but an aid in which to begin problem solving.

[@alexissmoot6291]

I agree that causes are not visible or obvious. This problem has been the reoccurring issue across multiple departments and companies of trying to point blame versus understanding what it wrong with the system. Using the "five whys" has been an important tool that my company has begun to use multiple times.

[@florahatzis5019]

This is a great tool to formalize a brainstorming session with a written and verbal root cause analysis. Great snapshot of a lot of information.

[@christianhagner6509]

This is great, I was introduced to the fishbone diagram in college, but was never educated on all the facets of proper use, so I never used it. I'm excited to see how I can apply this to my current job.

[@slee3249]

this helps to break down the problems into categories that are visual. And it helps to identify some of problem for quick wins.

[@joshklinzing4608]

What I like about things like the fishbone diagram and the "tree" diagram in problem solving is that they are graphical representations of aspects of our problems. The analogies and layouts are easy to understand, and therefore help structure and direct our thinking about output and/or defect causes, giving us a chance to solve them.

[@Envyslays16]

I really enjoyed this class and was able to break down and understand the lecture. I learned how to use this tool in every aspect of my life. The Fishbone tool is useful for: 1. Analyze actual conditions for product or service quality improvement, more efficient use of resources, and reduced costs. 2. Eliminate conditions causing nonconformities and customer complaints 3. Standardize existing and proposed operations 4. Educate and train personnel in decision-making and corrective -action activities.

[@brief1206]

Hello! Thank you for this lesson, you are a great teacher

[@kennethmckillip3983]

I have used these before. The one thing to keep in mind is that they work better when done as a team; not solo. The various ideas that come from "picking others brains" or as it was stated, using their mental map, is invaluable.

[@jorgecifuentes7283]

We just started to learn about the fishbone tool and this video has added value by further clarifying its purpose and method for getting to the end result. I can see how following this method would help because it adds the structure needed to maintain alignment with the desired results of getting to the root cause. Definitely a useful tool. From personal experience, I have been exposed to the free brainstorming process but see the value for using the fishbone method first.

[@adammademann4414]

I really enjoyed this "in class", hands on practice that we did in class. I'd never used let alone heard of the fishbone diagram, but I found it to be very helpful in breaking down the [previously] unknown causes into the 6 classification of causes that Dr. Ishikawa came up with. I also liked our instructors comparison, albeit with notable differences, to how young children practice the "5 whys" method. Clearly as adults we aim to be more pointed and prudent with our line of questioning with the goal of "peeling" back the top layers of explanations and seeking the true causes.

[@cesarlopez4907]

Very informative it enhances my thinking of to look at a problem, however i can see that we need to almost free our minds to just brainstorm first then formalized it in the ishikawa diagram.

[@nicholaspesek5902]

This video pairs well with the in class material. This tool will help to structure the 5 why process and get to the root of the problem.

[@Music1234Man]

This fishbone diagram seems like another very interesting tool to use. It seems that this would be a diagram that you would make before the SIPOC diagram.

[@ss-fs9gz]

Significant in detail explanation!

[@mariaflores-tl1gk]

Fish bone is a creative way to collect ideas, find the root causes of a problem and plan for changes and implementation.

[@julianmcdonough1590]

The free form approach with brainstorming sounds good to me.

[@margaritorios]

following the fishbone diagram is going to give us a better idea how to solve a problem

[@victorgomez1437]

Fishbone diagram in collaboration with the 5 why's makes for a great system for brainstorming many problems.

[@miawang7632]

Love this cause-and-effect analysis -- it allows us to see the overall picture of a problem, and to reach deeper for the root causes of a problem. We can apply this method to work and life in general.

[@dwartneywortham2353]

Fishbone diagram is something that I will implement immediately with my workers to show them the way we are trending.

[@DavidRoberg]

A simple tool, but a very effective way for the team to talk about and see what's actually going on.

[@douglasomachel2284]

Great way to visualize an issue or discrepancy. Interested to learn more in our next class session.

[@GlennFrazee]

I'll admit that looking at this in the course materials, I was having trouble knowing how to get started. But the in-class exercise where we went through the Fishbone Diagram really helped the idea sink in.

[@donnalevy8455]

Great explanation on the fishbone diagram! It is interesting going through the process not realizing that many of the causes and effects are hidden within how we work each and every day. By diagramming the causes and effects you can visually begin to see where the root causes of issues are so you can begin working to resolve them.

[@danielarcher9175]

Interesting diagram. Often there are more than one "why" in a process. This is a great tool to identify root issues in a process.

[@traceymathews9203]

Two points stand out to me when using this method for exploration. First, that these cause and effects are embedded into the way we work, which can mean so entangled they are unconsciously done . Also when using using the fishbone we must keep in mind and question both sides of things, the physical and non-physical or social.

[@antrioneday1272]

The fishbone diagram is the best tool to use for investigation. It's a productive tool for laying out all contributing factors to the problem at hand. It has also allowed me to identify latent weaknesses within my process. I find useful when I include the Why-Why analysis. But alone it is very helpful.

[@alanharker2433]

I am a firm believer in asking the WHYs bc it will answer the root cause of a lot of current issues. I've been asking why the last couple days in several projects and slowly getting the same answer from each area. Placing this in a diagram would be a great visual tool to share the common issue spread through multiple departments. Great recap/ quick explanation.

[@joycestadter945]

Fishbone diagram is a good way of further exploring problems within the system.

[@jamesmcelwee5666]

I have used this in problem solving as a PMP before. It is very effective in getting to root causes when accompanied by the 5 Why’s technique.

[@Ace_theMaster]

When conducting the development of Fishbone Diagrams or Affinity Diagrams, I do like the concept of giving people (the attendees of the meeting) some sticky notes (maybe like 3 per person), so that they write the ideas on the sticky notes themselves and then also let them put the sticky notes on to the diagram. I feel this small task inspires a sense of responsibility and ownership of the "process" for each person who participated in the activity, and thus, this exercise creates a great team-building experience for everyone.

[@user-xh6ro1mi1c]

In the previous video, I was proactively thinking on what would be a method to bring this to people that would not necessarily understand what Six Sigma is and does. The Fish Bone diagram, along with the refined affinity diagram process is the solution. It forces you to elaborate on keen details based in sections, thus making it more palatable to whom ever presented. Yee-haw!

[@jameshoward6634]

I've used these before but not with the Ishikawa template. Being more structured than the 5-why investigation this will be more useful for a process with multiple failures throughout the entire process.

[@johnstanley491]

I've used several different root cause analysis tools. I think the Fishbone diagram is great because of it's simplicity and accessible visual way of organizing information.

[@julieorozco9556]

Good suggestion of categories to get one started on using fishbones. Nice to see some flexibility offered in the approach by combining the infinity diagrams.

[@sheiladwyer6482]

I like your suggestion to use this tool multiple times initially as you develop a comfort level and learn to use it effectively. Once you develop that comfort level use it for free brainstorming and/or affinity diagram. I don't have much experience using it but I can see its utility in getting to the root cause.

[@rlcardcollection]

I would like to go deeper into the six categories to understand the fishbone diamgram more.

[@oscarchiquito2609]

From what I am understanding, this is pretty much a way to visualize cause. Every process that needs troubleshooting may use this to understand what needs fixing.

[@mremann893]

Had an "AH HA!" moment while watching this video. We had received a reject from a customer that was requiring us to use the 5 whys and a fishbone diagram to get at root causes. I was trying to get my boss to be engaged with this since this is our best customer.....we both had a hard time understanding what they were asking for since we had not run across this before, but the next time this comes up, I will have clarity thanks to the video.

[@fkiQuality]

MrE Mann, great to know this will be helpful in the future. Hitoshi Kume and Kaoru Ishikawa have written very practical, short books with plenty of examples that I used to write this video.

[@kristinwerner2431]

This actually is a nice tie in to the Business Analysis class I just took and would be a useful tool as you are trying to come up with solutions and understand a problem the business is encountering.

[@kimdaniels1736]

I've used the fishbone method(5 why's as well) to help drill down into the actual root cause of a particular problem(s). It's important to get the problem statement correct otherwise there can be scope creep or the issue can be defined too generally making it harder to drill down into specifics. I've found that using an IS and IS NOT table, helps stimluate the thinking of the inputters. Lastly, it's easy to get into "problem solving mode" instead of brainstorming possible causes; the facilitator needs to be strong in re-directing the team if they begin to go down a rabbit hole.

[@ronaldtucci6091]

Fishbone diagram is very helpful when leading a team to explore for root cause analysis of a defect. It helps keep the team on track and opens up all possible issues.

[@investing4legacy153]

Simple but effective exercise. Would love to see an example of one being made in real time with a group of workers.

[@michaelparks8673]

Very good explanation of a Fishbone diagram. I have used the fishbone before in problem solving but with only 4 attributes.

[@tonygarcia625]

I have used the Fishbone diagram and it is a very effective tool.

[@mitchzavesky4734]

We just refer to this as "brainstorming sessions," but we do a similar version of a fishbone diagram when designing new product. We focus on different aspects of our product, and using sticky notes, all members can voice what they would like to see improved. In a similar vein, the fishbone diagram works to find the root cause of a problem by asking "why" and really diving deep into the problem.

[@christopherrogers7303]

Seems like an extremely useful tool, not sure I am ready for this one just yet. I can see how sitting down with a few employees and using this diagram to capture their reasons for a failed process can be effective as far a fostering inclusivity and also building trust within the department(s).

[@denisek743]

The six categories recommended by Ishikawa are great for getting the root cause. Then asking the 5 whys. And finally using the fishbone diagram to bring it all together.

[@samanthadulceak7200]

The system of identifying multiple causes eliminates the finger pointing while adding employee value with the open discussion and brainstorming sessions.

[@cindygaborik4941]

Six Sigma Class - Fishbone diagram and asking 5 whys for root causes are helpful tools to getting to the true reasons for problems.

[@fkiQuality]

The fishbone is supported by tools such as the 5-whys, brainstorming and affinity grouping. It requires strong facilitation to keep the discussions going and avoid too much consensus which risks situations where everybody agrees on everything like "it's all because of lack of training."

[@patriciazuno1694]

Before we jump to the conclusion that something went wrong because of one person, we need to look at the picture as a whole and break it down. Looking at how each aspect impacts the outcome is critical to know where things may go wrong and implementing actions to control these situations.

[@kieshabracy7670]

Unfortunately, I haven't had the chance to utilize this particular diagram on any of my past projects, but based on the structure of how it helps to identify the cause of an issue is very helpful. That said, I look forward to utilizing this particular diagram on my future projects.

[@mikhailsirota9556]

Good system for finding the root cause of a result

[@donggunko9809]

Fishbone diagram is like putting brainstorm + 5 whys together. It sounds like an great tool, but I would like to see how it is being used in real life example.

[@nikiansell9949]

This is a great tool to utilize. I'm familiar with the 5 Why's so it was nice to see how that process is also incorporated into here. It would be nice to see an example of a completed one based on a made-up scenario, like the pizza delivery used in other videos.

[@fkiQuality]

Nicole, in addition to the 5-why's, you can use the fishbone along with the control chart in this way. As soon as the chart indicates a signal of special/uncontrolled variation, study the event by putting it in the head of the fishbone and ask "why" several times to get to the root causes. Now, sometimes the reason for the variation may be staring at you in which case you just need to try a change, see what happens and standardize the change (this is the PDSA cycle). Watch the video "A Japanese Control Chart"

[@nathanfey6835]

The corrective action process at my organization has the goal of finding the root cause. However, if someone outside the organization were to read through a sample of our corrective actions, they may find them insufficient. There tends to be a narrow focus on one or two categories towards solving a problem, without consideration to other areas. We are also lacking in a uniform and consistent approach to root cause analysis. If we were to introduce and train on the fishbone diagram, I believe we'd improve our root cause analysis by encouraging structured pathways of investigation and making sure we've considered all categories prior to closing out a corrective action.

[@danagreene6800]

This helped understand the fishbone diagram, having more tools. Thanks

[@jeffreysundwall7812]

This is an organized way to do brainstorming and free association. As we know, Ishikawa promoted the use of Quality Circles and I am sure that the diagram was used in that exercise as well.

[@joshturnbull1850]

The Fishbone diagram is a great tool that requires you to look at every part of the process to make sure you find the root cause.

[@Davidconga]

Excelent presentation!! Was pretty useful! Could you please create one explaining the Fault Tree Analysis? would be pretty useful!! Greetings from Costa Rica!!!

[@aaroncrenshaw6540]

The Fishbone is great, due to it is design to be hard on the process and not the people.

[@sblackmore27]

By using the 5 why's you can keep peeling away the layers of the problem and get to the root cause of the issue. The diagram helps to bring out the system of causes during a good brainstorming session.

[@nicholashumphrey8654]

I can see how this can be used with the entire team to both add ownership to the operation and get down to the nitty-gritty of what is really the cause of the problems. It is easy to think you know what the causes are, especially if you are in the work. But by having an open forum and brainstorming together you will realize the hidden causes.

[@kristukker5279]

Take it from our kids. Asking "Why?" over and over is a very natural way to learn about our environment, our systems, and our processes.

[@cocor3672]

We have to always ask questions why. Ishikawa's categories of things can be used as guidelines mental map to help us brainstorm all of possible causes.

[@user-yz5cw5st5b]

Before this video, I didn't think about how the fishbone diagram seeks to explain a system of causes and highlight the invisible when we can simply focus on the visible.

[@sherryclayton1778]

The team's ability to exercise trust during questioning process is key. Sometimes people will either panic, withdraw or push-back at probing questions. It's usually recommended that the "whys" go at least 5 levels deep. If a culture of trust does not exist within the team, that process is likely not going to be productive due to negative reactions. The question becomes how to build that trust if the organization is currently in flux?

[@charlesbonham8974]

Topic is well explained and wonderful analysis tool, can't wait to start a real fish bone diagram session.

[@MustaqueAliPMP]

The 6 causes recommended on the Fishbone diagram is manageable, however if there are large number of causes, it would be interesting to see if there is a maximum limit to Ishikawa method.