State the problem precisely before asking the first why

A vague problem statement produces vague root causes — be specific about what happened.

Why it works

The Five Whys chain is only as useful as its starting point. A problem stated as "things went wrong" or "quality was poor" can be explained by almost anything, so the first "why" branches in dozens of directions and the chain never converges. A precise problem statement — "the third weld in batch 47 failed at the seam, not the joint" — constrains the why-chain to the specific causal path relevant to this failure. Precision at the start is the investment that makes the rest of the analysis tractable.

How to do it

1. Describe the problem as specifically as possible: what failed, where, when, under what conditions?
2. Include what did NOT fail — this narrows the cause space.
3. Avoid evaluative language ("it was bad") — stick to observable facts.
4. If you are not sure of the precise facts, gather them before starting the why-chain.

Evidence

Problem specification is a foundational step in all formal root-cause analysis methods (FMEA, fault tree analysis, Ishikawa diagrams). Toyota’s own accounts of the Five Whys emphasize precise problem observation as the prerequisite. (mechanistic)

Precise specification is harder than it sounds in complex sociotechnical systems where the boundary of "the problem" is itself contested.

Sources

• Ohno (1988), Toyota Production System — problem specification as prerequisite to root cause analysis

Common mistake

Starting with a problem statement that is already a conclusion ("the process is inefficient") rather than an observation ("task X took 4 hours instead of 1"), which makes the first "why" circular.