Root Cause Analysis is a systematic method for identifying the underlying causes of problems. It helps teams not only address symptoms but also recognize and solve fundamental issues. This enhances long-term efficiency and effectiveness.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Root cause analysis systematically investigates an observed problem until actionable underlying causes and suitable countermeasures become clear.
The method belongs to quality and safety practice. Kepner and Tregoe systematized fact-based problem analysis in the 1950s, while cause-and-effect diagrams and related RCA tools became widely established through the Japanese quality movement.
Start with the visible failure and follow the chain of conditions that enabled it. Test each suspected cause with evidence, then change the system condition that prevents recurrence.
The observed sign or immediate effect of a problem.
An underlying, changeable condition contributing to the problem.
A targeted change that reduces recurrence or impact.
RCA helps teams address recurring failures at their conditions and justify corrective actions. Without evidence an analysis remains a hypothesis; multiple causes and interactions need consideration.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.