Use the Complete Toolkit to connect this model to guidance, working formats and a concrete next step.
In 2002 Microsoft looked at the error reports Windows users sent in after crashes. Steve Ballmer later described what they found: fixing the top 20% of the most-reported bugs would remove about 80% of the errors and crashes. That is a Pareto analysis, and it is why the method turns a long list of problems into a short list of priorities.
What Pareto analysis is
Pareto analysis ranks causes by how much of a problem they create, so you can see which few matter most. The pattern is named after Vilfredo Pareto, an Italian economist who noted in the 1890s that about 80% of the land in Italy belonged to about 20% of the people. In the 1940s the quality expert Joseph Juran noticed the same unevenness in defects and called it the "vital few and the trivial many". He used Pareto's name for it, and the "Pareto principle" stuck.
The 80/20 split is a rule of thumb, not a law. It might be 70/30 or 90/10 in your data. What holds almost everywhere is that causes are not equal, and a small number account for most of the effect.
The Pareto chart
The standard output is a bar chart with causes sorted from largest to smallest, plus a line showing the cumulative percentage. Where the line passes roughly 80%, you have your vital few.
Pareto example: 500 support tickets
An online shop receives 500 support tickets in a month. Sorted by reason:
Where is my order: 190 (38%, cumulative 38%)
Wrong size: 120 (24%, cumulative 62%)
Discount code not working: 75 (15%, cumulative 77%)
Damaged item: 40 (8%, cumulative 85%)
Payment failed: 30 (6%, cumulative 91%)
Seven other reasons: 45 (9%, cumulative 100%)
Three reasons out of twelve cause 77% of tickets. A tracking link in the shipping email, a better size guide and clearer discount rules would remove most of the workload. Rewriting the whole help centre would not.
One-page model visual
The one-page visual
Use this visual as a quick reference. The card in the deck adds the questions and the steps to run the model on your next real question.
How to run a Pareto analysis in 30 minutes with the card
- Minutes 0 to 5: define the effect and the period. "Support tickets in September" or "scrap cost in Q3". Choose a measure that matters: count, cost or time.
- Minutes 5 to 15: count by cause. Use real data from your system. If you have none, tally for a week before deciding.
- Minutes 15 to 20: sort and add the cumulative percentage. Group small causes into "other".
- Minutes 20 to 25: draw the cut-off. Mark the causes up to about 80%.
- Minutes 25 to 30: assign the vital few. One owner and one first action per cause.
The card gives the steps and an example on the back, so you can build the chart straight from your data without looking up how.
Common Pareto mistakes
- Counting when cost matters. Ten small complaints may matter less than one lost key account. Weight by cost or time where you can.
- Categories that overlap. "Late delivery" and "courier problem" may be the same thing. Clean the categories first.
- A huge "other" bar. If "other" is your biggest category, the categories are wrong.
- Treating 80/20 as a target. The point is the ranking, not hitting an exact ratio.
Pareto tells you which causes to tackle; a fishbone diagram helps you dig into why each one happens. If your issue is throughput rather than errors, start with the Theory of Constraints.
Pareto analysis FAQ
-
Is the 80/20 rule always exactly 80/20?
No. The numbers do not have to add up to 100 or match exactly. The principle is that a minority of causes produces the majority of the effect.
-
What is the difference between a Pareto chart and a histogram?
A histogram shows how data is distributed. A Pareto chart sorts categories from largest to smallest and adds a cumulative line, so you can see where the vital few end.
-
Can I use Pareto analysis for customers or products?
Yes. Many companies find that a small share of customers brings most of the revenue or most of the support cost. The same sort helps decide where to spend time.
Sort first, then act
The Pareto card has the steps and an example on one card, so the next problem meeting can start with a ranked list instead of a debate. The Miro board walks a team through the sort, and the Google Sheets template handles the cumulative percentages. Pareto is part of the MBA Tools deck.
