Pareto Analysis: Find the Vital Few Causes That Matter

Pareto analysis is a technique for finding the small number of causes that generate most of your problems, so you can rank them and act on the biggest ones first. It follows the 80/20 rule: roughly 80 percent of your defects, delays, or complaints usually trace back to about 20 percent of the possible causes. It’s a prioritization tool, not a diagnosis. Pareto analysis tells you where to dig. It won’t tell you why the problem exists. That part comes later.

Key Takeaways

Pareto analysis works because it turns a long list of causes into a short, ranked list of the ones actually worth fixing first.

Point	Details
Prioritize, don’t diagnose	Use Pareto analysis to rank causes by impact, then follow up with root-cause tools to find why they happen.
Sort before you chart	List categories, total each one, and sort descending before adding cumulative percent.
Watch the cumulative line	The causes below roughly 80 percent cumulative are your vital few, but the exact ratio varies by process.
Group the long tail	Combine low-frequency categories into an “Other” bar so the chart stays readable.
Build the skill into a credential	MSI’s Ultimate Six Sigma Certification Course Package covers Pareto diagrams and pairs them with the rest of the Six Sigma toolkit.

What the 80/20 Rule Means in Practice
When a Pareto Chart Is the Right Tool
Building a Pareto Chart in Excel or Google Sheets
Reading the Chart and Deciding What to Fix First
Limitations and Common Pitfalls to Watch For
How MSI Training Builds on Pareto Analysis
What the Data Actually Supports
Take Pareto Analysis Further With a Recognized Certification
Sources
FAQ

What the 80/20 Rule Means in Practice

Vilfredo Pareto noticed in the late 1800s that a small share of landowners controlled most of the land in Italy. Decades later, quality management pioneer Joseph Juran borrowed the idea and applied it to defects, complaints, and inefficiencies, coining the phrase “vital few and trivial many” and adding the cumulative percentage line to the Pareto chart itself.

The 80/20 split is a rule of thumb, not a law of physics. Some processes show a similar imbalance, but ratios like 70/30 or 90/10 can also occur. The exact ratio doesn’t matter nearly as much as the underlying pattern: causes are almost never distributed evenly. A handful of them do most of the damage, and everything else is noise by comparison.

That imbalance is the whole point. Once you accept that not all causes deserve equal attention, prioritization stops being a guessing game. You stop spreading your team thin across a dozen minor issues and start putting resources where they’ll actually move the needle. That’s the mindset behind Pareto analysis: less effort, more impact, applied where the data says it counts.

When a Pareto Chart Is the Right Tool

Pareto charts work best with categorical data (the kind you can count and sort into named buckets, like defect type, complaint category, or downtime reason) tallied over a fixed timeframe. Feed it continuous data, like exact cycle times or temperature readings, and the chart loses its meaning. That kind of data needs grouping first, or a different tool entirely, according to guidance from JMP’s statistical primer on Pareto chart construction.

You’ll know Pareto analysis fits your situation if you’re seeing:

A long list of possible causes and no clear sense of which ones matter most
The same handful of failures showing up repeatedly in logs, tickets, or inspection reports
Pressure to prioritize with limited time, budget, or staff
A need to justify where resources go before starting deeper root-cause work

If your data is countable, categorical, and collected consistently, you’re ready to build the chart.

Building a Pareto Chart in Excel or Google Sheets

You don’t need statistical software for this. A basic spreadsheet handles the entire workflow, and once you’ve built one Pareto chart, the next one takes about ten minutes.

Pick your categories and metric. Decide what you’re counting (defect type, complaint reason, downtime cause) and whether you’re measuring frequency, cost, or time. Fix a timeframe, like the last quarter or the last 500 units produced.
Collect and total the data. Build a simple two-column table: category name in column A, total count (or cost, or hours) in column B.
Sort descending. Order the rows from highest count to lowest. This step alone often reveals the pattern before you’ve even built the chart.
Add a cumulative count column. In column C, add each row’s total to the running sum of everything above it.
Convert to cumulative percent. In column D, divide each cumulative count by the grand total. This is the line that shows you where the 80 percent mark falls.
Group the stragglers. If you have more than seven or eight categories, roll the smallest ones into an “Other” bucket and place it last on the chart, so a long tail of one-off issues doesn’t clutter the view, following the approach JMP recommends for readability.
Build the combo chart. Highlight your table, insert a bar chart, then select the cumulative percent series and change its chart type to “line.” Move that line to the secondary axis so it reads on a 0 to 100 percent scale while the bars keep their own count scale.
Add an 80 percent guide line, if you want one. A flat horizontal line at the 80 percent mark makes it easy to see at a glance which bars fall under the cutoff.

This mirrors the same nine-step procedure ASQ outlines for constructing Pareto charts, condensed for a spreadsheet workflow. The order matters more than the tool: sort first, cumulate second, chart last.

Pro Tip: Name your categories consistently before you start collecting data. “Late shipment” and “shipment delay” will get counted as two separate causes if you’re not careful, and that alone can quietly change which cause looks “vital.”

Reading the Chart and Deciding What to Fix First

Once the chart is built, look for the point where the cumulative percent line crosses roughly 80 percent, and trace straight down to see which bars fall to the left of that point. Those are your vital few. Everything to the right is the trivial many, at least for now.

