Scenario
At a quality assurance (QA) meeting, the team leader announced: "This month we had a total of 871 defective products; everyone needs to step up!" Then, each person went off to improve the area they were responsible for. Three months later, the total number of defects decreased from 871 to 845. A 3% improvement.
Let's try a different approach: First, draw a Pareto chart. It reveals that "solder bridges" alone account for 36% of defects. All resources are then focused on solder bridges. Three months later, solder bridges alone were reduced by 60%, and the total number of defects decreased by 22%.
Plain Language Explanation
The Pareto Chart embodies an intuitive principle:
20% of causes lead to 80% of problems.
The X-axis represents problem types (sorted from most to least frequent), the left Y-axis is the quantity, and the right Y-axis is the cumulative percentage. Find the line where the cumulative percentage reaches 80%; the items to the left of this line are where you should concentrate your efforts—this is the "Vital Few."
Practical Judgment
When is a Pareto Chart most useful:
- After classifying monthly defective products, to determine next month's improvement priorities.
- Analyzing equipment downtime causes, to determine maintenance priorities.
- Classifying customer complaints, to find the issues that most impact customer satisfaction.
Common Mistakes:
- Using a Pareto chart based on "number of items," but some defects vary greatly in severity of consequences → Instead, use a weighted approach like "severity × number of items."
- Classification is too broad: "Appearance issues" account for 70%, but this category mixes over a dozen different causes → Needs further subdivision.
How InsightFab Does It
Upload defect categories and quantities, and InsightFab automatically generates a Pareto chart, marks the 80% cutoff line, and tells you: "The top 2 problems account for 78% of total defects; it is recommended to prioritize these two."
Golden Quote
"If improvement isn't progressing, it's not because you're not working hard enough; it's because you're using 100% of your effort to solve 20% of the problems."