Accendo Reliability

Your Reliability Engineering Professional Development Site

  • Home
  • About
    • Contributors
    • About Us
    • Colophon
    • Survey
  • Reliability.fm
    • Speaking Of Reliability
    • Rooted in Reliability: The Plant Performance Podcast
    • Quality during Design
    • CMMSradio
    • Way of the Quality Warrior
    • Critical Talks
    • Asset Performance
    • Dare to Know
    • Maintenance Disrupted
    • Metal Conversations
    • The Leadership Connection
    • Practical Reliability Podcast
    • Reliability Matters
    • Reliability it Matters
    • Maintenance Mavericks Podcast
    • Women in Maintenance
    • Accendo Reliability Webinar Series
  • Articles
    • CRE Preparation Notes
    • NoMTBF
    • on Leadership & Career
      • Advanced Engineering Culture
      • ASQR&R
      • Engineering Leadership
      • Managing in the 2000s
      • Product Development and Process Improvement
    • on Maintenance Reliability
      • Aasan Asset Management
      • AI & Predictive Maintenance
      • Asset Management in the Mining Industry
      • CMMS and Maintenance Management
      • CMMS and Reliability
      • Conscious Asset
      • EAM & CMMS
      • Everyday RCM
      • History of Maintenance Management
      • Life Cycle Asset Management
      • Maintenance and Reliability
      • Maintenance Management
      • Plant Maintenance
      • Process Plant Reliability Engineering
      • RCM Blitz®
      • ReliabilityXperience
      • Rob’s Reliability Project
      • The Intelligent Transformer Blog
      • The People Side of Maintenance
      • The Reliability Mindset
    • on Product Reliability
      • Accelerated Reliability
      • Achieving the Benefits of Reliability
      • Apex Ridge
      • Field Reliability Data Analysis
      • Metals Engineering and Product Reliability
      • Musings on Reliability and Maintenance Topics
      • Product Validation
      • Reliability by Design
      • Reliability Competence
      • Reliability Engineering Insights
      • Reliability in Emerging Technology
      • Reliability Knowledge
    • on Risk & Safety
      • CERM® Risk Insights
      • Equipment Risk and Reliability in Downhole Applications
      • Operational Risk Process Safety
    • on Systems Thinking
      • Communicating with FINESSE
      • The RCA
    • on Tools & Techniques
      • Big Data & Analytics
      • Experimental Design for NPD
      • Innovative Thinking in Reliability and Durability
      • Inside and Beyond HALT
      • Inside FMEA
      • Institute of Quality & Reliability
      • Integral Concepts
      • Learning from Failures
      • Progress in Field Reliability?
      • R for Engineering
      • Reliability Engineering Using Python
      • Reliability Reflections
      • Statistical Methods for Failure-Time Data
      • Testing 1 2 3
      • The Hardware Product Develoment Lifecycle
      • The Manufacturing Academy
  • eBooks
  • Resources
    • Accendo Authors
    • FMEA Resources
    • Glossary
    • Feed Forward Publications
    • Openings
    • Books
    • Webinar Sources
    • Journals
    • Higher Education
    • Podcasts
  • Courses
    • Your Courses
    • 14 Ways to Acquire Reliability Engineering Knowledge
    • Live Courses
      • Introduction to Reliability Engineering & Accelerated Testings Course Landing Page
      • Advanced Accelerated Testing Course Landing Page
    • Integral Concepts Courses
      • Reliability Analysis Methods Course Landing Page
      • Applied Reliability Analysis Course Landing Page
      • Statistics, Hypothesis Testing, & Regression Modeling Course Landing Page
      • Measurement System Assessment Course Landing Page
      • SPC & Process Capability Course Landing Page
      • Design of Experiments Course Landing Page
    • The Manufacturing Academy Courses
      • An Introduction to Reliability Engineering
      • Reliability Engineering Statistics
      • An Introduction to Quality Engineering
      • Quality Engineering Statistics
      • FMEA in Practice
      • Process Capability Analysis course
      • Root Cause Analysis and the 8D Corrective Action Process course
      • Return on Investment online course
    • Industrial Metallurgist Courses
    • FMEA courses Powered by The Luminous Group
      • FMEA Introduction
      • AIAG & VDA FMEA Methodology
    • Barringer Process Reliability Introduction
      • Barringer Process Reliability Introduction Course Landing Page
    • Fault Tree Analysis (FTA)
    • Foundations of RCM online course
    • Reliability Engineering for Heavy Industry
    • How to be an Online Student
    • Quondam Courses
  • Webinars
    • Upcoming Live Events
    • Accendo Reliability Webinar Series
  • Calendar
    • Call for Papers Listing
    • Upcoming Webinars
    • Webinar Calendar
  • Login
    • Member Home
