Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Pareto principle
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Analysis == [[File:Pareto analysis.svg|thumb|A Pareto analysis in a diagram showing which cause should be addressed first]] Pareto analysis is a formal technique useful where many possible courses of action are competing for attention. In essence, the problem-solver estimates the benefit delivered by each action, then selects a number of the most effective actions that deliver a total benefit reasonably close to the maximal possible one. Pareto analysis is a creative way of looking at causes of problems because it helps stimulate thinking and organize thoughts. However, it can be limited by its exclusion of possibly important problems which may be small initially, but will grow with time. It should be combined with other analytical tools such as [[failure mode and effects analysis]] and [[fault tree analysis]] for example.{{Citation needed|date=July 2009}} This technique helps to identify the top portion of causes that need to be addressed to resolve the majority of problems. Once the predominant causes are identified, then tools like the [[Ishikawa diagram]] or Fish-bone Analysis can be used to identify the root causes of the problems. While it is common to refer to pareto as "80/20" rule, under the assumption that, in all situations, 20% of causes determine 80% of problems, this ratio is merely a convenient rule of thumb and is not, nor should it be considered, an immutable law of nature. The application of the Pareto analysis in risk management allows management to focus on those risks that have the most impact on the project.<ref>David Litten, [http://www.pmhut.com/project-risk-and-risk-management Project Risk and Risk Management], ''Retrieved May 16, 2010''</ref> Steps to identify the important causes using 80/20 rule:<ref>{{cite web|title=Pareto Analysis|url=http://erc.msh.org/quality/pstools/pspareto.cfm|accessdate=12 January 2012|url-status=dead|archiveurl=https://web.archive.org/web/20120208180732/http://erc.msh.org/quality/pstools/pspareto.cfm|archivedate=8 February 2012}}</ref> # Form a frequency of occurrences as a percentage # Arrange the rows in decreasing order of importance of the causes (i.e., the most important cause first) # Add a cumulative percentage column to the table, then plot the information # Plot (#1) a curve with causes on ''x''- and cumulative percentage on ''y''-axis # Plot (#2) a bar graph with causes on ''x''- and percent frequency on ''y''-axis # Draw a horizontal dotted line at 80% from the ''y''-axis to intersect the curve. Then draw a vertical dotted line from the point of intersection to the ''x''-axis. The vertical dotted line separates the important causes (on the left) and trivial causes (on the right) # Explicitly review the chart to ensure that causes for at least 80% of the problems are captured
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)