Fishbone (Ishikawa) Diagram in Pharma: Meaning, 6M Categories & How to Use It

Fishbone (Ishikawa) Diagram in Pharma: Meaning, 6M Categories & How to Use It

Fishbone (Ishikawa) in Pharma: A Practical Cause-and-Effect Tool for GMP Investigations

Definition

Fishbone Diagram (also called an Ishikawa Diagram or Cause-and-Effect Diagram) is a structured investigation and brainstorming tool used to identify and organize potential causes of a problem. In GMP environments, fishbone analysis helps teams move beyond guesswork by systematically exploring causes across categories such as people, equipment, methods, materials, measurement, and environment. In simple terms: it’s a way to map “everything that could have caused this” in a clear, auditable structure.

Why Fishbone Is Used in Pharma

Many deviations and failures have multiple contributing causes. Fishbone is used because it:

  • Prevents “single-cause bias” (blaming one factor too early)
  • Organizes investigation thinking in a consistent, repeatable way
  • Encourages cross-functional input (QA, QC, Production, Engineering, Validation)
  • Helps identify systemic causes that support meaningful CAPA
  • Creates a strong, visual audit trail for investigation completeness

Fishbone vs 5 Whys (Quick Clarity)

  • Fishbone: explores many possible causes across categories (broad and structured).
  • 5 Whys: follows one likely cause path deeper to reach a root cause (narrow and deep).

Common practice is to use fishbone first (to identify and organize hypotheses), then use 5 Whys or evidence testing to confirm the

true root cause.

The 6M Categories (Most Common Pharma Version)

A classic fishbone uses the 6M structure. In pharma terms, it typically looks like this:

1) Man (People)

  • Training gaps or ineffective training
  • Operator fatigue, workload, shift patterns
  • Human error opportunities due to poor design
  • Communication gaps between teams

2) Machine (Equipment/Systems)

  • Equipment malfunction or wear
  • Calibration drift, sensor failure
  • Automation logic or alarm issues
  • Inadequate preventive maintenance
See also  RTM Full Form in Pharma: Requirements Traceability Matrix (Meaning & Use)

3) Method (Procedures/Process)

  • SOP unclear, not practical, or not followed
  • Incorrect sequencing or missing steps
  • Weak line clearance or verification practices
  • Inadequate sampling plan or execution

4) Material

  • Supplier variability, different lots behaving differently
  • Incorrect grade, wrong label, mix-up risk
  • Material storage conditions not maintained
  • Changes in critical attributes (moisture, PSD, potency)

5) Measurement

  • Test method issues or analyst technique variation
  • Instrument calibration and suitability problems
  • Data transcription errors or calculation mistakes
  • Sampling bias or incorrect sampling location

6) Environment

  • Temperature/humidity excursions
  • Cleanroom conditions (pressure, microbial, airflow) deviations
  • Power fluctuations, compressed air quality issues
  • Facility layout causing flow and mix-up risks

Organizations sometimes customize these categories (e.g., adding “Management” or “Software/Data”), but 6M is the most widely recognized structure.

How to Create a Fishbone Diagram (Audit-Ready Steps)

Step 1: Define the Problem Clearly

Write the problem at the “head” of the fishbone. It must be specific (what happened, where, when, and impact). Vague problem statements produce vague cause lists.

Step 2: Build a Cross-Functional Team

Fishbone works best when the right people are in the room: process owner, QA, engineering, QC/analytical (if data issue), validation (if control/qualification issue). This prevents blind spots.

Step 3: Brainstorm Causes Under Each Category

Add possible causes under each 6M branch. At this stage, causes are hypotheses—not conclusions. Keep them factual and testable where possible.

Step 4: Convert Hypotheses into Evidence Checks

This is where many teams fail. A fishbone is not a final answer by itself. For each high-likelihood or high-severity cause, define how you will verify it using evidence:

  • Review batch records and operator logs
  • Check calibration and maintenance history
  • Verify material COA, supplier lot data, storage logs
  • Inspect equipment physically and review alarm history
  • Review test method system suitability and analyst records
See also  Requalification vs Revalidation in Pharma: Meaning, Differences & Triggers

Step 5: Narrow to Probable Causes and Confirm Root Cause

Once evidence is reviewed, you narrow down probable causes and confirm the root cause(s). Sometimes there are multiple root causes, such as a method weakness plus an equipment drift. The key is that the confirmed cause(s) must be supported by evidence.

Step 6: Link Confirmed Causes to CAPA

CAPA must address confirmed causes. If the fishbone lists 20 possible causes but CAPA addresses only “training,” auditors will question whether you solved the real issue.

Mini Example (Practical Fishbone Use)

Problem: Content uniformity failure during tablet production.

A fishbone might identify potential causes like:

  • People: blender charge sequence not followed
  • Machine: blender RPM drift, worn impeller
  • Method: blend time too short, SOP unclear on sampling locations
  • Material: API PSD variation across lots
  • Measurement: sampling thief technique variation, assay method variation
  • Environment: humidity change affecting flow and segregation

Then evidence checks narrow down which causes are real. For example, batch data could show API PSD change plus inadequate blend time at scale—leading to CAPA focusing on material controls and blend strategy, not just training.

Common Fishbone Mistakes (Audit Traps)

  • Using fishbone as a “decorative” page: filled with generic causes without evidence follow-up.
  • Not defining verification: no proof that causes were evaluated or ruled out.
  • Blame bias: overloading “People” causes and ignoring system/design weaknesses.
  • Too narrow team: missing key contributors (engineering, QC, validation).
  • No linkage to CAPA: CAPA doesn’t match the confirmed causes.
  • Not revisiting after recurrence: repeat events with the same fishbone but no improved controls.
See also  OOS Full Form in Pharma: Out of Specification (Meaning & Use)

Audit-Ready Talking Points

  • Fishbone was used to systematically explore potential causes across 6M categories
  • Potential causes were treated as hypotheses and verified with objective evidence
  • Confirmed root cause(s) were supported by records, logs, and data review
  • CAPA actions directly address confirmed causes and include prevention
  • Effectiveness checks confirm the issue does not recur

FAQs

What is a fishbone diagram in pharma?

It is a structured cause-and-effect tool used to list and organize potential causes of deviations or failures across categories like People, Machine, Method, Material, Measurement, and Environment.

Is fishbone a root cause analysis method?

It is an RCA support tool. Fishbone helps identify and organize possible causes, but root cause must be confirmed using evidence and analysis.

Why do auditors like fishbone?

Because it shows structured investigation thinking and helps demonstrate that multiple potential causes were considered—not just the most convenient explanation.

Can fishbone identify more than one root cause?

Yes. Many GMP issues have multiple contributing root causes. The key is verifying them with evidence and aligning CAPA to them.

What is the most common fishbone audit finding?

Fishbone diagrams filled with generic causes but no documented evidence checks, no narrowing process, and no clear linkage to CAPA.

Also Check: