5 Whys Analysis in Small and Medium Manufacturing Enterprises - Excellence in Quality

Introduction

5 Whys 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 "5 Whys is too simple and ineffective," or they blindly adopt the complex analysis frameworks used by large enterprises, ultimately "failing to identify the root cause and find effective solutions." In reality, the essence of 5 Whys is "digging deep to find the root cause," and SMEs do not need to insist on "asking exactly 5 times." Instead, they should master the "minimalist application method" to avoid surface-level causes and find implementable solutions.

This article combines practical experience from guiding over 20 SMEs in applying 5 Whys, breaking down the minimalist application method tailored for SMEs. It includes 3 real cases and 1 universal template, all of which can be implemented by team leaders without specialized knowledge.

Core Principles

Key Principles

Three key principles for 5 Whys application in SMEs:

1. Avoid Hypothetical Questions: Focus on actual problems on the shop floor, not abstract management discussions.
2. Stop at Implementable Causes: Identify root causes that can be resolved with simple measures; no need to ask 5 times if the root cause is found.
3. Be Pragmatic: Each answer must be based on objective facts, not subjective assumptions.

Step-by-Step Minimalist Application of 5 Whys (SME Adapted Version)

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

The first step in 5 Whys analysis is to "clarify the problem" — the most common mistake in SMEs is "vague problem descriptions" (e.g., "poor product quality," "low efficiency"), which can lead to misguided analysis.

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

   • ❌ Incorrect Description: The machine often stops.
   • ✅ Correct Description: In the assembly workshop, Line A, Machine #3, the drilling machine stopped 10 times this week, with an average downtime of 15 minutes each time, mainly occurring after 10 AM.

2. On-Site Verification: After defining the problem, verify it on-site (e.g., check the downtime records, ask the operators) to avoid "describing problems based on memory from the office."

Practical Tip

Use the "simplified 5W1H" to describe the problem: What (the issue), Where (location), When (time), How many (frequency/impact). Avoid focusing on Who (responsibility) to prevent 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 when you reach a level where the cause can be resolved with simple measures; you don't need to ask exactly 5 times.

