# Pareto Analysis Step by Step

Pareto Analysis is a statistical technique in decision-making used for the selection of a limited number of tasks that produce significant overall effect. It uses the Pareto Principle (also known as the 80/20 rule) the idea that by doing 20% of the work you can generate 80% of the benefit of doing the entire job. In terms of quality improvement, a large majority of problems (80%) are produced by a few key causes (20%). This is also known as the vital few and the trivial many.

In the late 1940s quality management guru, Joseph M. Juran, suggested the principle and named it after Italian economist Vilfredo Pareto, who observed that 80% of income in Italy went to 20% of the population. Pareto later carried out surveys on a number of other countries and found to his surprise that a similar distribution applied.

The 80/20 rule can be applied to almost anything:

• 80% of customer complaints arise from 20% of your products and services.
• 80% of delays in the schedule result from 20% of the possible causes of the delays.
• 20% of your products and services account for 80% of your profit.
• 20% of your sales-force produces 80% of your company revenues.
• 20% of a systems defects cause 80% of its problems.

The Pareto Principle has many applications in quality control. It is the basis for the Pareto diagram, one of the key tools used in total quality control and Six Sigma.

In PMBOK, Pareto ordering is used to guide corrective action and to help the project team take action to fix the problems that are causing the greatest number of defects first.

## Pareto Analysis

Eight steps to identifying the principal causes you should focus on, using Pareto Analysis:

1. Create a vertical bar chart with causes on the x-axis and count (number of occurrences) on the y-axis.
2. Arrange the bar chart in descending order of cause importance, that is, the cause with the highest count first.
3. Calculate the cumulative count for each cause in descending order.
4. Calculate the cumulative count percentage for each cause in descending order. (Percentage calculation: {Individual Cause Count} / {Total Causes Count} *100)
5. Create a second y-axis with percentages descending in increments of 10 from 100% to 0%.
6. Plot the cumulative count percentage of each cause on the x-axis.
7. Join the points to form a curve.
8. Draw a line at 80% on the y-axis running parallel to the x-axis. Then drop the line at the point of intersection with the curve on the x-axis. This point on the x-axis separates the important causes on the left (vital few) from the less important causes on the right (trivial many).

This is a simple example of a Pareto diagram, using sample data showing the relative frequency of causes for errors on websites. It enables you to see what 20% of cases are causing 80% of the problems and where efforts should be focussed to achieve the greatest improvement. In this case, we can see that broken links, spelling errors and missing title tags should be the focus.

The value of the Pareto Principle for a project manager is that it reminds you to focus on the 20% of things that matter. Of the things you do during your project, only 20% are crucial. Those 20% produce 80% of your results. Identify and focus on those things first, but don't entirely ignore the remaining 80% of causes.

Download our free Pareto Analysis Template

We welcome constructive comments and approve any that meet our guidelines. It means providing helpful information that contributes to an article or discussion.

## Comments (1)

Topic: Pareto Analysis Step by Step
3/5 (2)
J Yeates (Birmingham) says...
I had never heard of Pareto Analysis before. It is an interesting way to record the ways in which we spend our time. It may help me and others to manage our time in a more effective way.
3rd February 2015 1:51pm

## Add Comment

*Required information
(never displayed)

1500
What is the day after Friday?

Enter answer:

Notify me of new comments via email.

Remember my form inputs on this computer.

## Article Categories

Pareto Charts
Pareto charts can be used to identify problems to work on. They can help you produce greater efficiency, conserve materials, reduce costs or increase safety.

Six Rules for Great IT Project Success
This article present six straightforward principles to turn your project into a bottom-line success.

The Non-Pareto Principle
The Pareto principle has become deeply rooted in our industrial literature. It is a shorthand name for the phenomenon that in any population which contributes to a common effect, a relative few of the contributors account for the bulk of the effect.

Six Time Management Tips for Project Managers
Time management is a basic skill for project managers. The best project managers ensure they are productive for most of their time and avoid time-wasters.

Belbin's Team Roles

Belbin's theory proposes that teams with a balance of team-roles perform better than those where there is an imbalance of roles.

Roles:

• Plant.
• Monitor Evaluator.
• Co-ordinator.
• Resource Investigator.
• Implementer.
• Completer Finisher.
• Teamworker.
• Shaper.
• Specialist.

Discover our forum where you can ask questions, get advice from other people and share your experience.