The problem is very complicated and the project team cannot identify the root cause.If the traditional way of approaching the problem (trial and error, trying all possible causes, and so on) is very time consuming.When there are many possible causes for a problem.To analyze and find the root cause of a complicated problem.You may find it helpful to use the Ishikawa diagram in the following cases: ProcessModel has a great “fishbone” diagramming tool built-in.

In some processes you will find problems for which the cause cannot be easily determined.How is this Relevant to ProcessModel, Process Improvement and Simulation? It is known as a fishbone diagram because of its shape, similar to the side view of a fish skeleton. It was first used in the 1960s, and is considered one of the seven basic tools of quality management, along with the histogram, Pareto chart, check sheet, control chart, flowchart, and scatter diagram. Ishikawa diagrams were proposed by Kaoru Ishikawa in the 1960s, who pioneered quality management processes in the Kawasaki shipyards, and in the process became one of the founding fathers of modern management. Causes are usually grouped into major categories to identify these sources of variation. Each cause or reason for imperfection is a source of variation. Ishikawa diagrams (also called fishbone diagrams or cause-and-effect diagrams) are diagrams that show the causes of a certain event. Common uses of the Ishikawa diagram are to identify potential factors causing an overall effect.

Ishikawa diagram used for