Practical guide · Root cause analysis and problem solving
Pareto chart: how to build and read one, with a worked example by count and by cost
Short answer
A Pareto chart is a bar chart of problem categories sorted from largest to smallest, with a line showing the cumulative percentage. It shows which few categories make up most of the total, so you work on those first. The bars can count occurrences, minutes or cost.
A Pareto chart ranks categories of one problem, such as defect types or downtime reasons, from the biggest to the smallest, with a cumulative percentage line over the bars. To build one, count each category, sort them, work out each share of the total and the running total, and draw the bars and the line. Read it from the left: the first few bars are the ones to work on. Build it by count and by cost, because the order often changes.
Last updated:
What a Pareto chart is
A Pareto chart is a bar chart with its bars sorted in descending order and a line on top showing the running total as a percentage. The bars use the left axis (a count, minutes or money) and the line uses the right axis (0 to 100%). It rests on the 80/20 idea: when several things contribute to a result, a few of them usually account for most of it. The chart shows which few, with your own data. It is one of the seven basic quality tools, and it is the usual first step before a fishbone or 5 Whys, because it tells the team which problem deserves the investigation.
The 80/20 split is a rule of thumb, not a law. In one set of data the top two categories may make up 85% and in another it takes five categories to reach 60%. Whatever your data says is the answer; a flat chart is a finding too, because it says there is no single big lever.
How to build a Pareto chart in six steps
- 1
Choose one problem and one period
Scrap on one line, downtime on one machine, complaints in one quarter. Mixing problems gives a chart nobody can act on.
- 2
Choose the categories and the measure
Use reason codes the floor already uses, such as a defect check sheet or the downtime reason codes. The measure is a count, minutes or cost. Keep it to 6 to 10 categories plus an Other.
- 3
Collect the data
Tally for long enough that the order of the bars is stable. A few events are not enough to rank anything.
- 4
Sort and total
Sort the categories largest first, with Other always last, however big it is. Add them up for the grand total.
- 5
Work out the share and the cumulative share
Share = category value ÷ grand total × 100. Cumulative = this share plus all the shares above it. The last one must be 100%.
- 6
Draw it and mark the cut
Bars in sorted order on the left axis, the cumulative points joined on the right axis, and a line at 80% if you use that cut. The Pareto chart template does the sorting and drawing in Excel.
Worked example: scrap on one line, by count and by cost (illustrative)
This example is made up. A machining cell scrapped 500 parts in a month across eight causes. The first table is the Pareto by count.
| Cause | Parts | Share | Cumulative |
|---|---|---|---|
| Burrs | 180 | 36.0% | 36.0% |
| Wrong dimension | 110 | 22.0% | 58.0% |
| Scratches | 75 | 15.0% | 73.0% |
| Porosity | 50 | 10.0% | 83.0% |
| Dents | 35 | 7.0% | 90.0% |
| Paint run | 25 | 5.0% | 95.0% |
| Wrong label | 15 | 3.0% | 98.0% |
| Other | 10 | 2.0% | 100.0% |
Check: 180 + 110 + 75 + 50 + 35 + 25 + 15 + 10 = 500. Four causes reach 83%, the first bar to pass 80%.
By count, burrs are the biggest problem and the first project. Now put a cost on each scrapped part, which is what it cost the plant to make up to the point it was scrapped. The costs per part, again illustrative, are: burrs $2, wrong dimension $8, scratches $3, porosity $12, dents $5, paint run $4, wrong label $20 and other $5.
| Cause | Parts × cost per part | Cost | Share | Cumulative |
|---|---|---|---|---|
| Wrong dimension | 110 × $8 | $880 | 32.7% | 32.7% |
| Porosity | 50 × $12 | $600 | 22.3% | 55.0% |
| Burrs | 180 × $2 | $360 | 13.4% | 68.4% |
| Wrong label | 15 × $20 | $300 | 11.2% | 79.6% |
| Scratches | 75 × $3 | $225 | 8.4% | 87.9% |
| Dents | 35 × $5 | $175 | 6.5% | 94.4% |
| Paint run | 25 × $4 | $100 | 3.7% | 98.1% |
| Other | 10 × $5 | $50 | 1.9% | 100.0% |
Check: 880 + 600 + 360 + 300 + 225 + 175 + 100 + 50 = $2,690.
Burrs fall from first to third: they are 36% of the parts and 13.4% of the money. Wrong dimension and porosity, 32% of the parts between them, are 55% of the cost. Wrong label is only 3% of the parts and 11.2% of the cost. Which chart to act on depends on the goal: to cut scrap cost, start with wrong dimension; to cut the number of rejects the operators handle, burrs are still worth a quick fix. Showing both charts side by side is what makes the choice an informed one.
How to read the chart
- Start at the left. The first bars are the ones to work on, and the cumulative line tells you how much of the total they cover.
- Look at where the line bends. A steep start and a flat tail means a few causes dominate. A line close to straight means the causes are about equal and a different cut of the data is needed.
- Check Other. If it is bigger than the largest named bar, the categories are too coarse. Split it and count again.
- Do not stop at one chart. Break the top bar down by machine, shift or product (a second Pareto inside the first) to find where it is made, as the reduce scrap and rework guide does for one month of reason codes.
- Re-draw it after the fix with the same categories and the same period length. If the top bar did not come down, the fix did not work.
Mistakes that mislead
| Mistake | What goes wrong | Do this instead |
|---|---|---|
| Only counting frequency | The cheap, frequent problem wins over the rare, costly one | Build it by cost or minutes as well |
| Not sorting, or putting Other in the middle | The chart no longer shows the vital few | Descending order, Other last |
| A big Other bar | The largest problem may be hiding in it | Split categories until Other is small |
| Too few events | The order of the bars changes next week | Count for long enough that the top bars hold |
| Treating 80% as exact | Work stops at a line that means nothing | Use it as a guide to where the bars level off |
| Stopping at the chart | The chart picks a problem but nothing is fixed | Hand the top bar to a root cause method and an owner |
What to do after the chart
The Pareto names the problem. It does not explain it. Take the top bar to a fishbone if it could come from several areas, or to the 5 Whys if it looks like one chain, and use the problem solving methods guide to choose between them. For downtime, the reduce machine downtime guide works a month of stops through the same sort-and-cut.
To keep a Pareto alive instead of redrawing it by hand each month, LeanSuite's loss and cost management page describes putting a cost on each loss so the biggest can be fixed first, and its micro-stops page covers logging short stops so they show up in the ranking.
Definitions and notes
- The Pareto chart is one of the seven basic quality tools: bars in descending order with a cumulative percentage line (ASQ, "Pareto chart"). It applies the 80/20 idea attributed to Vilfredo Pareto and brought into quality management by Joseph Juran.
- The scrap counts, costs per part and totals are made up for illustration. They are not from a real plant. Every share is the cause's value divided by its table's total, rounded to one decimal.
- Cost per scrapped part here is the cost put into the part up to the step where it was scrapped. How you set it is a decision for your own finance team.
Go deeper
This page is the short version. These guides cover each part in full.
- Pareto Analysis in Manufacturing: Applying the 80/20 Rule to Problem SolvingThe full blog guide to Pareto analysis in a plant, beyond the arithmetic here.
- The Six Big Losses in Lean ManufacturingA ready-made set of loss categories for a downtime or OEE Pareto.
- How to Reduce Manufacturing DowntimeWhat to do once a downtime Pareto has named the top reason.
- Root Cause Analysis Tools in ManufacturingWhich tool to take the top Pareto bar to next.
All our articles on this subject are in the root cause analysis and problem solving topic.
Free templates and tools
- Pareto chart templateA tally sheet, the Pareto by count and by cost with the cumulative line and the 80% cut, and a before and after comparison. Excel sorts and draws it.
- Defect check sheetTally defects by type and day, with units inspected, defect rates, a location sheet and the week's Pareto.
- Downtime reason codes template26 starter codes mapped to the six big losses, a log with drop-downs, a Pareto by code and by loss, and a code card for the line.
- Six big losses worksheetWhere a machine's planned time goes: the six big losses in minutes, ranked, with A, P, Q and OEE worked out.
- Root cause analysis templateOne report from problem statement to proof: containment, evidence, analysis, verified causes, actions and the effectiveness check.
- 5 Whys templateA problem statement, a why chain that can branch, evidence for every answer, root causes and countermeasures that are checked.
- Pareto chart makerPaste categories and counts: sorted bars, cumulative percentage line and the vital few at the 80% line, as a PNG or SVG.
- Scrap rate calculatorScrap rate, the cost of scrap per period and per year, and what reaching a target rate would save.
- Downtime cost calculatorWhat an hour, an event and a year of unplanned downtime cost, from lost output, idle labour, scrap and overtime.
- Cost of poor quality (COPQ) calculatorTotal COPQ and cost of quality, and each as a share of revenue, from the four quality cost categories.
Doing this in LeanSuite
Loss & Cost Management
Shows where your plant loses money, puts a cost on each loss and gives you the tools to remove it.
See Loss & Cost ManagementMicro-stops
Log the brief jams your ERP and MES never report, and see which micro-stops cost the most so you can win back OEE.
See Micro-stopsKPI Dashboards
Turns raw shop floor data into dashboards anyone can read, so everyone from operators to the plant manager can act on performance.
See KPI Dashboards
See it on your own lines
Bring the problem you are working on to a 45-minute demo. Or look around with sample data first, or pilot LeanSuite on your own lines for 90 days, with the setup done by our team.
FAQ
Questions about pareto chart
It is used to decide what to work on first. It ranks the categories of one problem, such as defect types or downtime reasons, from largest to smallest, with a cumulative line, so the few categories that make up most of the total stand out. It is usually drawn before a root cause investigation.
Read from the left. The tallest bars are the biggest contributors, and the cumulative line shows how much of the total they cover together. Look for where the line starts to flatten: the bars before that point are the ones to work on. A near-straight line means no single cause dominates.
It is the idea that a few causes, often about 20% of them, account for most of a result, often about 80%. It is a rule of thumb, not a law. Your own data may show 90% from two causes or 60% from five, and the chart shows which it is.
Build both when you can. A count shows what happens most often and a cost shows what hurts most, and the order often differs. In the worked example on this page, burrs are first by count at 36% of parts but third by cost at 13.4% of the money, so the choice of measure changes the first project.
A Pareto chart ranks separate categories, such as defect types, in descending order. A histogram groups measured values of one characteristic, such as a diameter, into ranges in their natural order to show how the values are spread. Use a Pareto to choose a problem and a histogram to understand variation.
Related guides and tools
More method guides
- The 6 Ms of production
- Poka-yoke
- Model area 90-day plans
- Moving from Excel to one system
- Reducing machine downtime: a worked month
- Andon and jidoka
- Cycle time vs lead time, worked through
- Root cause analysis
- How many operators a line needs
- Reducing scrap and rework: a worked month
- Unsafe acts and unsafe conditions
- Just culture
- Stop-work authority
- Material review board (MRB)
- What is an NCR?
- Problem solving methods
- Quad chart
- OEE calculation
- Quality assurance vs quality control
- SOP meaning and format
- Job hazard analysis
- Near miss reporting
- Fishbone diagram
- Histogram
- Control chart
Or browse the topics, the full library and the lean glossary.
Rather see it on your own problem?
Bring the problem you are stuck on, and we will show you on a call how LeanSuite handles it.

