5W1H Method: Problem Definition for Root Cause Analysis

The 5W1H method is the structured problem definition framework that answers six questions (Who, What, Where, When, Why, and How) before root cause investigation begins, ensuring that the investigation team works from a precise, factual problem statement rather than from assumptions, verbal descriptions, or incomplete recollections that distort the investigation before it starts. Also called the Kipling Method after Rudyard Kipling's 1902 poem in Just So Stories ("I keep six honest serving-men, they taught me all I knew; their names are What and Why and When and How and Where and Who"), the framework has been applied across journalism, investigation, project management, and quality problem solving for over a century. In lean manufacturing, 5W1H is the standard problem definition tool used at the start of any root cause analysis before the investigation team selects an analysis method and begins forming hypotheses about causes.

Taiichi Ohno, the architect of the Toyota Production System, made a distinction that remains operationally important in lean manufacturing: 5W1H defines the problem, and the 5 Whys investigate its cause. These are two different activities performed in sequence, not interchangeably. A team that skips 5W1H and proceeds directly to asking why encounters the most common RCA failure mode: the investigation team investigating different versions of the problem because no shared, precise definition was established before analysis began.

Why Problem Definition Comes Before Root Cause Investigation

The quality of a root cause analysis is determined at the problem definition stage, not during the investigation itself. An investigation that begins with a vague problem statement produces a vague root cause conclusion, which produces a corrective action that addresses the most plausible interpretation of the problem rather than the actual condition generating it.

Three failure modes in RCA investigations trace directly to inadequate problem definition.

Investigation scope drift. Without a specific problem statement defining what is and is not included in the investigation, the scope expands as different team members bring different interpretations of the problem to the analysis. The team spends its resources investigating a broader category of issues than the specific failure that triggered the investigation, producing a root cause that is too general to support a specific corrective action.

Assumption-based hypotheses. When the problem is defined verbally rather than factually, team members fill the information gaps with assumptions based on their experience and prior beliefs. The investigation then confirms the most senior person's assumption rather than identifying the actual root cause. [What is Root Cause Analysis in Lean Manufacturing?] identifies this assumption-based hypothesis selection as one of the five most consistent RCA failure modes across manufacturing environments.

Mismatched corrective actions. A corrective action designed to address a poorly defined problem may solve the problem as the team understood it while leaving the actual problem unchanged. The defect recurs, and the team repeats the investigation cycle.

5W1H breaks this pattern by requiring the investigation team to document specific, factual answers to six defined questions before any hypothesis is formed. The discipline of answering each question with verifiable data rather than opinion is what makes the framework valuable.

Key Insight: A root cause investigation is only as precise as the problem statement that initiates it. 5W1H produces the problem statement; the RCA tool investigates its cause.

The Six Questions: What Each Reveals

The six 5W1H questions each probe a distinct dimension of the problem. Together they produce a complete situational picture that defines the investigation scope, identifies stakeholders, establishes the timeline, and quantifies the impact before any causal analysis begins.

What: Defining the Defect with Specificity

The What question defines the specific defect or failure with factual, measurable terms. It must describe the observable characteristic that is failing to meet specification, the specific product or component affected, and the standard or requirement not being met.

Manufacturing What questions:

What specific defect is occurring? ("cracking at the weld joint on Part #HF-901, failing tensile strength test at 2.3 kN against a 3.5 kN specification")
What product, part number, and revision level is affected?
What quality standard or specification is not being met?

The What answer sets the investigation boundary. A What answer of "quality problems" is not a problem definition. "Hydraulic tube flares on Part #HF-901 cracking at the forming stage, producing a 15 percent field failure rate" is a problem definition.

Who: Identifying the Human Dimension

The Who question identifies the people involved in or affected by the problem, not to assign blame, but to understand the full human picture of the failure and identify who must be involved in the investigation.

Manufacturing Who questions:

Who discovered the problem and at what stage?
Who was operating the process when the failure first appeared?
Who is responsible for the affected process and must be part of the investigation team?
Who is the customer or downstream function affected by the defect?

The Who answer identifies which functions must have representation in the RCA team and which operators or supervisors hold the most relevant firsthand knowledge of the conditions at the time of the failure.

Where: Locating the Failure Precisely

The Where question pinpoints the physical location of the defect, covering both where in the production system it is generated and where on the product it appears.

Manufacturing Where questions:

Where in the facility does the failure occur: which line, workstation, machine, or cell?
Where on the product does the defect appear: which surface, dimension, joint, or interface?
Where in the process sequence is the defect first detectable?
Where is the defect escaping to: is it caught internally or reaching the customer?

The Where answer frequently provides the most discriminating investigation clue. A defect occurring only at Workstation 3 on Line B immediately focuses investigation on whatever is distinctive about that workstation, eliminating all other locations from the investigation scope before a single hypothesis is formed. This location-based elimination is the overlap point with [Is/Is Not Analysis: Problem Definition for Root Cause Analysis], which formalizes the contrast between where the defect occurs and where it does not.

When: Establishing the Timeline

