Simplified Application of 5Why Analysis in Small and Medium Manufacturing Enterprises - Quality Excellence

By: QTank Published: 4/17/2026 Views: 349

Current rating: ★★★☆☆ Rate this Equivalent to 8 ratings

5Why analysis is one of the core tools for solving quality issues, but small and medium manufacturing enterprises (SMEs) often fall into two extremes when using it: either they think "5Why is too simple and ineffective," or they copy the complex analysis frameworks of large enterprises, ultimately "failing to identify the root cause and find effective solutions." In reality, the essence of 5Why is "digging deep to find the root cause," and SMEs do not need to insist on "asking exactly five times." Instead, they should master the "simplified application method" to avoid surface-level causes and find actionable solutions.

This article, based on practical experience in guiding over 20 SMEs in applying 5Why, breaks down the "SME-specific" simplified 5Why application method. It includes three real cases and one general template, all of which can be implemented by team leaders without specialized knowledge.

Core Principles

Three core principles for 5Why application in SMEs: ① No abstract questions: only ask about actual problems on-site, not about management in general; ② Focus on actionable solutions: the root cause identified must be solvable through simple measures; ③ No rigid adherence: stop once the root cause is found, no need to ask exactly five times.

1. Simplified Application Steps of 5Why Analysis (SME Adapted Version)

Step 1: Clarify the Specific Problem, Avoid Vagueness (5 minutes)

The first step in 5Why analysis is to "clearly define the problem" — the most common mistake in SMEs is "vague problem descriptions" (such as "poor product quality" or "low efficiency"), which can lead to subsequent analysis going off track.

1. Three Elements of Problem Description: must include "object + phenomenon + data," for example:

❌ Incorrect description: equipment often stops;
✅ Correct description: in the assembly workshop, line A, #3 drilling machine, there were 10 shutdowns this week, each lasting an average of 15 minutes, mainly occurring after 10 AM.

2. On-site Verification: after the problem description is completed, it must be verified on-site (such as checking shutdown records, asking operators) to avoid "describing problems based on memory from the office."

Practical Tips

Use the "simplified 5W1H" to describe the problem: What (what problem), Where (where it occurs), When (when it occurs), How many (how many times/impact), without focusing on Who (who is responsible) to avoid blame-shifting among employees.

Step 2: Layered Questioning, Identify the Root Cause (15 minutes)

Core rule: each "why" must be based on the previous answer, and the answer must be an "objective fact," not a "subjective guess." Stop questioning once you reach a level where the problem can be solved through simple measures, without necessarily asking five times.

1. Questioning Logic: from "surface phenomena" to "root cause," for example (using the "drilling machine shutdown" as an example):

Why1: Why did #3 drilling machine shut down 10 times this week? → Answer: the drill bit broke, causing the shutdown;
Why2: Why does the drill bit break frequently? → Answer: the drill bit is used beyond its specified lifespan;
Why3: Why is the drill bit used beyond its lifespan? → Answer: the workshop does not record the drill bit replacement time, relying solely on the operator's experience;
Why4: Why is the drill bit replacement time not recorded? → Answer: there is no "drill bit replacement record form" and no one supervises;
(At this point, the root cause has been identified, no need to ask a fifth time)

2. Key Points to Avoid Pitfalls:

❌ Avoid subjective guessing: e.g., "Why did the drill bit break? → The operator made a mistake" (no evidence);
❌ Avoid shifting blame: e.g., "Why is the time not recorded? → Employees are lazy" (not addressing management issues);
✅ Insist on objective facts: each answer must be supported by on-site data/evidence.

Step 3: Develop Countermeasures, Focus on Actionability (10 minutes)

The ultimate goal of 5Why analysis is to "solve the problem." Countermeasures in SMEs must be "low-cost and easy to implement," avoiding "vague and unactionable measures."

1. Countermeasure Development Principles: develop countermeasures based on the root cause, and ensure they meet "who will do it, what will be done, when it will be completed," for example:

Root cause: no drill bit replacement record form, no supervision;
Countermeasure 1: the team leader will develop the "drill bit replacement record form" within 1 day, post it next to the equipment, and have operators fill it out after each replacement;
Countermeasure 2: the quality inspector will check the record form at the end of each day to ensure that drill bits beyond their lifespan are replaced in a timely manner;
Countermeasure 3: the warehouse will stock sufficient commonly used drill bits to avoid shortages leading to overuse.

2. Avoid Vague Countermeasures:

❌ Vague countermeasure: strengthen equipment management, improve employee responsibility;
✅ Specific countermeasure: develop a record form, specify the person responsible for checks, and ensure adequate spare parts.

Step 4: Verify Effectiveness, Standardize (1 week)

SMEs often "let countermeasures go unverified," so it is essential to validate the effectiveness through data and standardize successful countermeasures to prevent recurring issues.

1. Effectiveness Verification: after implementing the countermeasures, collect key data (such as the number of drilling machine shutdowns), for example:

Before implementation: 10 shutdowns this week;
After implementation: 1 shutdown next week (due to a sudden fault), achieving the expected results;

