012 min
The problem the Pareto Principle names
In October 2002 Steve Ballmer, then president of Microsoft, sent a security letter that described what the company had learned from error reports. Windows, Office and other products send a report back to Microsoft when something fails, and Microsoft had been counting them. The count showed that about 20 percent of the software's bugs caused about 80 percent of its errors.
That result changes how a team works. A bug list looks flat: hundreds of items, each with a title and a number. A team that fixes them in the order they were reported spends most of its effort on bugs that few people ever meet. A team that counts the reports first fixes the few bugs behind most of the failures, and removes most of the pain with a small part of the work.
Every team has a list like this. A product manager has feature requests, a founder has customers, a support lead has tickets. Without a count, every item looks equally important and the effort is spread evenly. The Pareto Principle is the name for what the count usually shows: the results are not spread evenly, so the effort should not be either.
Even steeper at the top
The same letter gave a second number that was sharper. Ballmer wrote that just 1 percent of the bugs caused half of all errors. The concentration did not stop at 20 percent. Inside the group that mattered, a handful of bugs mattered more than all the others in it.
022 min
Where the Pareto Principle comes from
The name belongs to Vilfredo Pareto, an Italian economist who taught at the University of Lausanne. In his first major work, Cours d'économie politique, he showed that about 80 percent of the land in Italy was owned by about 20 percent of the people. Pareto studied how wealth was spread, and he fitted a mathematical curve to it. He did not claim a rule for factories, software or time management.
The person who turned the pattern into a general rule for managers was an engineer, and he saw it long before he read Pareto.
How Juran first saw the pattern
Joseph Juran worked on quality in factories. In the mid-1920s, as a young engineer, Juran listed defects by how often each one occurred and saw that a few of them accounted for most of the defective products. In the following years he saw the same shape in employee absences and in the causes of car accidents.
His first contact with Pareto's work came later. While Juran worked as an industrial engineer at Western Electric, he visited General Motors. A manager there showed him that the company's executive salary pattern fitted one of Pareto's mathematical models closely. Juran remembered it, and by the late 1940s he was teaching the pattern as a universal, one that applies in many fields.
When Juran prepared the first edition of the Quality Control Handbook, he needed a short name for it. He chose Pareto's. He also coined the phrase "the vital few and the trivial many", and he later softened the second part to "the useful many" so that nobody would read the remaining causes as worthless.
Why Juran said the name is wrong
Juran came to regret the name. In a paper that the Juran Institute dates to 1974, he admitted that he had given the wrong name to the principle. The name stuck anyway. Other engineers had questioned the attribution, and Dorian Shainin was one of them. Their questions pushed Juran to read what Pareto had actually done. He found that Pareto's work was about wealth, not about other fields.
Juran also complained that later writers had added claims to Pareto's record that Pareto never made. The honest summary is that Pareto measured wealth, Juran saw the same shape in defects, and the label joined the two.

032 min
How the Pareto Principle works
Why do so many lists have this shape? In many systems the size of each item is very uneven: a few are large and most are small. Statisticians call a distribution with this shape a power law, and the Pareto distribution is its best-known form. A single number, the exponent, sets how steep it is. When the exponent is about 1.16, the largest 20 percent of items hold 80 percent of the total. Another exponent gives another split, such as 90/10 or 70/30.
The split also repeats inside the top group. At that exponent, the richest 20 percent of a population hold 80 percent of the wealth, and the richest 20 percent of that group hold 80 percent of its share again. So "the vital few" is not one sharp line. It is a slope, and the first few items on the list usually matter far more than the tenth.
The two numbers in "80/20" measure different things. The 80 is a share of the results, and the 20 is a share of the causes, so they do not have to add up to 100. A team may find that 3 of 25 causes produce 80 percent of the tickets, which is 12 percent and 80 percent. The pattern is still there. The exact figures belong to the data, not to the rule. Inequality measures such as the Gini coefficient summarise the same unevenness in one number, but a sorted list shows it more plainly.
Why the pattern appears at all
Nobody has fully settled why so many systems have this shape. The physicist M. E. J. Newman reviewed the evidence for power laws in a paper first posted in 2004. He listed city sizes, earthquakes, wars and personal fortunes among the quantities that appear to follow one. He also noted that where this behaviour comes from has been debated for more than a century.
That is why the principle is best treated as an observation, not as a law. It describes how results are often spread. It does not say that your list must look this way, which is why you count first.
042 min
How to apply the Pareto Principle
The method is a count, and the order matters. The numbers below are illustrative, for a subscription app with 600 support tickets in a quarter.
Choose one outcome to measure.
Tickets, revenue, crashes or hours are all fine, but pick one. Mixing them hides the pattern.
List the causes and add up each one's share of that outcome.
Group the tickets by cause, not by who sent them.
Sort from largest to smallest, and keep a running total.
Find where the running total passes about 80 percent.
The causes above that line are your vital few.
Act on those first, then count again.
| Cause | Tickets | Running share |
|---|---|---|
| Login failures | 240 | 40% |
| Export errors | 150 | 65% |
| Billing confusion | 90 | 80% |
| 22 other causes | 120 | 100% |
Three of 25 causes produce 80 percent of the tickets, so a product manager who starts with them removes four out of five tickets without touching the other 22. A chart of these rows, with sorted bars and a line for the running total, is called a Pareto chart. Juran's handbook popularised this kind of cumulative picture in quality work.
The same count works on revenue by customer, on crashes by bug and on page visits by feature. If the running total climbs slowly and every cause contributes about the same, the pattern is not there, and you have learned something too.

