Why Combine FMEA With Pareto and Fishbone Diagrams

Failure Mode and Effects Analysis (FMEA) is a structured, preventive method that systematically identifies potential failure modes in a product, process, or system, along with their causes and effects. On its own, FMEA provides a robust risk-prioritization framework, but it does not always reveal the underlying root causes of high-severity failures or help you rank which failures to tackle first in a resource-constrained environment. That is where complementary quality tools like Pareto charts and fishbone (Ishikawa) diagrams become invaluable. Integrating FMEA with these tools creates a powerful, continuous improvement loop that moves from risk identification to root cause analysis to focused action.

Many organizations treat quality tools as isolated exercises: the FMEA team completes the spreadsheet, the Pareto chart is made after a defect spike, and the fishbone diagram is drawn during a one-off problem-solving meeting. In reality, these tools reinforce one another. FMEA supplies the list of potential failure modes and their risk priority numbers (RPNs). Pareto charts help you decide which of those FMEA-identified failures are most critical by volume or cost. Fishbone diagrams then drill into the root causes of those prioritized failures, feeding back into the FMEA for updated controls and detection methods. This integrated workflow eliminates waste, reduces duplication of effort, and builds a data-driven quality culture.

Core Concepts of Each Tool

Failure Mode and Effects Analysis (FMEA)

FMEA is a bottom-up, inductive method that asks, “What could go wrong?” for every step or component. It assigns three ratings: Severity (how bad the effect would be), Occurrence (likelihood of the cause happening), and Detection (how well current controls catch the failure). These three scores are multiplied to produce a Risk Priority Number (RPN). Teams then focus on failure modes with the highest RPNs, but raw RPN is not the only prioritization tool—it can be influenced by subjective scoring. FMEA output is a structured table listing failure modes, effects, causes, current controls, and recommended actions.

Pareto Charts

Based on the Pareto principle (80/20 rule), a Pareto chart is a combination of a bar graph and a line graph. Bars represent individual categories (e.g., defect types, failure modes, cost categories) sorted in descending order. The line shows the cumulative percentage. Pareto charts quickly reveal which few categories account for the majority of the problem. When applied to FMEA data, Pareto charts can highlight the failure modes that contribute most to total RPN, to defect counts, or to customer complaints, helping teams prioritize action items objectively.

Fishbone (Ishikawa) Diagrams

The fishbone diagram is a cause-and-effect tool that visually organizes potential root causes of a specific problem. The problem (effect) is placed in the “head” of the fish, and major cause categories (often 4–6, such as Materials, Methods, Machines, Measurements, Environment, and People) branch off the spine. Teams brainstorm sub-causes under each category, drilling down until they reach actionable root causes. It is a group-mapping technique that prevents jumping to solutions and ensures a thorough exploration of contributing factors.

Step-by-Step Integration Framework

Instead of using these tools sequentially in separate workflows, embed them into a single quality improvement cycle. The following framework outlines how to combine FMEA, Pareto analysis, and fishbone diagrams effectively.

Step 1: Conduct the Initial FMEA

Start with a detailed FMEA of your process or product. Assemble a cross-functional team (design, manufacturing, quality, maintenance, and suppliers if relevant). Identify each function or step, then list all plausible failure modes. For each failure mode, assign Severity, Occurrence, and Detection scores using your organization’s rating scales (e.g., 1–10). Calculate RPN = S × O × D. Document failure effects and current controls. This creates a comprehensive but often lengthy list—some FMEAs can contain hundreds of rows.

Step 2: Extract Data for Pareto Analysis

From the FMEA table, extract the failure modes along with a metric you want to prioritize. Common options include:

  • RPN value: Focus on failure modes with the highest RPN (e.g., top 20%).
  • Severity alone: If safety is critical, prioritize based on Severity ≥ 9 regardless of RPN.
  • Occurrence frequency: Use historical occurrence data (not just FMEA ratings) to weight failure modes by actual defect counts.
  • Cost or impact: Multiply occurrence by cost per failure to get a financial Pareto.

Create a Pareto chart by sorting these items descending and plotting them as bars, with a cumulative percentage line. Identify the “vital few” failure modes that account for about 80% of the total metric. These become your priority list for root cause investigation.

Step 3: Apply Fishbone Diagram to Each Prioritized Failure Mode

For each failure mode selected from the Pareto chart, hold a structured brainstorming session using a fishbone diagram. Write the failure mode (or its effect) as the problem statement in the fish head. Choose appropriate cause categories—common ones for manufacturing are the 6Ms: Machine, Method, Material, Measurement, Mother Nature (Environment), and Man (People). For service processes, categories like Policy, Procedure, People, and Technology are effective. Draw the spine and the category ribs. Then systematically ask “why” at each sub-cause layer until you reach root causes that can be acted upon. Document the diagram, and list the root causes for each prioritized failure mode.

