I am working on my first small project and I’m struggling to categorize causes in my Ishikawa diagram. I know the standard categories are the 6Ms, but they seem very manufacturing-focused. Is there a better way to structure a Fishbone diagram for a service-oriented process like IT support or customer service to ensure I don’t miss any critical root causes?
3 answers
For service industries, the 6Ms (Man, Machine, Material, Method, Measurement, Mother Nature) can feel clunky. Many Yellow Belts find success using the "4Ps" instead: People, Place, Policies, and Procedures. For an IT support context, "Place" might refer to the remote environment, and "Policies" could cover SLAs. The goal of the Fishbone isn't to be perfect with categories, but to brainstorm broadly. Don't get hung up on where a cause goes; just get it on the bone. Once you have the causes, use the "5 Whys" technique on the most likely ones to drill down to the actual root.
Have you tried involve a cross-functional team in your brainstorming session, or are you trying to identify all these root causes by yourself?
Just remember that the Fishbone is a qualitative tool. It helps you find potential causes, but you still need data to prove which ones are actually significant.
Susan makes an excellent point. A Yellow Belt should use the Fishbone to generate hypotheses, then use a simple Pareto chart to see which causes occur most frequently.
Charles, I was trying to do it alone, but I realize now that’s a mistake. Linda, the 4Ps approach makes so much more sense for my IT helpdesk project! I was struggling to find "Materials" in a digital ticket flow, but "Policies" fits perfectly. I’ve scheduled a 30-minute session with two senior technicians next Tuesday to fill out the diagram together. I’m hoping this collaborative approach will uncover some of the "hidden factory" issues we’ve been ignoring.