The When question establishes the temporal context of the failure, covering when it first appeared, how its frequency has changed over time, and whether it correlates with any specific event.

Manufacturing When questions:

When did the problem first appear: which date, shift, or production run?
When during the production cycle does it occur: startup, steady state, changeover, end of run?
When was the last confirmed period of conforming production?
Does the frequency change at specific times: end of shift, after material lot changes, during high-volume production runs?

The When answer often reveals the triggering event. If defects began appearing three weeks ago and a new hydraulic press was installed three weeks ago, the timeline correlation is not proof of causation but is a strong investigative signal that directs attention to the installation and its effects on the process. The point where conforming production becomes non-conforming is frequently where the root cause investigation should focus first.

Why: Framing the Problem Significance

In 5W1H as a problem definition tool, the Why question asks why the failure is a problem, specifically what the business, quality, safety, or customer consequence of the defect is, distinct from the Why in 5 Whys analysis which investigates the causal chain.

Manufacturing Why questions:

Why does this failure matter: what is the business or customer consequence?
Why has this been escalated to formal RCA rather than handled informally?
Why is immediate corrective action required rather than monitoring?

The Why answer in 5W1H defines the stakes of the investigation and establishes the business justification for the investigation resources being committed. It confirms that the problem meets the threshold for formal RCA rather than informal resolution at the team level.

How: Quantifying Extent and Mechanism

The How question addresses both how the failure occurs mechanically and how large the problem is in terms of quantity, cost, and production impact.

Manufacturing How questions:

How did the failure occur: what is the mechanism of the defect?
How many units are affected and over what production period?
How was the failure detected: at what stage and by what method?
How much is the failure costing in scrap, rework, warranty, or production disruption?

The How answer quantifies the impact and provides the baseline against which corrective action effectiveness will be measured. Without a How baseline, the Check phase of PDCA cannot confirm whether the corrective action reduced the defect rate to an acceptable level.

Key Insight: The six questions cover complementary dimensions of the problem. Missing any one of them leaves an information gap that the investigation team fills with assumptions rather than facts.

5W1H in Manufacturing: A Worked Example

The hydraulic fitting failure below demonstrates how 5W1H produces a precise problem statement from an initial vague complaint.

Initial report: "We are getting customer complaints about leaking hydraulic fittings."

5W1H problem definition:

What: The flare on the end of hydraulic tube Part #HF-901 is cracking at the forming stage. The defect produces a slow leak after final assembly, failing pressure test specifications. Field failure rate is 15 percent over the past three weeks, generating warranty claim cost of approximately $45,000.

Who: The defect is being generated by the hydraulic press operators at Station 4. Final inspection is not detecting it before shipment. Customer service is receiving the complaints and the quality manager has escalated for formal RCA.

Where: The defect originates at Station 4 during flare forming. It is not detectable at final visual inspection and is only revealing itself after the product is installed and pressurized in the field.

When: The problem first appeared three weeks ago on the second shift, corresponding to the installation of a new hydraulic press at Station 4. No defects of this type were recorded in the 90 days prior to the machine installation.

Why: The defect is compromising structural integrity and producing field failures that create safety risk and significant warranty liability. The 15 percent field failure rate exceeds the quality threshold for informal management and requires formal root cause investigation.

How: The flare is cracking during the forming operation due to inconsistent press pressure. The mechanism has not yet been confirmed. That is the subject of the root cause investigation. Approximately 340 affected units have been shipped in the past three weeks, all requiring field inspection.

This completed 5W1H statement provides a precise, bounded problem definition that any investigation tool can work from.

Key Insight: A complete 5W1H statement produced from this example replaced a four-word complaint with a fully defined, bounded investigation scope. Every piece of information in it is verifiable and specific.

5W1H vs 5 Whys: The Critical Distinction

The most common misuse of 5W1H in manufacturing is treating the Why question as the start of root cause investigation rather than as a problem framing question. Taiichi Ohno's distinction is the correct operating model: 5W1H defines the problem, and [What is the 5 Whys Root Cause Analysis Method?] investigates its cause.

The two tools operate at different stages of the investigation and serve different purposes:

5W1H is applied before investigation begins. It produces the factual problem statement that the investigation team agrees on before any analysis starts. The Why question in 5W1H asks why this is a problem, not what caused it.

The 5 Whys is applied after 5W1H is complete. It begins with the precisely defined problem statement produced by 5W1H and asks why the problem occurred, then why about that answer, iterating until the systemic root cause is reached.

Applying 5 Whys before completing 5W1H produces a causal investigation of a vaguely defined problem. The root cause identified may be accurate for the problem as one team member understands it and incorrect for the problem as another member understands it. The 5W1H definition eliminates this divergence before it contaminates the investigation.

Key Insight: 5W1H defines what the problem is. 5 Whys investigates why it is occurring. Applying 5 Whys without 5W1H investigates a problem that has not been precisely defined.

5W1H in the RCA Tool Ecosystem

5W1H integrates with every RCA tool in the lean manufacturing problem-solving toolkit as the mandatory first step that precedes tool selection and application.