Step 4: Map Root Causes Back to FMEA and Update Controls

The root causes identified by the fishbone diagram often reveal gaps in the original FMEA controls. For example, the fishbone may expose that a machine calibration procedure is missing or that operator training is insufficient. These findings should be used to update the FMEA: add missing failure causes, adjust Occurrence ratings, modify Detection ratings, and propose new recommended actions. This closes the loop—the FMEA is no longer a static document but a living tool that evolves with deeper understanding.

Step 5: Develop and Implement Action Plans

With root causes uncovered, create action items for each. Assign owners, deadlines, and verification methods. Prioritize actions based on the same Pareto logic: use a second Pareto chart on the root causes themselves if there are many. Actions may include redesigning a component, adding inspection steps, updating work instructions, installing poka-yoke (error-proofing) devices, or improving supplier quality. Track completion and effectiveness.

Step 6: Monitor Results and Recalculate RPNs

After implementing actions, collect new data on occurrence and detection. Re-run the FMEA with updated scores. The RPN should decrease for the targeted failure modes. Also monitor overall defect rates and costs to validate that the Pareto improvement holds. If RPN does not drop sufficiently, revisit the fishbone analysis—perhaps the true root cause was not identified or the action was not effective. Periodic iteration of this integrated cycle (FMEA → Pareto → fishbone → updated FMEA) drives continuous improvement.

Practical Examples of Combined Use

Automotive Assembly Line Example

An automotive transmission assembly FMEA listed 45 failure modes. The top three by RPN were “incorrect shim selection” (RPN 252), “damaged O-ring during installation” (RPN 210), and “torque below specification on bell housing bolts” (RPN 196). A Pareto chart of RPN contributions showed these three accounted for 78% of total RPN. The team conducted a fishbone for “incorrect shim selection,” identifying root causes: ambiguous measurement procedure, uncalibrated micrometers, and lack of operator training on shim tolerance. Actions included updating the measurement standard operating procedure (SOP), implementing a calibration schedule, and creating a visual aid for shim sizes. After six months, RPN for that failure mode dropped to 42, and rework due to shim errors fell by 87%.

Healthcare Process Example

A hospital’s medication administration FMEA identified 30 potential failure modes. A Pareto chart on reported near-misses highlighted “look-alike/sound-alike drug confusion” as the top contributor. The fishbone diagram under categories Environment, Process, People, and Technology revealed root causes such as similar packaging, lack of tall-man lettering on labels, and no barcode verification at bedside. Integrating these findings back into the FMEA led to updated controls: implementing standard tall-man lettering for all high-risk look-alike drugs, adding barcode scanning for nurse verification, and redesigning storage layout. The hospital saw a 60% reduction in medication administration errors over the next quarter.

Advanced Techniques for Deeper Integration

Weighted Pareto Using FMEA Scores

Instead of a simple count of failures, weight each failure mode by its Severity or RPN. This produces a weighted Pareto that considers both frequency and consequence. For instance, a low-occurrence failure mode with extremely high severity (e.g., fire in an electrical panel) may appear in the vital few even if its occurrence is rare. This prevents teams from ignoring high-consequence failures that occur infrequently.

Hierarchical Fishbone Linked to FMEA Functions

When a failure mode has multiple causes, create separate fishbone diagrams for each cause-effect path. Then use a cause-and-effect matrix (C&E matrix) to score the relationship between root causes and failure modes, feeding results back into the FMEA’s Occurrence ratings. This formalized approach is common in Design for Six Sigma and Advanced Product Quality Planning (APQP).

Pareto Analysis of Fishbone Categories

After completing fishbone diagrams for several top failure modes, tally how many root causes fall under each category (e.g., 60% are Method-related, 20% are Material-related). Build a Pareto chart of these categories across failure modes. This reveals systemic weaknesses in your process—for example, if most root causes are Method-related, you can prioritize developing better standard work procedures rather than fixing one machine at a time.

Common Pitfalls and How to Avoid Them

  • Applying Pareto too early: Doing Pareto before a thorough FMEA can miss latent failure modes. Always complete the FMEA first to ensure you have a comprehensive list.
  • Using Pareto on raw occurrence numbers without severity context: A failure mode that happens often but has trivial consequences may dominate the Pareto chart. Weight by severity or RPN.
  • Fishbone sessions that go too broad: Without a clear problem statement (the FMEA failure mode or effect), the fishbone becomes speculative. Always anchor the fish head to a specific, prioritized failure mode.
  • Treating tools as one-off exercises: Quality tools lose effectiveness if not updated. Schedule periodic reviews (e.g., quarterly) of the FMEA, Pareto charts, and fishbone diagrams to reflect process changes and new data.
  • Ignoring cross-functional participation: Fishbone diagrams require diverse perspectives. Include operators, engineers, technicians, and quality inspectors. The FMEA alone may have been filled out by a small group; the fishbone session is the chance to validate and expand that knowledge.