2. Standardization: incorporate the "drill bit replacement record form" into the workshop's on-site management standards, requiring all equipment's wear-prone parts to be recorded for replacement times.

Simplified 5Why Analysis Template (SME Specific)

Problem Description (object + phenomenon + data):________________________

Why1: Why did this problem occur? → Answer:________________________

Why2: Why did the above situation occur? → Answer:________________________

Why3: Why did the above situation occur? → Answer:________________________

Why4: Why did the above situation occur? → Answer:________________________

Root Cause:________________________

Specific Countermeasures (who will do it + what will be done + when it will be completed):________________________

Effectiveness Verification (data comparison):________________________

2. Three Real Cases: Practical Application of 5Why in SMEs

Case 1: Dimensional Deviation Issue in a Hardware Factory

Problem Description: in the stamping workshop, line B, the φ10mm washers produced this week had a dimensional deviation nonconformance rate of 8%, exceeding the standard (≤3%).

5Why Analysis:

Why1: Why is there dimensional deviation in the washers? → The stamping die positioning is loose;

Why2: Why is the die positioning loose? → The die tightening screws are not checked regularly;

Why3: Why are the screws not checked regularly? → There is no daily die inspection form, and operators do not know they need to check;

Root Cause: no daily die inspection form, lack of inspection requirements.

Specific Countermeasures:

1. The technician will develop the "daily die inspection form" within 1 day, including the check for tightening screws, and post it next to the equipment;

2. Operators will perform a check once per shift before starting the machine, and the team leader will conduct random checks daily;

3. Effect: the nonconformance rate dropped to 2% after 1 week, meeting the standard.

Case 2: Packaging Damage Issue in an Electronics Factory

Problem Description: in the packaging workshop, the mobile phone chargers shipped this month had a packaging damage rate of 5%, leading to returns.

5Why Analysis:

Why1: Why is there packaging damage? → The cardboard boxes are too thin, causing deformation during transportation;

Why2: Why are thin cardboard boxes used? → The purchasing department changed to a thinner cardboard box supplier to save costs;

Why3: Why was the supplier change not evaluated? → The purchasing department does not require quality department approval for supplier changes;

Root Cause: no quality audit process for supplier changes.

Specific Countermeasures:

1. The purchasing department will immediately switch back to the original supplier's cardboard boxes, completing the change within 1 day;

2. Develop the "packaging material supplier change audit process," requiring quality department testing before any change;

3. Effect: the packaging damage rate dropped to 0.5% the following month.

Case 3: Screw Omission Issue in an Assembly Factory

Problem Description: in the assembly workshop, line C, 3 small motors produced this week were found to have missing fixing screws, which were then stored in the finished goods warehouse.

5Why Analysis:

Why1: Why are screws missing? → The assembly worker forgot to install them, and the inspector did not detect the issue;

Why2: Why did the worker forget to install them? → The assembly process lacks a work instruction, relying solely on experience;

Why3: Why is there no work instruction? → The workshop believes "the process is simple and does not require a work instruction";

Root Cause: core processes lack work instructions, resulting in a lack of standardized operations.

Specific Countermeasures:

1. The technician will compile the "motor assembly work instruction" within 2 days, clearly specifying the steps and quantity for screw installation;

2. Inspectors will check each item according to the work instruction and fill out the "finished product inspection record form";

3. Effect: no further screw omission issues occurred subsequently.

3. Core Considerations for 5Why Application in SMEs

1. No Rigid Adherence to "5 Questions": stop once you find a root cause that can be solved through simple measures, such as in the case where the root cause is found after 3 questions, without forcing 5 questions.

2. Avoid "Assigning Blame," Focus on "Identifying Causes": do not ask "who is at fault," but rather "why did it happen," to avoid employee resistance and focus on solving the problem.

3. On-site Questioning, Not Office Analysis: you must go to the production site to ask questions and gather data, avoiding "armchair analysis."

4. Countermeasures Must Be "Small and Specific": SMEs should not develop vague countermeasures like "improve the system, enhance training," but rather specific actions like "who will do what by when."

5. Involve All Employees, Not Just the Quality Department: involve operators and team leaders in the 5Why analysis, as they are most familiar with the site and can identify the most genuine causes.

4. Summary: Core Logic of 5Why Application in SMEs

The core of applying 5Why analysis in SMEs is not "mastering a complex analytical framework," but rather "using the simplest method to find the root cause and develop actionable countermeasures." Remember: the essence of 5Why is "a thinking habit," not "a complex tool" — as long as you adhere to "specific problem descriptions, fact-based questioning, and focused countermeasures," even asking just 3 times can solve 80% of on-site quality issues.

For SMEs, the value of a tool lies not in its "complexity," but in its "practicality and effectiveness." The simplified application of 5Why analysis perfectly aligns with the "flexible, pragmatic, low-cost" characteristics of SMEs, making it the "best value-for-money" solution for on-site problems.

If you encounter issues such as "unable to find the root cause" or "difficult to implement countermeasures" during the 5Why application process, feel free to contact us for discussion and together find solutions suitable for SMEs.

Return to Article List

Knowledge code: 5.2.3 Version: v20260417 Author: Quality Think Tank