5W2H

5W2H is the lean tool that prevents most of the wasted motion in problem-solving sessions. Without a scoped problem statement, teams jump to causes and countermeasures based on whoever is loudest in the room, and three weeks later the same problem is still happening. 5W2H slows the team down at the start. Seven questions, answered specifically and in writing, produce a problem statement sharp enough that the cause analysis afterwards is fast and the countermeasures actually target the right thing. The framework is older than lean and shows up in journalism, military doctrine, and engineering, but it remains underused on the shop floor.

"Most problems are not solved badly. They are scoped badly. Fix the scoping and the solving gets easier."

How 5W2H works

The seven questions are simple. The discipline is in answering each one specifically and in writing:

• Who. Who is affected, who is involved, who is responsible at each step.
• What. What exactly is happening, what is the deviation from the expected outcome, what does the defect look like.
• Where. Where in the process, where on the part, where in the shop, which shift.
• When. When does it occur, what time of day, what day of week, what point in the production cycle. Patterns matter.
• Why. Why is this a problem now, what is the impact on the customer or the operation. Not the root cause yet, just why it deserves attention.
• How. What mechanism can we observe. Not the root cause, but what we can see about how the failure unfolds.
• How Much. Cost, frequency, magnitude. The dollar number, the number of occurrences, the percentage of throughput affected.

The framework is best used in the first 20 to 30 minutes of a problem-solving session, with the team standing at a whiteboard. Each answer goes up in plain writing. The answers do not need to be polished. They need to be specific enough that anyone reading them later can picture the problem.

The output is a tightened problem statement, often a single paragraph, that names the problem in concrete terms. That problem statement is the input to whatever comes next: a five whys investigation, a fishbone diagram session, or an A3 draft.

Where 5W2H fits on the shop floor of a small manufacturer

Imagine a 22-person plastics injection molding shop where a particular cosmetic defect has been recurring on one product family for three months. Every meeting about it has ended with the team agreeing to "watch it more carefully" and nothing changes. The shift lead suggests a 5W2H session before the next problem-solving meeting.

Twenty-five minutes at the whiteboard scopes the problem sharply. Who: the defect appears regardless of operator, on both shifts. What: a specific sink mark in one corner of the housing, visible to the eye, no functional impact but customer-rejected. Where: same corner of the same part on press number two only. When: the first 30 minutes of every shift, almost never after that. Why: 800 dollars per occurrence in scrap, four occurrences a week. How: the corner cools differently than the rest of the part. How much: about 13,000 dollars a quarter.

The scoped problem leads the team toward a thermal-stability check on press number two during startup. A 25-minute 5W2H session turned a recurring complaint into a specific, attackable problem. The countermeasure work that followed took two weeks. Without the 5W2H, the same conversation would have repeated for another quarter.

Common mistakes with 5W2H

• Rushing the framework. 5W2H is supposed to slow you down. Skipping it to get to solutions costs the savings the next time the same problem reappears.
• One-line answers. Specificity is the point. "Where: the welding station" is not enough. "Where: the upper-left corner of the housing, the second pass, on shift B only" is.
• Not writing it down. A 5W2H done verbally is gone by Friday. Write the answers on a whiteboard or one-page sheet so the next person can use them.
• Forcing each question to apply. Not every question yields a useful answer for every problem. Move on rather than fabricate.
• Using 5W2H without follow-through. The scoping is the input to the next step. Without that step, 5W2H is just a meeting.

5W2H and related Lean tools

5W2H is a scoping framework that frequently precedes a five whys root cause investigation, since a sharper problem statement makes the why chain sharper. It is one of the discipline-of-thinking tools that supports root cause analysis broadly. The scoped output most often lands in the background or current-state sections of an A3. For team-led cause mapping after scoping, a fishbone diagram is the natural next tool.