Home » Articles » Quality Objective 5: TEAM

by Carl S. Carlson 2 Comments

Quality Objective 5: TEAM

Many ideas grow better when they are transplanted into another mind than the one where they sprang up.  Oliver Wendell Holmes

In this article, I will outline how to evaluate an FMEA against the FMEA Quality Objective for FMEA Team. I’ll include relevant information from the chapter in the FMEA Preparation series called “Assembling the Correct FMEA Team.”

The Oxford English Dictionary defines “correct” as “most appropriate for a particular situation or activity”

BusinessDictionary.com defines “team” as “a group of people with a full set of complementary skills required to complete a task, job, or project. A team becomes more than just a collection of people when a strong sense of mutual commitment creates synergy, thus generating performance greater than the sum of the performance of its individual members.”

Why is FMEA a team activity?

One of the most important steps in preparing for an FMEA is selecting the right team because FMEA is a cross-functional team activity. Doing an FMEA by one person, or with an inadequate or incomplete team, is unacceptable and inevitably results in poor quality.

There are three primary reasons for the necessity to have the correct team when doing an FMEA.

1. People have “blind spots.” A well-defined cross-functional team minimizes the errors inherent with “blind spots.”

2. The FMEA analysis requires subject-matter experts from a variety of disciplines to ensure incorporation of all necessary inputs into the exercise, and that the proper expertise is applied to the design or process being analyzed.

3. One of the indispensable values of an FMEA is the cross talk and synergy between subject-matter experts that occurs during the meetings. Well-defined groups can discover things that individuals often miss.

Who should be on an FMEA team?

The make-up of an FMEA team is specific to the scope of the FMEA for the product or process.

A typical core team for a System or Design FMEA might include representatives from system engineering, design engineering, manufacturing engineering, test engineering, field service, and quality or reliability. Large systems or subsystems may require more than one design representative.

A typical core team for a Process FMEA might include representatives from manufacturing engineering, plant assembly, product engineering, supplier quality, end-of-line test, maintenance, and quality or reliability.

What is the Quality Objective related to FMEA Team?

FMEA Quality Objective 5: TEAM The right people are identified and participate as part of the cross functional FMEA team throughout the analysis and are adequately trained in FMEA methods.

How can you assess how well an FMEA meets the Quality Objective for FMEA Team?

1. Ask the FMEA team leader for a roster of the FMEA team membership, including names and job positions. Request actual records of meeting participation.

2. Based on the type of FMEA being done, determine what would be the correct team composition.

3. Compare the actual vs correct team composition.

4. Determine how well the FMEA team was trained in FMEA methods.

What is an example of assessing FMEA Team

ExampleFMEATeam

Tip

Depending on the scope of the FMEA project, team size can vary from as small as three or four, for very small and simple projects, to as large as eight, for large complex products. Less than three or four may be too small to ensure adequate cross-functional input, and catch potential blind spots. More than eight may be too large to achieve consensus, and will greatly extend time in meetings.

Summary

One of the most important steps in achieving high quality FMEAs is selecting the right team. FMEA is a cross-functional team activity, and by following the advices in this chapter, you can assess how well the FMEA Team meets this quality objective.

