Cause and Effect Diagrams
It is difficult if not impossible to solve complicated problems without considering many factors and the cause-and-effect relationships between those factors. Defining and displaying those relationships helps. The first such cause-and-effect diagram was used by Kaoru Ishikawa in 1943 to explain to a group of engineers at the Kawasaki Steel Works how various work factors could be sorted and related. In recognition of this, these diagrams sometimes are called Ishikawa diagrams. They are also called fishbone diagrams, because they look something like fish skeletons.
What can it do for you?
Quality problems are typically not simple. They often involve the complex interaction of several causes. A cause-and-effect diagram will help you:
- Define and display the major causes, sub-causes and root causes that influence a process or a characteristic.
- Provide a focus for discussion and consensus.
- Visualise the possible relationships between causes which may be creating problems or defects.
Cause-and-effect diagrams are particularly useful in the measure and improve phases of Lean Six Sigma methodology.
How do you do it?
- Decide which quality characteristic, outcome or effect you want to examine. You might consider Pareto analysis to help you focus on the most important issue.
- Write your chosen effect on the right side of a paper, board or flipchart and draw a box around it. If you think of this as a fishbone diagram, this is the fish head.
- Draw a straight line to the left, the fish backbone.
- For each primary cause or category of causes, draw a diagonal line slanting from left to the centerline. Alternate these ribs on the top and bottom of the backbone. Label the end of each rib and draw a box around the label.
- Draw a horizontal line intersecting the appropriate diagonal line and label it to describe each secondary cause that influences a primary cause. Alternate these medium sized bones to the left and right of each rib.
- In a similar way, draw and label diagonal lines for third level or root causes, small bones, intersecting the secondary cause lines, medium sized bones.
- Examine the diagram. If certain causes seem to have a significant effect on the characteristic you are examining, mark them in a special way.
Variation 1: Cause Enumeration
Sometime it may be very difficult to determine the primary causes to be included in your diagram. If that is the case, after you have determined the characteristic or effect you are examining, follow these steps:
- Use brainstorming to create a list of all the possible causes. The list will contain a mixture of primary, secondary and tertiary (or big bone, middle sized bone and small bone) causes.
- Sort the list by grouping causes that are related.
- Identify or name each major grouping and make your cause-and-effect diagram.
- Machine, Manpower, Material, Measurement, Method and Environment are frequently used major causes that can apply to many processes.
The advantage of the cause enumeration technique is that you stand a much better chance that all causes will be listed, especially hidden ones, and your diagram will be a complete and useful picture. The disadvantage is that it may be difficult to relate all the causes clearly to the result, making the diagram hard to draw.
Variation 2: Process Classification
Sometimes it is more helpful to look at causes in the sequence in which they occur instead of considering overreaching logical categories. With this approach, the center line or backbone follows the sequence of the process.
- Instead of primary causes as the ribs, show the major process steps from left to right.
- Construct your cause-and-effect diagram as before.
The advantage of this technique is that, since it follows the sequence of the process, it will be easy for everyone to understand. The disadvantages are that similar causes will appear again and again, and causes due to a combination of factors will be difficult to show.
Hints for Making Good Diagrams
- Get input from many people involved in the process. Not only will this make for a more accurate diagram, everyone taking part will gain new knowledge.
- Make one cause-and-effect diagram for each Critical-To-Quality (CTQ) characteristic you are considering. Trying to include all CTQs on one diagram will make it too large and complicated to be of much use as a problem solving tool.
- Avoid generalities. Express each cause as concretely as possible.
- Since you will use your diagram to direct the examination of specific cause-and-effect relationships with data, the characteristic you are considering and all the causal factors should be measurable. If they are not, try to make them measurable or find substitutes.
- The objective of the cause-and-effect diagram is action. Be sure your causes are broken down to the level at which they can be acted on.
- Use your diagram to develop a common understanding of the factors potentially influencing or causing a quality problem.
- Use your diagram as a road map for collecting data to verify the causal relationship of various factors to the characteristic.
- Continue to annotate and modify your diagram as you verify relationships and learn more.
Using a cause-and-effect diagram this way will help you to see which factors in your process need to be checked, modified or eliminated.
Steven Bonacorsi is a Senior Master Black Belt instructor and coach. Steven Bonacorsi has trained hundreds of Master Black Belts, Black Belts, Green Belts, and Project Sponsors and Executive Leaders in Lean Six Sigma DMAIC and Design for Lean Six Sigma process improvement methodologies.
Bonacorsi Consulting, LLC., Steven Bonacorsi, President, Lean Six Sigma Master Black Belt, 47 Seasons Lane, Londonderry, NH 03053, email@example.com, 603-401-7047
Root Cause Analysis
The Root Cause Analysis method, when used properly, gives the project manager the ability to diagnose a problem that negatively impacted the project and remove it when it is first noticed.
Pareto Analysis Step by Step
Pareto Analysis or the 80/20 rule enables you to see what 20 percent of cases are causing 80 percent of the problems on a project.
A Word (Or Two) On Quality
Project teams are often focused on completion of the build, forgetting that actual completion is achieved at the end of successful testing and bug resolution, not at the end of the build.
Planning a Project using a Work Breakdown Structure & Logic Network
How to create a well thought out, detailed project plan using a Work Breakdown Structure and Logic Network while building a committed high performing team.
The POST method is a way to give clarity at the beginning of a meeting.
- Purpose: What is the purpose of the meeting?
- Objective: What are you trying to achieve in the meeting, what does success look like?
- Structure: What is the structure of the meeting we are having?
- Timing: How much time is allocated to the meeting?
Discover our forum where you can ask questions, get advice from other people and share your experience.