052 min
What the Pareto Principle changes in your work
The count changes a different decision for each role.
A product manager decides what to fix or build next. If a few features account for most of the use, those features deserve the best attention, and a request for a rarely used one has to argue its case with data. An engineer decides where to spend a week. Profiling or crash reports show which few places cause most of the failures, so the week goes there and not to the code that merely looks untidy. A designer decides which screens to polish. The screens that most people reach carry most of the experience. A founder decides whom to protect. If a few customers produce most of the revenue, losing one costs far more than losing an average customer, so the concentration is a risk as well as an opportunity.
The same habit works on a personal list. Write down what you did over two weeks, note which few activities produced the results you care about, and protect time for them. The principle does not say work less. It says to find the part of the work that carries the outcome and look after it first.
In every case the Pareto count starts the argument and does not end it. It tells you where the weight is. Whether that weight is the thing you care about is a judgment the count cannot make.
062 min
When the Pareto Principle misleads
A count is a tool, and it misleads in a few known ways.
When the small part is the dangerous part
After the 2011 earthquake in Japan, companies that managed their supply chains by the 80/20 rule were severely disrupted. Patrick Brennan, a supply chain expert, wrote that typical supply chain risk programmes looked only at the 20 percent of suppliers that made up about 80 percent of spend. Some of the other 80 percent supplied parts that could stop the whole chain. In an example Brennan gave, a part that costs 1 dollar can stop a company from making a product worth 30,000 dollars.
The lesson is that a ranking by money says nothing about what a part can break. The cheap part was in the group the rule told them to ignore.
Frequent is not the same as serious
A Pareto count ranks causes by one measure, usually how often they occur. Ranking by frequency can send effort to common minor issues while rare, catastrophic ones wait. A tool that sorts complaints by count would put a rare safety fault at the bottom of the list. When severity matters, count harm instead of events, or weigh each event by its cost before you sort.
Other limits
A count is a photograph of one period. Customers, competitors and products change, so the vital few change, and an old count can point at the wrong place. Repeat it on a schedule.
A count can also be steered. Moving the cutoff, or choosing a different measure, changes the split. Decide the outcome before you look, and prefer the outcome a customer or the business cares about over the output that is easy to count, such as the number of tasks closed.
The remaining 80 percent is also not worthless. Juran softened "trivial" to "useful" for that reason: the long tail still holds the work that keeps the product running. And the principle does not mean that 20 percent of a team does 80 percent of its work. It describes the spread of a measured quantity in a measured group, and gives no reason to dismiss anyone.
071 min
The Pareto Principle vs nearby concepts
Several ideas share the name or the feeling of the Pareto Principle, and they answer different questions.
Pareto efficiency, a term from welfare economics, describes a state where nobody can be made better off without making someone else worse off. It carries Pareto's name, but it is a different idea and has no 80/20 split in it.
diminishing returns describes how the gain from each extra unit of one input shrinks as you add more. The Pareto Principle describes how results are spread across many causes at one moment. The first is about one input over time, and the second is about many causes side by side. They often appear together, because the last 20 percent of effort tends to buy little.
opportunity cost is what you give up by choosing one option over another. A Pareto count shows which choice has the largest payoff, so it makes the opportunity cost of ignoring the vital few easy to see. triage sorts cases by urgency and need, which is a different ranking from sorting by contribution. A count of contribution can feed a triage decision but cannot replace it. leverage points is the wider idea that a small change in the right place of a system moves the whole system, and the vital few are one way to find such a place.
?3 questions
Questions people ask
Is the Pareto Principle always 80/20?
How do I know whether my data follows a Pareto pattern?
Can I use the Pareto Principle on my own time?
§7 sources
Sources
Show all 7 sourcesHide sources
Susan M. Menke, "Microsoft's Ballmer says 1 percent of software bugs cause 50 percent of errors," GCN, 3 October 2002, a news report on Steve Ballmer's security e
Joseph M. Juran, "The Non-Pareto Principle; Mea Culpa," Juran Institute archive, dated 1974:
An encyclopedia article on the Pareto principle:
An encyclopedia article on the Pareto distribution:
M. E. J. Newman, "Power laws, Pareto distributions and Zipf's law," preprint first posted 2004:
A newspaper feature on the limits of the 80/20 rule, City A.M.:
A quality-practice article, "Pareto - A Tool Often Abused," 2025:





