What needs to be finished first
A countable list of events, causes, or items with a numeric value per entry exists for a clearly bounded time period.
A categorization of causes or error classes exists so items are not counted twice.
What needs to be ready before start
Spreadsheet with columns Item, frequency or cost, cumulative sum, cumulative percentage; bar-line chart template; shared document for conclusions.
One analyst prepares the data; two to three domain experts verify categories; one decider approves consequences from the distribution.
Data period (at least 60 days or 100 incidents); measurement source and collection method; known outliers or exceptions; definition of the unit being counted.
60-90 min
Load data extract into spreadsheet. Sort items descending. Calculate cumulative sum and percentage. Prepare chart without sharing yet to avoid bias.
The one question this method answers
Which 20% of items drive 80% of impact, and which levers in the top group are truly actionable?
Marker: Sektion
| Step | Duration | Action | Hint |
|---|---|---|---|
1Section 1: Validate categories | 15 min | Review items with domain experts and check for overlaps, duplicate counting, or catch-all categories. Fix definitions in writing. | A "Other" category above 15% is a critical problem; it hides the real drivers. |
2Section 2: Calculate distribution | 10 min | Sum frequencies or costs, sort descending, calculate cumulative sum and cumulative percentage. | If top 3 are below 40%, there is no Pareto distribution. Then the method does not deliver clear focus. |
3Section 3: Chart and threshold | 15 min | Create Pareto chart (bars for frequency, line for cumulative percentage). Mark 80% threshold as a horizontal line. | The threshold does not have to be exactly 80. 70 or 90 are valid if the distribution has a bend there. Search for the inflection point. |
4Section 4: Leverage check | 20 min | For each item in the top group rate leverage: actionable in 30 days, actionable in 90 days, not actionable. Only actionable items become actions. | If the top cause is external (for example market demand), Pareto leads astray. The method then delivers awareness, not a plan. |
5Section 5: Decision | 10 min | Define one to three items with owner and due date as actions. Keep remaining long-tail items intentionally untouched and document rationale. | Long tail must be explicitly held. Otherwise the team discusses again in 4 weeks whether to work on it. |
What comes out at the end
Pareto chart and tabular distribution (item, frequency, cumulative percentage), marked 80% threshold, leverage column, action list with owner and due date, documented long-tail decision.
One analysis version per period with date, data source, and snapshot hash. Keep earlier versions to visualize distribution shifts by quarter.
Compact working template for Pareto Analysis with context, input, output artifacts, and next step.
Uses the 80/20 principle to identify the few most important causes or options.
When and for what do we use this method?
Which data, observations, decisions, or materials are available?
Short notes along the runsheet.
Owner, date, and success signal.
Concrete filled scenario, fictional example
Concrete filled scenario, fictional example
| Cause | Tickets | Share | Cumulative |
|---|---|---|---|
| Login failed (SSO timeout) | 612 | 33.2% | 33.2% |
| Mail address undeliverable | 401 | 21.8% | 55.0% |
| Export limit exceeded | 248 | 13.5% | 68.5% |
| Language switching failed | 197 | 10.7% | 79.2% |
| Remaining 23 categories | 384 | 20.8% | 100.0% |
Top 4 cover 79.2%. Leverageability:
Long tail (23 categories, 20.8%): kept intentionally, re-review in Q3.
Recognize symptoms and steer against them
"Other" or "Misc" is in the top 5 and above 15%.
Review items in Other manually and split into at least three new categories. Sort again after recoding.
Top 3 below 40%, distribution is flat.
Stop the method, work with cluster analysis or a broader data basis. Pareto otherwise enforces false focus.
Top item is frequent but cheap per incident; expensive incidents are in the long tail.
Calculate Pareto twice: by frequency and by cost or severity. Compare both distributions and derive actions from the intersection.
Collection covers two weeks, results are strongly influenced by the last incident.
Use at least 60 days or 100 incidents, whichever is larger. For seasonality, include same period of previous year.
Largest driver is outside team influence (market, regulation).
Mark the item clearly and do not treat it as action. Choose the next most actionable item from the list.
Team works on tail items in parallel, delaying top actions.
Document a long-tail hold agreement. Automatically deprioritize tail tickets in triage.
Done signals checkable in under a minute
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.