The 5 Whys method is one of the simplest yet most effective root cause analysis techniques. Developed by Sakichi Toyoda at Toyota, it asks one question repeatedly: "Why?" Below are 10 real-world examples showing exactly how teams use the 5 Whys to move from visible symptoms to actionable root causes.
In this article
- Manufacturing: Machine Downtime
- Software: Production Outage
- E-commerce: Cart Abandonment
- Healthcare: Medication Errors
- Customer Service: Long Response Times
- Logistics: Shipping Delays
- HR: High Employee Turnover
- Marketing: Falling Conversion Rate
- Construction: Budget Overruns
- Education: Low Course Completion
1. Manufacturing: Machine Downtime
A production line in an automotive parts factory experienced recurring unplanned stops, costing an estimated $15,000 per incident in lost output.
5 Whys Analysis
Industry: Manufacturing (Automotive)
Problem: CNC milling machine stops unexpectedly 3 times per week, causing 2-hour production delays each time.
Why #1 Why does the machine stop? — The thermal overload protection trips due to excessive motor temperature.
Why #2 Why does the motor overheat? — The coolant flow is insufficient to dissipate heat during continuous operation.
Why #3 Why is coolant flow insufficient? — The coolant filter is partially clogged with metal shavings, restricting flow by 40%.
Why #4 Why is the filter clogged? — The filter has not been replaced in 6 months, well past its 2-month service interval.
Root Cause Why was the filter not replaced on time? — There is no preventive maintenance schedule for coolant system components; replacements only happen after breakdowns.
Corrective action: Implement a preventive maintenance checklist with scheduled coolant filter replacement every 8 weeks. Add a visual indicator gauge to the coolant system for real-time flow monitoring.
2. Software: Production Outage
A SaaS company's payment processing service went down for 47 minutes during peak hours, affecting thousands of transactions.
5 Whys Analysis
Industry: Software / SaaS
Problem: Payment API returned 500 errors for 47 minutes on Tuesday between 2:00-2:47 PM, blocking all checkout transactions.
Why #1 Why did the API return errors? — The database connection pool was exhausted; all 50 connections were occupied by long-running queries.
Why #2 Why were queries running so long? — A new report query was scanning 12 million rows without an index on the created_at column.
Why #3 Why was there no index? — The migration adding the report feature did not include index creation; it passed code review without a database review.
Why #4 Why was there no database review? — The team has no mandatory database review step for migrations that touch tables with more than 1 million rows.
Root Cause Why is there no such process? — Database performance guidelines exist in a wiki but are not enforced as part of the CI/CD pipeline or PR checklist.
Corrective action: Add an automated CI check that flags migrations on large tables without corresponding index changes. Add a "database review required" label to PRs that modify migration files.
3. E-commerce: Cart Abandonment
An online retailer noticed checkout abandonment jumped from 35% to 58% over two months, directly impacting revenue.
5 Whys Analysis
Industry: E-commerce / Retail
Problem: Checkout abandonment rate increased from 35% to 58% in the last 8 weeks, resulting in $120K lost monthly revenue.
Why #1 Why are customers abandoning checkout? — Session recordings show 73% of drop-offs happen at the shipping cost reveal on step 3 of 5.
Why #2 Why does the shipping cost cause drop-offs? — The new carrier contract increased standard shipping from $4.99 to $11.99; customers see the price jump only at checkout.
Why #3 Why do customers only see the cost at checkout? — Shipping cost is calculated after entering a delivery address (step 3), with no upfront estimate on product or cart pages.
Why #4 Why was no upfront estimate built into the original flow? — The checkout was designed when shipping was flat-rate $4.99, so there was no perceived need for early cost communication.
Root Cause Why wasn't the checkout redesigned when the carrier contract changed? — The product team treated the carrier switch as a backend-only change; there is no UX review process triggered by pricing changes that affect customer experience.
Corrective action: Add a shipping cost estimator on the product page and cart page based on IP geolocation. Introduce a free-shipping threshold ($75+) to reduce price shock. Establish a mandatory UX review step for any backend pricing change that affects the customer checkout experience.
Try the 5 Whys method yourself
Use our free interactive tool to run your own root cause analysis. No signup, no downloads.
Start Free Analysis →4. Healthcare: Medication Errors
A regional hospital recorded a spike in wrong-dosage medication incidents in the oncology ward, triggering a patient safety review.
5 Whys Analysis
Industry: Healthcare
Problem: 7 wrong-dosage medication errors reported in the oncology ward over the past quarter, up from 1 in the previous quarter.
Why #1 Why are wrong dosages being administered? — Nurses are manually calculating doses from weight-based tables instead of using the electronic prescribing system.
Why #2 Why are they calculating manually? — The electronic system frequently times out during peak hours (8-10 AM), forcing staff to use paper charts.
Why #3 Why does the system time out? — The hospital network bandwidth was not upgraded when the oncology ward added 30 new connected devices last quarter.
Why #4 Why was the network not upgraded? — IT resource planning is done annually during budget season, but department equipment purchases are approved independently on a rolling basis throughout the year.
Root Cause Why are equipment purchases not coordinated with IT? — There is no cross-departmental procurement policy requiring an IT infrastructure impact assessment before adding networked devices to any ward.
Corrective action: Implement a cross-departmental procurement policy requiring IT infrastructure impact assessment before purchasing networked devices. Immediately upgrade oncology ward bandwidth to handle current load with 50% headroom. Add quarterly IT-department coordination reviews to catch capacity gaps proactively.
5. Customer Service: Long Response Times
A B2B software company's support team saw average first-response time grow from 2 hours to 11 hours, triggering SLA breach warnings.
5 Whys Analysis
Industry: B2B Software / Customer Support
Problem: Average first-response time to support tickets increased from 2 hours to 11 hours over the last month, breaching SLA for 34% of enterprise accounts.
Why #1 Why are response times so long? — The support queue has grown from 40 to 130 daily tickets, but the team size has not changed.
Why #2 Why did ticket volume triple? — 60% of new tickets are about the same issue: users cannot export reports after the v4.2 update.
Why #3 Why is this known bug generating so many tickets? — The status page and in-app banner were not updated to inform users about the issue and the expected fix timeline.
Why #4 Why was proactive communication not sent? — The engineering team reported the bug in Slack, but no one on the support or comms team was notified because there is no automatic alert when critical bugs are flagged.
Root Cause Why is there no automatic cross-team alert? — There is no incident communication workflow connecting engineering bug tracking to customer-facing channels; each team operates in its own tools without cross-functional triggers.
Corrective action: Build a cross-functional incident communication workflow: when engineering flags a critical bug, auto-notify the support and comms teams via Slack and PagerDuty. Create a playbook: when a bug affects 100+ users, update the status page, send an in-app banner, and email affected accounts with a timeline. Assign an incident communicator role in the on-call rotation.
6. Logistics: Shipping Delays
A third-party logistics provider noticed that 22% of shipments were arriving late to a key retail client, putting the contract at risk.
5 Whys Analysis
Industry: Logistics / Supply Chain
Problem: 22% of shipments to RetailCo arrive 1-3 days late, up from 4% last quarter. Contract penalty threshold is 10%.
Why #1 Why are shipments arriving late? — Trucks are departing the warehouse 2-4 hours behind the scheduled cutoff time.
Why #2 Why are trucks departing late? — The picking and packing process for RetailCo orders takes 6 hours instead of the planned 3 hours.
Why #3 Why does picking take twice as long? — RetailCo's new SKU assortment (added in January) is stored in a distant warehouse zone, requiring double the walking distance per order.
Why #4 Why are new SKUs stored in a distant zone? — Warehouse slotting is only reviewed annually, so high-velocity new SKUs were placed in leftover slots rather than optimized positions near the primary picking area.
Root Cause Why is slotting only reviewed annually? — The warehouse management system does not support incremental zone-by-zone optimization; reslotting requires a full warehouse replan during the annual inventory shutdown, so it is avoided mid-year.
Corrective action: Upgrade the WMS to support incremental zone-by-zone reslotting without a full warehouse shutdown. Immediately reslot RetailCo's top 50 SKUs to the primary picking zone. Implement a trigger: any new SKU with projected volume above 500 units/month gets priority slotting within 2 weeks of onboarding. Move to quarterly slotting reviews for key accounts.
7. HR: High Employee Turnover
An engineering team at a mid-size tech company lost 5 of 12 engineers in 6 months, disrupting multiple projects.
5 Whys Analysis
Industry: Technology / HR
Problem: 5 out of 12 engineers on the platform team resigned in the last 6 months, a 42% turnover rate versus 12% company average.
Why #1 Why did engineers leave? — Exit interviews show the top reason is lack of career growth and repetitive maintenance work.
Why #2 Why is the work perceived as repetitive? — The team spends 70% of time on legacy system maintenance and only 30% on new features, compared to 50/50 on other teams.
Why #3 Why is maintenance load so high? — The legacy system was built without automated tests or documentation, making every change slow and risky.
Why #4 Why has the technical debt not been addressed? — Sprint planning is driven entirely by the product backlog, and the engineering manager has no formal mechanism to reserve capacity for non-feature work.
Root Cause Why can't engineering reserve capacity for tech debt? — Product OKRs measure only feature delivery velocity, not engineering health metrics like deploy frequency or change failure rate, so tech debt work has no organizational support or visibility.
Corrective action: Add engineering health metrics (deploy frequency, change failure rate, tech debt ratio) to team OKRs alongside product metrics. Reserve 20% of each sprint for tech debt and test coverage on the legacy system. Create a 6-month modernization roadmap with visible milestones to restore team morale and reduce attrition.
8. Marketing: Falling Conversion Rate
A SaaS company's landing page conversion rate dropped from 4.2% to 1.8% after a website redesign, reducing qualified leads by more than half.
5 Whys Analysis
Industry: SaaS / Marketing
Problem: Landing page conversion rate dropped from 4.2% to 1.8% within 3 weeks of the new website launch, cutting qualified leads from 840 to 360 per month.
Why #1 Why did conversion drop? — Heatmap data shows visitors scroll past the CTA button without clicking; only 12% of visitors see the main CTA.
Why #2 Why do so few visitors see the CTA? — The new design moved the primary CTA from above the fold to below a 900px hero image and a testimonial section.
Why #3 Why was the CTA moved below the fold? — The design agency prioritized brand storytelling and visual impact over conversion-focused layout.
Why #4 Why did the agency prioritize brand over conversion? — The creative brief did not include performance benchmarks or conversion goals; it only specified visual and brand guidelines.
Root Cause Why did the brief exclude performance requirements? — There is no cross-functional review process for creative briefs; the brief was approved by the brand team alone without involving the growth team who owns conversion metrics and A/B testing.
Corrective action: Add a secondary CTA above the fold immediately. Establish a cross-functional brief review: all creative briefs for high-traffic pages must be co-signed by the growth team with performance benchmarks (minimum CTA visibility, target conversion rate, mandatory A/B testing before full rollout).
Ready to find your root cause?
Walk through your own 5 Whys analysis with our guided, step-by-step tool.
Start Free Analysis →9. Construction: Budget Overruns
A commercial construction firm found that 4 out of 5 recent projects exceeded budget by 15-25%, eroding profit margins.
5 Whys Analysis
Industry: Construction
Problem: 4 of 5 commercial projects completed this year exceeded budget by 15-25%, reducing average project margin from 18% to 4%.
Why #1 Why are projects over budget? — Material costs consistently exceed estimates by 12-20% across all four projects.
Why #2 Why are material estimates too low? — Estimators use a price database that is updated only once per year, while material prices have been fluctuating quarterly due to supply chain volatility.
Why #3 Why is the database only updated annually? — The update process is manual and takes one estimator 3 full days to complete, so it keeps getting deprioritized during busy seasons.
Why #4 Why is the update manual? — The estimating software (purchased in 2018) predates the suppliers' modern API pricing systems, and no integration was ever built.
Root Cause Why was no integration built? — The firm's IT budget is allocated exclusively to field operations tools (project management, BIM); back-office estimating software has no dedicated technology improvement budget or owner.
Corrective action: Create a dedicated back-office technology budget with owner accountability. Integrate the estimating software with the top 3 suppliers' pricing APIs for real-time cost updates. Until integration is live, schedule monthly manual price checks on the 20 highest-spend materials and add a 10% contingency line to all estimates.
10. Education: Low Course Completion
An online learning platform saw that only 11% of enrolled students completed their courses, far below the 35% industry benchmark.
5 Whys Analysis
Industry: EdTech / Online Learning
Problem: Average course completion rate is 11%, compared to 35% industry benchmark. 68% of drop-offs happen between modules 2 and 3.
Why #1 Why do students drop off at module 3? — Module 3 is the first module with graded assignments, and 54% of students who attempt it score below the passing threshold.
Why #2 Why do most students fail the first graded assignment? — The assignment requires skills that were demonstrated in video lectures but never practiced by students in modules 1-2.
Why #3 Why is there no practice before grading? — Modules 1-2 are lecture-only with no interactive exercises; the course template does not include practice activities before graded work.
Why #4 Why does the template skip practice activities? — The template was originally designed for instructor-led classrooms where the instructor provides live practice and real-time feedback between lectures.
Root Cause Why was the template never adapted for online learning? — The platform scaled rapidly from 5 to 200+ courses by cloning the original template; there is no instructional design review process for new courses and no dedicated learning experience team to update the template for self-paced delivery.
Corrective action: Hire or assign a learning experience designer to adapt the course template for self-paced online delivery. Redesign the template to include ungraded practice exercises after every lecture module. Add a low-stakes quiz at the end of modules 1 and 2 for self-assessment. Require an instructional design review for all new courses before launch. Pilot with 3 courses and compare completion rates before rolling out platform-wide.
Key takeaways from these examples
Across all 10 case studies, several patterns emerge that can improve your own root cause analysis:
- Start with a measurable problem. Every example begins with a specific, quantified symptom. Vague problems lead to vague root causes.
- Look for process gaps, not people failures. In each case, the root cause was a missing process, missing integration, or missing review step — not an individual mistake.
- The root cause is often 2-3 levels deeper than expected. The obvious answer (e.g., "the filter is clogged") is almost never the root cause. Keep asking why.
- Corrective actions should be systemic. The best fixes change processes, add automation, or create feedback loops — not just address the immediate symptom.
- Different industries, same method. The 5 Whys works in manufacturing, software, healthcare, HR, and marketing. The logic is universal.
Frequently asked questions
How many Whys do you need in a 5 Whys analysis?
Five is a guideline, not a rule. Some problems reach the root cause in 3 levels, others need 7. Stop when you reach a systemic cause that, if eliminated, would prevent the problem from recurring.
Can a 5 Whys analysis have multiple root causes?
Yes. Complex problems often have more than one root cause. If the causal chain branches at any level, investigate each branch separately. You may end up with 2-3 root causes that each need their own corrective action.
Who invented the 5 Whys method?
The 5 Whys was developed by Sakichi Toyoda, founder of Toyota Industries. It became a core practice in the Toyota Production System and later spread to Lean, Six Sigma, and Agile methodologies worldwide.
What industries use the 5 Whys method?
The 5 Whys is used across virtually every industry: manufacturing, software, healthcare, logistics, customer service, HR, marketing, construction, education, and finance. The method is universal because causal logic applies to any type of problem.
Run your own 5 Whys analysis now
Our free, guided tool walks you through each step. No signup required. Export results as a screenshot.
Start Free Analysis →📚 Recommended Reading
- The Lean Six Sigma Pocket Toolbook — George et al. — Quick reference to 100+ tools including 5 Whys
- The Toyota Way — Jeffrey K. Liker — The definitive guide to Toyota's management principles
- Beyond the Five Whys — James C. Paterson — Deep dive into extending the 5 Whys method