Software and Template Considerations

Many organizations use Excel or specialized FMEA software (such as Quality-One’s FMEA software) to manage RPN tables. Pareto charts can be generated in Excel, Minitab, or any statistical analysis tool. Fishbone diagrams are often drawn with Visio, Lucidchart, or online diagramming tools. For tight integration, consider a quality management system (QMS) that links FMEA modules with root cause analysis templates. Some platforms, such as Sphera’s risk management platform, allow you to tag Pareto data to FMEA items and store fishbone images alongside the FMEA worksheet. Choose a solution that balances ease of use with data traceability—avoid tools that create data silos.

Linking to Regulatory and Industry Standards

Many regulated industries require or recommend this combined approach. In automotive, the AIAG & VDA FMEA Handbook (1st edition) emphasizes that FMEA should be used with other core tools such as Process Flow Diagrams and Control Plans. The handbook explicitly states that “the FMEA is not a standalone tool.” In healthcare, The Joint Commission’s standards for proactive risk assessment (e.g., Sentinel Event prevention) encourage using FMEA, Pareto, and root cause analysis (fishbone). In aerospace, SAE ARP5580 recommends integrated risk management using Pareto charts for prioritization and cause-and-effect diagrams for root cause. Adopting the combined method helps you meet these standards while reducing audit findings.

For further reading, see the ASQ FMEA resource page and iSixSigma’s Pareto chart guide for detailed methodology.

Measuring Success of the Combined Approach

Track these key performance indicators (KPIs) to validate that your integrated FMEA-Pareto-fishbone process is delivering results:

  • RPN reduction rate for targeted failure modes (aim for ≥ 50% reduction within six months of action implementation).
  • Pareto shift: The vital few failure modes should change over time as the most critical ones are resolved. A static Pareto indicates no improvement.
  • Defect rate or incident rate for specific failure modes (e.g., from fishbone-identified root causes).
  • Time to root cause identification: Measure how quickly a fishbone session reveals actionable root causes after a Pareto priority is set. Faster identification means your cross-functional team is effective.
  • First-pass yield (FPY) or Overall Equipment Effectiveness (OEE) for the process under study.

Publish these metrics in regular quality reviews. When teams see that their fishbone insights directly lower RPNs and improve customer quality, the integrated approach becomes self-sustaining.

Case Study: Automotive Supplier Deploys Integrated Tools

A mid-sized automotive tier-1 supplier of injection-molded components faced high scrap and customer complaints. Their existing FEMA had 120 failure modes with RPNs ranging from 48 to 240. A Pareto chart of scrap cost by failure mode revealed that just 8 failure modes (6.7% of the total) caused 73% of scrap costs. The three highest were “short shot” (incomplete fill), “flash on parting line,” and “warpage beyond specification.” For each, the team built a fishbone diagram. For “short shot,” root causes included inadequate injection pressure, blocked nozzle, and material moisture content. Corrective actions included pressure calibration, scheduled nozzle cleaning, and raw material drying procedure. After six months, scrap from short shots dropped from 8.5% to 1.1%, and the RPN decreased from 240 to 72. The company established a quarterly review cycle where the updated FMEA was fed into a new Pareto chart, and the highest RPN items were again analyzed with fishbone diagrams. Over two years, overall scrap fell by 45%.

Training and Culture for Successful Integration

The tools themselves are only effective if people know how to use them. Invest in training that covers not just the mechanics but the integration logic. Conduct workshops where teams practice taking an FMEA row, creating a Pareto chart from the same data, and then running a fishbone exercise. Encourage a culture of “fail early, learn fast” so operators and technicians feel safe bringing up potential failure modes. Recognize teams that demonstrate closed-loop improvements using the combined tools. Without culture change, even the best integrated process will gather dust on a shared drive.

Conclusion

Combining FMEA with Pareto charts and fishbone diagrams transforms a static risk assessment into a dynamic problem-solving engine. FMEA identifies what could fail, Pareto tells you where to invest limited resources, and fishbone diagrams explain why those failures happen. By closing the loop—updating the FMEA with root cause insights—you continuously improve your risk landscape. Start with a pilot project on one high-impact process, document the integrated steps, and then roll it out across the organization. The result is a leaner, smarter quality system that reduces defects, cuts costs, and satisfies customers.