Five Whys

Five whys is the simplest, fastest, and most underused root cause tool in lean. The whole technique fits in one sentence: when a problem appears, ask why it happened, then ask why of that answer, and keep asking until the chain reaches a cause that, if removed, would prevent recurrence. Toyota engineers built the discipline as a daily habit, not a special technique reserved for big failures. Most shops can run a useful five whys in fifteen minutes on the floor with a pencil and a clipboard.

"If the answer to the last 'why' is a person, ask one more. The cause is the system that let them fail."

How five whys works

Five whys is a chain. Start with a clear, specific problem statement: "a critical bore on part 4711 came out 0.02 inches oversize on the third shift." That statement is the head of the chain. The first question is "why?" The answer becomes the second link, and the second "why" is asked of that answer. The chain continues until the team reaches an answer that points at an underlying system, standard, or design flaw.

The number five is a heuristic, not a rule. Some chains resolve in three. Others take seven. The signal that you have reached the root is that the answer is a process or design issue you can act on, not a behavior you can lecture about. "The operator was tired" is not a root cause. "The standard work assumes a two-minute changeover after lunch and provides no checklist, so the regulator drift is missed" is a root cause.

Two practical disciplines make the technique work. First, do it on the floor, with the people who were present when the problem occurred. Memory blurs in a conference room two days later. Second, write the chain down on one sheet so the reasoning is visible and reviewable. A five whys done verbally and lost to memory teaches nothing the next time.

When a chain branches, follow each branch. If the problem has two real causes, both chains need to reach a root. The pretty single-thread chain is a story; the real chain often forks once or twice.

Where five whys fits on the shop floor of a small manufacturer

Imagine a 25-person plastics injection molding shop. A defective shot is pulled from the press at 2:15 in the afternoon. The cosmetic finish is wrong. The operator's first instinct is to clear the part, blame the material lot, and keep running. The shift lead intervenes and runs a five whys at the press.

Why was the shot defective? The mold surface temperature was off spec. Why? The chiller is cycling too widely. Why? The chiller's set point was changed last week. Why? Maintenance adjusted it during preventive work. Why? The chiller setting is not in the press setup standard work, and there is no log entry for the maintenance change. Root cause: the setup standard and the maintenance log have a gap. The countermeasure is a one-line update to the press setup sheet and a standing rule that any maintenance change is logged at the press. Cost: fifteen minutes of writing.

That is five whys at small scale. No software, no analysis, no consultant. A discipline of refusing to stop at the obvious answer and a willingness to keep walking the chain until the cause is something the shop can change.

Common mistakes with five whys

• Stopping at the person. "Operator made a mistake" is a symptom. The cause is the standard or design that allowed the mistake. Keep asking.
• Forcing exactly five questions. The number is a guideline. Some roots appear at three, some at seven. The signal is the answer being systemic, not the count of whys.
• Doing it from a desk. Memory loses detail in hours. Five whys belongs on the floor, near the occurrence, with the people involved.
• Following only one chain. Some problems have two real causes. If the team senses a fork, follow both branches to their roots.
• No written record. A five whys done verbally is invisible the next time the same problem appears. Write the chain on one sheet and pin it where the team meets.

Five whys and related Lean tools

Five whys is the depth-first tool inside root cause analysis, complementary to the breadth-first fishbone diagram. Most well-built A3 sheets carry a five whys chain in the analysis section. The deepest root identified by five whys is paired with a countermeasure, the lean term for an action that targets the cause directly rather than the symptom.