Example data table
| Category | Cause | Severity | Occurrence | Detection | Score | Owner | Countermeasure |
|---|---|---|---|---|---|---|---|
| Method | Polishing step skipped on rush orders | 8 | 6 | 5 | 240 | QA Lead | Add gated checklist and scan-off |
| Machine | Worn fixture causing misalignment | 7 | 5 | 6 | 210 | Maintenance | Replace fixture; add PM interval |
| Material | Inconsistent coating thickness from supplier | 9 | 4 | 6 | 216 | Purchasing | Tighten incoming specs; audits |
Formula used
This tool prioritizes suspected causes using a simple risk-style score:
- Score = Severity × Occurrence × Detection
- Severity (1–10): impact on the customer, compliance, cost, or safety.
- Occurrence (1–10): how often the cause is likely to happen.
- Detection (1–10): how likely current controls miss it (higher = harder to detect).
Use the ranked table to focus investigations and countermeasures on the highest scores first.
How to use this calculator
- Write a clear problem statement for the effect you observe.
- Confirm or edit categories (defaults match common quality practice).
- Add causes under each category; include evidence, owner, and a countermeasure idea.
- Optionally score each cause (1–10). Submit to generate a ranked list and diagram.
- Export CSV for tracking and PDF for audits or sharing.
Why structured cause mapping improves investigations
Fishbone analysis turns scattered opinions into a single, testable hypothesis set. By forcing causes into clear categories, teams reduce confirmation bias and avoid jumping to fixes. A written problem statement anchors scope, while evidence fields capture where data came from, such as inspection logs, SPC charts, photos, or audit notes. This tool also encourages ownership by linking each suspected cause to a responsible role.
Using scores to focus limited improvement time
When severity, occurrence, and detection are rated on a 1–10 scale, the score highlights where risk concentrates. High severity with high occurrence signals customer impact and cost exposure. High detection ratings indicate weak controls, meaning defects can escape. Ranking causes helps teams decide which experiments, containment actions, or control-plan updates should happen first, especially when resources are constrained or deadlines are tight.
Interpreting categories with real shop-floor signals
Method issues often appear as skipped steps, outdated work instructions, or unstable changeovers. Machine causes show up as drift, wear, vibration, and sensor faults. Material causes include variability, contamination, and supplier process changes. Measurement causes involve calibration gaps, lighting inconsistency, and poor gauge repeatability. Environment can include dust, humidity, temperature swings, and layout constraints that increase handling damage.
Turning hypotheses into verified root causes
A fishbone diagram is not proof; it is a prioritized map for testing. Start with the top ranked causes and define what would confirm or reject each one. Use short trials, targeted inspections, or designed checks to collect data quickly. If a cause is confirmed, convert the countermeasure idea into a controlled action with a due date and a verification metric, such as defect rate, rework hours, or Cpk.
Documenting decisions for audits and continuous learning
Exporting results supports traceability in quality systems. CSV is useful for action registers and follow-up meetings, while PDF captures a snapshot for audits, customer reviews, and management reporting. Over time, saved diagrams create a knowledge base of recurring failure modes, effective countermeasures, and control weaknesses. That history shortens future investigations and strengthens preventive planning across product lines. Review trends quarterly to spot systemic gaps and standardize best practices across shifts sitewide.
FAQs
What is a fishbone diagram used for in quality control?
It organizes potential causes of a problem into categories, helping teams investigate systematically and avoid guessing. It supports root-cause testing and action planning.
Do I need scores for the diagram to work?
No. You can enter causes without scoring and still generate the diagram. Scores simply rank causes so you can focus investigations first.
How should we rate Detection on the 1–10 scale?
Higher Detection means the issue is harder to catch with current controls. Rate it high when inspections, alarms, or tests often miss the failure.
How many causes should we add under each category?
Start with three to six strong hypotheses per category. Too many weak guesses reduces clarity. Use evidence to narrow the list quickly.
What should be included in the Evidence field?
Reference the proof you will use, such as SPC charts, inspection records, photos, maintenance logs, supplier reports, or ticket numbers. This makes follow-up faster and auditable.
How can we use exports in meetings and audits?
Use CSV for action tracking, owners, and deadlines. Use PDF to share a consistent snapshot of the diagram and ranked causes during reviews and audits.