A short example makes this concrete. Say a call center logs five complaint types over a month: billing errors, long hold times, wrong information, rude service, and app crashes. If billing errors and long hold times together account for close to 80 percent of all complaints, those two categories are where a team should spend its next quarter, not the other three combined.

A pattern worth remembering: in most real-world defect logs, the top two or three categories, not the top one, are what clear the 80 percent line. Treating a single “biggest” cause as the whole answer is a common misread.

A few cautions matter here:

Frequency isn’t the same as root cause. The chart shows you what happens most, not why. Pair it with a Fishbone diagram or the 5 Whys before you commit resources to a fix.
Watch how categories are defined. Vague or overlapping buckets can quietly shift which causes look “vital.”
Rebuild the chart periodically. Distributions shift as processes change, and a chart from six months ago may no longer reflect reality, a caution practitioners raise regularly when discussing Pareto’s limits.

Limitations and Common Pitfalls to Watch For

The 80/20 split is approximate, and treating it as an exact target leads people astray. A process running 65/35 still has a vital few worth chasing.

Pareto analysis also has a blind spot: it ranks by frequency, so a rare but catastrophic failure can rank near the bottom of the chart even though it deserves more attention than anything above it. And it isn’t built for continuous or ordinal data without grouping first, per JMP’s guidance.

Don’t treat 80/20 as a fixed rule; treat it as a pattern to look for.
Don’t ignore low-frequency, high-severity risks just because they don’t make the top of the chart.
Don’t skip grouping when your data is continuous or ordinal.

Pro Tip: Run a quick FMEA (Failure Mode and Effects Analysis) alongside your Pareto chart. It catches the low-frequency, high-severity risks that a pure frequency count will always underrank.

How MSI Training Builds on Pareto Analysis

Management and Strategy Institute covers Pareto diagrams as part of its broader Six Sigma curriculum, mapping the tool into the Seven Basic Quality Tools framework practitioners rely on across industries. The natural next step after reading this guide is applying it: build one Pareto chart on a real dataset from your own work, then pair it with a root cause investigation to confirm what the chart is actually pointing at.

What the Data Actually Supports

Most Pareto write-ups oversell the 80/20 ratio like it’s a formula to hit rather than a pattern to notice. That’s backwards. The number that matters isn’t 80. It’s whichever cumulative percent line your own data draws, and whether the causes above it are the ones actually worth fixing.

The bigger gap I see is teams stopping at the chart. They build it, spot the top two causes, declare victory, and move straight to a fix, skipping the step where they actually confirm why those causes happen. A Pareto chart handled that way is just a fancier way to guess. It’s a sorting tool, not an answer.

If there’s one thing worth prioritizing first, it’s discipline about data collection, not chart-building. Sloppy category definitions (lumping “billing error” and “invoice mistake” as separate items, for instance) will distort your ranking before you ever touch a spreadsheet. Get the categories clean, then build the chart, then go find out why those bars are tall. That order rarely gets followed, and it’s exactly why so many Pareto exercises produce fixes that don’t stick.

Take Pareto Analysis Further With a Recognized Certification

Knowing how to build a Pareto chart puts you ahead of most people on your team. Turning that skill into a credential that shows up on a resume is a different step, and that’s where the Ultimate Six Sigma Certification Course Package comes in.

The package bundles training, study materials, and a certification exam into one flat price, no hidden add ons, covering Pareto diagrams alongside the rest of the Seven Basic Quality Tools, root cause methods, and process improvement frameworks used in real Six Sigma projects. You work through it at your own pace, from home, on your own schedule. If you’ve already got a Pareto chart pointing at your top causes, the next move is running that project through to completion and having a certification to show for it. Start with the Six Sigma certification package and put what you just learned to work on something real.

Sources

For the formal procedure, ASQ’s Pareto chart guide covers all nine construction steps. For data-type guidance, see JMP’s statistical primer. For applied examples in a business context, review Seattle Software Developers’ project workflow guide. MSI’s Pareto diagram resource rounds out the list.

FAQ

What Is the 80/20 Rule in Pareto Analysis?

It’s the observation that roughly 80 percent of outcomes, like defects or complaints, tend to come from about 20 percent of the possible causes, a pattern Joseph Juran applied to quality control after Vilfredo Pareto first noticed it in land distribution.

What Is a Good Example of Pareto Analysis?

A call center tracking five complaint types and finding that billing errors and long hold times together account for most of the volume is a classic example: those two categories become the priority, not the other three.

Is a Pareto Chart One of the Seven Basic Quality Tools?

Yes. ASQ lists the Pareto chart as one of the seven basic quality tools, alongside tools like the Fishbone diagram and control charts. MSI’s curriculum covers it in the same framework.

How Do I Create a Pareto Chart in Excel?

Sort your category totals in descending order, add cumulative count and cumulative percent columns, then insert a combo chart with bars for counts and a line on the secondary axis for cumulative percent.

Does Pareto Analysis Replace Root Cause Analysis?

No. Pareto analysis ranks causes by frequency or impact so you know where to focus, but it doesn’t explain why those causes occur; that’s the job of tools like a Fishbone diagram or the 5 Whys.