8 PROBLEM-SOLVING METHODS COMPARED: WHICH ONE FITS YOUR PROBLEM?
Quick ANSWER
The eight most established structured problem-solving methods are Shainin Red X® (recurring technical variation), Six Sigma / DMAIC (process capability with many contributing factors), Kepner-Tregoe® Problem Analysis (precise problem definition), Apollo Root Cause Analysis (single-occurrence events with known causes), TapRooT® (single-occurrence events involving human or systemic factors), PDCA (ongoing incremental improvement), TRIZ (design and engineering contradictions), and the 8D Problem-Solving Method (a framework for customer complaint response and containment). The right method depends on the type of problem, not personal preference.
1. WHat is shainin red x®?
Shainin Red X® is a methodology for finding the dominant cause of variation, called the Red X, in a recurring technical problem, by contrasting the best and worst conditions instead of brainstorming possible causes.
Best for: manufacturing defects, product performance variation, and field failure problems where the root cause is not known.
Strength: converges on the cause quickly, using small sample sizes, without complex statistics.
Limitation: requires accessibility to failed samples and dedicated training to apply well.
2. What is Six Sigma (DMAIC)?
Six Sigma is a data-driven improvement methodology that uses the DMAIC process (Define, Measure, Analyze, Improve, Control) to statistically characterize a process and reduce variation from multiple contributing factors.
Best for: process capability improvement where several factors each contribute to variation.
Strength: widely taught, data-driven, and effective for optimizing complex processes over time.
Limitation: Uses brainstorming of potential causes displayed in a fishbone diagram or prioritized list. Testing the various possible causes results in projects taking a long time, often running months, and the statistical analysis can be complex.
3. What is Kepner-Tregoe® Problem Analysis?
Kepner-Tregoe® Problem Analysis is a structured questioning process, built around Is/Is Not analysis, that defines a problem precisely by documenting where, when, and on what it does and does not occur.
Best for: ambiguous problems that need a rigorous, shared description before analysis begins.
Strength: minimizes human bias and produces a clear, standardized problem definition.
Limitation: the published method does not include tools for converging on a root cause or confirming it.
4. What is Apollo Root Cause Analysis?
Apollo Root Cause Analysis is a method for investigating a single-occurrence event by building a visual cause-and-effect chart, called a Reality Chart, that traces each effect back through its causes.
Best for: single-occurrence events, such as an accident or injury, where the causal factors are largely known.
Strength: produces a chart that cross-functional teams can build and understand without special training.
Limitation: causal links rely on team consensus rather than independent evidence, and charts become unwieldy on complex problems.
5. What is TapRooT®?
TapRooT® is an incident investigation system that uses a visual event timeline and a pre-built taxonomy of human-performance and equipment failure modes to identify the systemic causes of a single-occurrence event.
Best for: safety incidents and other single-occurrence events involving human performance or systemic factors.
Strength: identifies causes that existed before the event and supports organization-wide prevention.
Limitation: the root cause taxonomy is fixed and proprietary, and proficiency requires dedicated training.
6. What is PDCA?
PDCA (Plan, Do, Check, Adjust) is an iterative improvement cycle in which a team plans a change, tries it, measures the result, and adjusts based on what it learns.
Best for: ongoing, incremental improvement of a stable process.
Strength: simple, participative, and enforces measurement through its Check phase.
Limitation: can be slow when a fast response is needed, and hasty cycles risk addressing symptoms instead of root causes.
7. What is TRIZ?
TRIZ (Theory of Inventive Problem Solving) is a systematic innovation methodology that applies patterns drawn from patent literature to resolve technical contradictions, such as making a component both lighter and stronger.
Best for: design or engineering contradictions that require an inventive solution, not a root cause.
Strength: makes innovation more repeatable and reduces trial and error.
Limitation: difficult to learn and can be time-consuming on complex problems.
8. what Is the 8D problem-solving method?
8D (Eight Disciplines) is a framework that organizes a team’s response to a defect or customer complaint through eight structured steps — covering team formation, containment, corrective action, and customer sign-off.
Best for: customer complaints and escaped defects in automotive, aerospace, and other regulated supply chains that require documented containment and corrective action.
Strength: widely recognized and often required by customers; structures the full response from containment through prevention and closes the loop with formal sign-off.
Limitation: Step D4 calls for a verified root cause but does not specify how to find one. So, teams typically pair 8D with an analytical method such as Shainin Red X®, Six Sigma tools, or Kepner-Tregoe® Problem Analysis.
Which problem-solving method should I use?
Match the method to the problem type: Shainin Red X® for recurring technical variation, Six Sigma for process capability issues with many factors, Kepner-Tregoe® for defining an ambiguous problem, Apollo or TapRooT® for single-occurrence events, PDCA for incremental process improvement, TRIZ for design contradictions, and 8D for organizing the response to a customer complaint (paired with one of the above to identify the root cause).
