ASQ root cause analysis is the American Society for Quality’s approach to finding the highest-level cause of a problem so you can remove it permanently instead of patching symptoms. ASQ defines a root cause as a factor that caused a nonconformance and should be eliminated through process improvement. It treats root cause analysis (RCA) as a collective term for many approaches, tools, and techniques, not as one method.
This article explains why that framing matters, how to run an analysis with a team, and which methods and tools ASQ lists. It also compares ASQ’s RCA courses and specialized credential on time and price, and shows where a broader Lean Six Sigma program fits.
Lean Six Sigma Experts has trained and advised organizations on process improvement since 2011. RCA sits inside the Analyze phase of DMAIC, so the advice below applies ASQ’s published material the way a practitioner would use it on a real project.
Why ASQ’s root cause analysis matters
Root cause analysis matters because a problem fixed at the symptom level comes back. ASQ’s framing pushes you to ask what set the whole cause-and-effect chain in motion, then remove that.
Fixing causes instead of symptoms
A symptom fix restores output today. A root cause fix changes the process so the failure cannot recur. If a machine jams and you clear it, you have treated a symptom. If you find that the feed spec was changed without updating the setup sheet, and you fix the sheet and the change procedure, you have treated the cause.
Recurring defects, repeat incidents, and rework are the usual signs that an organization is stopping too early. Each repeat costs time, scrap, and customer trust, which is why quality, operations, and continuous improvement teams treat this skill as core.
A problem is not solved until the cause that produced it is gone.
What RCA cannot do on its own
ASQ is clear that RCA alone produces no results. It is one building block inside a larger problem-solving effort and inside continuous improvement. The analysis only pays off when someone implements and verifies the corrective action.
There is also a practical limit. In an endless chain of causes, no absolute root cause exists. Your job is to stop at the deepest cause you can act on, support with evidence, and verify by watching the problem stay away.
How to run a root cause analysis with a team
To run an ASQ-style root cause analysis, form a small team from the affected process, meet in short, regular sessions, and move from a clear problem statement to a verified fix. Tools can be used alone, but ASQ notes that results are generally better when a group works together.
Build the team and set a cadence
ASQ’s typical design uses a small team drawn from the area with the problem. Add a line manager who can approve solutions, an internal customer of the process, and a quality improvement expert if the team is new to RCA. The people responsible for removing the cause should be on the team.
For a major problem, ASQ describes an analysis of about two months. The team meets at least weekly, with sessions capped at two hours, and one person keeps the work moving. Implementation can then take anywhere from a day to several months.
Work from problem statement to verified fix
The steps below follow the flow of ASQ’s credential outline, from defining the problem to sustaining the fix.

- Write a problem statement with data: what failed, where, how often, and since when.
- Plan data collection and gather evidence from the process, not from memory.
- Brainstorm possible causes, usually with a cause-and-effect diagram.
- Drill into the likeliest branches with 5 Whys.
- Select the most likely root cause using evidence, and test it.
- Implement corrective and preventive action.
- Verify that the problem stays gone, then standardize the fix.
Here is an illustration. Say a packaging line shows 6% seal failures since March. Why do seals fail? The heater runs cool. Why? The temperature sensor reads high. Why? A wrong sensor type was installed during maintenance. Why? The work order did not list the part spec. The root cause is a missing parts specification, so the fix is to update the work order template, not just to swap the sensor again.
Write the problem down with numbers first, because every later step depends on it.
ASQ root cause analysis methods and tools
ASQ groups RCA into approaches, which structure the whole investigation, and tools, which support the analysis inside them. Match the approach to the kind of problem, then pick tools to fit.
The five approaches ASQ lists
| Approach | Use it when |
|---|---|
| Events and causal factor analysis | A major single event, such as a refinery explosion. You build a timeline from evidence, then find causal and contributing factors. |
| Change analysis | System performance shifted significantly. You examine changes in people, equipment, and information. |
| Barrier analysis | You want to know which controls should have prevented or detected the problem, and which failed. |
| Management oversight and risk tree analysis | You need a tree diagram of what occurred and why it might have occurred. |
| Kepner-Tregoe | You want four phases: situation, problem, solution, and potential problem analysis. |
Most recurring process problems fit change analysis or barrier analysis. One-off serious incidents suit events and causal factor analysis.
Core tools that support the analysis
Inside these approaches, a handful of tools do most of the work:

- 5 Whys: repeated questioning that drills from effect to cause.
- Cause-and-effect (fishbone) diagram: sorts possible causes by category.
- Pareto chart: shows which few causes drive most of the problem.
- Scatter diagram and control charts: test whether a suspected factor really moves the result.
- FMEA: ranks failure modes by risk before or after an event.
- Fault tree and logic trees: structure complex cause-and-effect relationships.
For routine problems, start with a fishbone and 5 Whys. Reach for a fault tree when several causes combine. Whatever you choose, select the root cause on evidence, not on the loudest opinion in the room.
Choose the approach for the type of problem, then let data decide which cause you act on.
ASQ root cause analysis training and credential options
ASQ offers three ways to learn RCA: a self-paced e-learning Specialized Credential, a live virtual course, and a face-to-face course. They differ mainly in time and price.
Comparing the three ASQ options
| Option | Format and time | Member / list price |
|---|---|---|
| Root Cause Analysis Specialized Credential | Self-paced e-learning of about 7 hours, plus a 60-item, open-book exam of 90 minutes. Access lasts 365 days. | $299 / $399 |
| Root Cause Analysis, live virtual | Instructor-led online course | $1,099 / $1,209 |
| Root Cause Analysis, face-to-face | 16 hours, as four half-days or two full days | $1,399 / $1,599 early bird, $1,609 / $1,839 regular |
The credential has no prerequisites and carries 0.8 CEUs and 1.3 RUs. ASQ notes that completing the e-learning does not by itself mean you passed the exam. The exam covers fundamentals (20%), data (15%), methods and tools (30%), project and team management (20%), and sustaining improvements (15%).
Prices come from ASQ’s listings and change, so check them before you budget. At early-bird member rates, four people cost $5,596 in the face-to-face course (4 × $1,399) and $1,196 on the credential (4 × $299), before any membership dues.
Choosing a path for your goal
Choose the credential if you want a low-cost, verifiable grounding in RCA terminology, data, and tools. Choose a live course if your team needs facilitated practice on shared problems.

RCA is one skill within a larger system, though. Our Green Belt Online Training Course (about 28 hours, $1,195) walks through each DMAIC phase, with emphasis on measuring. Our Green Belt Certification Training ($3,600, one week) adds a field project with mentoring from an LSSE Master Black Belt. Learn the method first, then practice it on your own process.
Pick a course to learn the method, and a real project to make it stick.
Putting root cause analysis to work
ASQ’s view comes down to three ideas. A root cause is the deepest factor you can act on, RCA only pays off inside a full problem-solving effort, and the right method depends on the problem in front of you. Define the problem with data, work as a small team, and verify the fix.
If you want help applying this on a live problem or building your team’s skills, talk with a Lean Six Sigma Experts specialist about the best next step for your organization.
