Root cause analysis (RCA) is the method to stop fighting symptoms — low OTIF, saturated docks, inflated accessorials — and reach a cause someone can change this week. In Mexico–US logistics the most useful kit is five tools: Pareto, 5 Whys, Ishikawa, scatter diagram, and FMEA.
This guide is not a plant or MES upsell. It is the operable hub for DCs, docks, towers, and freight: definition, when-to-use matrix, a Mexico example per tool, and the order to chain them without quality theater.
- RCA tools in the kit
- 5
- Pareto, fish, and 5 Whys
- 1 order
- DC, dock, freight, trip file
- MX–US
- evidence tied to the trip
- ID
Useful cluster: Pareto chart · Ishikawa diagram · lean supply chain · 5S methodology.
What root cause analysis is (short answer)
Root cause analysis (RCA; análisis de causa raíz or ACR in Spanish) is a structured discipline: you define the effect with a number, collect evidence, pick the right tool, and do not stop at the first comfortable explanation (“the carrier failed”, “we were short-staffed”).
In a distribution center (DC) or on a Mexico–US corridor, the effect is often on-time in-full (OTIF), dock dwell, accessorial spend, customer chargebacks, demurrage, or mismatches between digital tax invoice (CFDI) / Carta Porte and proof of delivery (POD).
RCA does not replace a warehouse management system (WMS), a transportation management system (TMS), or the key performance indicator (KPI) board. It prioritizes and investigates; systems record and execute.
Benefits in logistics: clarity, speed, stability
Three concrete benefits — not slogans — when RCA is tied to trip ID and pesos:
Clarity
What you see on the floor: Tower, dock, and accounts payable talk about the same effect (same ID, same window)
What you avoid: Twenty causes in a spreadsheet with no owner
Speed
What you see on the floor: You attack 2–3 vital fronts in 30 days, not “the whole complaint catalog”
What you avoid: Endless continuous-improvement pilots with no baseline
Stability
What you see on the floor: Re-measure in 2–4 weeks; the failure stops returning under a new name
What you avoid: Fighting the same fire every Friday
In freight, stability shows when the accessorial stops “appearing” without a rate, or when OTIF stops being inflated by replacement orders. That needs evidence — not more meetings.
Matrix: which RCA tool when
The right question is not “which tool is best?” but “what decision do I need today?” Use this matrix before you draw anything.
Pareto
Best for…: Prioritize among many problems or causes
Complexity: Low
Mexico–US example: 80% of leak pesos in 3 accessorials or 3 customers
5 Whys
Best for…: A clear causal chain; deepen fast
Complexity: Low
Mexico–US example: Why did trip 4821 arrive late to Laredo?
Ishikawa
Best for…: Wide or cross-functional cause space
Complexity: Medium
Mexico–US example: Broken OTIF: dock + packaging + measurement + border
Scatter
Best for…: Test whether two variables move together
Complexity: Medium
Mexico–US example: Dock dwell hours vs demurrage / chargeback %
FMEA
Best for…: Prevent failures on a critical or new process
Complexity: High
Mexico–US example: New lane, hazmat, or fiscal trip file before scale
Pareto chart: prioritize the pain
A Pareto chart sorts bars from highest to lowest impact and adds the cumulative percentage. It finds the “vital few”: roughly 80% of the effect often concentrates in roughly 20% of the causes.
DC / freight example: in one month you close leak pesos — demurrage, detention, redelivery, storage, CFDI mismatch — and see three codes concentrate ~80% of MXN. That is where deep RCA goes; the rest waits.
Full guide with charts and picking + leak examples: Pareto chart in Mexico–US logistics.
5 Whys: deepen one chain
The 5 Whys method asks “why?” iteratively until you reach a cause the process can change. Five is a guide, not dogma: stop when the next answer is no longer actionable or blames a person with no system behind them.
Tower / OTIF example:
- Why did trip 4821 miss OTIF? — It arrived outside the destination DC window.
- Why outside the window? — It left the origin dock 4 hours late.
- Why late departure? — The load appointment moved without notifying the carrier.
- Why no notice? — The change lived in WhatsApp, not in the TMS.
- Why in WhatsApp? — No owner or rule for “appointment change = update tender + confirm”.
The actionable cause is not “the operator”; it is the handoff method. That is where you standardize (and, if needed, apply digital 5S to the trip file). Full guide with template, limits, and OTIF example: what the 5 Whys are in Mexico logistics.
Ishikawa diagram: map causes
An Ishikawa diagram — also fishbone or cause-and-effect — puts the effect in the “head” and organizes candidate causes into categories (usually the 6Ms: method, materials, machine, manpower, measurement, milieu/environment).
Dock / freight example: effect = “% of trips with dwell > 4 h at customer DC”. Typical branches: misaligned appointments (method), wrong labels/SKU (materials), forklift down (machine), shift handoff gaps (manpower), OTIF inflated by replacement orders (measurement), saturated yard or border (environment).
Guide with visual fishbone and plain-language 6Ms: Ishikawa diagram in Mexico–US logistics.
Scatter diagram: test correlation
A scatter diagram plots two variables to see if they move together. It does not prove causation alone, but it stops you from spending a full RCA on a false correlation.
Accounts payable / dock example: X = dock dwell hours; Y = demurrage or chargeback pesos per trip. If points rise together, you prioritize cutting dwell with appointment and POD evidence. If there is no pattern, look at another branch (mis-captured rate, mistyped accessorial code).
Dock dwell vs demurrage
If there is a pattern…: Attack appointments, slotting, and handoff
If there is no pattern…: Review accessorial typing / rate
ETA delay vs OTIF
If there is a pattern…: Tower and early-alert rules
If there is no pattern…: Review OTIF definition (does it include replacements?)
Missing POD vs days-to-pay
If there is a pattern…: Close the trip file before release
If there is no pattern…: The bottleneck may be approval, not evidence
FMEA: prevent failures before they cost
Failure Mode and Effects Analysis (FMEA; AMFE in Spanish) lists possible failure modes, scores severity, occurrence, and detection, and defines actions before you scale a critical process.
Mexico–US example: before opening a new lane or a hazmat flow, the team lists: “incomplete Carta Porte”, “POD without usable signature”, “GPS not tied to ID”, “DC appointment not confirmed”. Each mode has an owner, a detective control, and a plan if it occurs.
FMEA does not replace reactive RCA when the trip already failed. It complements it: fewer fires, more controls on the trip file and the dock.
How to chain them (operable order)
The classic mistake is starting by drawing the universe fishbone. The order that works in freight and DC operations is this:
RCA stack
From pain to prevention
Pareto
Pick the pain
Ishikawa
Map causes
5 Whys
Drill one branch
Scatter
Validate if needed
FMEA
Prevent recurrence
Then you attack waste with lean, organize the floor or the trip file with 5S, and measure with distribution KPIs that do not lie.
Checklist: turn RCA into action
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 number and ID
Close 1
From hypothesis to trip file: what OCL executes
Many Mexico–US RCA branches end in the same place: status re-keyed by hand, loose POD, GPS not tied to the ID, and pay without a trip file. OCL Cargo attacks that digital segment.
OCL is an autonomous TMS with AI agents that operate the screens and portals you already use. It builds the trip file, reduces the human bridge, and — when fiscal scope applies — can stamp invoice and Carta Porte. It coexists with your TMS; no day-one migration. Your team decides typed exceptions. When you audit 100% of the pilot flow, the typical pattern is recovering 5–7% of freight spend in 6–8 weeks.
Work done
Hypothesis with evidence
Track
Typed status
Tie
GPS + POD to ID
Stamp
Invoice / Carta Porte
Exceptions
Your team decides
Key takeaways5 points
- RCA = move from symptom to actionable cause with evidence tied to order or trip ID — not a rain of opinions.
- Five tools: Pareto (prioritize), Ishikawa (map), 5 Whys (deepen), scatter (correlation), FMEA (prevent).
- Useful Mexico–US order: Pareto, Ishikawa, and 5 Whys, scatter if needed, and FMEA on critical processes.
- Effect examples: OTIF, dock, accessorials, DC chargebacks, demurrage, POD, and CFDI/Carta Porte mismatches.
- Without owner, deadline, and re-measurement, the diagram is a poster; with a trip file, RCA moves cash and service.
Is your team fighting symptoms — or closing the cause?
Related reading
Frequently asked questions
It is the structured method to move from a symptom (low OTIF, high accessorial spend, incomplete POD) to a cause you can change — with evidence, not opinion. The tools (Pareto, 5 Whys, Ishikawa, scatter, FMEA) are the kit; RCA is the discipline of closing with owner, deadline, and re-measurement.
Pareto chart (prioritize), 5 Whys (deepen one chain), Ishikawa / fishbone (map causes), scatter diagram (test correlation), and FMEA (prevent failures before they scale). In Mexico–US logistics they chain as: Pareto, Ishikawa, and 5 Whys, scatter if needed, and FMEA on critical processes.
Use 5 Whys when the causal chain is clear and the team already suspects the branch. Use Ishikawa when the cause space is wide or cross-functional (dock + freight + measurement). Usual pattern: Ishikawa opens the map; 5 Whys drills one branch to an actionable cause.
It works in DCs, docks, control towers, and freight. The measurable effect can be OTIF, dock dwell, accessorials, chargebacks, demurrage, or CFDI/Carta Porte mismatches vs POD. Unlike a plant, the “data” must tie to order or trip ID — not a machine downtime code.
No. Pareto prioritizes which problem hurts most. Ishikawa and 5 Whys investigate why. Scatter helps you avoid mistaking correlation for cause. Without evidence (GPS, POD, rate, CFDI), RCA is quality theater.
Failure Mode and Effects Analysis (FMEA; AMFE in Spanish) lists possible failure modes, severity, occurrence, and detection before a critical process fails at the border, dock, or trip file. It complements reactive RCA: you prevent instead of only fighting fires.
When the root is incomplete evidence or a human bridge (re-keyed status, loose POD, pay without a trip file), OCL builds the trip file, can stamp invoice and Carta Porte when fiscal scope applies, audits pre-pay, and escalates typed exceptions. It coexists with your TMS; no day-one migration.