In [8D Problem Solving: The Eight Disciplines Method for Manufacturing], 5W1H provides the structure for D2 (problem description), the discipline that defines the problem with sufficient precision to direct the D4 root cause investigation. A well-completed D2 using 5W1H is the foundation of an effective 8D investigation.

In [Is/Is Not Analysis: Problem Definition for Root Cause Analysis], the 5W1H dimensions of What, Where, and When map directly to the Is/Is Not framework's four dimensions. 5W1H gathers the full informational picture; Is/Is Not then extracts the contrasts within that picture that eliminate causal hypotheses. The two tools are sequential and complementary: 5W1H first, Is/Is Not second where the failure pattern warrants contrast-based narrowing.

In [Fishbone Diagram: A Root Cause Analysis Visual Tool] sessions, the completed 5W1H statement is the problem placed at the head of the fishbone. The specificity of the problem statement determines how focused and productive the brainstorming session is. A vague problem at the fishbone head generates vague causes across the six bones.

In [Pareto Analysis in Manufacturing: Applying the 80/20 Rule to Problem Solving], 5W1H answers clarify which defect category is being analyzed, what time period the data covers, and which production location the chart represents. Without these boundaries, a Pareto chart may combine data across different problem types and locations, producing a priority ranking that reflects mixed data rather than a coherent defect distribution.

Key Insight: 5W1H is not an alternative to other RCA tools. It is the prerequisite step that precedes every other tool in the toolkit.

Within the Lean System

Connection to Lean Principles

5W1H operationalizes the lean principle of genchi genbutsu , go and see for yourself by requiring that the problem definition be built from direct observation and factual evidence rather than from second-hand reports and assumptions. Every answer in the 5W1H framework should be verified at the gemba rather than constructed in a conference room. [Gemba Walks vs Audits: Key Differences Explained] describes the observation discipline that produces the accurate What, Where, and When answers that 5W1H requires. A 5W1H completed from memory and verbal reports is less reliable than one completed from direct observation of the failure at the point where it occurs.

Connection to Lean Tools

5W1H feeds directly into the full lean RCA toolkit. [What is Root Cause Analysis in Lean Manufacturing?] positions 5W1H as the problem definition step that precedes every investigation tool. [The 6Ms of Production: A Complete Manufacturing Guide] categories (Man, Machine, Method, Material, Measurement, Mother Nature) serve as the investigative framework that 5W1H answers point toward: the Where and When answers frequently indicate which of the six domains is most likely to contain the root cause, directing the fishbone brainstorming effort before the session begins.

Connection to Continuous Improvement

5W1H connects to the [PDCA Cycle: The Foundation of Continuous Improvement] as the problem definition discipline of the Plan phase. A PDCA cycle that begins without a completed 5W1H statement is planning against an imprecise problem, which produces an imprecise plan and an imprecise corrective action. The How question in 5W1H, which quantifies the defect rate and its financial impact, provides the baseline that the Check phase measures against to confirm that the corrective action achieved its intended improvement.

Frequently Asked Questions

What is the 5W1H method in manufacturing? The 5W1H method is the structured problem definition framework that answers six questions before root cause investigation begins: Who is involved, What specifically is failing, Where the failure occurs, When it first appeared, Why it matters, and How it occurs and at what scale. Also called the Kipling Method, it ensures that the investigation team works from a precise factual problem statement rather than assumptions. In lean manufacturing, it is the standard first step in any root cause analysis process.

What is the difference between 5W1H and 5 Whys? 5W1H is a problem definition tool used before investigation begins. It answers what the problem is, who is involved, where and when it occurs, why it matters, and how it happens and at what scale. The 5 Whys is a root cause investigation tool used after 5W1H is complete. It begins with the precisely defined problem statement from 5W1H and iteratively asks why the problem occurred until the systemic root cause is identified. Taiichi Ohno described this distinction clearly: 5W1H defines the problem, 5 Whys investigates its cause.

What are the six 5W1H questions? The six questions are What (what specific defect or failure is occurring and what specification is not met), Who (who discovered it, who was operating the process, who is affected), Where (where in the facility and on the product the failure appears), When (when it first appeared, when during the production cycle, what changed at that time), Why (why this failure is a significant problem requiring formal investigation), and How (how the failure occurs mechanically and how many units and how much cost is involved).

How does 5W1H connect to the 8D problem solving process? In 8D problem solving, 5W1H provides the structure for D2, the problem description discipline that defines the failure with sufficient specificity to direct the D4 root cause investigation. A complete 5W1H completed in D2 gives the investigation team a shared, precise, factual problem definition before any root cause hypothesis is formed. D4 root cause analysis is only as focused as the D2 problem description that precedes it.

When should 5W1H be used in manufacturing? 5W1H should be used at the start of any root cause investigation before the investigation team selects an analysis tool or begins forming hypotheses. It is the mandatory first step preceding the 5 Whys, fishbone diagram, Is/Is Not analysis, and 8D. It is also used in problem reporting, non-conformance documentation, and escalation to management to ensure that the problem is communicated with specificity rather than in general terms.