How to Facilitate a 5-Why With Supervisors Who Hate It

Supervisors hate 5-whys for a good reason. Most of the ones they have sat through were either a 90-minute conference room exercise that ended in "operator error," or a form somebody filled in alone at a desk to satisfy quality. Neither one fixed anything. So when you say "let's do a quick 5-why on that," what they hear is "let's spend an hour deciding whose fault it was." Good 5 why facilitation is mostly about proving that wrong in the first five minutes.

Here is how to run one standing at the machine, in 15 minutes, with the supervisor and the operator, without anyone getting blamed.

Set it up in 60 seconds

Do it at the machine, not in an office. Do it the same shift the problem happened, or the next morning at the latest. Bring the part if there is one.

Say out loud, before the first question: "We are looking for what in the process let this happen. Nobody is in trouble." Say it every time, even with people who have heard it before. The supervisor has been burned by one of these and needs to hear it again.

Then state the concern as a fact, no diagnosis. "Twelve parts on the 3:00 hour had the bore 0.02 mm oversize." Not "the operator ran oversize parts." The wording of the first line decides whether the next 14 minutes are about a process or a person.

The two questions that keep it on process

Every "why" answer will drift toward a person, because a person is the easiest thing to point at. Two questions pull it back.

"What would have had to be true for that not to happen?" When the answer to a why is "he didn't check the offset," ask this. The answer comes back as "the offset check would have to be on the setup sheet" or "the first-piece gauge would have to be at the machine." Now you are talking about the setup sheet and the gauge, not about him.

"Would a different, competent person on that machine have done the same thing?" If the honest answer is yes, the process is broken, it is not an operator issue. If the answer is no, you still do not stop at the person. You ask why the process depends on one particular person knowing something.

Use these whenever you hear a name, "careless," "should have," or "always does that." Those words are the signal that the chain has left the process and started walking toward somebody.

When to stop before why number five

Five is not a rule. It is a reminder that the first answer is never the root. Stop when you hit something you can change this week and that would have prevented the concern. Sometimes that is why number three. Sometimes it is why number seven.

You have gone too far when the answer is "because we don't have enough people" or "because the customer wants it cheap." Those may be true and you cannot fix them by Thursday. Back up one step to the last thing you can change.

You have not gone far enough if the countermeasure is "retrain" or "remind everyone." Those are not countermeasures, they are a second copy of the problem waiting to happen. Keep asking.

A worked example on a machining defect

Concern: 12 parts with the bore 0.02 mm oversize, found at final inspection, 3:00 hour, station 9.

Why were they oversize? The boring bar offset was 0.02 mm too large after a tool change.

Why was the offset wrong? The operator entered the measured value from the presetter ticket, but the ticket in the tray was from the previous insert. The old one had never been thrown away.

Here the supervisor says "he grabbed the wrong ticket." You ask: what would have had to be true for that not to happen? Answer: the presetter ticket would have to be attached to the tool holder, not left loose in a tray.

Why are tickets left in the tray? Because the presetter prints them loose and there is nowhere on the holder to clip them.

Why did nobody catch it on the first piece? Because the setup sheet says "verify bore" with no gauge named, and the bore gauge lives at inspection, 40 feet away. Operators eyeball it or skip it.

Stop there. That is why number four and you have two things you can change this week: a clip on the tool holder for the presetter ticket, and a bore gauge staged at station 9 with "measure bore, first piece after tool change" on the sheet. The countermeasure goes on a 3C with the supervisor's name and a date; the free 3C form has a line for each. Total time, standing at the machine: about 12 minutes.

Notice what did not happen. Nobody said "operator error." The operator is standing right there and just told you where the gauge is kept, which is the single most useful fact in the whole chain.

Getting supervisors to stop hating it

Run the first three yourself and keep each under 15 minutes. Close every one with a change that is visible on the floor within a week. After that, hand the facilitation to the supervisor and stand at the back.

What changes their mind is not the method. It is watching one of these end with a clip and a gauge instead of a lecture, and then watching the defect not come back. Write the chain on the board next to the red box that started it, in pen, five lines, so the whole cell can see how it ended.

If you want to see what this looks like when the 5-why sits in the A3 for that problem, next to the cell's trend for the metric that went red, the demo runs on sample data, no signup needed: Try the live demo →