Root cause
The earliest identifiable decision or condition in a causal chain that, had it been different, would have prevented the failure or substantially reduced its severity. A root cause is not necessarily a careless or unreasonable decision; well-reasoned engineering judgments, made under real constraints, are frequently documented as root causes once their consequences become clear. (see Topic 3.3)
Defined in 6 GAGE programs, which carry 10 distinct definitions of it. The wording above is taught in Engineering Judgment and Professional Formation.
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
The earliest identifiable decision or condition in a causal chain that, had it been different, would have prevented the failure or substantially reduced its severity. A root cause is not necessarily a careless or unreasonable decision; well-reasoned engineering judgments, made under real constraints, are frequently documented as root causes once their consequences become clear. (see Topic 3.3)
The underlying condition that is the necessary and sufficient cause of an observed failure, as distinct from the symptom (the observed behavior) and from proximate causes (conditions that contributed to the failure but whose absence would not have prevented it). Finding the root cause is the goal of the diagnostic procedure; fixing only symptoms leads to recurrence.
The cause that, if corrected, would prevent recurrence of this and similar occurrences, having generic implications to a broad group of possible occurrences, and being the most fundamental aspect that can logically be identified and corrected.
A single, primary explanation for why an incident occurred. This topic treats the search for one root cause with caution, since real incidents commonly involve multiple independent contributing factors that each need their own remediation.
The mechanism that produced a weakness, found by asking "why" until the answer stops describing one instance and names how the file was assembled or how a control was designed. Fixing the root cause governs a category of findings.
Where it is taught
The exact lessons this term appears in. The first module of every program is free with a free account.
- After the Incident · Rollout, Monitoring, and Incident Response, Certified Agentic AI Governance Professional (CAAGP)
- The post-incident review: fixing the estate, not blaming the intern · Data Incidents, Certified AI Data Governance Professional (CADGP)
- Governance that survives: rebuilding the file so the next attack finds less · Adversarial Governance, Certified AI Governance Professional (CAIGP)
- Root-cause methods · Findings, Issues, Root Cause, and Remediation, Certified Enterprise Governance, Risk and Compliance Professional (CEGP)
- The debugging mindset and the safety habits to build from day one · Your Robotics Command Center, Foundations of Robotics and Physical AI
- Simplifying instead of adding: the principle of elegant minimalism · Engineering Thinking and Elegant Minimalism, Engineering Judgment and Professional Formation
- Famous robot and automation failures and what really caused them · Failure Analysis, Learning From How Robots Break, Engineering Judgment and Professional Formation
- Root cause analysis that finds the real cause · Failure Analysis, Learning From How Robots Break, Engineering Judgment and Professional Formation
- Engineering writing: reports a non-engineer can act on · Design Reviews and Engineering Communication, Engineering Judgment and Professional Formation
- Evolve it from what failed: turn the review verdict into the next iteration · Capstone: The GAGE Design Review, Engineering Judgment and Professional Formation
Where it shows up at work
A definition is where Root cause starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.
Turns technical uncertainty into a one-page decision: material risks, trends, exceptions, remediation, and what the board is being asked to accept.
One lesson on this page teach it as a primary outcome.
Recognizes hallucination, drift, skew, brittleness and biased outcomes, and knows how each one enters a system.
One lesson on this page teach it as a primary outcome.
Roles that hire for it
Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.
- Model Risk Managerneeds it at depth
- AI Risk Managerneeds working knowledge · 2 open postings this week
- Chief AI Officerneeds it at depth
- Chief Audit Executive, AI audit editionneeds it at depth
- Chief Risk Officer, AI risk editionneeds it at depth
- VP of AI Governance and Ethicsneeds it at depth
How job descriptions say it
Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.
Where the frameworks place it: NIST AI RMF MEASURE 2; ISO/IEC 42001.
One interview question about it
Brief a board on an AI risk in two minutes. What do you say, and what do you leave out?
Asked of candidates for executive and board communication on ai risk. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.
If you come from another field
Some backgrounds already carry this competency, and the readiness check gives credit for it.
- Internal audit and IT audit carries it as a claim to back up: Audit committee reporting is part of senior audit roles.
- Nonprofit program and grants oversight carries it as a claim to back up: Board and funder reporting is the cadence a governance committee needs.
- A business, MBA or technology management degree carries it as work you can show: Executive briefs and presentations are your assignments.
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.