Pareto analysis is a structured technique for deciding where to focus improvement efforts. Based on the Pareto Principle — the idea that 80% of effects come from 20% of causes — it turns raw frequency data into a prioritized action list. This guide covers what Pareto analysis is, how to do it step by step, and 7 real-world examples across industries. At the end, you can build your own Pareto chart instantly with our free tool.
What Is Pareto Analysis?
Pareto analysis takes its name from Vilfredo Pareto, a 19th-century Italian economist who observed that roughly 80% of Italy’s land was owned by 20% of the population. He found the same uneven distribution pattern in many other datasets. Decades later, quality management pioneer Joseph Juran applied this observation to organizational problems, coining the phrase “vital few vs. trivial many.” Juran formalized the Pareto chart as a standard quality tool in the 1950s, and it has been a fixture of Lean, Six Sigma, and continuous improvement programs ever since.
A Pareto chart is a specific type of bar chart that combines two visual elements:
| Chart Element | What It Shows | Visual Style |
|---|---|---|
| Bars (descending) | Frequency or count of each category, sorted highest to lowest | Vital few: blue — Useful many: gray |
| Cumulative % line | Running total of cumulative percentage across categories | Red curve overlaid on bars |
| 80% threshold line | Horizontal reference line at 80% cumulative | Orange dashed horizontal line |
| Left Y-axis | Frequency / count scale | Numeric, matches bar heights |
| Right Y-axis | Cumulative percentage scale (0–100%) | Percentage, matches the line graph |
The key insight: categories to the left of where the cumulative line crosses the 80% threshold are your “vital few” — the small number of causes responsible for most of the problem. Categories to the right are the “useful many” — worth addressing eventually, but not where your limited resources should go first.
The 80/20 split is a guideline, not a law. In practice you may find 70/30 or 90/10 patterns. What matters is the shape of the distribution: does a small number of categories dominate? If so, Pareto analysis gives you a clear, data-backed prioritization.
When to Use Pareto Analysis
Pareto analysis works best when you have recurring problems across multiple categories and need a defensible way to decide what to fix first. It does not work well for every situation.
Use Pareto analysis when…
- You have multiple recurring issue types
- You have quantitative frequency or count data
- You need to prioritize limited resources
- You want to communicate priorities to stakeholders visually
- You are choosing which root cause to investigate first
Do NOT use Pareto analysis when…
- You are investigating a single unique incident
- Your data is qualitative rather than quantitative
- All categories occur at nearly equal frequency
- You have fewer than 20–30 data points total
- You need to map all potential causes (use fishbone instead)
When Pareto analysis is the wrong tool, consider a fishbone diagram for exploring potential causes or the 5 Whys technique for drilling into a specific incident.
How to Do a Pareto Analysis (Step by Step)
Follow these seven steps to complete a Pareto analysis from raw data to prioritized action list.
-
1Define your problem category and time period
Specify exactly what you are counting — defect types, complaint categories, error codes, call reasons — and the time window for data collection. Example: “Defect type on PCB assembly line, January–March 2026.” A clear scope prevents category drift and ensures your data is comparable.
-
2Collect and count data by category
Gather frequency counts for each category from your logs, tickets, inspection reports, or databases. Each category must be mutually exclusive — a single event should belong to exactly one category. Aggregate the total count for each.
-
3Sort categories from highest to lowest frequency
Rank all categories in descending order of count. This establishes the left-to-right order of bars in your Pareto chart. If you have an “Other” category, always place it last regardless of its count — it is a catch-all and should not drive your prioritization.
-
4Calculate cumulative percentages
For each category: divide its count by the total count to get its percentage share. Then calculate the running cumulative percentage as you move down the ranked list. The last category should reach exactly 100% (or very close, accounting for rounding).
-
5Build the Pareto chart
Plot descending bars for frequency (left Y-axis). Overlay a cumulative percentage line (right Y-axis). Draw a horizontal dashed line at 80%. The point where the cumulative line first crosses 80% separates the vital few from the useful many. Or skip the manual work — our free Pareto Chart Maker does all calculations and builds the chart automatically.
-
6Identify the vital few above the 80% line
The bars to the left of the 80% crossing point are your vital few. In most analyses this will be 1–3 categories. These are the issues where fixing them will deliver the greatest reduction in total problem frequency.
-
7Prioritize corrective action on the vital few
For each vital few category, initiate a deeper investigation — typically a 5 Whys or fishbone analysis — to find the root cause. Assign an owner, set a deadline, and schedule a verification check to confirm improvement after corrective actions are implemented.
Build your Pareto Chart now
Enter your categories and counts. The tool calculates cumulative percentages, draws the chart, and highlights the vital few automatically — no spreadsheet required.
Open Pareto Chart Maker →7 Pareto Analysis Examples by Industry
The following examples are drawn from realistic quality improvement scenarios across seven industries. Each includes the raw data table, the vital few finding, and the corrective action taken.
Example 1: Manufacturing — PCB Assembly Defects
Problem statement
Defects in printed circuit board assembly line, Q1 2026 — n = 324 total defects
| Defect Type | Count | % of Total | Cumulative % |
|---|---|---|---|
| Solder bridging | 142 | 43.8% | 43.8% |
| Missing component | 78 | 24.1% | 67.9% |
| Cold solder joint | 52 | 16.0% | 83.9% |
| Component misalignment | 31 | 9.6% | 93.5% |
| Wrong orientation | 21 | 6.5% | 100.0% |
Vital few: Solder bridging + Missing component = 67.9% of all defects. Adding cold solder joint reaches 83.9%, so the first two categories are the clear priority.
Corrective action: Audit solder paste application settings and stencil aperture dimensions. Review component reel change procedure to eliminate the root cause of missing components. Implement automated optical inspection (AOI) immediately after paste application.
Example 2: Healthcare — Medication Administration Errors
Problem statement
Medication administration errors, Regional Medical Center, 12-month period — n = 187 incidents
| Error Type | Count | % of Total | Cumulative % |
|---|---|---|---|
| Wrong dose | 74 | 39.6% | 39.6% |
| Omitted dose | 48 | 25.7% | 65.2% |
| Wrong time | 32 | 17.1% | 82.4% |
| Wrong patient | 19 | 10.2% | 92.5% |
| Wrong route | 14 | 7.5% | 100.0% |
Vital few: Wrong dose + Omitted dose = 65.2% of all medication errors. Together with Wrong time, the top three categories account for 82.4%.
Corrective action: Implement mandatory double-check protocol for high-alert medications (insulin, anticoagulants, opioids). Redesign dose rounding policy to reduce calculation errors. Add barcode medication administration (BCMA) scanning to flag omitted doses in real time.
Example 3: Software — Customer-Reported Bugs
Problem statement
Customer-reported bugs, SaaS platform, Q4 2025 — n = 411 support tickets
| Bug Category | Count | % of Total | Cumulative % |
|---|---|---|---|
| Login / auth failures | 128 | 31.1% | 31.1% |
| Slow page load | 94 | 22.9% | 54.0% |
| Data sync errors | 71 | 17.3% | 71.3% |
| UI rendering bugs | 58 | 14.1% | 85.4% |
| Notification failures | 60 | 14.6% | 100.0% |
Vital few: Login failures + Slow page load = 54.0%. Adding data sync errors extends the vital few to 71.3% — three categories justify a dedicated three-sprint remediation roadmap.
Corrective action: Dedicate one sprint to auth service reliability (token refresh logic, session expiry handling). Add CDN edge caching for the five highest-traffic pages. Fix sync queue race condition causing data sync errors. Assign each fix to a squad with a release date and regression test suite.
Example 4: Customer Service — E-Commerce Escalations
Problem statement
Escalated support tickets, e-commerce platform, 90-day period — n = 256 escalations
| Escalation Reason | Count | % of Total | Cumulative % |
|---|---|---|---|
| Late delivery | 112 | 43.8% | 43.8% |
| Wrong item shipped | 68 | 26.6% | 70.3% |
| Damaged item | 41 | 16.0% | 86.3% |
| Missing item | 23 | 9.0% | 95.3% |
| Billing error | 12 | 4.7% | 100.0% |
Vital few: Late delivery + Wrong item shipped = 70.3% of all escalations. These two categories are the clear priority for intervention.
Corrective action: Audit all carrier SLA compliance reports for the past 6 months; renegotiate or switch underperforming carriers. Implement barcode verification at the packing station to confirm correct item before sealing. Target: reduce escalations by 50% within 60 days.
Example 5: Logistics — Warehouse Pick Errors
Problem statement
Warehouse pick errors, distribution center, January–March 2026 — n = 193 errors
| Error Type | Count | % of Total | Cumulative % |
|---|---|---|---|
| Incorrect quantity | 81 | 42.0% | 42.0% |
| Wrong SKU picked | 55 | 28.5% | 70.5% |
| Damaged during pick | 29 | 15.0% | 85.5% |
| Wrong location | 18 | 9.3% | 94.8% |
| Missing label | 10 | 5.2% | 100.0% |
Vital few: Incorrect quantity + Wrong SKU picked = 70.5% of all warehouse errors. Both are process accuracy issues addressable through technology and verification.
Corrective action: Implement a pick-to-light system for the top 50 SKUs by volume. Add a quantity verification step (scan + weight check) before bin consolidation. Provide targeted refresher training for pickers with above-average error rates.
Example 6: Restaurant / Food Service — Customer Complaints
Problem statement
Customer complaints, restaurant chain (24 locations), Q1 2026 — n = 312 complaints
| Complaint Type | Count | % of Total | Cumulative % |
|---|---|---|---|
| Long wait time | 124 | 39.7% | 39.7% |
| Incorrect order | 87 | 27.9% | 67.6% |
| Food temperature | 53 | 17.0% | 84.6% |
| Rude staff | 28 | 9.0% | 93.6% |
| Cleanliness | 20 | 6.4% | 100.0% |
Vital few: Long wait time + Incorrect order = 67.6% of all complaints. Reducing these two categories would nearly eliminate two-thirds of customer dissatisfaction across the chain.
Corrective action: Install kitchen display order screens at all 24 locations to reduce wait time and improve ticket accuracy. Standardize an order confirmation read-back protocol at the counter. Pilot at 3 high-volume locations before chain-wide rollout; track complaint rate weekly.
Example 7: HR — Voluntary Employee Resignations
Problem statement
Voluntary employee resignations, tech company, FY2025 — n = 94 exits
| Primary Exit Reason | Count | % of Total | Cumulative % |
|---|---|---|---|
| Better compensation elsewhere | 34 | 36.2% | 36.2% |
| Limited growth opportunity | 26 | 27.7% | 63.8% |
| Poor manager relationship | 19 | 20.2% | 84.0% |
| Work-life balance | 11 | 11.7% | 95.7% |
| Relocation | 4 | 4.3% | 100.0% |
Vital few: Compensation + Growth opportunity = 63.8%. Adding Manager relationship extends the vital few to 84.0% — three actionable causes that account for more than four in five voluntary exits.
Corrective action: Conduct a pay-band audit against market benchmarks; adjust compensation for roles more than 8% below median. Create mandatory individual development plans (IDPs) reviewed quarterly. Add manager effectiveness score to quarterly engagement surveys and tie manager coaching to results.
Pareto Analysis vs. Other RCA Tools
Pareto vs. 5 Whys: Pareto analysis answers which problems should we fix first? The 5 Whys answers why is this specific problem happening? Use them in sequence: Pareto to identify the vital few categories, then 5 Whys to drill into the root cause of each top category. Trying to do 5 Whys on every category equally wastes resources on low-impact causes.
Pareto vs. Fishbone: A fishbone diagram maps all potential causes for a single problem statement broadly, regardless of frequency data. Pareto ranks known causes by frequency across a category set. Fishbone is for exploration when you do not yet know where causes live; Pareto is for prioritization when you have data showing how often each category occurs. See our full RCA tools comparison for a side-by-side breakdown.
Pareto vs. FMEA: Failure Mode and Effects Analysis (FMEA) is proactive — it predicts potential failure modes and their severity before problems occur. Pareto is reactive — it analyzes data from problems that have already occurred to set priorities. They are complementary: FMEA defines what to monitor and prevent, Pareto tells you what is currently happening most often and needs immediate attention.
Common Pareto Analysis Mistakes to Avoid
- Using too few data points (< 20 events). With small samples, the distribution is driven by random variation rather than meaningful patterns. Collect more data or use a different tool. A fishbone or 5 Whys is better for single incidents or small data sets.
- Mixing apples and oranges. Categories must be mutually exclusive. If “wrong item” and “packing error” partially overlap, your data will be misleading. Define clear, non-overlapping category boundaries before you begin data collection.
- Treating 80/20 as an absolute law. The Pareto Principle is a guideline, not a mathematical constant. Your data may yield a 70/30 or 90/10 split — both are valid Pareto distributions. What matters is whether a small number of categories dominates. If the distribution is flat, Pareto analysis won’t add value.
- Stopping at prioritization. A Pareto chart tells you where to look, not why the problem exists. Always follow up with a root cause analysis tool — 5 Whys, fishbone, or fault tree — on the vital few categories before jumping to solutions. Without understanding why, corrective actions are guesses.
Free Pareto Chart Maker — No Signup Required
Enter your categories and counts. Get an 80/20 chart with vital few callout, cumulative line, and PNG export. Used by quality managers, Lean Six Sigma teams, and DevOps engineers.
Build Pareto Chart Now →Frequently asked questions
What is Pareto analysis?
Pareto analysis is a decision-making technique based on the Pareto Principle (80/20 rule), which states that roughly 80% of problems come from 20% of causes. It uses a Pareto chart — a combined bar and line graph — to rank issues by frequency or impact, helping teams focus on the vital few causes that drive the most significant results.
How do you do a Pareto analysis?
To do a Pareto analysis, follow these steps:
- Define the problem category you want to analyze (e.g., defect types, complaint categories).
- Collect data — count how often each category occurs over a set period.
- Sort categories from highest to lowest frequency.
- Calculate the cumulative percentage for each category.
- Plot a bar chart with a cumulative percentage line.
- Identify the categories that account for the first 80% of total occurrences — these are your “vital few.”
- Prioritize corrective action on those categories.
What is the 80/20 rule in quality management?
The 80/20 rule (Pareto Principle) in quality management states that approximately 80% of defects, complaints, or failures come from about 20% of the possible causes. This principle guides teams to focus limited resources on the small number of causes that drive the majority of problems, rather than treating all issues equally.
What is the difference between Pareto analysis and 5 Whys?
Pareto analysis answers “which problems should we fix first?” — it prioritizes issues using frequency data and the 80/20 rule. The 5 Whys answers “why is this specific problem happening?” — it drills into root causes by asking why repeatedly. The most effective approach is to use Pareto first to identify the vital few problems, then use 5 Whys to find the root cause of each top category.
When should I NOT use Pareto analysis?
Pareto analysis is not ideal when you are investigating a single unique incident (use 5 Whys or fishbone instead), when you have fewer than 20–30 data points (too small for reliable patterns), when all categories occur at nearly equal frequencies (the 80/20 pattern won’t emerge), or when the impact metric is qualitative rather than quantitative.
How many bars should a Pareto chart have?
Most effective Pareto charts have between 4 and 10 bars. Fewer than 4 categories may not show a meaningful pattern. More than 10 often means categories need consolidation or the “other” bucket is too large. Aim for the smallest number that captures at least 80% of occurrences without an “Other” bar dominating.
Can Pareto analysis be used in healthcare?
Yes, Pareto analysis is widely used in healthcare for patient safety and quality improvement. Common applications include analyzing medication error types, categorizing adverse event root causes, prioritizing readmission diagnoses, and reducing surgical site infection risk factors. The Joint Commission and IHI both recommend Pareto charts as standard quality improvement tools.
Recommended Reading
- The Lean Six Sigma Pocket Toolbook — George et al. — Comprehensive reference covering Pareto analysis, fishbone diagrams, 5 Whys, and dozens of other quality tools
- Quality Is Free — Philip B. Crosby — The classic that introduced quality improvement economics to mainstream management
- The Goal — Eliyahu M. Goldratt — Theory of Constraints presented as a novel; essential reading for anyone prioritizing bottleneck improvements
Related resources
- Pareto Chart Examples: 6 Real-World Cases Across Industries — see the method in action with full data tables
- Free Pareto Chart Template (Online & Excel) — build yours in 60 seconds
- 5 Whys vs. Pareto Analysis: When to Use Each
- RCA Tools Compared: 5 Whys, Fishbone, Fault Tree, FMEA & Pareto
- Root Cause Analysis: A Complete Guide
- How to Write a Corrective Action Plan After RCA
- Free Pareto Chart Maker (online tool)