The 5 Whys is a lean problem-solving method that repeatedly asks why something happened, using each answer as the next question, until the team reaches a cause it can control and change. These 5 whys examples in manufacturing show ten factory problems traced end to end, from the first symptom to the corrective action that actually stops it coming back.
The method came out of the Toyota Production System and gets used every day by quality managers, maintenance leads, production supervisors and improvement teams. You will meet the same pattern in all ten examples below: a measurable problem statement, five evidence-backed whys, a root cause somebody owns, and a fix that removes the cause instead of treating the symptom.
One caution before you start. A 5 Whys is fast, which is exactly why it goes wrong. Teams that pad the chain to hit five, or that stop the moment somebody says “operator error,” get a fix that fails. Read the corrective action line in each example, because that is where most factory problems get solved badly.
Table of Contents
- 5 Whys Examples in Manufacturing at a Glance The table below compares all ten scenarios by problem type, the root cause each one reaches, the evidence that supports the chain, and the corrective action it demonstrates. ScenarioProblem typeRoot cause reachedKey evidenceCorrective action Dimensional defectsQualityCavity wear past service limitFirst article reports, cavity shot-count recordsCavity maintenance interval by shot count Short shotsQualityHold pressure dropped after a no-load trialProcess log, mold temperature chartRecipe lock plus verified restart check Unexpected downtimeAvailabilityInterlock sensor failing intermittentlyMaintenance history, fault log, sensor readingsInterlock function test at each PM Supplier delaysDeliveryNo firm promise date in the planning systemPurchase order history, promise date fieldSupplier scorecard with firm date Transfer damageLogisticsContainer nested too deeply for handlingDamage photos, packing recordsContainer redesign and max fill standard Near missSafetyStandard work assumes a stable loadNear miss report, conveyor load dataLoad limit in standard work plus guard Changeover scrapScrapTrial parameters recorded only on paperSetup sheet, scrap by run, parameter historyRecipe parameter set before release Short-shipped kitWarehousePick face replenished without a count checkReplenishment log, kit build recordScan verification at replenishment Tool failureMaintenanceTool returned from storage without protectionMaintenance history, storage area auditProtected storage and return check ContaminationCustomer complaintCleaning step had no verified standardCustomer sample, cleaning record, change logDefined cleaning standard with sign-off 1. Recurring Dimensional Defects in a Plastic Part
- 2. Injection-Molding Short Shots
- 3. Repeated Unexpected Machine Downtime
- 4. Late Deliveries from a Critical Parts Supplier
- 5. Damaged Parts During Internal Transfer
- 6. A Packaging Line Near Miss
- 7. Excess Scrap After a Product Changeover
- 8. Missing Components in a Customer Kitting Order
- 9. Premature Failure of a Production Tool
- 10. Contamination Complaints from Finished Goods
- Frequently Asked Questions
- What are 5 Whys examples in manufacturing used for?
- How many Whys should a manufacturing investigation use?
- What is the difference between 5 Whys and root-cause analysis?
- Does the 5 Whys method work for equipment failures?
- How do you document and verify a 5 Whys conclusion?
- When is 5 Whys not the right problem-solving method?
- Conclusion
5 Whys Examples in Manufacturing at a Glance
The table below compares all ten scenarios by problem type, the root cause each one reaches, the evidence that supports the chain, and the corrective action it demonstrates.
| Scenario | Problem type | Root cause reached | Key evidence | Corrective action |
|---|---|---|---|---|
| Dimensional defects | Quality | Cavity wear past service limit | First article reports, cavity shot-count records | Cavity maintenance interval by shot count |
| Short shots | Quality | Hold pressure dropped after a no-load trial | Process log, mold temperature chart | Recipe lock plus verified restart check |
| Unexpected downtime | Availability | Interlock sensor failing intermittently | Maintenance history, fault log, sensor readings | Interlock function test at each PM |
| Supplier delays | Delivery | No firm promise date in the planning system | Purchase order history, promise date field | Supplier scorecard with firm date |
| Transfer damage | Logistics | Container nested too deeply for handling | Damage photos, packing records | Container redesign and max fill standard |
| Near miss | Safety | Standard work assumes a stable load | Near miss report, conveyor load data | Load limit in standard work plus guard |
| Changeover scrap | Scrap | Trial parameters recorded only on paper | Setup sheet, scrap by run, parameter history | Recipe parameter set before release |
| Short-shipped kit | Warehouse | Pick face replenished without a count check | Replenishment log, kit build record | Scan verification at replenishment |
| Tool failure | Maintenance | Tool returned from storage without protection | Maintenance history, storage area audit | Protected storage and return check |
| Contamination | Customer complaint | Cleaning step had no verified standard | Customer sample, cleaning record, change log | Defined cleaning standard with sign-off |
1. Recurring Dimensional Defects in a Plastic Part
A molded housing keeps failing inspection on one dimension, and the first instinct is to tighten the process window. The 5 Whys chain below shows why that rarely holds.
Problem: Bore diameter out of tolerance on 18 of 240 pieces across three consecutive runs.
Why 1: Why did parts fail inspection? Because the bore measured oversize on the go side.
Why 2: Why was the bore oversize? Because material was packing on the go side of the cavity.
Why 3: Why was material packing unevenly? Because the cavity core had worn past its service limit.
Why 4: Why had the cavity worn past service limit? Because nothing measured wear against shot count.
Why 5: Why did nothing measure wear? Because tool life was tracked by calendar, not by cycles run.
Root cause: No shot-count-based criterion for cavity maintenance.
Corrective action: Set a cavity service interval by shot count and add wear measurement to the tool room record.
Evidence used: First article inspection reports, cavity shot-count log, and the go-side wear measurement the team took before touching the process.
Verification: Re-run 30 shots on the rebuilt cavity and measure bore diameter at first article and again after 200 shots.
2. Injection-Molding Short Shots
Short shots come from resin that froze before it filled the cavity, and an operator parameter tweak rarely fixes it for long. Here the chain stays on process conditions instead.
Problem: Nine percent of a 1200-piece batch incomplete at the far end of flow.
Why 1: Why were parts incomplete? Because flow stopped short of the end of fill.
Why 2: Why did flow stop short? Because cavity pressure fell during the fill phase.
Why 3: Why did cavity pressure fall? Because hold pressure was lower than the standard value.
Why 4: Why was hold pressure low? Because the machine was restarted after a no-load trial that reset the recipe.
Why 5: Why did a no-load trial reset the recipe? Because parameters were edited at the machine panel with no verification step.
Root cause: Process parameters can be changed at the panel without a check against the approved recipe.
Corrective action: Lock parameters to the recipe and require a verified restart check before production release.
Evidence used: Machine process log for the batch, mold temperature chart, and the recipe history from the restart.
Verification: Confirm the pull shot after any restart and review three weeks of batch data for pressure variation.
3. Repeated Unexpected Machine Downtime
Machine downtime investigations fail when every stop is treated as the same fault. This chain separates a genuine failure from a reset that needed no repair at all.
Problem: Unplanned stops averaging 40 minutes a week over two months, no failed part recorded.
Why 1: Why did the machine stop? Because a door interlock signal dropped and the cycle halted.
Why 2: Why did the interlock drop? Because the sensor read inconsistently under vibration.
Why 3: Why did the sensor read inconsistently? Because its mounting bracket had loosened.
Why 4: Why had the bracket loosened? Because the sensor was checked visually only.
Why 5: Why was it checked visually only? Because no function test existed in the preventive maintenance plan for this interlock.
Root cause: Preventive maintenance covered cleaning and lubrication but not functional verification of the interlock.
Corrective action: Add an interlock function test to each planned maintenance visit and tighten the bracket standard to a torque spec.
Evidence used: Maintenance history, the machine fault log, and a vibration reading taken while the line ran.
Verification: Log stops by cause code for eight weeks and confirm no interlock event repeats.
4. Late Deliveries from a Critical Parts Supplier
Late deliveries from a supplier usually trace back to your own planning practice, not the supplier’s effort. The chain in this example ends inside your own system.
Problem: A machined housing supplier delivered late on six of the last eleven orders, stopping the final assembly line twice.
Why 1: Why did material arrive late? Because the confirmed ship date moved after the order was released.
Why 2: Why did the ship date move? Because the supplier had no firm promise date on record.
Why 3: Why was there no firm promise date? Because the purchase order left the promise date field blank.
Why 4: Why was the field blank? Because buyers could release orders without entering one.
Why 5: Why was that allowed? Because the order system had no rule requiring a confirmed date.
Root cause: Orders were released without a confirmed supplier promise date.
Corrective action: Make the promise date a required field and run a supplier scorecard that measures delivery against it.
Evidence used: Purchase order history, the promise date field contents, and the receiving records showing the gap against the build schedule.
Verification: Check that every new order carries a date and measure on-time delivery for 90 days.
5. Damaged Parts During Internal Transfer
When parts keep arriving damaged from another department, the chain usually ends at packaging design rather than at carelessness. This example shows the evidence that gets you there.
Problem: Twelve percent of polycarbonate covers arrive with cracked corner posts after moving from kitting to the assembly line.
Why 1: Why were covers cracked? Because one corner post had broken in transit.
Why 2: Why did the corner post break? Because the covers were stacked loosely in an open tote.
Why 3: Why were they stacked loosely? Because the nest that separated covers had been removed for a different part number.
Why 4: Why was the nest missing? Because the container was returned without its insert.
Why 5: Why was it returned without the insert? Because the transfer record did not include container contents.
Root cause: Container inserts were not controlled as part of the transfer kit.
Corrective action: Redesign the tote for this part so covers cannot stack corner to corner, and add the insert to the container check.
Evidence used: Damage photos by transfer route, container records, and a count of missing inserts on the route.
Verification: Run 20 transfers with the new tote and check damage rate at assembly receipt.
6. A Packaging Line Near Miss
A near miss is a free investigation if you run it without blame. No whys below stop at a person’s attention, because attention is not a control.
Problem: A carton slid to the conveyor edge and was caught by the guard rail before it reached the floor.
Why 1: Why did the carton move toward the edge? Because the conveyor was running with uneven loading.
Why 2: Why was loading uneven? Because cartons were accumulated by hand at the infeed.
Why 3: Why was accumulation done by hand? Because the standard work assumed a metered infeed.
Why 4: Why did the assumption fail? Because product mix changed and no longer matched the layout.
Why 5: Why did the layout not change with the mix? Because standard work has no review trigger tied to product changes.
Root cause: Standard work was not revisited when the product mix changed.
Corrective action: Add a load limit to the standard work and fit a fixed guide on the infeed so the loading pattern no longer depends on judgement.
Evidence used: Near miss report, infeed footage, and the change record for the new product mix.
Verification: Review loading behaviour on each new mix for 30 days and audit the guide position at startup.
7. Excess Scrap After a Product Changeover
Scrap that appears only after changeovers points at the setup process, not the run itself. The chain below stops at a missing verification step.
Problem: Scrap rate on the line rose from 2 percent to 9 percent on the first 60 pieces after each changeover, then settled.
Why 1: Why was scrap high after changeover? Because early parts held the wrong fill weight.
Why 2: Why was fill weight wrong? Because the setup sheet recorded the set value, not the value actually run.
Why 3: Why did the sheet show the set value? Because no one verified the running machine value.
Why 4: Why was no verification done? Because the setup standard requires a first-piece check on dimensions only.
Why 5: Why does the standard miss fill weight? Because the standard predates the current product range.
Root cause: The changeover standard did not include verification of fill weight.
Corrective action: Add fill weight to the setup standard and store the running parameter set as the recipe for each product.
Evidence used: Setup sheets, scrap by run number, and the parameter history saved at each changeover.
Verification: Track scrap on the first 60 pieces across 15 changeovers.
8. Missing Components in a Customer Kitting Order
A short-shipped kit usually traces to a control that was never checked, not to the person who picked it. Here the root cause sits in the replenishment step.
Problem: Nine customer kits shipped with one fastener pack missing, all picked from the same face on the same afternoon.
Why 1: Why was the pack missing? Because the pick location was empty when the picker reached it.
Why 2: Why was it empty? Because the face had not been replenished from the forward pick location.
Why 3: Why was it not replenished? Because the replenishment task was marked complete.
Why 4: Why was it marked complete with nothing there? Because completion was recorded from the task scan, not from a count.
Why 5: Why was there no count? Because replenishment has no scan verification at the pick face.
Root cause: Replenishment completion was recorded without verification at the pick face.
Corrective action: Require a scan of the replenished item at the pick face and add a kit reconciliation step before release.
Evidence used: Kit build records, the replenishment log for that face, and the shipping documents.
Verification: Reconcile every kit for two weeks and review short-ship counts monthly.
9. Premature Failure of a Production Tool
Tools that fail early often carry their story in the maintenance record and the storage area. This example uses both instead of assuming an operating fault.
Problem: A cutting tool averaging 40 minutes of run time against a 200-minute standard.
Why 1: Why did the tool fail early? Because the cutting edge chipped within minutes of use.
Why 2: Why did the edge chip immediately? Because the edge was damaged before it reached the machine.
Why 3: Why was it damaged before use? Because it was returned loose in an open tray after the previous job.
Why 4: Why was it returned loose? Because tool return was not recorded in the tool crib process.
Why 5: Why was return not recorded? Because tooling was owned by two departments with no shared return step.
Root cause: Tool return and condition checking sat outside a single owned process.
Corrective action: Define one return process with protected storage and a condition check at every return.
Evidence used: Maintenance history for the tool, a storage area audit, and inspection of returned inserts.
Verification: Log run time for the next 20 tools and compare against the 200-minute standard.
10. Contamination Complaints from Finished Goods
Contamination complaints arrive at the customer’s dock, so the chain runs backwards. Working backwards from the sample is what makes this one defensible.
Problem: A customer reported silicone-like contamination in three cases of finished assemblies sealed at the plant.
Why 1: Why was material in the sealed cases? Because the residue was on parts before final packaging.
Why 2: Why was it on the parts? Because the wash step before packaging did not remove it.
Why 3: Why did the wash not remove it? Because the cleaning step had no defined concentration or time.
Why 4: Why was it undefined? Because the standard was set by habit rather than written down.
Why 5: Why was it never written down? Because equipment changes did not trigger a standard review.
Root cause: The cleaning standard was undocumented and not reviewed after equipment changes.
Corrective action: Write the cleaning standard with concentration and time, verify it on a swab, and add a first-off swab check to the packaging line.
Evidence used: Customer sample analysis, cleaning records for the shift, and the equipment change log for the prior month.
Verification: Swab the first part after every cleaning for 30 days and log each result.
Frequently Asked Questions
What are 5 Whys examples in manufacturing used for?
They are worked demonstrations of the method on real factory problems: dimensional defects, short shots, unplanned downtime, supplier delays, transfer damage, near misses, changeover scrap, short-shipped kits, premature tool failure and contamination complaints. Each one shows a problem statement, five evidence-backed whys, a root cause someone can control, a corrective action, and how to verify the fix worked.
How many Whys should a manufacturing investigation use?
As many as it takes, and usually fewer than five. Keep asking while each answer is supported by evidence and still leads somewhere a team can act on. Stop at three when the third answer is already a controllable cause. Padding the chain to reach five produces invented answers that nobody trusts.
What is the difference between 5 Whys and root-cause analysis?
Root cause analysis is the whole activity of finding out why a problem happened. The 5 Whys is one method inside it, and the quickest one. A fishbone diagram broadens the search across categories, fault tree analysis works down from a defined top event, and FMEA scores risks before they happen. The 5 Whys is fast, cheap and weak on problems with several interacting causes.
Does the 5 Whys method work for equipment failures?
Yes, and it is at its best on breakdowns with a clear event and a short chain. A door interlock sensor failing intermittently, for example, resolves in a few whys once you pull the fault log and maintenance history. It struggles with chronic degradation, where wear, settings and load drift interact and no single chain holds up.
How do you document and verify a 5 Whys conclusion?
Capture the problem statement with numbers, list the evidence behind each why, name the corrective action owner, and set a review date. Many plants require a 5 Whys on any breakdown over two hours for exactly this reason. Verify the cause first with a counter-test or a controlled reproduction, then verify effectiveness by reviewing the metric after 30 to 90 days.
When is 5 Whys not the right problem-solving method?
Skip it when causes are numerous and interacting, when the failure is too rare to reproduce, or when the problem involves safety-critical systems where a single cause story is dangerous. Use a fishbone diagram to widen the search, fault tree analysis for complex top events, or DMAIC and A3 when the problem is chronic and needs measured improvement over months.
Conclusion
Start with the problem and write it down with numbers, the way the dimensional defect example does. Gather the evidence before anyone offers a theory, then keep asking why until the answer is a condition your team controls rather than a person’s attention.
Verify the cause with a counter-test, pick a corrective action that changes the process, and book the effectiveness review before you close the paperwork. If your team runs similar investigations, the root cause analysis methods for manufacturing defects guide covers the wider toolkit, and the poka yoke examples in manufacturing show what the strong technical controls look like once you know what to remove.