E6S-117 Ishikawa- Fishing for the Truth - Part 1

Like / Dislike  **We'd Appreciate Your Opinion**

Intro:  Welcome to the E6S-Methods podcast with Jacob and Aaron, your weekly dose of tips and tricks to achieve excellent performance in your business and career.  Join us as we explore deeper into the practical worlds of Lean, Six Sigma, Project Management and Design Thinking.  In this episode number 117, Jacob and I go fishing, well, soft of.  We're "Fishing for the Truth" with the Ishikawa diagram, more commonly known as the "Fishbone," We discuss its typical format and some alternative approaches.  Here we go. http://bit.ly/E6S-117  Leave a Review! http://bit.ly/E6S-iTunes

                                                                   

Objection 1:  This is too cumbersome, and I get no value from it

Counter 1: Can be overkill.  Only use it for when you need to consider multiple options and don't want to rule anything out too soon. Far less valuable if using it for situations where the root cause is already known, but you need to "show a tool". 

Objection 2:  Why can't I just use a list? This is chaotic

Counter 2: You can. If this style is too chaotic, consider an outline breakdown.  Fishbone, Work Breakdown structure, Org charts, Outlines serve the same basic function. Choose the format that works best for you and your org.

Objection 3:  Gets too busy, too much detail                                                                              

Counter 3: Can be overwhelming.  There is a danger of going down a rabbit hole.                                                                         

 

I            Origins, Wikipedia, https://en.wikipedia.org/wiki/Ishikawa_diagram; Ishikawa diagrams (also called fishbone diagrams, herringbone diagrams, cause-and-effect diagrams, or Fishikawa) are causal diagrams created by Kaoru Ishikawa (1968)

a.       One of “THE SEVEN” basic tools of quality: (Ishikawa, Check sheet, Control Chart, Histogram, Pareto, Scatter diagram, Flow Diagram

i.      suitable for most people & situations, minimal technical training necessary

ii.      Useful almost anywhere, (DMAIC, Design, Root Cause Analysis)

b.      Causes are usually grouped into major categories to identify these sources of variation. (6Ms, 4Ps, custom)

II         Looks “like a fish” 

a.       The defect, problem or output (Y) is the “head”

b.      The body is branched off into several categories, larger general inputs (X), “the bones”

c.       Bones broken down further, into potential root causes

d.      Potential causes broken down further, if necessary

                       

III      Typical categories (bones)

a.       6Ms, (originally 5), typically used for manufacturing

i.      Man,  Machine, Method, Materials, Measurement, Mother Nature

ii.      Potential up to 8Ms? (not typical), Management/Money Power, Maintenance

b.      For service

i.      4Ps – Policies, Procedures, People and Plant

ii.      4Ss - Surroundings, Suppliers, Systems, Skills

c.       The 8 P's (used in marketing)

i.      Product/Service, Price, Place, Promotion, People, Process, Physical Evidence, Publicity

Outro: Thanks for listening to episode 117 of the E6S-Methods podcast.  Stay tuned for episode number 118, where Jacob and I continue our expedition with Ishikawa.  Jacob and I both review some real "fishy" applications with part 2 of "Fishing for the truth!,"  If you subscribe to this program we'd like to know who you are.  Drop us a note on twitter @e6sindustries, email Aaron at aaron@e6s-methods.com, or contact us through our website.  As always, reviews on iTunes are much appreciated.  If you are one of the most awesome people who leave a review, be sure to let us know. Don't forget to you can find notes and graphics for all shows and more at www.E6S-Methods.com. "Journey Through Success. If you're not climbing up, you're falling down?    Leave a Review! http://bit.ly/E6S-iTunes

Like / Dislike  **We'd Appreciate Your Opinion**