Processes

Identify root cause(s)

How identify root cause(s) are reshaped as AGI capability advances.

ProcessesIdentify root cause(s)
Identify root cause(s) — illustrated

The bottom line

Roughly 75% of the work in Identify root cause(s) is information-shaped — already within reach of AI delivery. The question here is not whether it shifts, but which tasks go first and who staffs the residual.

Why: Because no child occupations are seeded, this scalar relies on the PCF lens 'Manage enterprise quality' and the process description. Performing root-cause analysis via 'documentary evidence,' 'interviews,' and 'risk assessment' represents cognitive, information-processing work that occurs primarily on knowledge surfaces, placing it firmly in the digital band.

grounded in the economy graph · digital scalar 0.75 · digital

Related articles

No articles yet for this entity.

Recent capability events

No capability events for this entity yet.

How the work flows

Trigger: A nonconformance event, defect, or operational failure is reported and logged.

  1. Gather nonconformance data and documentary evidence
  2. Interview involved personnel and subject matter experts
  3. Apply formal root-cause analysis techniques
  4. Assess the risk and broader impact of the identified causes
  5. Document the verified root causes and underlying factors

Outcome: The fundamental systemic or operational reasons for the failure are verified and documented to inform corrective actions.

Measured by

Root Cause Identification Cycle TimeRepeat Incident RateCause Analysis Completion Rate