augmented skill · Stage 09

Root-cause investigation

Anchor skill

Root-cause investigation is the discipline of distinguishing external events from design flaws. It helps a designer read outcomes, investigate drift, and feed validated learning into the next cycle while keeping the final judgment traceable and human-owned.

This is an anchor skill. Weakness here limits maturity for the entire Continuous Learning stage because it protects the non-negotiable human checkpoint.

Stage outcome

Monitor the shipped experience continuously and feed findings back into Stage 01 of the next cycle. Decoupled from Stage 07 because this is an always-on loop, not a one-time gate

01

Frames root-cause investigation against a clear goal, relevant evidence, and the stage quality gate.

02

Directs AI with scoped inputs, reviews uncertainty, and redirects weak or unsupported output.

03

Documents the decision, trade-off, correction, or override so another designer can follow the reasoning.

Apply this skill before the Stage 09 gate is approved. The accountable designer must be able to explain how it changed the work, what evidence was considered, and why the result is safe to advance.

Common failure patterns

  • Optimising a positive metric without investigating trust, harm, external causes, or long-term behaviour.
  • Accepting fluent or high-confidence output without testing its evidence, assumptions, exclusions, and downstream effects.
  • Recording the final artefact while omitting the rejected option, correction, trade-off, or override that explains the decision.

Use it on the work you already have.

Take one current continuous learning artifact. Apply root-cause investigation for five minutes, then record one AI contribution, one human correction, and the evidence that justified the final decision.

  • A reviewed experiment readout, anomaly investigation, or validated learning log showing the skill in use.
  • A short rationale linking the decision to evidence, risk, and intended outcome.
  • An example of an AI suggestion that was corrected, rejected, or deliberately accepted.

Leadership assessment questions

01

Can the designer demonstrate root-cause investigation on a real continuous learning decision?

02

What observable evidence distinguishes competent performance from confident explanation?

03

Would weakness in this skill make the human checkpoint ceremonial rather than protective?

01 · Prompting

Can use root-cause investigation with a defined task, suitable inputs, and a basic validation check.

02 · Directing

Can diagnose weak output, redirect the work, combine sources, and explain the resulting trade-off.

03 · Orchestrating

Can decide when not to delegate, own the human checkpoint, and remain accountable for the outcome.