Key takeaways
Short answer: Pareto charts and fishbone diagrams are two classic quality tools that do different jobs and work best in sequence. A Pareto chart ranks problems or causes by frequency or impact, exposing the vital few that account for most of the trouble — it answers which problem deserves attention. A fishbone, or Ishikawa, diagram then maps the possible causes of one chosen problem across categories — it answers why this problem happens. Pareto prioritises; fishbone investigates. For where they fit in improvement cycles, see PDCA vs DMAIC.
A Pareto chart is a ranked bar chart that orders problems or causes from most to least frequent (or most to least costly), usually with a cumulative line, to reveal which few account for most of the impact. It embodies the Pareto principle — the rough idea that a small number of causes drive most of the effect, often summarised as the vital few versus the trivial many. Its job is prioritisation: faced with a dozen different defects or downtime reasons, a Pareto chart tells you which two or three to attack first, because fixing them removes most of the problem. A Pareto chart does not explain why a problem happens; it tells you which problem is worth explaining. It turns a confusing list into a clear order of attack.
A fishbone diagram — also called an Ishikawa or cause-and-effect diagram — maps the possible causes of a single, specific problem, organised into branches by category. The problem sits at the head of the fish, and the bones branch into cause categories (classically the 6 Ms: Man, Machine, Method, Material, Measurement, and Mother Nature or Environment), with specific possible causes filling each branch. Its job is exploration: it pushes a team to consider the full range of possible causes systematically, rather than jumping to the first guess. A fishbone does not tell you which problem to work on or which cause is the real one — it organises the hypotheses for one problem so investigation is thorough. It turns a single problem into a structured map of where to look.
The clean distinction is the job each does. A Pareto chart prioritises — it ranks many problems to find the vital few worth attacking. A fishbone diagram investigates — it explores the possible causes of one problem in depth. Pareto answers which, fishbone answers why. They operate at different stages of problem-solving and on different scopes: Pareto looks across many problems to choose one; fishbone looks within one problem to find its causes. Confusing them leads to wasted effort — investigating causes with a fishbone before prioritising with a Pareto means you might thoroughly analyse a trivial problem, while ranking with a Pareto but never exploring causes means you know what to fix but not why it happens.
A line suffers many different defects, and the team does not know where to start. First, the Pareto chart: they tally defects by type over a month and rank them. The chart shows that two defect types — out of eleven — account for nearly 70% of all rejects. That is the prioritisation done: attack those two first. Now the fishbone, on the top defect: the team draws a cause-and-effect diagram for that one defect, branching into Machine, Method, Material, Measurement, Man, and Environment, and brainstorming possible causes under each. The fishbone surfaces a likely cause in the Machine branch worth testing. Pareto told them which defect to chase; fishbone organised the hunt for why it happens. Used in that order, the two turned a vague mess into a targeted investigation.
The reason these two tools are so often taught together is that they form a natural sequence: prioritise, then investigate. You start with a Pareto to avoid the classic mistake of working hard on a problem that barely matters — it focuses effort on the vital few. Then, having chosen the problem worth solving, you use a fishbone to explore its causes thoroughly before jumping to a fix, avoiding the equally classic mistake of treating the first plausible cause as the real one. Pareto without fishbone leaves you targeting the right problem but guessing at causes; fishbone without Pareto risks a thorough investigation of the wrong problem. Together they answer both which problem and why, in the right order — which is exactly why both appear in the analyse phase of structured improvement.
Both tools are workhorses for turning OEE data into action. A Pareto of downtime reasons or defect types — exactly the loss data behind OEE — reveals which of the six big losses dominate, so improvement targets the vital few rather than scattering effort. Then a fishbone on the top loss organises the search for its root cause. This is the practical bridge from an OEE score to a fix: OEE quantifies and ranks the losses (Pareto), and the team investigates the biggest one's causes (fishbone). The combination is how a number on a dashboard becomes a specific, root-caused improvement — and it feeds directly into the analyse step of DMAIC and PDCA.
Fabrico generates the ranked loss data a Pareto needs, automatically. By capturing downtime and defects with reason codes and quantifying their cost in lost OEE, it produces the prioritised picture — the vital few losses — that a Pareto chart would, pointing teams straight at the problems worth investigating. From there, the team brings a fishbone to the top loss to find its root cause, and Fabrico confirms in the trend whether the fix worked. It turns the raw events on the floor into the prioritised starting point for structured problem-solving. Book a demo to see your losses ranked and ready to investigate.
A Pareto chart ranks problems or causes by frequency or impact to find the vital few worth attacking. A fishbone (Ishikawa) diagram maps the possible causes of one specific problem across categories. Pareto prioritises which problem; fishbone investigates why it happens.
Pareto first, to prioritise which problem deserves attention, then a fishbone on the chosen problem to explore its causes. Working in that order avoids deeply investigating a trivial problem or fixing the right problem without understanding why it occurs.
Classically the 6 Ms: Man (people), Machine, Method, Material, Measurement, and Mother Nature (environment). The problem sits at the head and possible causes branch under each category, prompting a systematic search rather than a guess.
The Pareto principle is the observation that a small number of causes typically account for most of the effect — often summarised as roughly 80% of problems coming from 20% of causes. A Pareto chart uses this to focus effort on the vital few.
A Pareto of OEE downtime reasons or defects reveals which of the six big losses dominate, prioritising improvement. A fishbone then organises the search for the top loss's root cause. Together they turn an OEE score into a specific, root-caused fix.
Iniciar sesión
Blog
