What is a Fishbone Diagram?
The Fishbone Diagram, also known as the Ishikawa Diagram or Cause-and-Effect Diagram, is a powerful visual tool used in Six Sigma methodology for identifying and organizing potential causes of a problem. Named after its creator, Dr. Kaoru Ishikawa, this diagram resembles the skeleton of a fish, with the problem statement as the "head" and potential causes branching off like "bones."
This systematic approach helps teams move beyond symptoms to identify root causes, making it an essential tool in the Analyze phase of the DMAIC process. By visualizing cause-and-effect relationships, teams can focus their improvement efforts on the most impactful areas.
Key Benefits of Fishbone Diagrams
- Structured Problem Analysis: Organizes brainstorming sessions and prevents overlooking potential causes
- Team Collaboration: Facilitates group discussion and knowledge sharing
- Visual Clarity: Makes complex cause-and-effect relationships easy to understand
- Root Cause Focus: Helps distinguish between symptoms and actual causes
- Documentation: Creates a permanent record of the problem-solving process
Fishbone Diagram Structure and Components
Basic Structure
A typical Fishbone Diagram consists of the following components:
1. Problem Statement (Fish Head)
The effect or problem being analyzed is placed in a box on the right side of the diagram, forming the "head" of the fish.
2. Main Spine (Backbone)
A horizontal arrow pointing to the problem statement represents the main spine of the fish.
3. Major Categories (Main Bones)
Primary cause categories branch off the main spine at angles, forming the major "bones" of the fish.
4. Sub-causes (Minor Bones)
Detailed causes within each category branch off from the major bones, creating smaller "bones."
Common Category Systems
The 6 M's (Manufacturing)
- Man/People: Human factors, training, skills, experience
- Machine: Equipment, tools, technology, maintenance
- Material: Raw materials, supplies, components, quality
- Method: Processes, procedures, work instructions
- Measurement: Data collection, metrics, calibration
- Mother Nature/Environment: Environmental factors, conditions
The 4 P's (Service Industries)
- People: Staff, customers, stakeholders
- Process: Procedures, workflows, systems
- Place/Physical Evidence: Environment, facilities, equipment
- Policies: Rules, regulations, guidelines
The 4 S's (Service/Marketing)
- Surroundings: Physical environment, atmosphere
- Suppliers: Vendors, partners, dependencies
- Systems: Information systems, processes
- Skills: Competencies, training, knowledge
How to Create a Fishbone Diagram: Step-by-Step Guide
Step 1: Define the Problem
Clearly state the problem or effect you want to analyze. Write it in a box on the right side of your workspace. Be specific and measurable when possible.
Step 2: Draw the Main Spine
Draw a horizontal arrow pointing to the problem statement. This forms the backbone of your fishbone diagram.
Step 3: Identify Major Categories
Choose an appropriate category system (6 M's, 4 P's, etc.) based on your industry and problem type. Draw these as diagonal lines branching from the main spine.
Step 4: Brainstorm Potential Causes
For each major category, brainstorm specific causes that could contribute to the problem. Use techniques like:
- Team brainstorming sessions
- 5 Whys technique
- Historical data analysis
- Expert consultation
Step 5: Add Sub-causes
For each cause, ask "Why does this happen?" to identify sub-causes. Draw these as smaller branches extending from the main causes.
Step 6: Review and Refine
Review the completed diagram with your team. Look for:
- Missing categories or causes
- Causes that appear in multiple categories
- Vague or unclear cause statements
- Opportunities for further detail
Step 7: Prioritize for Investigation
Use data, evidence, and team expertise to prioritize which causes deserve immediate investigation. Mark high-priority items for further analysis.
Best Practices for Effective Fishbone Diagrams
Team Composition
- Include diverse perspectives from different departments
- Involve subject matter experts familiar with the process
- Keep team size manageable (5-8 participants)
- Include frontline workers who experience the problem daily
Facilitation Tips
- Use a trained facilitator to guide the process
- Encourage open communication without judgment
- Build on others' ideas rather than criticizing
- Keep the session focused on causes, not solutions
- Document all ideas, even seemingly unlikely ones
Common Mistakes to Avoid
- Vague Problem Statements: Be specific about the effect being analyzed
- Listing Solutions: Focus on causes, not potential fixes
- Insufficient Detail: Drill down to specific, actionable causes
- Blame-Focused Thinking: Focus on process issues, not personal blame
- Lack of Data Validation: Verify causes with evidence before pursuing them
Fishbone Diagrams in the DMAIC Process
Define Phase
Use fishbone diagrams during problem definition to ensure comprehensive understanding of potential contributing factors. This helps refine the problem statement and project scope.
Measure Phase
The categories and causes identified in the fishbone diagram guide data collection efforts. Determine which causes can be measured and establish metrics for validation.
Analyze Phase
This is the primary phase for fishbone diagram usage. Use the diagram to:
- Organize root cause analysis efforts
- Guide hypothesis development
- Prioritize investigation areas
- Support statistical analysis planning
Improve Phase
Validated causes from the fishbone diagram become the focus of improvement solutions. The diagram helps ensure solutions address root causes rather than symptoms.
Control Phase
Use the fishbone diagram to develop monitoring plans that watch for the recurrence of validated root causes.
Advanced Fishbone Diagram Techniques
Weighted Fishbone Analysis
Assign weights or probability scores to different causes based on:
- Historical data and frequency of occurrence
- Expert judgment and experience
- Cost or impact of each cause
- Ease of investigation or measurement
Multi-Level Fishbone Diagrams
For complex problems, create multiple levels:
- Level 1: High-level categories and major causes
- Level 2: Detailed sub-causes and contributing factors
- Level 3: Specific conditions or triggers
Time-Based Fishbone Analysis
Consider temporal aspects by organizing causes by:
- Before the problem occurs
- During the problem manifestation
- After the problem is detected
Digital Tools and Software
Leverage technology for more sophisticated analysis:
- Microsoft Visio: Professional diagramming with templates
- Lucidchart: Collaborative online diagramming
- Minitab: Statistical software with fishbone capabilities
- SmartDraw: Automated diagramming with Six Sigma templates
Real-World Fishbone Diagram Examples
Manufacturing Example: High Defect Rate
Problem: 15% defect rate in electronic component assembly
Major Categories and Key Causes:
- Machine: Calibration drift, worn tooling, inadequate maintenance
- Material: Supplier quality variation, incorrect specifications, contamination
- Method: Unclear work instructions, process variability, setup procedures
- Man: Training gaps, fatigue, experience level
- Measurement: Gauge accuracy, inspection frequency, criteria clarity
- Environment: Temperature fluctuations, humidity, contamination
Result: Investigation revealed that temperature fluctuations and supplier quality variation were the primary root causes, leading to targeted improvements that reduced defects to 3%.
Service Example: Customer Complaint Response Time
Problem: Customer service response time exceeds SLA of 2 hours
Major Categories and Key Causes:
- People: Staffing levels, skill gaps, workload distribution
- Process: Ticket routing, escalation procedures, priority classification
- Place: System accessibility, workspace ergonomics, information availability
- Policies: SLA definitions, approval requirements, communication protocols
Result: Analysis showed that inefficient ticket routing and unclear priority classification were major contributors, leading to process redesign that reduced response time to 45 minutes average.
Validating and Acting on Fishbone Diagram Results
Data-Driven Validation
Never assume causes are valid without evidence. Use these methods to validate potential causes:
Statistical Analysis
- Correlation analysis to identify relationships
- Regression analysis for predictive relationships
- Hypothesis testing for cause validation
- Design of experiments (DOE) for cause confirmation
Process Analysis
- Time studies to understand process timing
- Value stream mapping to identify waste
- Process observation and documentation
- Historical data analysis
Measurement Techniques
- Check sheets for data collection
- Control charts for process stability
- Capability studies for process performance
- Gauge R&R for measurement system analysis
Prioritization Matrix
Use a prioritization matrix to rank causes based on:
- Impact: How much does this cause contribute to the problem?
- Frequency: How often does this cause occur?
- Detection: How easily can this cause be detected?
- Control: How easily can this cause be controlled or eliminated?
Common Applications Across Industries
Healthcare
- Patient safety incidents analysis
- Medical error reduction
- Treatment outcome improvement
- Infection control investigations
Manufacturing
- Quality defect analysis
- Equipment downtime reduction
- Safety incident investigation
- Production efficiency improvement
Financial Services
- Transaction error analysis
- Customer complaint resolution
- Compliance violation investigation
- Process improvement initiatives
Information Technology
- System downtime analysis
- Software defect investigation
- Security incident response
- User experience improvements
Frequently Asked Questions
Q: How long should a fishbone diagram session take?
A: Typically 1-3 hours depending on problem complexity. Simple problems may require 30-60 minutes, while complex issues might need multiple sessions over several days.
Q: How many causes should be included in a fishbone diagram?
A: There's no fixed number, but aim for completeness rather than quantity. Most effective diagrams have 20-50 specific causes across all categories, with 3-8 causes per major category.
Q: Can fishbone diagrams be used for positive effects?
A: Yes! While typically used for problem analysis, fishbone diagrams can also analyze positive outcomes to understand what drives success and how to replicate it.
Q: How do you handle causes that fit multiple categories?
A: Place the cause in the most relevant category, but note the relationship with other categories. Some practitioners use dotted lines to show cross-category relationships.
Q: What's the difference between fishbone diagrams and fault tree analysis?
A: Fishbone diagrams are broader brainstorming tools that explore all potential causes, while fault tree analysis uses logic gates to model specific failure sequences with mathematical precision.
Q: Should solutions be included in fishbone diagrams?
A: No, focus solely on causes during diagram creation. Solutions should be developed after causes are validated through data analysis. Mixing causes and solutions reduces analytical clarity.
Master Six Sigma Root Cause Analysis
The Fishbone Diagram is just one of many powerful tools in the Six Sigma methodology. Enhance your problem-solving skills with comprehensive Six Sigma training from Eastman Business Institute.