Project Smart ~ Exploring trends and developments in project management today

Calendar iconNot recorded
Adobe PDF icon

Pareto Analysis Step by Step

~ By Duncan Haughey

Pareto principle or eighty-twenty rule represented on a blackboard

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).
Pareto Analysis Example Diagram

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.


Excel icon Download our free Pareto Analysis Template


Comments (1)

4/5 (4)
Gravatar
Full StarFull StarFull StarFull StarEmpty Star
Clock icon 3rd February 2015 1:51pm
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.

Add a comment



(never displayed)



 
1000
Enter the word shark backwards.
Notify me of new comments via email.
Remember my form inputs on this computer.

Extreme Project Management

The running back dives for the first down with the defender on his back

Three war room strategies to try when you need to bring life back to a dead project, or save an engagement that is on the brink of disaster.

Demand a Strong Project Plan

Gantt chart

What to look for to advance your consulting projects from contract to execution.

Belbin and Successful Project Teams

Business team brainstorming using coloured labels on an office table

Creating successful project teams is a daunting task for project leaders. A good method for matching people to roles is the Belbin Team Inventory Method (BTIM).

But What is Best for the Customer?

Four business people's hands holding puzzle pieces

Ideally our project management methodology in a box process works perfectly for everyone. But clients come in all types and sizes and one size doesn't fit all.

PROJECT SMART is the project management resource that helps managers at all levels improve their performance. We provide an important knowledge base for those involved in managing projects of all kinds. With weekly exclusive updates, we keep you in touch with the latest project management thinking.

WE ARE CONNECTED ~ Follow us on social media to get regular updates on what's happening in the world of project management.


Latest Comments

Quinton van Eeden commented on…
Perception Is Not Always Equal
- Thu 30 July 10:56am

Duncan commented on…
Project Management Success with the Top 7 Best Practices
- Wed 29 July 7:11pm

Rafael de la Cruz commented on…
Project Management Success with the Top 7 Best Practices
- Tue 28 July 9:42pm

Latest tweets

RT @pm4girls: In this article, we’ll look at five specific ways you can collaborate with business analysts to help create more... http://t.… about 1 day ago

Seven of the most important areas to consider when auditing a construction site http://t.co/OXlKGatc4m #pmot #pm #projectsmart about 1 day ago

General Project Management • Wanting to become a PM from a developer role http://t.co/J7KZj8KpJ1 #pmot #projectsmart about 2 days ago