An Ishikawa diagram — also called a fishbone or cause-and-effect diagram — is a visual tool to organize candidate causes of a problem. The fish “head” is the effect (for example, late deliveries); the “bones” are categories (usually the 6Ms) where hypotheses hang.
This guide translates it to Mexico–US logistics: dock, OTIF (On Time In Full), freight, and the trip file. It includes a real diagram — not prose only — with a filled example. OCL Cargo is an autonomous TMS with agents: it helps validate causes with evidence and close the loop without a big bang. When you audit 100% of a pilot flow, the typical pattern is recovering 5–7% of freight spend in 6–8 weeks.
- standard cause–effect categories
- 6Ms
- readable fishbone (SVG)
- Visual
- OTIF / dock / border example
- MX–US
- pattern auditing 100% of pilot freight
- 5–7%
Useful cluster: lean supply chain and wastes · distribution KPIs · 5S methodology.
What an Ishikawa diagram is (short answer)
An Ishikawa diagram is a cause-and-effect scheme created and popularized by Japanese engineer Kaoru Ishikawa (1940s–60s) as one of the seven basic quality tools. Its shape looks like a fish skeleton — hence “fishbone”.
Three names, one tool:
- Ishikawa diagram — after its author.
- Fishbone — after the shape.
- Cause-and-effect — after the logic (causes on the bones; effect in the head).
It does not predict the future or replace a KPI board. It organizes collective thinking so you do not attack the loudest symptom first.
FIGURE 1 · STRUCTURE
Empty fishbone: head + 6Ms
First learn the shape. Then fill each bone with causes from your operation — not textbook phrases.
Head = effect · Bones = 6M · Twigs = candidate causes
Effect: Problem / effect
Method
Add candidate causes…
Materials
Add candidate causes…
Machine
Add candidate causes…
Manpower
Add candidate causes…
Measurement
Add candidate causes…
Mother Nature
Add candidate causes…
6M template: Method, Materials, Machine, Manpower, Measurement, Mother Nature.
What it is for: root cause vs symptoms
Use it when the same problem repeats and the team already “fixed” the symptom three times. In Mexico–US freight the symptom is “the truck arrived late”; the root may be a dock appointment, a broken OTIF definition, a tractor down, or a saturated yard.
Symptom (what hurts)
- Late delivery truck
- Customer claims OTIF breach
- Invoice fights the POD
- Driver “at fault” again
Root cause (what changes the outcome)
- Appointment window vs actual load start
- OTIF with OR (inflates the KPI)
- POD not tied to the trip ID
- Shift handoff without a checklist
Run short workshops (45–90 min) with dock, tower, traffic, and accounts payable. If only leadership attends, the fish fills with conference-room theories.
Diagram elements and the 6Ms
Every Ishikawa has the same blocks. Categories can adapt, but in logistics the 6Ms cover almost everything that breaks a trip.
Effect (head)
What it is: The measurable problem you want to explain
Mexico–US freight example: Late deliveries / broken OTIF on Monterrey–Laredo
Central spine
What it is: Line pointing to the effect
Mexico–US freight example: “Trip flow” from origin to destination
Categories (bones)
What it is: Cause groups (6Ms or others)
Mexico–US freight example: Method, Materials, Machine, Manpower, Measurement, Mother Nature
Sub-causes (twigs)
What it is: Concrete, observable hypotheses
Mexico–US freight example: “Dock appointment 6:00; actual load start 9:40”
The 6Ms in plain English
Method
Means: Procedures, policies, work sequence
Operations question: Does a load/appointment SOP exist and get followed?
Materials
Means: Inputs, product, packaging, physical docs
Operations question: Are packaging, labels, and seals correct?
Machine
Means: Equipment, tractor, forklifts, scanners, systems
Operations question: Did an asset or digital tool fail?
Manpower
Means: People: skills, shifts, communication
Operations question: Missing staff, handoff, or training?
Measurement
Means: How you measure (KPI, clock, GPS, sampling)
Operations question: Is the indicator lying or arriving late?
Mother Nature
Means: Environment: yard, weather, border, regulation
Operations question: Congestion, weather, or yard saturation?
How to build it step by step
Value is not a pretty drawing: it is a well-defined effect, categories filled with floor people, and validation with data before you invest.
Workshop
Operable Ishikawa cycle
Effect
Measurable problem
6Ms
Base bones
Brainstorm
Floor causes
Validate
Data + 5 Whys
Elige un paso para ver el detalle
Detalle del paso · 01
Step 1 — Write the effect in one measurable sentence
Step 1
Mexico–US logistics example: delays, OTIF, and dock
Effect in the head: late deliveries / broken OTIF on a Mexico–US corridor (for example Monterrey–Laredo). Below, the same fish filled with typical dock, freight, and measurement causes.
FIGURE 2 · MX–US EXAMPLE
Filled Ishikawa: dock, freight, and measurement
Each twig is an observable hypothesis. Next step is not “talk more”: cross GPS, appointments, POD, and the OTIF formula.
Head = effect · Bones = 6M · Twigs = candidate causes
Effect: Late deliveries / broken OTIF
Method
- Misaligned dock appointments
- Informal loading SOP
- Tender without fixed window
Materials
- Fragile packaging
- Wrong label / SKU
- Missing seals
Machine
- Forklift down
- Tractor in shop
- Scanner out of battery
Manpower
- Short dock staffing
- Shift handoff gaps
- Incomplete training
Measurement
- OTIF with OR (inflates KPI)
- GPS not tied to trip ID
- ETA without an owner
Mother Nature
- Border congestion
- Yard saturation
- Weather / road closure
Illustrative example: prioritize 3–5 causes with your corridor data; do not copy the whole fish as a plan.
OCL operating playbook — calibrate with your dock times and SLA.
Method
Candidate cause: Dock appointments misaligned with real ETA
How to validate (data): Compare appointment vs load-start time (last 20 departures)
Materials
Candidate cause: Wrong label / SKU to rework at the gate
How to validate (data): Shipment rejects for labeling in 30 days
Machine
Candidate cause: Forklift or tractor down in a critical window
How to validate (data): Shop orders vs missed appointments
Manpower
Candidate cause: Shift change without dock handoff
How to validate (data): Dead minutes between shifts; signed checklist yes/no
Measurement
Candidate cause: OTIF with OR (on time OR in full) inflates the KPI
How to validate (data): Recalculate OTIF with AND (on time AND in full)
Mother Nature
Candidate cause: Border congestion or saturated yard
How to validate (data): Yard dwell / crossing time vs plan
Advantages and honest limits
Ishikawa shines on multi-cause problems. It fails as quality theater or when nobody validates branches.
| Advantage | Limit |
|---|---|
| Makes the cause map visible (stops fighting over one villain) | Does not prove causation: it organizes hypotheses |
| Enables a cross-functional workshop (dock + tower + finance) | Fills with smoke if floor people are missing |
| Fits 5 Whys, Pareto, and PDCA | Without prioritization it becomes an infinite tree |
| Translates industrial quality to freight and DCs | Does not replace KPIs, trip files, or freight audit |
Combine with 5 Whys, Pareto, lean, 5S, and KPIs
The fish alone does not close the loop. In Mexico–US operations the sequence that works is: pick the pain (Pareto), map causes (Ishikawa), and deepen (5 Whys), then attack waste/order (lean / 5S) to measure (KPIs).
Pareto chart
What it adds: Prioritizes the ~20% of causes/problems that drive ~80% of pain
Sister guide: Pareto in logistics
5 Whys
What it adds: Deepens one branch to an actionable cause
Sister guide: Use in the workshop (checklist above)
Lean / muda
What it adds: Names the waste (wait, empty miles, overprocessing, defect)
Sister guide: Lean supply chain Mexico
Distribution KPIs
What it adds: OTIF, drop size, cost — with the correct formula
Sister guide: Distribution indicators
Checklist: an Ishikawa that closes the loop
Use this list when you close the workshop. If three items are missing, you are still brainstorming.
Elige un paso para ver el detalle
Detalle del paso · 01
Effect with a number
Close 1
What OCL executes when the cause is evidence and freight
Many fishbone branches in Mexico–US end in the same place: re-keyed status, loose proof of delivery (POD), GPS not tied, and payment without a trip file. OCL Cargo attacks that digital stretch.
OCL is an autonomous TMS with agents (computer use: they operate the screens you already use). It builds the trip file, reduces the human bridge, and — when applicable — can stamp invoices and Carta Porte. It coexists with your transportation management system (TMS); no day-one migration. Your team decides exceptions.
Work done
From hypothesis to evidence
Track
Typed status
Tie
GPS + POD to ID
Stamp
Invoice / Carta Porte
Exceptions
Your team decides
Key takeaways5 points
- Ishikawa = fishbone = cause-and-effect: the head is the effect; the bones are cause categories (usually the 6Ms).
- It separates symptom (late truck) from root cause (appointment, dock, OTIF math, border) — not “blame the driver”.
- The 6Ms: Method, Materials, Machine, Manpower, Measurement, Mother Nature (environment).
- Without data (GPS, POD, times) the diagram is a brainstorm; with data it is a prioritized attack plan.
- It pairs with Pareto (which problem), 5 Whys (deepen a branch), lean/5S, and honest distribution KPIs.
Is your team fighting symptoms or mapping the cause?
Related reading
Frequently asked questions
It is a cause-and-effect (fishbone) diagram that puts the problem in the “head” and organizes candidate causes into categories (usually the 6Ms) so you find the root, not just the symptom.
Yes: three names for the same tool. Kaoru Ishikawa popularized it in quality control; the shape looks like a fish; the logic is causes to effect.
Method, Materials, Machine, Manpower (people), Measurement, and Mother Nature (environment). In Mexico–US logistics they cover dock, freight, evidence, and border — not only the plant.
Pareto picks the problem that hurts most. Ishikawa maps candidate causes. 5 Whys deepens one branch to an actionable root. Then you measure with honest KPIs (OTIF, cost, exceptions).
It works in DCs, docks, control towers, and accounts payable. Late deliveries, broken OTIF, damage, and invoices without a trip file are perfect effects for the fish head.
No. It organizes hypotheses. Validate with data (GPS, proof of delivery, CFDI, dock times) before spending on a “fix”. Without evidence it is a brainstorm with a drawing.
OCL builds the trip file (rate, GPS, POD) and can stamp invoices and Carta Porte when applicable. Agents reduce re-keying; your team see typed exceptions. It coexists with your TMS; no day-one migration.