Filed Under: Articles, Inside FMEA Tagged With: FMEA Quality Objectives

About Carl S. Carlson

Carl S. Carlson is a consultant and instructor in the areas of FMEA, reliability program planning and other reliability engineering disciplines, supporting over one hundred clients from a wide cross-section of industries. He has 35 years of experience in reliability testing, engineering, and management positions, including senior consultant with ReliaSoft Corporation, and senior manager for the Advanced Reliability Group at General Motors.

« Today’s Gremlin – Lube it wrong
The Variety of Statistical Tools »

Comments

  1. Sven-Erik Adamsen says

    July 1, 2025 at 11:59 PM

    Hi Carl,

    Always enjoying your articles and insights.
    Designing the right team for a DFMEA is for sure extremely important and will have a huge impact on the final result.
    I consider the optimum team size to be 3 – 5 persons to create the best team dynamics and results.
    This means that it will often be advantageous to break down the DFMEA into smaller work groups, An example could be
    DFMEA group 1: Design for meeting customer requirements
    DFMEA group 2: Design for a consistently produceable design (Design for Manufacturing)

    By doing this you are also avoiding that highly skilled members are boring their brain of half of the time😊

    Reply
    • Carl S. Carlson says

      July 9, 2025 at 5:16 AM

      Hello Sven,
      Good comments.
      I like to differentiate the functions. In your example, DFMEA group 1 would describe the related product design function(s), so their focus is on potential design deficiencies to ensure customer requirements are met. And DFMEA group 2 would describe the related DfM function(s), so their focus is on potential DfM deficiencies to ensure producible design.
      There would be overlap between group 1 and 2, such as the design owner would need to be present in both groups.
      Regarding ideal number of team members, as long as you have the right cross functions, so that blind spots can be mitigated, and the team has the right subject matter experts to examine the design from different points of view, it will work.
      Carl

      Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Articles by Carl Carlson
in the Inside FMEA series

Logo Info

Information about FMEA Icon

Inside FMEA can be visually represented by a large tree, with roots, a solid trunk, branches, and leaves.

- The roots of the tree represent the philosophy and guiding principles for effective FMEAs.
- The solid trunk of the tree represents the fundamentals for all FMEAs.
- The branches represent the various FMEA applications.
- The leaves represent the valuable outcomes of FMEAs.
- This is intended to convey that each of the various FMEA applications have the same fundamentals and philosophical roots.

 

For example, the roots of the tree can represent following philosophy and guiding principles for effective FMEAs, such as:

1. Correct procedure         2. Lessons learned
3. Trained team                 4. Focus on prevention
5. Integrated with DFR    6. Skilled facilitation
7. Management support

The tree trunk represents the fundamentals of FMEA. All types of FMEA share common fundamentals, and these are essential to successful FMEA applications.

The tree branches can include the different types of FMEAs, including:

1. System FMEA         2. Design FMEA
3. Process FMEA        4. DRBFM
5. Hazard Analysis     6. RCM or Maintenance FMEA
7. Software FMEA      8. Other types of FMEA

The leaves of the tree branches represent individual FMEA projects, with a wide variety of FMEA scopes and results.

Join Accendo

Receive information and updates about articles and many other resources offered by Accendo Reliability by becoming a member.

It’s free and only takes a minute.

Join Today

Recent Posts

  • 9: Validation
  • Reliability Test can be Done in Parallel to Design Validation
  • Reliability is Not Metrics, It’s Decision Making
  • Oil/Gas Evacuation Management: Leave No One Behind
  • Useful Key Performance Indicators for Maintenance 

© 2025 FMS Reliability · Privacy Policy · Terms of Service · Cookies Policy

Book the Course with John
  Ask a question or send along a comment. Please login to view and use the contact form.
This site uses cookies to give you a better experience, analyze site traffic, and gain insight to products or offers that may interest you. By continuing, you consent to the use of cookies. Learn how we use cookies, how they work, and how to set your browser preferences by reading our Cookies Policy.