What the 5 Whys are: root-cause technique in Mexico logistics

What the 5 Whys are

The 5 Whys technique is easy to explain and hard to do well. You take a concrete effect (on-time in-full — OTIF — for trip 4821, demurrage spend for the month, unsigned proofs of delivery) and ask why it happened, using facts. Each answer feeds the next question.

“Five” is a Toyota Production System (TPS) heuristic: it pushes the team past the first comfortable explanation. It is not a ritual — stop earlier if you already have an actionable cause; keep going if the fifth answer is still a symptom.

In a distribution center (DC), dock, or control tower, the data must tie to an order or trip identifier. Without that, the analysis mixes different cases and produces “fixes” you cannot measure.

Origins: Sakichi Toyoda, Ohno, and TPS

The technique is associated with the problem-solving culture driven by Sakichi Toyoda and, above all, with how Taiichi Ohno used and described it inside the Toyota Production System: repeat “why” until the nature of the problem and the solution become clear.

Ohno presented it as the basis of a scientific approach on the floor — not as a lab formula. Lean and Toyota sources place it in that TPS tradition; you do not need to invent an exact “invention year” to use it well in 2026.

What you should inherit from TPS: go to the gemba (the real place of work), prefer facts over opinions, and look for system causes — method, standard, handoff — before blaming a person.

How it works (with a freight example)

The operable flow is short: define the effect, gather evidence, drill the chain, validate that the cause belongs to the process, and close with a measurable action.

Mexico–US example (tower / OTIF): trip 4821 missed OTIF at the destination DC. The team does not start with “the carrier is bad”; it starts with the appointment window and the TMS record.

The actionable cause is not “the coordinator.” It is the handoff process: without a mandatory update in the transportation management system (TMS), OTIF will keep breaking under other labels.

Benefits in Mexico–US logistics

Three concrete benefits when the chain ties to trip and pesos — not continuous improvement slogans:

On a Monterrey–Laredo–Dallas lane, a closed 5 Whys chain stops tower, dock, and accounts payable from blaming the carrier without evidence: tower sees OTIF down at destination, dock confirms on-time departure, and AP finds a detention accessorial with no proof of delivery (POD) supporting the window. The chain ends at “appointment moved on WhatsApp without TMS update” — not a blame meeting.

Another common pattern: illegible or unsigned POD. Quality and Delivery share the same effect; the benefit is stopping payment on re-deliveries or duplicate accessorials while someone “investigates” without a trip file. Re-measure at two weeks and the same leakage code drops off the Pareto chart.

When to use vs Ishikawa and Pareto

The right question is not “which tool is best?” but “which decision do I need today?”

Practical example: if 80% of leakage pesos are three accessorials (detention, demurrage, re-delivery), start with Pareto — not 5 Whys in parallel on ten trips. When code #1 is detention at the customer DC, Ishikawa opens branches (appointment, dock, OTIF measurement); 5 Whys drills the “misaligned appointment” branch to an actionable handoff rule.

If you already have a clear chain (“left late because tender did not reflect the new appointment”), skip Ishikawa and run 5 Whys directly — with GPS, POD, and rate on the same trip ID. Mixing tools without a prior decision turns root cause analysis into a quality poster.

Deep guides: Pareto in logistics, Ishikawa, and the hub RCA with five tools.

Limits and biases

5 Whys fail in predictable ways. Know them before selling the method as a “full RCA.”

• Forced single cause: many freight failures are multifactorial (appointment + yard + measurement). One chain can hide the second root.
• Facilitator bias: whoever leads the workshop can push toward a favorite hypothesis (“it’s always the carrier”).
• Opinion without evidence: “because they don’t care” is not a fact. Each why must cite GPS, POD, rate, CFDI, or a log.
• Blaming people: if the answer is a person’s name, ask which standard, tool, or handoff failed.
• Stopping too early: three whys that end on a symptom (“it arrived late”) are not root cause.

Step by step and document template

Use this sequence in the huddle or exception workshop. Then fill the template — without a template, the analysis evaporates.

Minimum template fields

With Ishikawa, Pareto, lean, and 5S

5 Whys do not compete with the rest of the kit — they complete it. The order that usually works on the Mexico–US corridor is this:

For action after the cause: lean supply chain and warehouse 5S. For honest measurement: distribution KPIs.

Operable close-out checklist

Before you call the workshop done, run this list. If any item fails, you still have a draft — not an RCA.

Exceptions and evidence: what OCL executes

When the why chain points to incomplete evidence, informal handoff, or your team bridge — re-keyed status, loose POD, payment without a trip file — the next step is not another poster: it is executing the record.

OCL is an autonomous TMS with AI agents (computer use): it builds the trip file, can stamp invoice and Carta Porte when fiscal scope applies, audits before payment, and escalates typed exceptions to your team. It coexists with your TMS; it does not require a day-one migration.

If the problem is “false digitization” (screens full, work still human), read false digitization of freight. If the pain lives in the tower: logistics control tower.

Related reading

• Root cause analysis: 5 RCA tools
• Ishikawa / fishbone diagram
• Pareto chart in logistics
• Lean supply chain Mexico
• 5S methodology in the warehouse
• False digitization of freight

Frequently asked questions