📈Graphical Representation: Cause-Effect Diagram (Definitions)

"A chart that can be used to systematically gather the problem causes of quality defects. Sometimes referred to as the 5M- or 6M-chart because most causes can be related to man (e.g., human factors), machine, method, material, milieu (i.e., the work environment), or the medium (the IT-platform)." (Martin J Eppler, "Managing Information Quality" 2nd Ed., 2006)

"A root cause approach to identifying, exploring, and graphically displaying all possible causes of an issue using a standard quality technique." (Danette McGilvray, "Executing Data Quality Projects", 2008)

"A chart that links an outcome to chains of possible contributing factors as tree structure working backwards from an event to determine possible root causes, drawn sideways so that it resembles the skeleton of a fish. Because the chart resembles the skeleton of a fish, it is often called a fishbone diagram." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A chart associated with a technique for identifying factors linked to potential problems, risks, or effects. Factors can include time, machinery, methods, material, energy, measurements, personnel, and environment. Also known as the Ishikawa diagram or fishbone diagram." (Bonnie Biafore & Teresa Stover, "Your Project Management Coach: Best Practices for Managing Projects in the Real World", 2012)

"A decomposition technique that helps trace an undesirable effect back to its root cause." (For Dummies, "PMP Certification All-in-One For Dummies" 2nd Ed., 2013)

"A model used for identifying cause and effect. Also known as a fishbone diagram and named after its creator, Kaoru Ishikawa." (Sally-Anne Pitt, "Internal Audit Quality", 2014)

"Named after Kaoru Ishikawa, a diagram that shows possible causes of effects that you want to study such as excessive bugs, delays, and other failures in the development process." (Rod Stephens, "Beginning Software Engineering", 2015)

"A diagramming technique, also called the Ishikawa diagramming, which teams can use to identify root causes to a problem, the effects of an action, or the action items they could take to meet a goal." (David K Pham, "From Business Strategy to Information Technology Roadmap", 2016)

"A decomposition technique that helps trace an undesirable effect back to its root cause." (Project Management Institute, "The Standard for Organizational Project Management (OPM)", 2018)