Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Last revisionBoth sides next revision
articles:using_red_team_vs_blue_team_to_improve_quality [2023/02/20 10:34] – [The Tools] rrandallarticles:using_red_team_vs_blue_team_to_improve_quality [2023/02/20 10:39] – [The Tools] rrandall
Line 54: Line 54:
 In order to find a solution to a problem, the Blue Team MUST first distill the high-level problem down to its constituent, individual "causes" – using one or more "Cause and Effect Chain" (CEC) analysis methods (e.g., 5 Whys, [[articles:those_who_fail_to_plan|Ishikawa (fishbone) diagrams]], Apollo RCA, Fault Tree analysis). In order to find a solution to a problem, the Blue Team MUST first distill the high-level problem down to its constituent, individual "causes" – using one or more "Cause and Effect Chain" (CEC) analysis methods (e.g., 5 Whys, [[articles:those_who_fail_to_plan|Ishikawa (fishbone) diagrams]], Apollo RCA, Fault Tree analysis).
  
-Once the individual causes and any contributing factors are identified, these can be assessed and categorized as "common cause" or "assignable cause" variations in the process.+Once the individual causes and any contributing factors are identified, these can be assessed and categorized as "common cause" or "assignable cause" variations in the process. Common cause variations can only be eliminated through fundamental changes in the process (e.g., using different or more modern equipment) OR a re-design of a product (e.g., combining or eliminating parts). Most often, emphasis should be placed on identifying and implementing risk mitigation (and counter-measures.
  
- + 
-addressed individually. +