{"id":73,"date":"2019-12-20T16:07:35","date_gmt":"2019-12-20T16:07:35","guid":{"rendered":"https:\/\/dev-managing-ils-reporting.pantheonsite.io\/?page_id=73"},"modified":"2019-12-20T16:07:35","modified_gmt":"2019-12-20T16:07:35","slug":"root-cause-analysis-the-fishbone-diagramme","status":"publish","type":"page","link":"https:\/\/managing-ils-reporting.itcilo.org\/en\/tools\/root-cause-analysis-the-fishbone-diagramme\/","title":{"rendered":"Root cause analysis: the fishbone diagramme"},"content":{"rendered":"<h3>Purpose<\/h3>\n<p>The fishbone\u00a0diagram is\u00a0a cause-and-effect\u00a0diagram\u00a0that\u00a0can\u00a0be\u00a0used \u00a0to \u00a0identify \u00a0the \u00a0potential \u00a0(or \u00a0actual) \u00a0 cause(s) \u00a0for \u00a0a performance \u00a0problem. \u00a0Fishbone \u00a0diagrams \u00a0provide \u00a0a \u00a0structure \u00a0for \u00a0a \u00a0group\u2019s \u00a0discussion \u00a0around \u00a0 the \u00a0potential \u00a0causes \u00a0of the problem.<\/p>\n<h3>Needs assessment applications<\/h3>\n<p>Fishbone diagrams are often used in needs assessment to assist in illustrating and\/or communicating the relationships among several potential (or actual) causes of a performance problem. \u00a0Likewise, these graphical representations of relationships between needs (i.e., discrepancies between desired and actual results) offer you a pragmatic tool for building a system of performance improvement interventions (for instance, a combination of mentoring, job aids, training, motivation, new expectations) around the often complex relationships found across potential (or\u00a0actual) causes.<\/p>\n<h3>Advantages and disadvantages<\/h3>\n<p><strong>Advantages<\/strong><\/p>\n<ul>\n<li>Fishbone \u00a0diagrams \u00a0permit \u00a0a \u00a0thoughtful \u00a0analysis \u00a0that \u00a0avoids \u00a0overlooking \u00a0any \u00a0possible \u00a0root \u00a0causes \u00a0for \u00a0a\u00a0need.<\/li>\n<li>The \u00a0fishbone \u00a0technique \u00a0is \u00a0easy \u00a0to \u00a0implement \u00a0and \u00a0creates \u00a0an \u00a0easy-to-understand \u00a0visual \u00a0representation \u00a0of\u00a0the \u00a0causes, \u00a0categories \u00a0of \u00a0causes, \u00a0and \u00a0the \u00a0need.<\/li>\n<li>By \u00a0using \u00a0a \u00a0fishbone \u00a0diagram, \u00a0you \u00a0are \u00a0able \u00a0to \u00a0focus \u00a0the \u00a0group \u00a0on \u00a0the\u00a0 &#8220;big \u00a0picture&#8221;\u00a0 as \u00a0to \u00a0possible \u00a0causes or \u00a0factors \u00a0influencing \u00a0the \u00a0problem\/need.<\/li>\n<li>Even \u00a0after \u00a0the \u00a0need \u00a0has \u00a0been \u00a0addressed, \u00a0the \u00a0fishbone \u00a0diagram \u00a0shows \u00a0areas \u00a0of \u00a0weakness \u00a0that\u00a0 \u2013 once exposed\u00a0 \u2013\u00a0 can \u00a0be \u00a0rectified \u00a0before \u00a0causing \u00a0more \u00a0sustained \u00a0difficulties.<\/li>\n<\/ul>\n<p class=\" \"><strong>Disadvantages<\/strong><\/p>\n<ul>\n<li>The \u00a0simplicity \u00a0of \u00a0a \u00a0fishbone \u00a0diagram \u00a0can \u00a0be \u00a0both \u00a0its \u00a0strength \u00a0and \u00a0its \u00a0weakness. \u00a0As \u00a0a \u00a0weakness, \u00a0the \u00a0 simplicity \u00a0of the \u00a0fishbone \u00a0diagram \u00a0may \u00a0make \u00a0it \u00a0difficult \u00a0to \u00a0represent \u00a0the \u00a0truly \u00a0interrelated \u00a0nature \u00a0of \u00a0 problems \u00a0and \u00a0causes \u00a0in \u00a0some very \u00a0complex \u00a0situations.<\/li>\n<li>Unless \u00a0you \u00a0have \u00a0an \u00a0extremely \u00a0large \u00a0space \u00a0on \u00a0which \u00a0to \u00a0draw \u00a0and \u00a0develop \u00a0the \u00a0fishbone \u00a0diagram, \u00a0you may \u00a0find \u00a0that \u00a0you \u00a0are \u00a0not \u00a0able \u00a0to \u00a0explore \u00a0the \u00a0cause \u00a0and \u00a0effect \u00a0relationships \u00a0in \u00a0as \u00a0much \u00a0detail \u00a0as \u00a0you would \u00a0like \u00a0to.<\/li>\n<\/ul>\n<h3>How to use the tool<\/h3>\n<ol>\n<li>Identify \u00a0gaps \u00a0between \u00a0the \u00a0results \u00a0(i.e., \u00a0performance) \u00a0that \u00a0are \u00a0required \u00a0for \u00a0the \u00a0successful \u00a0accomplishment of your \u00a0programs\/projects \u00a0results \u00a0chain \u00a0(i.e., \u00a0logic \u00a0frame) \u00a0and \u00a0current \u00a0achievements \u00a0to-date.<\/li>\n<li>Generate \u00a0a \u00a0clear, \u00a0concise \u00a0statement \u00a0of \u00a0the \u00a0need(s). \u00a0Make \u00a0sure \u00a0that \u00a0everyone \u00a0in \u00a0the \u00a0group \u00a0agrees \u00a0with \u00a0the need as \u00a0it \u00a0is \u00a0stated. \u00a0For \u00a0example, \u00a0the \u00a0national \u00a0administration \u00a0has \u00a0been \u00a0able \u00a0to \u00a0provide \u00a0reports \u00a0on \u00a0time \u00a0 in \u00a0respect \u00a0of (on average) 25% of reports actually requested during the last 10 years and the aim of your \u00a0program\/project \u00a0is \u00a0for \u00a0100% of \u00a0the \u00a0reports requested each reporting year to be provided on time, with informative and responsive content.<\/li>\n<li>Using \u00a0a \u00a0long \u00a0sheet \u00a0of \u00a0paper, draw a line horizontally along the page. \u00a0This line will be the &#8220;spine&#8221; of the fish. Write \u00a0the \u00a0need \u00a0along \u00a0the \u00a0spine, \u00a0on \u00a0the left hand side.<\/li>\n<li>Identify \u00a0the overarching categories of causes of the need. Brainstorming is often an effective technique for identifying \u00a0the \u00a0categories of causes. \u00a0For each category of causes, draw a &#8220;bone&#8221;, a line at a 45 degree angle from the spine of the fish. Label \u00a0each \u00a0spine \u00a0(see \u00a0Figure \u00a01).<\/li>\n<li>Have the group brainstorm to identify the factors that may be affecting the cause and\/or the need. \u00a0For each category of causes, the group should be asking:\u00a0 &#8220;Why is this happening&#8221;? \u00a0Add each &#8220;reason why&#8221; to the diagram, clustered around the major cause category it influences.<\/li>\n<li>Repeat the procedure for \u00a0asking &#8220;Why \u00a0is \u00a0this \u00a0happening&#8221; for each effect, until the question yields no more meaningful \u00a0answers (see \u00a0Figure \u00a02).<\/li>\n<li>When the group has come to the consensus that the diagram contains an adequate amount of information, analyze the \u00a0diagram. \u00a0In particular, look for causes that are appearing in more than one section of the diagram.<\/li>\n<li>Circle anything that seems to be a root cause for the need. \u00a0Prioritize the root causes and decide to take action. This action may involve further investigating the root causes.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-74\" src=\"https:\/\/dev-managing-ils-reporting.pantheonsite.io\/wp-content\/uploads\/2019\/12\/fishbone_diagram_1_en.jpg\" alt=\"\" width=\"450\" height=\"222\" srcset=\"https:\/\/managing-ils-reporting.itcilo.org\/wp-content\/uploads\/2019\/12\/fishbone_diagram_1_en.jpg 450w, https:\/\/managing-ils-reporting.itcilo.org\/wp-content\/uploads\/2019\/12\/fishbone_diagram_1_en-300x148.jpg 300w\" sizes=\"auto, (max-width: 450px) 100vw, 450px\" \/><\/p>\n<p>&nbsp;<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-75\" src=\"https:\/\/dev-managing-ils-reporting.pantheonsite.io\/wp-content\/uploads\/2019\/12\/fishbone_diagram_2_en.jpg\" alt=\"\" width=\"600\" height=\"329\" srcset=\"https:\/\/managing-ils-reporting.itcilo.org\/wp-content\/uploads\/2019\/12\/fishbone_diagram_2_en.jpg 600w, https:\/\/managing-ils-reporting.itcilo.org\/wp-content\/uploads\/2019\/12\/fishbone_diagram_2_en-300x165.jpg 300w\" sizes=\"auto, (max-width: 600px) 100vw, 600px\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3>Tips for success<\/h3>\n<ul>\n<li>Make sure that there is consensus in the group about both the \u201cneed\u201d and the characteristics of the &#8220;cause statement&#8221;\u00a0 before \u00a0beginning the process of building the fishbone diagram.<\/li>\n<li>If appropriate, you can &#8220;graft&#8221; branches that do not contain a lot of information onto other branches. \u00a0 Likewise, you can &#8220;split&#8221; branches that have too much information into two or more branches as you go.<\/li>\n<li>Make parsimonious use of words while populating the fishbone diagram. \u00a0Only use as many words as<br \/>\nnecessary to describe the cause or effect.<\/li>\n<\/ul>\n<p>References and resources<\/p>\n<ul>\n<li>This tool\u00a0is adapted from a WBI Evaluation Group tool, first published in 2007.<\/li>\n<li>Gupta, \u00a0K., \u00a0Sleezer, \u00a0C.M., \u00a0&amp; \u00a0Russ-Eft, \u00a0D.F. \u00a0(2007): \u00a0<i>A \u00a0Practical \u00a0Guide \u00a0to \u00a0Needs \u00a0Assessment<\/i>,\u00a0Pfeiffer.<\/li>\n<li><a class=\"external-link\" href=\"http:\/\/www.isixsigma.com\/library\/content\/t000827.asp\">The \u00a0Fishbone \u00a0Diagram<\/a>\u00a0(from \u00a0Six \u00a0Sigma; \u00a0has \u00a0templates \u00a0for \u00a0making \u00a0fishbone \u00a0diagrams \u00a0in \u00a0Microsoft \u00a0Word\u00a0\u00a0and \u00a0Microsoft \u00a0Excel).<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Purpose The fishbone\u00a0diagram is\u00a0a cause-and-effect\u00a0diagram\u00a0that\u00a0can\u00a0be\u00a0used \u00a0to \u00a0identify \u00a0the \u00a0potential \u00a0(or \u00a0actual) \u00a0 cause(s) \u00a0for \u00a0a performance \u00a0problem. \u00a0Fishbone \u00a0diagrams \u00a0provide \u00a0a \u00a0structure \u00a0for \u00a0a \u00a0group\u2019s \u00a0discussion \u00a0around \u00a0 the \u00a0potential \u00a0causes \u00a0of the problem. Needs assessment applications Fishbone diagrams are often used in needs assessment to assist in illustrating and\/or communicating the relationships among several [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":59,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-73","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/managing-ils-reporting.itcilo.org\/en\/wp-json\/wp\/v2\/pages\/73","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/managing-ils-reporting.itcilo.org\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/managing-ils-reporting.itcilo.org\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/managing-ils-reporting.itcilo.org\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/managing-ils-reporting.itcilo.org\/en\/wp-json\/wp\/v2\/comments?post=73"}],"version-history":[{"count":1,"href":"https:\/\/managing-ils-reporting.itcilo.org\/en\/wp-json\/wp\/v2\/pages\/73\/revisions"}],"predecessor-version":[{"id":76,"href":"https:\/\/managing-ils-reporting.itcilo.org\/en\/wp-json\/wp\/v2\/pages\/73\/revisions\/76"}],"up":[{"embeddable":true,"href":"https:\/\/managing-ils-reporting.itcilo.org\/en\/wp-json\/wp\/v2\/pages\/59"}],"wp:attachment":[{"href":"https:\/\/managing-ils-reporting.itcilo.org\/en\/wp-json\/wp\/v2\/media?parent=73"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}