FISH BONE TECHNIQUE PRESENTED BY ASHA MATHEW – 03   ANKIT KANOJIA – 22 NIBHA NAIK - 35
Introduction In 1943, Dr. Kauro Ishikawa, a Japanese quality control statistician, invented the Fish Bone Technique. It is also called  CAUSE AND EFFECT DIAGRAM  and  ROOT CAUSE ANALYSIS .
Fish Bone Diagram Problem Category 2 Category 1 Cause 1 Cause 2 Category 3 Category 4 When a Fish Bone diagram is constructed it resembles a skeleton of the fish
TASK INVOLVED IN CONSTRUCTING A FISH BONE DIAGRAM Define the problem Brainstorming Identify cause
CASE STUDY DROP IN  SALES MANAGEMENT MACHINERY MATERIAL MANPOWER MARKET CONDITION LOW MAINTAINENCE OBSELETE  TECHNOLOGY LACK OF PROPER RESEARCH AUTOCRATIC MANAGEMENT HIGH COST HIGH ATTRITION RATE UNSKILLED STAFF CHEAP  IMPORTS COMPETITION POOR QUALITY METHODS MARKETING APPROACH
WHAT IS THE ROOT CAUSE  ? ?
AUTOCRATIC    BEHAVIOUR   OF    MANAGEMENT
WHEN TO USE  ? To find the root cause Many possible causes Time consuming traditional approach Complicated problem
WHEN NOT TO USE  ? Simple problem Small team size Communication problem Expert team
THANK YOU   …..

Fishbone[1]

  • 1.
    FISH BONE TECHNIQUEPRESENTED BY ASHA MATHEW – 03 ANKIT KANOJIA – 22 NIBHA NAIK - 35
  • 2.
    Introduction In 1943,Dr. Kauro Ishikawa, a Japanese quality control statistician, invented the Fish Bone Technique. It is also called CAUSE AND EFFECT DIAGRAM and ROOT CAUSE ANALYSIS .
  • 3.
    Fish Bone DiagramProblem Category 2 Category 1 Cause 1 Cause 2 Category 3 Category 4 When a Fish Bone diagram is constructed it resembles a skeleton of the fish
  • 4.
    TASK INVOLVED INCONSTRUCTING A FISH BONE DIAGRAM Define the problem Brainstorming Identify cause
  • 5.
    CASE STUDY DROPIN SALES MANAGEMENT MACHINERY MATERIAL MANPOWER MARKET CONDITION LOW MAINTAINENCE OBSELETE TECHNOLOGY LACK OF PROPER RESEARCH AUTOCRATIC MANAGEMENT HIGH COST HIGH ATTRITION RATE UNSKILLED STAFF CHEAP IMPORTS COMPETITION POOR QUALITY METHODS MARKETING APPROACH
  • 6.
    WHAT IS THEROOT CAUSE ? ?
  • 7.
    AUTOCRATIC BEHAVIOUR OF MANAGEMENT
  • 8.
    WHEN TO USE ? To find the root cause Many possible causes Time consuming traditional approach Complicated problem
  • 9.
    WHEN NOT TOUSE ? Simple problem Small team size Communication problem Expert team
  • 10.