1. Questioning Logic: Move from "surface phenomena" to "root cause," for example (using the "drilling machine downtime" issue):

   • Why1: Why did Machine #3 stop 10 times this week? → Answer: The drill bit broke, causing downtime.
   • Why2: Why did the drill bit break frequently? → Answer: The drill bit was used beyond its specified lifespan.
   • Why3: Why was the drill bit used beyond its lifespan? → Answer: The workshop did not record the drill bit replacement times, relying solely on the operator's experience.
   • Why4: Why were the drill bit replacement times not recorded? → Answer: There was no "drill bit replacement record form" and no supervision.
   • (At this point, the root cause has been identified, so there's no need to ask the 5th why.)

2. Pitfall Avoidance:

   • ❌ Avoid Subjective Guesses: For example, "Why did the drill bit break? → The operator did not handle it properly" (no evidence).
   • ❌ Avoid Blame-Shifting: For example, "Why were the times not recorded? → The employees were lazy" (did not address management issues).
   • ✅ Insist on Objective Facts: Each answer should be supported by on-site data/evidence.

Step 3: Develop Solutions, Focus on Implementability (10 minutes)

The ultimate goal of 5 Whys analysis is to "solve the problem." Solutions in SMEs must be "low-cost and easy to implement," avoiding "vague and unimplementable solutions."

1. Solution Development Principles: Develop solutions based on the root cause and ensure they meet "who, what, when," for example:

   • Root Cause: No drill bit replacement record form, no supervision.
   • Solution 1: The team leader will create a "drill bit replacement record form" within 1 day, post it next to the machine, and have the operator fill it out after each replacement.
   • Solution 2: The quality inspector will check the record form before the end of each shift to ensure that drill bits beyond their lifespan are replaced promptly.
   • Solution 3: The warehouse will stock sufficient commonly used drill bits to avoid shortages that lead to overuse.

2. Avoid Vague Solutions:

   • ❌ Vague Solutions: Improve equipment management, enhance employee responsibility.
   • ✅ Specific Solutions: Create a record form, designate a checker, and ensure adequate spare parts.

Step 4: Verify Effectiveness, Standardize (1 week)

SMEs often "let solutions fade away after implementation." It is essential to verify the effectiveness through data and standardize successful solutions to prevent recurring issues.

1. Effectiveness Verification: After implementing the solution, track key data (e.g., downtime frequency of the drilling machine), for example:

   • Before Implementation: 10 stoppages this week.
   • After Implementation: 1 stoppage next week (due to an unexpected fault), achieving the expected results.

2. Standardization: Incorporate the "drill bit replacement record form" into the workshop's on-site management standards, requiring all replaceable parts of equipment to be recorded in this manner.

5 Whys Minimalist Template (SME Specific)

5 Whys Analysis Minimalist Template (SME Specific)

Problem Description (object + phenomenon + data): ________________________

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

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

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

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

Root Cause: ________________________

Specific Solutions (who + what + when): ________________________

Effectiveness Verification (data comparison): ________________________

Real Cases: Practical Application of 5 Whys in SMEs

Case 1: Dimensional Deviation in a Hardware Factory

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

5 Whys Analysis:

• Why1: Why did the washer dimensions deviate? → The stamping die positioning was loose.
• Why2: Why was the die positioning loose? → The die's securing screws were not checked regularly.
• Why3: Why were the screws not checked regularly? → There was no daily inspection form for the die, and the operators were unaware of the need to check.

Root Cause: No daily inspection form for the die, lack of inspection requirements.

Specific Solutions:

1. The technician will create a "daily die inspection form" within 1 day, including the inspection of securing screws, and post it next to the machine.
2. The operator will inspect the die once before each shift, and the team leader will conduct random checks daily.
3. Effect: After 1 week, the nonconformity rate dropped to 2%, meeting the standard.

Case 2: Packaging Damage in an Electronics Factory

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

5 Whys Analysis:

• Why1: Why did the packaging damage occur? → The cardboard boxes were too thin and deformed during transportation.
• Why2: Why were thinner boxes used? → The purchasing department switched to a thinner cardboard box supplier to save costs.
• Why3: Why was the supplier change not evaluated? → The purchasing department did not require quality department approval for supplier changes.

Root Cause: No quality review process for supplier changes.

Specific Solutions:

1. The purchasing department will immediately switch back to the original supplier's cardboard boxes, completing the change within 1 day.
2. Develop a "packaging material supplier change review process," requiring quality department testing before any changes.
3. Effect: The following month, the packaging damage rate dropped to 0.5%.

Case 3: Screw Omission in an Assembly Factory

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

5 Whys Analysis:

• Why1: Why were screws omitted? → The assembler forgot to install them, and the inspector did not detect the omission.
• Why2: Why did the assembler forget to install them? → There was no work instruction for the assembly process, relying solely on experience.
• Why3: Why was there no work instruction? → The workshop believed that "the process was simple and did not require a work instruction."

Root Cause: No work instruction for core processes, lack of standardized operations.

Specific Solutions:

1. The technician will compile a "motor assembly work instruction" within 2 days, clearly outlining the steps and number of screws to be installed.
2. The inspector will check each item according to the work instruction and fill out the "finished goods inspection record form."
3. Effect: No further screw omission issues occurred.

Core Considerations for 5 Whys Application in SMEs

1. Avoid Dogmatic Pursuit of "5 Questions": Stop when you find a root cause that can be resolved with simple measures, such as in the cases where 3 questions were sufficient.
2. Avoid Blame, Focus on Causes: Don't ask "who's fault it is," but rather "why it happened," to avoid employee resistance and focus on problem-solving.
3. On-Site Questioning, Not Office Analysis: Conduct questioning at the production site, using physical items and data, to avoid "armchair analysis."
4. Solutions Must Be "Small and Specific": Avoid broad, unimplementable solutions like "improving the system" or "enhancing training"; be specific about "who does what and when."
5. Involve All Employees, Not Just Quality Departments: Engage operators and team leaders in 5 Whys analysis, as they are most familiar with the shop floor and can identify the most genuine causes.

Conclusion: Core Logic of 5 Whys Application in SMEs

The core of applying 5 Whys in SMEs is not "mastering a complex analysis framework" but "using the simplest method to find the root cause and develop implementable solutions." Remember: 5 Whys is "a thinking habit," not "a complex tool" — as long as you "describe the problem clearly, base questions on facts, and focus on implementable solutions," you can solve 80% of on-site quality issues even with just 3 questions.

For SMEs, the value of a tool lies not in its complexity but in its usability and effectiveness. The minimalist application of 5 Whys aligns perfectly with the "flexible, practical, and low-cost" characteristics of SMEs, making it the "best value" for solving on-site problems.

If you encounter issues such as "not finding the root cause" or "difficulty in implementing solutions" during the 5 Whys process, feel free to reach out for discussion and together we can find solutions suitable for SMEs.

[Return to Article List]